Catimimi wrote:
Catimimi replied:
I've tne same problem with SuSe 9.3 and the vanilla kernel. Add in this order : uhci-hcd ehci-hcd ohci-hcd to the list of modules to load at boot.
Thanks for this; it helped me make some progress. I found that if I do:
modprobe ehci-hcd
then my USB2 memory stick works and if I do
modprobe uhci-hcd
my USB scanner works, so that's great. I don't think I need ohci-hcd because I don't have any controllers of that type? I think I should load ehci-hcd first to ensure USB2 devices are correctly detected?
Now I'd like to make these settings persistent but I'm not sure of the best way to do that. I believe I could add those modules to the INITRD_MODULES list and make a new initrd, but that seems like a kludge. Or I could add them to MODULES_LOADED_ON_BOOT? Or should they be loaded automatically?
Add the modules there and they'll be loaded during the boot process. For the order, SuSE 9.3 detects uhci controllers before ehci and ohci. It seems to be necessary in some cases, it is the reason why I gave you that order.
When I was googling, I think I saw somewhere that the controller detection order doesn't matter but that to make sure that all USB2 devices are correctly recognized when plugged in, the ehci driver needs to be first. But I can't find it now, so I'll try uhci first :)
A quick experiment with another SuSE 9.3 box (a 32-bit Intel rather than the 64-bit Athlon that is giving me trouble) shows that ehci-hcd and uhci-hcd are already loaded before I insert any USB plugs. The only files I can find in /etc that mention them are things like /etc/init.d/kbd (I have a PS/2 keyboard), so I don't understand what's loading these modules?
It depends on the kernel, as I told you, with the regular SuSE kernel I've no problem but with the vanille or the SuSE kotd kernel, it doesn't work. I reported to SuSE who discovered the problem so there is no troubleshooting guide.
I'm confused here, I'm afraid. I don't know what the 'kotd' kernel is at all and I'm not sure which you mean by 'regular' and vanilla'? As I said in my original message, I am using the SuSE kernel 2.6.11.4-21.7-default You say SuSE have discovered the problem. You mean they have a solution? What is it? Is there an SDB entry? Do I need to do a YOU update or something? I don't understand how this fits in with still having to manually edit the modules list!??? Thanks and regards, Dave
Can anybody point me to a troubleshooting guide or somesuch?
Thanks, Dave
Good luck.
Michel