New problem, old Touch

[taming]

Well, you guys have been busy whilst I was away . Has anyone else had a positive experience adding the books onto the card in smaller batches?

[PeterT]

Originally Posted by davidfor

Removing these lines would be a good test. As would changing to ext3. Someone has done that recently, so it is possible.

But be careful.. If you DO change the SD card to ext3 and change the various scripts, unless you either use Linux or install a totally unsupported driver on Windows, you will not be able to access the card via calibre.

[DNSB]

Originally Posted by davidfor

Interesting idea. I had a look in the firmware. In etc/init.d/rcS, I find:

dosfsck -a -w /dev/mmcblk0p3
mount -t vfat -o iocharset=utf8 /dev/mmcblk0p3 /mnt/onboard
rm -rf /mnt/onboard/fsck*
rm -rf /mnt/onboard/FSCK*
rm -rf /usr/local/Kobo/db.tgz

And in /usr/local/Kobo/udev/sd:

dosfsck -a -w $DEVNAME
mount -r -t vfat -o shortname=mixed $DEVNAME /mnt/sd

But, these are unchanged since at least FW2.4.0. So that doesn't explain why the change in behaviour with FW2.5.2.

Removing these lines would be a good test. As would changing to ext3. Someone has done that recently, so it is possible.

I commented out the fsck line for the sd card (and the collection of lines that deleted the fsck*.rec files on the onboard storage) and it seems to have reduced the startup time from a power off. At least now, it is taking close to the same amount of time whether I have a 2GB or a 32GB card installed though it is still slower than I think it needs to be. I did notice that when I used my computer to copy the contents between SD cards, the Aura deleted the image files during the power on. Which brings up the request below:

Is it possible to give Kobo Utilities a progress indicator? I used Kobo Utilities to restore the cover images but for 1600+ books, this took several minutes with no indication that anything was happening.

Regards,
David

[DNSB]

Sort of just for the heck of it, I decided to revert my Aura to 2.4.1 -- factory reset, setup using the computer, delete the update files before disconnecting. Using a 2GB, 8GB and 16GB uSD card (2GB is a Sandisk c4, 8GB is Lexar c10 and 16GB is Sandisk c10), the boot time from power off to displaying the carousel did not change noticeably Ghod though, it looks sad with the carousel and the menus looking like stretched versions of the Glo's menus.

Next step (it's giving me something to do while on hold with Symantec's tech support) will be to upgrade to 2.5.0 and continue on.

Hmmm... 2.5.0 stalls at the same spot as did 2.5.2. I wonder if any driver updates are included between 2.4.1 and 2.5.x. Time to go diving into the firmware files... again.

Regards,
David

[taming]

What I never really understand is why this kind of problem (and it's a biggie) seems to hit some people, and not others. My Aura and Glo are fine--both with sd cards. I don't have a Touch around to test on.

[Corpsegoddess]

Originally Posted by DNSB

Sort of just for the heck of it, I decided to revert my Aura to 2.4.1 -- factory reset, setup using the computer, delete the update files before disconnecting. Using a 2GB, 8GB and 16GB uSD card (2GB is a Sandisk c4, 8GB is Lexar c10 and 16GB is Sandisk c10), the boot time from power off to displaying the carousel did not change noticeably Ghod though, it looks sad with the carousel and the menus looking like stretched versions of the Glo's menus.

Next step (it's giving me something to do while on hold with Symantec's tech support) will be to upgrade to 2.5.0 and continue on.

Hmmm... 2.5.0 stalls at the same spot as did 2.5.2. I wonder if any driver updates are included between 2.4.1 and 2.5.x. Time to go diving into the firmware files... again.

Regards,
David

2.5.1 stalled for me the same way, but that was before I cleared and reformatted my card. I'll be honest--I didn't understand a thing about your last couple of posts--but did you wipe and format the card before installing the old FW? I think that whatever 2.5.2 did, it stayed on there until I did that (which was *after* I tried 2.5.1).

[speakingtohe]

Originally Posted by Corpsegoddess

2.5.1 stalled for me the same way, but that was before I cleared and reformatted my card. I'll be honest--I didn't understand a thing about your last couple of posts--but did you wipe and format the card before installing the old FW? I think that whatever 2.5.2 did, it stayed on there until I did that (which was *after* I tried 2.5.1).

FYI the problem with the SD card (mine seems similiar to yours) is present in 2,51 as well. I have never installed 2.52 and I may even have had it with 2.5. Can't remember if I even had 2.5 on the Aura.

Helen

[speakingtohe]

Originally Posted by taming

What I never really understand is why this kind of problem (and it's a biggie) seems to hit some people, and not others. My Aura and Glo are fine--both with sd cards. I don't have a Touch around to test on.

Perhaps it is the size of the card? mine is 32G. Have you tried a 32G with no problems? (grasping at straws here)

Helen

[Corpsegoddess]

Originally Posted by speakingtohe

FYI the problem with the SD card (mine seems similiar to yours) is present in 2,51 as well. I have never installed 2.52 and I may even have had it with 2.5. Can't remember if I even had 2.5 on the Aura.

Helen

Well, I know that my last update before installing 2.5.2 was on April 24th. I don't know when 2.5.0 or 2.5.1 came out, but I *do* know that between April 24th and the day I posted about this issue, I had no problems.

[speakingtohe]

Not arguing with your experience, I had problems from the minute I put in the SD card and have not ever installed 2.52. Just not a fan of the kepubs

Helen

Ps. For me it is not that big a deal as it only happens when it resets or I power down completely, which is seldom. A very minor problem as Kobo problms go for me anyway.

[Corpsegoddess]

Originally Posted by speakingtohe

Not arguing with your experience, I had problems from the minute I put in the SD card and have not ever installed 2.52. Just not a fan of the kepubs

Helen

Ps. For me it is not that big a deal as it only happens when it resets or I power down completely, which is seldom. A very minor problem as Kobo problms go for me anyway.

Oh, no--I know you weren't. I just realised that when I read your post, I had another piece of (possibly useful) information to share--my last update date.

[DNSB]

Originally Posted by Corpsegoddess

2.5.1 stalled for me the same way, but that was before I cleared and reformatted my card. I'll be honest--I didn't understand a thing about your last couple of posts--but did you wipe and format the card before installing the old FW? I think that whatever 2.5.2 did, it stayed on there until I did that (which was *after* I tried 2.5.1).

One of the cards was not wiped. I just removed it from the Aura, reverted back to 2.4.1 and reinstalled it and there was no stall on bootup. The other two were SD formatted and then I copied the files from the first card to them on my laptop before inserting them into the Aura. That was where I found the bootup was removing the image files so for that card, I used Kobo Utilities to copy the image files over. For the 3rd card, I wiped the files from it, inserted it in the Aura and used Calibre to copy the books, covers, etc. over to the Aura.

2.4.1 didn't seem to have any problems with any three of the cards. 2.5.0, 2.5.1 and 2.5.2 all stall on startup and eventually continued on.

Regards,
David

[Corpsegoddess]

Originally Posted by DNSB

One of the cards was not wiped. I just removed it from the Aura, reverted back to 2.4.1 and reinstalled it and there was no stall on bootup. The other two were SD formatted and then I copied the files from the first card to them on my laptop before inserting them into the Aura. That was where I found the bootup was removing the image files so for that card, I used Kobo Utilities to copy the image files over. For the 3rd card, I wiped the files from it, inserted it in the Aura and used Calibre to copy the books, covers, etc. over to the Aura.

2.4.1 didn't seem to have any problems with any three of the cards. 2.5.0, 2.5.1 and 2.5.2 all stall on startup and eventually continued on.

Regards,
David

Thank you for clarifying! You all are so good at this; not only knowing what to do, but then explaining it all clearly.

I just supply data.

[filmo]

I have been having problems 2.5.2 on my Kobo Touch. After reading a book then trying to open new book it stalls and will not open new book. Sometimes it will say cannot load because of DRM. Strange because it has always been DRM free. Also had stalled booting from off. Last time I removed SD card to get it to start then inserted SD card without turning off and it was right at page when it turned off. I didn't turn it off. Some really strange stability problems.

[davidfor]

Originally Posted by DNSB

I commented out the fsck line for the sd card (and the collection of lines that deleted the fsck*.rec files on the onboard storage) and it seems to have reduced the startup time from a power off. At least now, it is taking close to the same amount of time whether I have a 2GB or a 32GB card installed though it is still slower than I think it needs to be. I did notice that when I used my computer to copy the contents between SD cards, the Aura deleted the image files during the power on. Which brings up the request below:

That all makes some sense. Except why were the images deleted?

Is it possible to give Kobo Utilities a progress indicator? I used Kobo Utilities to restore the cover images but for 1600+ books, this took several minutes with no indication that anything was happening.

If such a thing as "Kobo Utilities" existed, then that would be a good idea But it would probably be better run it as a background job. And of course, if it existed, it might have been updated in the last 24 hours with somet