Kobo making USB ports temporarily fail #70
Comments
|
Also happens on macOS: |
|
Are you there @gtalusan? And I'll test this with the new firmware and see if this issue is still there. |
|
This issue does not appear to be there with the new firmware (I'm not 100% sure though), so I'll close this for now. BTW, the new firmware was worth the wait. I didn't realise how useful the new Page Flip feature was until I tried it. The new firmware is also a lot more responsive and does not have the touchscreen offset issue which there was in the past few versions. |
|
The issue seems to have been introduced or at least caused by USB3 (either the protocol or the kernel module for Linux). The bug traces back to RedHat Linux and others, quite a while ago. I managed to fix this issue by disabling USB3.0 in my bios (therefore falling back to USB2.0 mode) since my laptop does not have USB2.0 ports. |
|
@XenHat That might be the issue, but it also happened even when I turned off USB3... Does it happen for you with the latest firmware with USB3 on? It seems to be fixed for me (as I said above). |
|
@geek1011 Yes it still happens. I truly have to disable usb3. Even USB3 (smart) modes fail on my Windows desktop machine (Device has encountered error thing) My laptop runs Linux and is what lead me here, so perhaps not a software issue on the OS side. USB 2 seems to be the fastest mode that is reliable over time. |
|
@XenHat Have you tried turning off legacy USB support in the BIOS? That has fixed it for some. Also, see if turning off USB power saving in Windows helps anything your desktop. I'll try to figure out why I haven't been getting this issue myself recently. If @gtalusan knows anything about this, it would be nice if he could respond... |
|
Hmmm, my motherboard is only usb3, if I turn off some of those options, my BIOS is unusable. power saving is off though, and I haven't seen the issue since. I don't really need usb3 (I only use it for 2 usb sticks) so I don't really mind that much. |
|
I'm also running into the same issue, also on linux, running the newest firmware ( |
|
This could be a problem on the USB OTG implementation in the kobo (kernel or hardware), but it could also be an issue on the computer chipset / kernel driver you're using. The usual workaround for issues with USB2 devices on USB3 ports is to have an USB2 high-quality hub connected to one of the USB3 ports, and connect your USB2 devices (kobo included) through the hub. |
|
@gtalusan do you know anything about this? |
|
I can confirm that by setting usb3 ports to work in compatibility (usb2) mode, I was able to access my Kobo Touch again (I was experiencing the same issue). Tested with a Kobo Touch on an i7 ThinkPad T440. |
|
I confirm this issue with Kobo Aura 514A462006943 4.8.11073 08/05/2018 And Linux Ubuntu 17.10 Using a USB2 Hub connected to USB3 is a good workaround but it would be nice if you could fixe this issue Thank you |
|
Any news about this issue? |
|
Nope. @gtalusan, can you at least say if this is planned to be fixed or not? |
|
This issue just got worse (I don't know why). Now, instead of failing randomly, it just doesn't connect properly at all (with the same error as before). It goes completely read-only. On my chromebook with USB3 ports, it isn't even recognized. At least I enabled telnet in the developer settings before, so I will install a sftp server on my Kobo and copy stuff that way. |
|
I had a similar issue (Arch Linux, etc). Nothing was recognized in my |
|
I had to RMA my first Kobo due to connector issues of some kind, but while it was still working intermittently I found that, after trying 5 different cables, the only way to get a reliable data connection for transferring books to the device was to use the cable it came with. I'm not 100% sure, but I think it had something to do with manufacturing tolerances in my case. The OEM cable fit snugly in the Kobo, none of my others did. When the slightest force was applied to the other cables while plugged in, the connection would be lost. |
|
I have two cables: one I bought cheaply and one that I got with an expensive USB3 hub. It looks a lot more sturdy. If I put the cheap cable in the USB3 machine and connect my kobo then dmesg shows all sorts of random I/O errors in dmesg. I can imagine the random errors can lead to very erratic behaviour and badness. I had a corrupt database on my kobo some time ago which might be caused by this issue. If I put the cheap cable in the USB2 machine all goes well. So, my advice would be to buy a good micro USB cable. |
|
hi, impacted by the same issue on my kobo.... y wasnt aware that emulating a mass storage support was so difficult. 73.858372] usb usb2-port2: disabled by hub (EMI?), re-enabling... |
|
Hi, I would like to mention that this bug still exists on my Kobo Forma, which is almost brand new (although it did sit in a box unopened until a month ago) with firmware 4.26.16704 I referenced this bug in a mobileread discussion where others had interpreted the lack of activity on this bug as evidence that it had "fixed itself" or something. I just want to confirm that the ball is still in Kobo's court. Also -- and this may be key to fixing the bug -- the KOReader firmware, which has its own totally independent implementation of the USB mass storage stack -- does NOT exhibit this bug, on EXACTLY the same hardware, with exactly the same boxful of USB cables. This is definitely a software bug. Some cables might be better than others at triggering it, but the fact that it can be fixed by using KOReader's USB Mass Storage stack instead of the native stack is incontrovertible evidence. Kobo, please fix this bug, or (better) just start shipping KOReader instead of your own firmware. You guys make awesome hardware and KOReader makes awesome software. Together you could rule the world! Well, the world of eReaders at least. Which is close enough, really... |
|
Huh. We don't do things significantly differently, FWIW... Basically, a real unmount instead of a lazy one, and that shouldn't really affect much on that front. The only other difference was the |
|
An easier workaround for Libra 2 which can be seen in Finder but not in Calibre: from Calibre choose Connect/Share then 'Connect to folder'. Choose the root of the Kobo and continue as normal. |
|
I have a Kobo GLO and while attempting to download some dictionaries it updated the firmware, now the USB Port is totally broken. |
This issue affects every linux distro I have tried it with.
Usually the Kobo works fine. Once in a while (on both my Kobo Minis, Glo, and Aura ed2), it will cause issues with my usb ports, causing them to not work until I reboot my computer. This will continue to happen to every linux device I plug the Kobo into until I reboot the Kobo. This issue seems to be triggered randomly when copying and reading many small files from the Kobo, but it is hard for me to reproduce on purpose.
Here is the relevant dmesg messages from my computer:
The text was updated successfully, but these errors were encountered: