Bug 26318
Summary: | USB gets not initialized | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Markus Kaufhold <m.kaufhold> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-02-06 16:33:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Markus Kaufhold
2001-02-06 16:33:02 UTC
No, it's checking for usb in /proc/devices, because if it's already there there is no reason to load the host controller module. Still, we should check later if we need to do the rest of the initialization. This will be fixed in 5.62-1. Hmmm, Indeed after looking into my kernel config (i'm using a vanilla kernel 2.4.1), i've saw that the USB support (CONFIG_USB) is compiled into the kernel, wheras the USB controller is compiled as a module. So when booting up, the USB device is allocated by the kernel, but the controller isn't loaded (because only available as a module). So i've change the USB support to a module compilation, but then i'm running into other problems. Indeed now no USB device is found, and the USB init code is executed in rc.sysinit (with the original statement) But when trying to modprobe the USB controller (usb-uhci), lot's of unresolved symbol error messages appear. After inserting a statement "modprobe usbcore" just before the modprobe of the controller, the init is going well. So the usbcore needs to be loaded too? usbcore should get picked up automatically by modprobe. If it doesn't, your kernel has symbol problems. Ooops, forgot to run depmod -a, shame on me. |