I have an old mainboard with a card reader attached to one USB port. Since when I upgraded to Feisty, I have not been able to read two of my USB sticks, which I could read before Feisty and which I can read on a different PC with Feisty. However, the card reader works and moreover I can read an MP3 reader with a USB interface. The "modprobe -r ehci_hcd" trick works for me. If, after trying unsuccessfully to read a USB stick, I launch usbview, it hangs and the kernel logs show repeatedly this: May 6 21:33:12 localhost kernel: [ 648.336000] sde : READ CAPACITY failed. May 6 21:33:12 localhost kernel: [ 648.336000] sde : status=0, message=00, host=1, driver=00 May 6 21:33:12 localhost kernel: [ 648.336000] sde : sense not available. May 6 21:33:12 localhost kernel: [ 648.337000] sde: Write Protect is off May 6 21:33:12 localhost kernel: [ 648.337000] sde: Mode Sense: 00 00 00 00 May 6 21:33:12 localhost kernel: [ 648.337000] sde: assuming drive cache: write through May 6 21:33:12 localhost kernel: [ 648.338000] sde : READ CAPACITY failed. May 6 21:33:12 localhost kernel: [ 648.338000] sde : status=0, message=00, host=1, driver=00 May 6 21:33:12 localhost kernel: [ 648.338000] sde : sense not available. May 6 21:33:12 localhost kernel: [ 648.339000] sde: Write Protect is off May 6 21:33:12 localhost kernel: [ 648.339000] sde: Mode Sense: 00 00 00 00 May 6 21:33:12 localhost kernel: [ 648.339000] sde: assuming drive cache: write through
Kernel is 2.6.20-15-lowlatency, mainboard is an anonymous PM-999BA-AVS, chip VIA KM133+686B, AGP 4x, integrated Savage4 (disabled), FSB 266 MHz, ATA 100, AMD Duron 1000 MHz, Radeon 9250 128 MB, USB audio Creative. In the attached kern log, I attach the USB stick at May 6 21:45:10, which fails. I then remove the ehci_hcd module and try again at May 6 21:51:45, when it works. ** Attachment added: "kern.log" http://librarian.launchpad.net/7572637/kern.log -- USB devices are not recognized when having ehci_hcd modprobed https://bugs.launchpad.net/bugs/88746 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
