Ubuntu

SOLVED - USB Mass Storage Phone gives Error -5 On Probe

Bug #407746 reported by Alan Goldblatt
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

And fails to mount. This error began with Jaunty. My phone works fine if I boot with the live CD into Intrepid 8.10. In 9.04 the phone begins to connect, then encounters an error and never gets fully connected. Attached is the dmesg and lsusb for both the failed 9.04 and the successful 8.10. I'm running with all the latest updates including the newest kernel. The phone is an LG Shine CU-720. I did try this on another machine and found the same problem with 9.04, but booting with an older kernel (I believe it was 2.6.27-9, but I can double check that if it would be helpful) allowed it to work successfully.

Thanks much for your help!
-Alan

Revision history for this message
Alan Goldblatt (alan-b-goldblatt) wrote :
Revision history for this message
Alan Goldblatt (alan-b-goldblatt) wrote :

More info: I did try booting with "usbcore.old_scheme_first=1". I'm not sure I did it right, as there was no modprobe.conf file, so I created one. That didn't work. I also tried entering "modprobe usbcore old_scheme_first=1" at the terminal and got back "FATAL: Module usbcore not found." Hmmmm....
-AG

Revision history for this message
Alan Goldblatt (alan-b-goldblatt) wrote :

Still the same problem with 2.6.28-15 Kernel.
Anyone have any ideas on this one?
-Alan

Alan Goldblatt (alan-b-goldblatt)
summary: - USB Mass Storage Phone gives Error -5 On Probe
+ SOLVED - USB Mass Storage Phone gives Error -5 On Probe
Revision history for this message
Alan Goldblatt (alan-b-goldblatt) wrote :

Workaround for this issue: add "usb-storage option_zero_cd=2" to /etc/modules. After that it worked fine for me until I upgraded to Karmic. Then no error, but no mount either. I'm told the drawback to this workaround is that modems with an emulated windows driver cd probably won't work.
-AG

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in ubuntu:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.