From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 Description of problem: Modutils isn't loading usb-uhci. This on an Abit AT7 MAX mobo means that I don't get any keyboard/mouse, since this thing is PS/2-free. It's loading usb-ehci for the USB 2.0 ports, and the hid, usbcore, and input modules are being loaded against the 2.0 ports. Version-Release number of selected component (if applicable): modutils-2.4.22-8 How reproducible: Always Steps to Reproduce: 1.Boot RH 9 on an Abit AT7 MAX 2.Find no keyboard/mouse. 3.Sulk... Actual Results: No input devices Expected Results: Keyboard and mouse happy as before upgrade. Additional info: sshing in and modprobing usb-uhci is a workaround.
lspci output?
Created attachment 90890 [details] lspci -vvv of affected machine
Odd, can you post /etc/sysconfig/hwconf and /etc/modules.conf?
Created attachment 90897 [details] /etc/sysconfig/hwconf from affected machine
Created attachment 90898 [details] /etc/modules.conf from affected machine
Does it try to load both controller modules on boot, or *only* ehci-hcd? If it tries both, are there errors from loading usb-uhci?
I don't see it trying to load usb-uhci during boot at all, just ehci-hcd. Nothing turns up in /var/log/messages or /var/log/boot.log pertaining to usb-uhci.
Something else I've noticed is that during boot, two lines refer to loading ehci-hcd, back to back. This was during rc.sysinit. There's a clue to the problem in rc.sysinit in line 174. This line attempts to pull out all of the usb devices in the current modprobe configuration, which for whatever reason doesn't match /etc/modules.conf. I'll attach the output of "modprobe -c" where you can see that the usb-controller and usb-controller1 definitions are different in /etc/modules.conf, but the same in "modprobe -c".
Apologies for the duplicate. Bugzilla falsely detected a mid-air collision that I couldn't recover from gracefully.
Created attachment 90911 [details] Results of "modprobe -c" from affected machine
Your modules.conf has: alias usb-controller usb-uhci alias usb-controller1 ehci-hcd alias ieee1394-controller ohci1394 ... alias usb-controller ehci-hcd The second entry for usb-controller is overriding the first when run through modprobe -c. Is your modules.conf exactly as it was written after install?
Yes, the attachments reflect the current state of the machine. That's what has me badly confused - modprobe seems borked.
No, it's behaving correctly. You have two entries for 'usb-controller' in modules.conf; the later one overrides the first. So the question then is: how did two entries for usb-controller get added in that way? Is that how modules.conf looked right after you installed?
You are correct that the usb-controller entry is in modules.conf twice. I didn't catch that. This is the state of /etc/modules.conf as a result of the upgrade. The date on the file is consistent with when I performed the upgrade. I've done no hand-editing post-upgrade. Just as a data point, this box has eight USB ports. Four of them are usb-uhci and four of them are ehci-hcd, all coming from the mobo.
Hi, I'm having the same problem. After upgrading from RedHat 8.0 to 9, my USB mouse stopped working. It worked during the upgrade (in anaconda). modprobing uhci fixes it. I also have two entries in modules.conf that specify the uhci module and then a duplicate specifying the ehci module. So, how do I configure modules.conf to load both the uhci and ehci modules? Both need to be loaded to support USB 1.1 and 2.0 devices.
I have quite a similar problem with the exact same modules.conf. I also did an upgrade from rh8 to rh9 and all my usb devices ceased functioning. My modules.conf looks like this: alias parport_lowlevel parport_pc pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || : alias usb-controller usb-uhci alias eth0 3c59x alias usb-controller1 ehci-hcd alias ieee1394-controller ohci1394 alias sound-slot-0 emu10k1 post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || : alias eth1 e100 alias usb-controller ehci-hcd alias char-major-195 nvidia my fix was to make a new initrd like so: mkinitrd --preload=uhci initrd-2.4.20-9.img 2.4.20-9 Is that the right way to go, or should we do something clever in modules.conf to fix it?
Just change it so that they're all distinct, i.e.: usb-controller usb-controller1 usb-controller2 Also, you only need one for each module.
So, is this an anaconda bug which only happens on upgrade? Or it's just specific to motherboards having usb 1 and usb 2 controllers? BTW, I think bug 85933 may be a dupe of this bug.
Yes, it's an anaconda upgrade bug.
I'm going through Bugzilla closing some bugs that have been marked as Modified for some period of time. I believe that most of these issues have been fixed, so I'm resolving these bugs as Rawhide. If the bug you are seeing still exists, please reopen this report and mark it as Reopened.