I'm having trouble getting USB to work on a SuSE 9.3 system. I don't know much about how it all works. I tried usbview and it gives me an error "Can not open the file /proc/bus/usb/devices" and indeed /proc/bus/usb is an empty directory. usbview says "Verify that you have USB compiled into your kernel, have the USB core modules loaded, and have the usbdevfs filesystem loaded". I don't know how to check what's compiled into the kernel but it's the standard SuSE kernel (2.6.11.4-21.7-default) so I hope so! And /var/log/messages has this (but only this about usb): Jul 20 22:46:47 piglet kernel: usbcore: registered new driver usbfs Jul 20 22:46:47 piglet kernel: usbcore: registered new driver hub Jul 20 22:46:47 piglet kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic Jul 20 22:46:47 piglet kernel: usbcore: registered new driver usbserial_generic Jul 20 22:46:47 piglet kernel: usbcore: registered new driver usbserial Jul 20 22:46:47 piglet kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0 There are lots of messages like this: Jul 25 20:43:00 piglet hal.hotplug[26331]: DEVPATH is not set but that seems to be something to do with the CD drive, not USB. lsmod shows: usbserial 34800 0 usbcore 132976 1 usbserial so I guess the core modules are loaded? Should I see ehci or uhci? I don't. ps shows udevd is running lspci -v shows the following controllers: 0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI]) Subsystem: Micro-Star International Co., Ltd.: Unknown device 0320 Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at d400 [size=32] Capabilities: [80] Power Management version 2 0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20 [EHCI]) Subsystem: Micro-Star International Co., Ltd.: Unknown device 0320 Flags: bus master, medium devsel, latency 32, IRQ 10 Memory at cfffb600 (32-bit, non-prefetchable) [size=256] Capabilities: [80] Power Management version 2 I've tried plugging a Sony micro vault and a scanner in and out of various USB sockets on the PC with no effect. I have set hotplug debug to verbose with yast, but I don't see anything in /var/log/messages when I do. I have created a /events directory but don't see anything there. (I rebooted and saw a lot of stuff but nothing when I plug or unplug devices). USB is enabled in the BIOS. The mobo is an MSI K8M Neo-V. I've looked in the admin and user manual, in the suse sdb and mailing list archives, and with google, but haven't managed to find a solution. I'm sure I've missed something obvious, but what is it? Thanks, Dave
Dave Howorth a écrit :
I'm having trouble getting USB to work on a SuSE 9.3 system. I don't know much about how it all works.
I tried usbview and it gives me an error "Can not open the file /proc/bus/usb/devices" and indeed /proc/bus/usb is an empty directory. usbview says "Verify that you have USB compiled into your kernel, have the USB core modules loaded, and have the usbdevfs filesystem loaded". I don't know how to check what's compiled into the kernel but it's the standard SuSE kernel (2.6.11.4-21.7-default) so I hope so! And /var/log/messages has this (but only this about usb): Jul 20 22:46:47 piglet kernel: usbcore: registered new driver usbfs Jul 20 22:46:47 piglet kernel: usbcore: registered new driver hub Jul 20 22:46:47 piglet kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic Jul 20 22:46:47 piglet kernel: usbcore: registered new driver usbserial_generic Jul 20 22:46:47 piglet kernel: usbcore: registered new driver usbserial Jul 20 22:46:47 piglet kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
There are lots of messages like this: Jul 25 20:43:00 piglet hal.hotplug[26331]: DEVPATH is not set but that seems to be something to do with the CD drive, not USB.
lsmod shows: usbserial 34800 0 usbcore 132976 1 usbserial so I guess the core modules are loaded? Should I see ehci or uhci? I don't.
ps shows udevd is running
lspci -v shows the following controllers: 0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI]) Subsystem: Micro-Star International Co., Ltd.: Unknown device 0320 Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at d400 [size=32] Capabilities: [80] Power Management version 2
0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20 [EHCI]) Subsystem: Micro-Star International Co., Ltd.: Unknown device 0320 Flags: bus master, medium devsel, latency 32, IRQ 10 Memory at cfffb600 (32-bit, non-prefetchable) [size=256] Capabilities: [80] Power Management version 2
I've tried plugging a Sony micro vault and a scanner in and out of various USB sockets on the PC with no effect. I have set hotplug debug to verbose with yast, but I don't see anything in /var/log/messages when I do. I have created a /events directory but don't see anything there. (I rebooted and saw a lot of stuff but nothing when I plug or unplug devices).
USB is enabled in the BIOS. The mobo is an MSI K8M Neo-V.
I've looked in the admin and user manual, in the suse sdb and mailing list archives, and with google, but haven't managed to find a solution. I'm sure I've missed something obvious, but what is it?
Thanks, Dave
Hi, 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. Michel.
I wrote:
I'm having trouble getting USB to work on a SuSE 9.3 system. I don't know much about how it all works. <details snipped> I've looked in the admin and user manual, in the suse sdb and mailing list archives, and with google, but haven't managed to find a solution. I'm sure I've missed something obvious, but what is it?
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? 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? Can anybody point me to a troubleshooting guide or somesuch? Thanks, Dave
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.
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.
Can anybody point me to a troubleshooting guide or somesuch?
Thanks, Dave
Good luck. Michel
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
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
I call regular kernel, the kernel included in the SuSE package. The vanilla kernel is the Linus Torvalds kernel found at kernel.org The kotd kernel is the SuSE "kernel of the day" found at ftp.suse.com.
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!???
I didn't get a new reply from SuSe nor see a fix on their site.
Thanks and regards, Dave
Michel.
participants (2)
-
Catimimi -
Dave Howorth