[opensuse-support] After zypper dup my Tumbleweed system does not see the keyboard anymore
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. How do I enable the keyboard? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
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? -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
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?
ltfctum:~ # lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 064e:9400 Suyin Corp. HD WebCam Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ltfctum:~ # lspci 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/ Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.1 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 2 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader (rev 01) 01:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12) 02:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) I don't see a keyboard here. It is the same when I start kernel 5.7.7, the above is 5.7.9. Also Leap 15.2 does not see the keyboard either. I upgraded this system from 15.0 to 15.1 and after that from 15.1 to 15.2. However Leap 15.1 behaves normal and shows exactly the same output as above on these two commands. I have four systems on this laptop, Windows, Leap 15.1, leap 15.2 and Tumbleweed updated a few days ago. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
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?
Leap 15.1: ltfc151:~ # 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 Number: char 13:64 Driver Info #0: XkbRules: xfree86 XkbModel: pc104 Config Status: cfg=no, avail=yes, need=no, active=unknown 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 -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
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
Op zaterdag 1 augustus 2020 14:44:32 CEST schreef Axel Braun:
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?
I don't know how to enable or disable these settings. The only thing I did was the "zypper dup". This only happened on my laptop. On my desktop all things are normal.
Cheers Axel
-- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Op zaterdag 1 augustus 2020 13:12:32 CEST schreef 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?
I tried to remedy the problem by upgrading the system using the iso image. However on the first YaST screen the keyboard is also dead. It works on the first boot screen. Adding an external keyboard works. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Il 10/08/20 10:40, Freek de Kruijf ha scritto:
Op zaterdag 1 augustus 2020 13:12:32 CEST schreef 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?
I tried to remedy the problem by upgrading the system using the iso image. However on the first YaST screen the keyboard is also dead. It works on the first boot screen. Adding an external keyboard works.
It could be an hardware issue? Perhaps a firmware issue? Or even a wrong keyboard selection to use the updated packages? Do you have the availability of a dual boot OS to verify it once per all? Cheers, -- Marco Calistri Build: openSUSE Tumbleweed 20200807 Kernel: 5.7.11-1-default - Cinnamon 4.2.2 -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (3)
-
Axel Braun -
Freek de Kruijf -
Marco Calistri