Comment 14 for bug 296710

Revision history for this message
Luis Silva (lacsilva) wrote :

@fishor: That was the solution for me. In fact it seems that udev has nothing to do with this. the problem is that there is no control over what modules are loaded and when if they are in the initram.

@scot: If you only have usb 1.0 hardware then ehci-hcd will do nothing. only when you load uhci-hcd will you have access to those deices. The point is the ehci-hcd driver does not block the uhci-hcd controlled devices. But the later drier acts on the USB 2.0 devices and prevents them from working full speed, even if you load ehci afterwards.

A lot of drivers have been being compiled into the kernel lately, to the point of the need for an initram dropping to almost nil. As a bonus i got 4 seconds less in my boot time.