How can I force the kernel to use USB1.1 instead of USB2.0 Host controller

[boknoy]

It seems that I have a problem with my USB2.0 host controller, its probably not functioning correctly.

So my problem is how can I force the kernel to fallback and use the USB1.1 host controller when I plug-in a USB2.0 device?

From the below /var/log/messages log, it seems that the kernel just keeps trying to assign a usb address for the host controller but as the USB2.0 HC is probably faulty, it can't get the assigned address to use for the USB2.0 device. It doesn't even try to fallback to use the USB 1.1 HC.

When I plug-in a USB1.1 device, everything is ok and the device gets connected.

When I dualboot into my WindowsXP partition, all my USB2.0 devices gets connected and fallsback to the USB1.1 host controller.

Thanks in advance for any helps or tips!

Boknoy

/var/log/messages
------------------------------------------------------------------------------
Dec 11 12:14:15 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 4
Dec 11 12:14:19 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 18
Dec 11 12:14:21 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 23
Dec 11 12:14:24 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 35
Dec 11 12:14:24 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 36
Dec 11 12:14:27 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 45
Dec 11 12:14:28 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 48
Dec 11 12:14:32 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 64
Dec 11 12:14:33 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 66
Dec 11 12:14:34 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 68
Dec 11 12:14:34 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 69
Dec 11 12:14:35 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 71
Dec 11 12:14:37 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 78
Dec 11 12:14:40 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 89
Dec 11 12:14:46 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 111
Dec 11 12:14:47 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 113
Dec 11 12:14:47 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 114
Dec 11 12:14:50 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 123
Dec 11 12:14:51 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 126
Dec 11 12:14:52 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 5
Dec 11 12:14:56 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 20
Dec 11 12:14:56 thinkfed kernel: ehci_hcd 0000:00:1d.7: port 4 reset error -110
Dec 11 12:14:56 thinkfed kernel: hub 1-0:1.0: hub_port_status failed (err = -32)
Dec 11 12:15:01 thinkfed crond(pam_unix)[3644]: session opened for user root by (uid=0)
Dec 11 12:15:02 thinkfed crond(pam_unix)[3644]: session closed for user root
Dec 11 12:15:04 thinkfed kernel: usb 1-4: new high speed USB device using ehci_hcd and address 48

[boknoy]

Should have googled this first before posting but if anybody is interested, the solution is to simply unload the USB2.0 driver. I did this with:

#modprobe -r ehci_hcd