SuSE Linux: Version 6.4
This article refers to an older version of SuSE Linux.
Therefore some of the informations given in this article may
be outdated or the article may contain stale links.
modprobe usbcoreNow you have to try, which module fits for your controller, either usb-uhci or usb-ohci. Execute as follows:
modprobe usb-uhciIf you don't see the message,
/lib/modules/2.2.14/misc/usb-uhci.o: init_module: Device or resource busy /lib/modules/2.2.14/misc/usb-uhci.o: insmod /lib/modules/2.2.14/misc/usb-uhci.o /lib/modules/2.2.14/misc/usb-uhci.o: insmod usb-uhci failedthen usb-uhci is the right driver for your computer. Otherwise type the command:
modprobe usb-ohciIf that also fails, the output of the command dmesg may give you a hint on what went wrong.
Now edit the file /etc/rc.config as root. Look up the line that begins with the word INITRD_MODULES. There may be other drivers in that line, e.g. if you boot from a SCSI hard drive. You will need to keep the other drivers. Add the names of the necessary USB driver modules:
INITRD_MODULES="usbcore usb-uhci input hid mousedev keybdev"or
INITRD_MODULES="usbcore usb-ohci input hid mousedev keybdev"Here only the second module differs, usb-uhci or usb-ohci. Then execute as root the command
mk_initrdAfterwards run lilo the from
yast
menu: System administration -> Kernel and boot configuration ->
LILO configuration