[SOLVED] USB keyboard and mouse not detected at boot with kernel 5.13.4, 5.12.11 is OK

Didier Spaier · 07-25-2021, 04:12 PM

System: Slint64-14.2.1 based on Slackware64-14.2
kernel generic + initrd (kernel config very close to the one used for Slackware-current)

Symptom: USB keyboard and mouse don't work after booting so no way to log in when using a 5.13.4 kernel, no issue with 5.12.11. Which is sad as 5.12 is tagged EOL upstream.

I have added a few commands at the end of /etc/rc.d/rc.M to investigate:

Code:

kerver=$(uname -r)
dmesg >/tmp/dmesg$kerver
lsmod >/tmp/lsmod$kerver
lsusb >/tmp/lsusb$kerver
modinfo usbhid >/tmp/usbhid$kerver
cat /proc/bus/input/devices >/tmp/input_devices$kerver

I have compared the output of lsmod after booting in both cases, nearly identical.

"modinfo usbhid" gives the same output with both kernels, kernel version put aside.

In dmesg5.12.11 but not in dmesg5.13.4 I find these lines:

Code:

input: Lite-On Technology Corp. USB Multimedia Keyboard as /devices/pci0000:00/0000:00:1c.5/0000:06:00.0/usb3/3-1/3-1:1.0/0003:04CA:005A.0001/input/input0
input: Lite-On Technology Corp. USB Multimedia Keyboard Consumer Control as /devices/pci0000:00/0000:00:1c.5/0000:06:00.0/usb3/3-1/3-1:1.1/0003:04CA:005A.0002/input/input1
input: Lite-On Technology Corp. USB Multimedia Keyboard System Control as /devices/pci0000:00/0000:00:1c.5/0000:06:00.0/usb3/3-1/3-1:1.1/0003:04CA:005A.0002/input/input2
input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:1c.5/0000:06:00.0/usb3/3-2/3-2:1.0/0003:046D:C077.0003/input/input3

In lsusb5.12.11 only:

Code:

Bus 003 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 003 Device 002: ID 04ca:005a Lite-On Technology Corp. USB Multimedia Keyboard

in the output of cat /proc/bus/input/devices for 5.12.11 only:

Code:

I: Bus=0003 Vendor=04ca Product=005a Version=0111
N: Name="Lite-On Technology Corp. USB Multimedia Keyboard"
P: Phys=usb-0000:06:00.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1c.5/0000:06:00.0/usb3/3-1/3-1:1.0/0003:04CA:005A.0001/input/input0
U: Uniq=
H: Handlers=sysrq kbd leds event0 
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=04ca Product=005a Version=0111
N: Name="Lite-On Technology Corp. USB Multimedia Keyboard Consumer Control"
P: Phys=usb-0000:06:00.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:1c.5/0000:06:00.0/usb3/3-1/3-1:1.1/0003:04CA:005A.0002/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=1f
B: KEY=300ff 0 0 483ffff17aff32d bfd4444600000000 1 130c730b17c000 267bfad9415fed 9e168000004400 10000002
B: REL=1040
B: ABS=100000000
B: MSC=10

I: Bus=0003 Vendor=04ca Product=005a Version=0111
N: Name="Lite-On Technology Corp. USB Multimedia Keyboard System Control"
P: Phys=usb-0000:06:00.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:1c.5/0000:06:00.0/usb3/3-1/3-1:1.1/0003:04CA:005A.0002/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=13
B: KEY=c000 10000000000000 0
B: MSC=10

I: Bus=0003 Vendor=046d Product=c077 Version=0111
N: Name="Logitech USB Optical Mouse"
P: Phys=usb-0000:06:00.0-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:1c.5/0000:06:00.0/usb3/3-2/3-2:1.0/0003:046D:C077.0003/input/input3
U: Uniq=
H: Handlers=mouse0 event3 
B: PROP=0
B: EV=17
B: KEY=70000 0 0 0 0
B: REL=903
B: MSC=10

I would like to know why these input devices are detected when using the kernel 5.12.11 but not 5.13.4.

Any clue appreciated.

marav · 07-25-2021, 06:48 PM

Bonsoir Didier

Quote:

Originally Posted by Didier Spaier

System: Slint64-14.2.1 based on Slackware64-14.2
kernel generic + initrd (kernel config very close to the one used for Slackware-current)

Symptom: USB keyboard and mouse don't work after booting so no way to log in when using a 5.13.4 kernel, no issue with 5.12.11. Which is sad as 5.12 is tagged EOL upstream.

I have added a few commands at the end of /etc/rc.d/rc.M to investigate:

Code:

kerver=$(uname -r)
dmesg >/tmp/dmesg$kerver
lsmod >/tmp/lsmod$kerver
lsusb >/tmp/lsusb$kerver
modinfo usbhid >/tmp/usbhid$kerver
cat /proc/bus/input/devices >/tmp/input_devices$kerver

I suggest :

Code:

kerver=$(uname -r)
dmesg >/tmp/dmesg$kerver
lsmod >/tmp/lsmod$kerver
lsusb >/tmp/lsusb$kerver
modinfo usbhid >/tmp/usbhid$kerver
cat /proc/bus/input/devices >/tmp/input_devices$kerver
udevadm monitor > /tmp/udevadm$kerver

Didier Spaier · 07-26-2021, 06:31 AM

Merci marav, but this didn't help (console stuck after that).

I also tried to compare outputs of pstree and ps -ef, which gave no more clue.

As I have Slackware64-current installed on the same machine, I updated this system using slackpkg, which installed kernels huge and generic also at version 5.13.4, to no avail: same symptoms, so I can't log in using either the generic + initrd or the huge one.

Still puzzled.

marav · 07-26-2021, 06:41 AM

Quote:

Originally Posted by Didier Spaier

Merci marav, but this didn't help (console stuck after that).

right

my bad

Code:

udevadm monitor > /tmp/udevadm$kerver &

Franklin · 07-26-2021, 06:55 AM

Can confirm same behavior here. Unplugging and re-plugging the usb devices (keyboard & mouse) allows them to be recognized. I applied last 4 upgrades at the same time so could not place blame on any one in particular.

marav · 07-26-2021, 06:59 AM

Just a thought

Do you have :

Code:

Enable loadable module support / Path to modprobe binary / (/sbin/modprobe)

In your kernel menuconfig ?

Or in .config

Code:

CONFIG_MODPROBE_PATH="/sbin/modprobe"

EDIT : ignore it
http://ftp.slackware.com/pub/slackwa...ric-5.13.4.x64

Didier Spaier · 07-26-2021, 07:29 AM

Having put "udevadm monitor" in the background (which I should have done from the beginning, *my* mistake) gives interesting results (in Slint in this case), attached.

Should I understand that for some reason the kernel does not send uevents related to the mouse and keyboard so there's nothing eudev can do when using 5.13.4?

How do I confirm or infirm that? scanning /sys to check that the paths are created as they should?

Oh, and yes I have CONFIG_MODPROBE_PATH="/sbin/modprobe"

ZhaoLin1457 · 07-26-2021, 07:33 AM

Quote:

Originally Posted by Didier Spaier

Any clue appreciated.

I use the generic kernel and the following modules loaded on initrd:

Code:

usb-storage:uas:xhci-pci:ehci-pci:ohci-pci:xhci-hcd:ehci-hcd:uhci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-asus:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:mbcache:jbd2:ext4:f2fs:crc32_generic:vfat

With this setup, I never had problems with the USB mouses or keyboards. Even while running the latest kernel.

marav · 07-26-2021, 07:48 AM

The use of :

Code:

 /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 5.13.4

could be helpful ?

Didier Spaier · 07-26-2021, 11:58 AM

It appears that the input devices for the mouse and the keyboard are not exposed in the /sys directory in case of the kernel 5.13.4, thus the corresponding uevent files do not exist. So eudev not being informed of theses devices' existence by uevent can't create paths in /dev for them.

Find why /sys is not populated as it should when using a 5.13.4 kernel needs more investigation.

Meanwhile I will provide a kernel 5.12.19 for Slint to stay on the safe side of the world.

PS
@marav: Thanks but I ran geninitrd (with a few modifications in Slint and as is in Slackware) and anyway using the huge kernel in Slackware doesn't help
@ZhaoLin1457: thanks for the hint. Maybe either mkinitrd_command_generator.sh and/or the kernel's configuration need an adaptation (I would assume the latter at least as the huge kernel doesn't help), I don't know yet. There could be a bug in the source code of the kernel, but then someone would have found it already and filed an issue upstream, I assume.

Didier Spaier · 07-26-2021, 05:15 PM

Update: same symptoms with 5.12.19...

But I just realized that two USB ports out of 6 on this machine are affected. Maybe a commit applied on 5.2.x and also on 5.13.y is the cause?

Anyway I am uploading kernel packages at version 5.12.19 on the main Slint mirror. At worst users will be able to boot using the kernel in use when applying the upgrade, which will be preserved.

Still I am curious to know a fix: this is still an issue and not only an hardware one, as even with the problematic USB ports the keyboard and mouse work using the kernel 5.12.11. In the mean time I am not ready to build and try all kernels between 5.12.11 and 5.12.19, then do a git bisect to maybe find the offending commit... Any idea to find it more easily is warmly welcome.

marav · 07-26-2021, 05:40 PM

Our fantastic wizard has published each changelog here :

https://www.linuxquestions.org/quest...3/page244.html

suggested by someone you know well ... :-)

chris.willing · 07-27-2021, 01:59 AM

Another data point here. In a mature machine (about 6yrs old), all the USB-2 ports work fine but none of the 3x USB-3.0 ports work with kernels 5.13.3,4. On a newer machine all the USB ports are USB-3.2 Gen 2 and all seem to be working OK (as do the USB-2 ports).

The resulting conjecture would be that older USB-3.0 ports are problematic with 5.13.x kernels.

chris

marav · 07-27-2021, 02:30 AM

In attachment, the result of :

Code:

#!/bin/bash
mkdir $HOME/change/
VER="5.12.12 5.12.13 5.12.14 5.12.15 5.12.16 5.12.17 5.12.18 5.12.19 5.13.0 5.13.1 5.13.2 5.13.3 5.13.4"
for i in $VER; do
  wget -O $HOME/change/changelog_"$i".txt https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-"$i"
done
grep usb $HOME/change/* > $HOME/change/all_usb_change.txt

And good luck with the rest
I am clearly not able to interpret the changelog of a kernel.

marav · 07-27-2021, 04:55 AM

otherwise, just to know
why not use an LTS kernel in this case? (5.10.x for ex.)