![]() |
#331 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,855
Karma: 22003124
Join Date: Aug 2014
Device: Kobo Forma, Kobo Sage, Kobo Libra 2
|
Quote:
I’m curious if those having issues eject and unplug when the OS reports it safe or unplug when the Kobo goes back to the homescreen as these events aren’t always in sync with each other. |
|
![]() |
![]() |
![]() |
#332 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
The other thing we don't know is if they use other things such as:
Or other things. Some of those will be loaded or active during the import process. I don't use them and I don't know how they interact at the times when the issues seem to happen. But, if someone is having these problems and is using them, then testing without is needed to prove it isn't them. |
|
![]() |
![]() |
![]() |
#333 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
That's probably a sensible guess.
FWIW, what I did the last time (after first noticing the issue outside of Nickel entirely), is simply to enable the force wifi flag, and then to look at what's happening before/during/after the USBMS session in an SSH shell (... one that doesn't have its claws on onboard itself, though ^^), mostly by poking at dmesg, the syslog, the procfs tree and lsof. (Nickel does a lazy unmount, which means you'll see a whole lot of fds pointing to / instead of /mnt/onboard, since that's how the magic happens ![]() Another thing that changed on 4.31: all the kernels have been updated, and I don't have the source delta to tell you how exactly, except for a relevant bit on mx6sll & mx6ull devices, where most of the USBMS machinery is now built-in to the kernel, instead of being pluggable modules (this *will* affect timings, which is a sensible issue on NTX boards ^^). Patches shouldn't have any impact on fs handles; nor should NM (barring direct user interaction with NM and very unlucky timing, and even then, highly unlikely). KOReader/Plato won't have any impact on this, since they're completely inert inside Nickel. Restarting Nickel after a KOReader/Plato session *might* exacerbate/uncover weird issues though, but nothing on a cold boot. NanoClock is a very sneaky piece of trickery, so I can't honestly say no, although I wouldn't think it would affect these sorts of things (i.e., on some devices, it's more likely to crash the kernel during the import progress bar than anything else ;p). NickelSeries interacts directly with the import process, so, who knows, but, much like NickelMenu, it's by definition bound by Nickel's own constraints. Last edited by NiLuJe; 02-14-2022 at 09:52 AM. |
![]() |
![]() |
![]() |
#334 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,274
Karma: 5935030
Join Date: Jun 2011
Location: Ontario, Canada
Device: Kobo Aura HD
|
Quote:
I have installed none of the patches. The only thing Unusual I did was enable the new sideload mode. When the Kobo is connected to my system, I see a "File system error, Run repair" error in dmesg. (I'm paraphrasing from memory.) The kobo ejects without problem and seems to be working. However, if I start reading a book, then power it off, (from within the book.),, when I turn it back on, my reading position was not updated. If the kobo is powered off then back on after being connected to PC, there is no issue with reading position not saving on following power off. None of these problems are present after downgrading to 4.30 Edit: It's worth noting that I had been using the device since the firmware was first released without noticing any problem. It wasn't until I went looking for it that I was even aware there was an issue. I generally don't power off my kobo, (only sleep and wake.) Last edited by rashkae; 02-14-2022 at 10:15 AM. |
|
![]() |
![]() |
![]() |
#335 | |
Swedish Kobo User
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 144
Karma: 43316
Join Date: Jul 2021
Device: Kobo Forma, Kindle Paperwhite 11, iPad mini 6
|
Quote:
|
|
![]() |
![]() |
![]() |
#336 |
Linux User
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,282
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
|
Just tested USB connection on Libra 2, 4.31 firmware, no mods installed (other than dev mode enabled for telnet access).
Umount always fails when you connect within KEPUB (nickel does not release KEPUB filehandle), and sometimes fails when you connect from Home menu (nickel does not release KoboReader.sqlite filehandle). Umount works well from within regular EPUB book. So if you have USB corruption issues I recommend you open a regular EPUB first before making the connection, and see if that helps. Lazy umount is a bug that helps sweep other bugs under the rug, so no one will ever notice or fix them. ---- if anyone wants to test, put the following code in /usr/local/Kobo/udev/usb just *before* sync umount -l /mnt/onboard it will try to umount regularly 5 times, if it fails you'll find umount.txt in the exported filesystem showing a process list and open filehandles and such Code:
attempts=5 for i in $(seq $attempts) do grep " /mnt/onboard " /proc/mounts || break umount /mnt/onboard && break ( echo "-------- umount failed ($i / $attempts) --------" umount /mnt/onboard 2>&1 date -Is pstree -p grep -E '^([^ ]+ ){3}b3:0[39] ' /proc/*/maps find /proc/[0-9]*/cwd /proc/[0-9]*/fd -exec stat -tL {} + | grep -E '^([^ ]+ ){6}b30[39]' | xargs ls -l ) > /tmp/umount.txt cat /tmp/umount.txt >> /mnt/onboard/umount.txt sleep 1 done Last edited by frostschutz; 02-27-2022 at 07:43 PM. |
![]() |
![]() |
![]() |
#337 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,490
Karma: 239746053
Join Date: Jan 2014
Location: Estonia
Device: Kobo Sage & Libra 2
|
|
![]() |
![]() |
![]() |
#338 |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 817
Karma: 6528026
Join Date: Sep 2012
Device: Kobo Elipsa
|
I always eject my Elipsa and wait for the OS to tell me it's "safe" to disconnect it. I never just yank the cable. BTW, I'm on Windows 11.
|
![]() |
![]() |
![]() |
#339 | ||
Custom User Title
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 10,989
Karma: 75337983
Join Date: Oct 2018
Location: Canada
Device: Kobo Libra H2O, formerly Aura HD
|
Quote:
Sometimes I connect from the home screen and sometimes I connect while I'm reading a book. I do always make sure to switch back to home menu if I'm sending a new version of the book I'm currently reading (e.g. in-progress fanfics). Quote:
![]() |
||
![]() |
![]() |
![]() |
#340 | ||
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
I'm mixing epubs and kepubs, so that might explain some of what I am seeing. Quote:
Code:
if [ $CPU == mx6sll ] || [ $CPU == mx6ull ]; then PARAMS="idVendor=$VENDOR_ID idProduct=$PRODUCT_ID iManufacturer=Kobo iProduct=eReader-$VERSION iSerialNumber=$SN" /sbin/insmod /drivers/$PLATFORM/usb/gadget/configfs.ko /sbin/insmod /drivers/$PLATFORM/usb/gadget/libcomposite.ko /sbin/insmod /drivers/$PLATFORM/usb/gadget/usb_f_mass_storage.ko else Code:
if [ $CPU == mx6sll ] || [ $CPU == mx6ull ]; then PARAMS="idVendor=$VENDOR_ID idProduct=$PRODUCT_ID iManufacturer=Kobo iProduct=eReader-$VERSION iSerialNumber=$SN" /sbin/insmod /drivers/$PLATFORM/usb/gadget/configfs.ko && /sbin/insmod /drivers/$PLATFORM/usb/gadget/libcomposite.ko && /sbin/insmod /drivers/$PLATFORM/usb/gadget/usb_f_mass_storage.ko else Hopefully someone with better knowledge on this sort of thing can comment and possibly test. |
||
![]() |
![]() |
![]() |
#341 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,012
Karma: 500000
Join Date: Jun 2015
Device: Rocketbook, kobo aura h2o, kobo forma, kobo libra color
|
|
![]() |
![]() |
![]() |
#342 |
Custom User Title
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 10,989
Karma: 75337983
Join Date: Oct 2018
Location: Canada
Device: Kobo Libra H2O, formerly Aura HD
|
Can I just mention a moment of appreciation for everyone on MobileRead?
![]() |
![]() |
![]() |
![]() |
#343 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,012
Karma: 500000
Join Date: Jun 2015
Device: Rocketbook, kobo aura h2o, kobo forma, kobo libra color
|
Quote:
And I'll report that this is an issue from before 30, let alone 31. It just isn't as frequent. I've corrupted my database multiple times with calibre using send to device / eject / import / reconnect cycles in short order. I think the first time I corrupted it, I thought I had maybe not ejected correctly once or twice so I didn't report it. Now I strongly suspect I didn't miss any steps and something was just holding the mount after an import. Note that I found it is much less likely if I only do one cycle per day, which leads me to believe that something is taking its sweet time to finish after the import completes. |
|
![]() |
![]() |
![]() |
#344 | |
Custom User Title
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 10,989
Karma: 75337983
Join Date: Oct 2018
Location: Canada
Device: Kobo Libra H2O, formerly Aura HD
|
Quote:
Also explains why rebooting the device fixed it: it would've made Kobo shut down whatever it was doing. Last edited by ownedbycats; 02-14-2022 at 09:18 PM. |
|
![]() |
![]() |
![]() |
#345 | |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@davidfor:
Quote:
![]() (c.f., this for gnarlier details). Last edited by NiLuJe; 02-14-2022 at 10:38 PM. |
|
![]() |
![]() |
![]() |
Tags |
firmware, firmware release |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Firmware Update Instructions and the latest Firmware Versions | mitchwah | Ectaco jetBook | 113 | 10-24-2023 09:02 PM |
Nouveau firmware firmware 6.5.765 pour la Inkpad 3/PB740 | mooms | PocketBook | 0 | 11-08-2021 08:23 AM |
Firmware Update Kindle firmware 5.12.1 | eilon | Amazon Kindle | 102 | 09-26-2019 08:38 PM |
Firmware glitch - typing text slow on some firmware+device combinations | mdp | Onyx Boox | 11 | 11-11-2017 12:48 AM |
Firmware 2.0.3 Pocketbook IQ - another firmware is release for IQ | tvpupsik | PocketBook | 26 | 12-13-2010 03:03 PM |