Slackware 12.0 disable ehci_hcd kernel module

foouser · 02-24-2008, 10:47 AM

Hello,

I have an IBM Thinkpad T40 where the USB 2.0 chip is broken. That's an common issue with that model and the fix is very expensive. But it is still possible to use USB 1.1.

Having used OpenSuSE 10.3 before I always got a resetting error concerning ehci_hcd. I only did

Code:

rmmod ehci_hcd

and my USB 2.0 sticks worked with USB 1.1.

Using Slackware 12.0 now I got the same error (of course, the chip is still broken

) and tried to rmmod ehci_hcd again. But I was told that there is no ehci_hcd module, and even

Code:

lsmod

didn't show that up. So is there a fix?

Thanks so far.

eagleheart · 02-24-2008, 09:48 PM

what kernel are you running ( i'm guessing it's from the install disk for Slackware 12). If "huge" (-2.6.21.5 or whatever) it probably has ehci_hcd compiled in. rmmod can't touch it then.

Code:

uname -r

grep image lilo.conf
(if it's just image=vmlinuz then...)
ls -l /boot/vmlinuz

Do you have something like "ehci-hcd.ko" under the directory corresponding to your running kernel under /lib/modules?

Maybe the "generic" install disk kernel has it as a module. OR You can compile your own kernel to make it so.

HTH

foouser · 02-24-2008, 09:54 PM

Oh thanks, that explains a lot to me. Yes, actually it is the default kernel found on the install DVD and yes, there is ehci-hcd.ko. Now I know why rmmod fails.

Thank you!

H_TeXMeX_H · 02-25-2008, 01:01 PM

Quote:

Originally Posted by foouser

Having used OpenSuSE 10.3 before I always got a resetting error concerning ehci_hcd. I only did

Code:

rmmod ehci_hcd

and my USB 2.0 sticks worked with USB 1.1.

Using Slackware 12.0 now I got the same error (of course, the chip is still broken

) and tried to rmmod ehci_hcd again. But I was told that there is no ehci_hcd module, and even

I hope you typed that in right, isn't it supposed to be 'ehci-hcd' ? Not, ehci_hcd ...

EDIT:
Oh, you already figured it out, I didn't read your post properly.