| View previous topic :: View next topic |
| Author |
Message |
jubo
Tux's lil' helper
Joined: 30 Aug 2004
Posts: 87
|
 Posted: Thu Aug 04, 2005 5:49 am Post subject: USB 2.0 Ports on Nforce2 don't work |
 |
|
I have been trying every combo of uhci, ehci, and ohci support in the kernel and I am not getting anything that works. I know it is not a hardware problem because the ports work fine in windows.
my lspci -v shows:
| Code: |
0000:00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 12
Memory at ef087000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <available only to root>
0000:00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard
Flags: 66Mhz, fast devsel
Memory at ef082000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <available only to root>
0000:00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 5
Memory at ef083000 (32-bit, non-prefetchable) [size=256]
Capabilities: <available only to root>
|
I see the OHCI ports working when I tail dmesg and I put in a usb device, but nothing happens in the ehci ports. In my BIOS I have both v1.1 and v2.0 ports enabled. Anyone have any ideas? |
|
| Back to top |
|
 |
fangorn
Veteran
Joined: 31 Jul 2004
Posts: 1886
|
| Posted: Thu Aug 04, 2005 8:17 am Post subject: |
|
|
Are the USB devices plugged in at boot or do you plug them when the system is already up?
Do you use modules and automatically load them or load the modules by hand?
Do you use DEVFS or UDEV?
Do you use Hotplug and/or Coldplug?
could use a little more information here  |
|
| Back to top |
|
|
jubo
Tux's lil' helper
Joined: 30 Aug 2004
Posts: 87
|
| Posted: Thu Aug 04, 2005 7:54 pm Post subject: |
|
|
I use udev, hotplug, and coldplug.
I have tried the device (a USB 1.1 device) at startup and after startup. When I get home I can post the full emerge info, but I am running both kernel 2.6.11 and 2.6.12 and I have found the problem on both. I am going to boot a gnoppix cd later, to see if the problem occurs there as well. |
|
| Back to top |
|
|
widan
Veteran
Joined: 07 Jun 2005
Posts: 1512
Location: Paris, France
|
| Posted: Thu Aug 04, 2005 9:28 pm Post subject: |
|
|
| jubo wrote: | | a USB 1.1 device |
You will never see a USB 1.1 device bound to ehci_hcd. EHCI controllers can only handle USB 2.0 devices (the bus protocol is different from USB 1.x, and not compatible). In order for older devices to work, EHCI controllers have "companion controllers" (UHCI or OHCI) that handle the slow speed devices. So a USB 1.1 device will always be bound to a companion, and never to the EHCI, even if the port is USB-2.0 capable.
There are a few EHCI controllers that are able to "talk" to USB 1.1 devices through an integrated transaction translator (that converts from one bus protocol to the other, so the EHCI controller thinks it has a USB 2.0 device in front, and the device a USB 1.1 controller), but they are not widespread yet. |
|
| Back to top |
|
|
jubo
Tux's lil' helper
Joined: 30 Aug 2004
Posts: 87
|
| Posted: Thu Aug 04, 2005 10:00 pm Post subject: |
|
|
| Quote: |
You will never see a USB 1.1 device bound to ehci_hcd
|
But if I have the ohci and uhci compiled in the kernel, should the kernel detect that and do the right thing when a USB 1.1 device is plugged into those ports?
If not, should EHCI be disabled in the kernel? |
|
| Back to top |
|
|
widan
Veteran
Joined: 07 Jun 2005
Posts: 1512
Location: Paris, France
|
| Posted: Thu Aug 04, 2005 11:01 pm Post subject: |
|
|
| If you connect a USB 1.1 device, it will automatically use ohci_hcd, and the ports will work as USB 1.1 ports. So you can leave EHCI support enabled in the kernel, it won't cause problems. |
|
| Back to top |
|
|
fangorn
Veteran
Joined: 31 Jul 2004
Posts: 1886
|
| Posted: Fri Aug 05, 2005 6:11 am Post subject: |
|
|
I (on my sh***y laptop) had much less problems with all but USB_core compiled as modules. Hotplug then automatically loads the appropriate module. Coldplug did not work that good for me. My mouse is getting detected by the udev startup and I load the module usb_storage out of /etc/modules.autoload.d/kernel-2.6 to get my USB 2.0 harddisk to work. The harddisk works perfect on my Athlon 64 workstation even with hotplugging. Clearly I will never ever by any medion crap again  |
|
| Back to top |
|
|
jkomar
Apprentice
Joined: 24 Sep 2004
Posts: 192
Location: Calgary, Canada
|
| Posted: Sat Aug 13, 2005 11:16 pm Post subject: |
|
|
I'm having a similar issue with an Nforce3 USB 2.0 controller. I found that I had to compile ehci and ohci as modules and rmmod the ehci module to get usb flash drives to work. If I left the ehci module running, I would just get errors in dmesg and no device created.
I am running udev with no devfs using hotplug and coldplug.
Thanks,
Jason
_________________
www.jbox.ca
www.flashinthepan.ca
stormfront Portage/Paludis overlay |
|
| Back to top |
|
|
jkomar
Apprentice
Joined: 24 Sep 2004
Posts: 192
Location: Calgary, Canada
|
|
| Back to top |
|
|
|
Kernel & Hardware
