Am Samstag, 1. August 2020, 13:12:32 CEST schrieb Freek de Kruijf:
Op dinsdag 28 juli 2020 19:33:29 CEST schreef Axel Braun:
Am Dienstag, 28. Juli 2020, 19:22:06 CEST schrieb Freek de Kruijf:
Om my Acer laptop, a few days ago, I did a "zypper dup" after which the system does not see the keyboard anymore. It does not react on any key pressed. So it is unusable. Today, via ssh, I did again a "zypper dup", but I still have the same problem. The touchpad or the mouse are still working. So I can login using the virtual keyboard, but that is hardly usable.
what is the result of lspci / lsusb - is the keyboard visible?
[...]
Tumbleweed: ltfctum:~ # hwinfo --keyboard 19: PS/2 00.0: 10800 Keyboard [Created at input.226] Unique ID: nLyy.+49ps10DtUF Hardware Class: keyboard Model: "AT Translated Set 2 keyboard" Vendor: 0x0001 Device: 0x0001 "AT Translated Set 2 keyboard" Compatible to: int 0x0211 0x0001 Device File: /dev/input/event0 Device Files: /dev/input/event0, /dev/input/by-path/platform-i8042-serio-0- event-kbd Device Number: char 13:64 Driver Info #0: XkbRules: xfree86 XkbModel: pc104 Config Status: cfg=no, avail=yes, need=no, active=unknown
On my Laptop (ThinkPad) I get exactly the same entry, except the last line: Config Status: cfg=new, avail=yes, need=no, active=unknown Hm, no real idea. Is it maybe disabled in the settings of your desktop? Cheers Axel -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org