keyboard stops working after login unless I change usb ports

TheUnknownBone · 2023-09-03 17:28:29

My pc is a x79 chipset with a 3930k and an nvidia 1080ti. I'm doing no overclocking right now. I'm running sddm, kde and x11. On my arch installation I have this ridiculous bug. When the pc boots up and gets to the sddm login screen, the keyboard works. I can confirm this by pressing caps lock and seeing the caps light toggle states. I can type in my password and log in. However, once I log in and the desktop loads, the keyboard no longer works. Typing on the keyboard doesn't do anything and pressing the caps lock key doesn't toggle the state of the caps lock light. If I unplug the keyboard and plug it into a different usb port, that makes the keyboard work again. Sometimes plugging the keyboard into an adjacent port doesn't work and sometimes it does. I've to date never seen it not work after plugging the keyboard into a usb port not adjacent to whatever port the keyboard was plugged into when I logged in.

Note that pressing ctrl+alt+any function key does not do anything when the keyboard gets disabled after logging in.

When I first installed Arch, I wasn't having this problem. This issue developed some time after installation.

I have no idea how to fix this at all. Here is the output of "sudo lspci". Here is the output of sudo dmesg

Has anyone ever had this issue before?

Last edited by TheUnknownBone (2023-09-03 17:39:31)

nl6720 · 2023-09-03 18:00:18

Sounds similar to my FS#79144 (see also the linked systemd and KDE bugs).

seth · 2023-09-03 18:19:26

[    1.366952] usb 1-1.5: new full-speed USB device number 4 using ehci-pci
[    6.602168] usb 1-1.5: USB disconnect, device number 4
[    7.270288] usb 1-1.5: new full-speed USB device number 5 using ehci-pci
[    9.674165] usb 1-1.5: USB disconnect, device number 5
[   10.343617] usb 1-1.5: new full-speed USB device number 6 using ehci-pci
[  127.950429] usb 1-1.5: USB disconnect, device number 6
[  129.436986] usb 1-1.6: new full-speed USB device number 7 using ehci-pci
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
[  132.046690] usb 1-1.6: USB disconnect, device number 7
[  132.660274] usb 1-1.6: new full-speed USB device number 8 using ehci-pci
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[  133.838768] usb 1-1.6: USB disconnect, device number 8
[  136.346956] usb 1-1.4: new full-speed USB device number 9 using ehci-pci
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
[  138.190828] usb 1-1.4: USB disconnect, device number 9
[  138.753656] usb 1-1.4: new full-speed USB device number 10 using ehci-pci
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

See the two framed cycles? The device reconnects within half a second.
Either you're really good at plugging usb devices, or the connection is unstable.
Do you have a spare keyboard?

TheUnknownBone · 2023-09-06 00:06:20

Dang, I kind of don't have a spare usb keyboard right now. I can get one but it'll take time. I do have a ps/2 keyboard and my motherboard has ps/2 ports though. The usb keyboard I have is a logitech g910.

I did try installing Cinnamon. I didn't get the keyboard bug when I logged in with Cinnamon however but several other equally annoying things were messed up enough that prospects of getting all those issues resolved are lower than hopefully fixing this one kde bug + I didn't even use it long enough to discover what other mind boggling issues it probably has. So many people use KDE on arch. I'm really surprised my daily "pacman -Syu" hasn't fixed it by now.

Last edited by TheUnknownBone (2023-09-06 00:07:23)

seth · 2023-09-06 07:00:45

I didn't get the keyboard bug when I logged in with Cinnamon

nl6720 wrote:

https://bugs.archlinux.org/task/79144

Since he's specifically talking about wayland only and you suggest it also affects x11 it might still be a different issue.

* Is your keyboard connected to an internal hub (our Evil Wiki Admin uses the hub in his monitor)
* try downgrading systemd to 253.6-2

===============================

@nl6720

Jul 19 12:23:02 kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3
Jul 19 12:23:06 kernel: usb 1-2.1: USB disconnect, device number 3
Jul 19 12:23:07 kernel: usb 1-2.1: new low-speed USB device number 6 using xhci_hcd
Jul 19 12:23:07 kernel: usb 1-2.1: New USB device found, idVendor=046d, idProduct=c31c, bcdDevice=64.00
Jul 19 12:23:07 kernel: usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 19 12:23:07 kernel: usb 1-2.1: Product: USB Keyboard
Jul 19 12:23:07 kernel: usb 1-2.1: Manufacturer: Logitech
Jul 19 12:23:07 kernel: input: Logitech USB Keyboard as 
…
Jul 19 12:23:08 kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3

The proximity of the amdgpu errors there is a bit too much to be ignored w/ the specific context…
They don't show up in the 253 log, but there're no major differences.
You do have two AMD GPUs, though - the internal Raphael and the 7900 XTX kwin_wayland runs on.

The Ryzen Raphael IGP is otr for this, https://gitlab.freedesktop.org/drm/amd/-/issues/2666
Maybe also try

drm.vblankoffdelay=0

, https://gitlab.freedesktop.org/drm/amd/-/issues/1887

Where is the monitor wired and (assuming the XTX ) can you deactivate the IGP?
Or "pci-stub.ids=1002:164e"?

nl6720 · 2023-09-08 11:24:07

seth wrote:

Jul 19 12:23:02 kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3
Jul 19 12:23:06 kernel: usb 1-2.1: USB disconnect, device number 3
Jul 19 12:23:07 kernel: usb 1-2.1: new low-speed USB device number 6 using xhci_hcd
Jul 19 12:23:07 kernel: usb 1-2.1: New USB device found, idVendor=046d, idProduct=c31c, bcdDevice=64.00
Jul 19 12:23:07 kernel: usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 19 12:23:07 kernel: usb 1-2.1: Product: USB Keyboard
Jul 19 12:23:07 kernel: usb 1-2.1: Manufacturer: Logitech
Jul 19 12:23:07 kernel: input: Logitech USB Keyboard as 
…
Jul 19 12:23:08 kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3
The proximity of the amdgpu errors there is a bit too much to be ignored w/ the specific context…
They don't show up in the 253 log, but there're no major differences.
You do have two AMD GPUs, though - the internal Raphael and the 7900 XTX kwin_wayland runs on.
The Ryzen Raphael IGP is otr for this, https://gitlab.freedesktop.org/drm/amd/-/issues/2666
Maybe also try
drm.vblankoffdelay=0
, https://gitlab.freedesktop.org/drm/amd/-/issues/1887
Where is the monitor wired and (assuming the XTX ) can you deactivate the IGP?
Or "pci-stub.ids=1002:164e"?

The IGP is connected to a TV via HDMI. It's placed in a separate seat (seat-tv) which autologin's to a kodi session from LightDM.

The https://bugs.kde.org/show_bug.cgi?id=472736 bug has been confirmed, so I'm cautiously hopeful.

Arch Linux

#1 2023-09-03 17:28:29

keyboard stops working after login unless I change usb ports

#2 2023-09-03 18:00:18

Re: keyboard stops working after login unless I change usb ports

#3 2023-09-03 18:19:26

Re: keyboard stops working after login unless I change usb ports

#4 2023-09-06 00:06:20

Re: keyboard stops working after login unless I change usb ports

#5 2023-09-06 07:00:45

Re: keyboard stops working after login unless I change usb ports

#6 2023-09-08 11:24:07

Re: keyboard stops working after login unless I change usb ports

Board footer