On Monday, 6 October 2025 08:45:21 British Summer Time Dale wrote: > Michael wrote: > > On Saturday, 4 October 2025 00:08:18 British Summer Time Dale wrote: > >> Since lsusb shows it, doesn't that mean it should > >> work? Or can it show up and still not work? Keep in mind, it did work > >> in the old sysrescue thingy so the keyboard itself is fine. However, it > >> did not work on the new Gentoo rescue images. It does work within the > >> Ventoy menus. I can use the arrow keys and return to navigate and > >> select in the menu. Once I tell it to boot, no keyboard again. Only > >> the old sysrescue image works. > > > > Does Xorg.0.log reveal anything about the keyboard, e.g. a missing kernel > > driver? > > > > You can compare the kernel config of the liveUSB image which works and > > your own kernel config, as well as the corresponding dmesg output. In > > particular check the USB, HID and KEYBOARD modules. > > > > In case your kernel image on disk has been corrupted due to the faulty > > memory stick, you could rebuilt it and copy it over to /boot. > > > > PS. It is unlikely you need UHCI, if you have OHCI enabled in your kernel > > for USB 1.1. > > There's no GUI on this machine. It's just a server setup. This is from > messages when I plug in the keyboard. > > > Oct 6 01:01:25 nas kernel: usb 4-3: new low-speed USB device number 3 > using ohci-pci > Oct 6 01:01:26 nas kernel: usb 4-3: New USB device found, > idVendor=413c, idProduct=2107, bcdDevice= 1.04 > Oct 6 01:01:26 nas kernel: usb 4-3: New USB device strings: Mfr=1, > Product=2, SerialNumber=0 > Oct 6 01:01:26 nas kernel: usb 4-3: Product: Dell USB Entry Keyboard > Oct 6 01:01:26 nas kernel: usb 4-3: Manufacturer: DELL > > > This is the thing. On the Gentoo boot media, the keyboard didn't work > there either. I could only get the keyboard to work when I booted the > old sysrescue from years ago, decade or so maybe. It's odd that it > works in the old sysrescue media but doesn't work on anything newer like > the Gentoo images. Since it works in the sysrescue media, hardware is > OK.
... and since it works with the sysrescue kernel but not with other kernels, it points to some kernel driver missing. > I just don't get why it doesn't work on anything newer. I'm not > sure looking at the kernel of the very old sysrescue is going to help. > Whatever version of kernel that thing uses, it is very old. Sure, but that old kernel has the required modules enabled to get allow the keyboard to function. It may give you a hint. > I came up with a idea after typing the above. I did a grep on the > kernel config on my main rig. Different version but closer to version > the NAS box has. I found a couple options that were enabled on my main > rig but not on the NAS box. I enabled them, something like USB_HID, > there were two hits in the search so I enabled both. Yep, that's why I said check USB, HID & KEYBOARD modules. If one of these drivers is missing you won't have a functioning USB keyboard. > Then I rebuilt the > kernel. When I rebooted, I could type again. So, even tho it could > "see" the keyboard plugged in, it couldn't see what I was typing. > > So, kernel it was. It's weird, I would have thought I logged into that > thing at least once since the install. Maybe not. That's why I > mentioned in first post, I wasn't sure if I ever used the keyboard > before. I usually ssh in. I read this, but thought you meant just the last time you were booting that box. Either way, glad you got this problem resolved. I was stuck once with a new box which did not have a PS/2 port and I had only PS/2 keyboards available. A PS/2-to-USB adaptor didn't work. It was frustrating being unable to work on the PC until I was able to get a USB keyboard.
signature.asc
Description: This is a digitally signed message part.
