Red Hat Bugzilla – Bug 145624
USB2.0 broken on nForce4
Last modified: 2015-01-04 17:15:56 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.5)
Description of problem:
On an Athlon 64 system using an Asus A8N-SLI Deluxe motherboard
(NVIDIA nForce4 chipset), I have an internal USB 2.0 flash reader
drive, and a Kingston USB 2.0 pen drive. Both of these used to work
fine as late as kernel 2.6.9-1.724. Using kernel 2.6.10-741 no USB 2.0
devices seem to be recognized at all. The ehci-hcd module is loaded
but there is no sign that any devices connected to it have been
detected in the dmesg and they do not show up in lsusb. If I rmmod
ehci-hcd then I can use those devices as USB 1.1 only. Devices
supporting only USB 1.1 still work fine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run 2.6.10-741_FC3 kernel on above system
Actual Results: USB 2.0 devices not detected at all
Expected Results: USB 2.0 devices detected
Tried the previous 2.6.10-1.737 kernel, that one didn't work either.
Still broken in update kernel 2.6.10-1.760. I still have to use kernel
2.6.9 because of this issue.
Will attach output of dmesg and lsusb when devices are not detected.
Created attachment 110685 [details]
dmesg output from bootup with affected kernel
Created attachment 110686 [details]
lsusb output from when devices are not detected
Reported to linux-usb-devel - this was found to be due to a workaround
for another issue in 2.6.10 causing problems on nForce4 due to another
issue in the nForce4 EHCI controller. The patch described in this
thread resolved the issue:
Problem still present in kernel 2.6.10-766.
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
This seems to be fixed in recent FC3 kernels as well as FC4.