[Bug 21800] kernel does not detect mp3 player via USB

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Thu Jan 5 00:20:00 UTC 2006


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=21800
Ubuntu | linux





------- Additional Comments From tburmas at yahoo.com  2006-01-05 00:20 UTC -------
(In reply to comment #2)
> It seems that your kernel does not recognize the device when using the USB 2.0
> driver. That's a fairly common bug unfortunately.
> 
> Can you please try the following:
>  * remove the device
>  * sudo rmmod ehci_hcd
>  * plug in the device again
> 
> does it work then?
Wow this bugzilla thing is cool (I'm not being sarcastic).  I appreciate you
letting me know it
is a common bug - I had a feeling it might be.

Ok so on to your question:
I removed the device and did
su
rmmod ehci_hcd

and the command line just hangs.   On another command line I typed 
tail /var/log/messages and got

Jan  4 15:19:14 localhost gconfd (user-8872): Resolved address
"xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at
position 7
Jan  4 15:19:20 localhost gconfd (user-8872): Resolved address
"xml:readwrite:/home/tburmas/.gconf" to a writable configuration source at
position 0
Jan  4 15:35:20 localhost -- MARK --
Jan  4 15:55:20 localhost -- MARK --
Jan  4 16:09:46 localhost kernel: [4298319.830000] usb 4-7: new high speed USB
device using ehci_hcd and address 3
Jan  4 16:10:53 localhost kernel: [4298387.271000] ehci_hcd 0000:00:03.3:
remove, state 1


I couldn't kill rmmod so I killed the terminal
I plugged the ipod in again ... no luck

This time I unplugged the ipod and in a fresh terminal I typed
sudo rmmod ehci_hcd   and got
"ERROR: Removing 'ehci_hcd': Device or resource busy"    - this is with the ipod
removed

I plugged the ipod back in and typed
sudo rmmod ehci_hcd and got the same message

Thank you


-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the desktop-bugs mailing list