[SOLVED] Slackware 14.2

SpacePlod · 07-12-2017, 01:40 PM

I have a system that has been giving me fits. I created an initrd and the system will boot to the prompt, but the USB keyboard will not work. The keyboard works fine for navigating the bios. It also works fine for the Slackware64 boot media.

Similar to this issue, but I'm using an ASUS motherboard, and I have no access to non-usb ports for a keyboard, and the problem is not intermittent. And again, the keyboard works fine in the boot media, but not in the booted system

I'm using an initrd with ext4/usbhid/xhci* and several others I've added just to try out.

Code:

mkinitrd -c -k 4.4.14 -m ext4:usbhid:usb_storage:hid:hid_generic:xhci_hcd:xhci_pci:ehci_hcd:evdev
OK: /lib/modules/4.4.14/kernel/fs/jbd2/jbd2.ko added.
OK: /lib/modules/4.4.14/kernel/fs/mbcache.ko added.
OK: /lib/modules/4.4.14/kernel/fs/ext4/ext4.ko added.
OK: /lib/modules/4.4.14/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/4.4.14/kernel/drivers/hid/usbhid/usbhid.ko added.
OK: /lib/modules/4.4.14/kernel/drivers/usb/storage/usb-storage.ko added.
OK: /lib/modules/4.4.14/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/4.4.14/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/4.4.14/kernel/drivers/hid/hid-generic.ko added.
OK: /lib/modules/4.4.14/kernel/drivers/usb/host/xhci-hcd.ko added.
OK: /lib/modules/4.4.14/kernel/drivers/usb/host/xhci-hcd.ko added.
OK: /lib/modules/4.4.14/kernel/drivers/usb/host/xhci-pci.ko added.
OK: /lib/modules/4.4.14/kernel/drivers/usb/host/ehci-hcd.ko added.
OK: /lib/modules/4.4.14/kernel/drivers/input/evdev.ko added.

I've messed with xhci/ehci handoff in the bios (which is set to legacy, currently) and none of the changes make any difference. Google reveals some references to iommu, but I cannot find a setting for that in the bios.

Any suggestions would be most welcome.

Thanks.

volkerdi · 07-12-2017, 01:50 PM

Was the keyboard working with the huge kernel and no initrd?

You might try taking a look at the output of /usr/share/mkinitrd/mkinitrd_command_generator.sh to see if that will make a working initrd for your system.

Gerard Lally · 07-12-2017, 02:19 PM

I had this kind of thing last year when I plugged the keyboard into any of the USB 3.0 ports on my new motherboard. Plugging it in to another port fixed it for me. I also kept up with Asrock's UEFI firmware updates for this board.

SpacePlod · 07-12-2017, 02:38 PM

Quote:

Originally Posted by volkerdi

Was the keyboard working with the huge kernel and no initrd?

You might try taking a look at the output of /usr/share/mkinitrd/mkinitrd_command_generator.sh to see if that will make a working initrd for your system.

Thank you for the response sir.

That did the trick. There were quite a few modules included in there that I would not have thought of (and did not see in lsmod output), but one (or a combination) of them obviously worked. System is up and running.