|
Bugzilla – Full Text Bug Listing |
| Summary: | No keyboard input on laptop when installing from iso and during use | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Freek de Kruijf <freek> |
| Component: | X.Org | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Gfx Bugs <gfx-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | freek, tiwai |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Output of dmesg | ||
I tried to remedy the problem by upgrading the system with an upgrade from the newest iso image. Only during booting I could use the keyboard input to control the system, but when the first YaST screen appeared, the keyboard remained dead. The next idea was to connect an external keyboard to the laptop. Typing on that keyboard works!! I upgraded to the newest version of Tumbleweed, which renewed almost all packages, but still the keyboard is dead as soon as the login screen is shown. It is alive when in the grub menu and during the boot process. Do I understand correctly that the keyboard does not work in the X with the YaST? Or you are in a virtual console. If it is X, does Ctrl+Alt+F1 or double fast press of Ctrl+Alt+Backspace work? Are you able to retrieve logs? (In reply to Stanislav Brabec from comment #3) > Do I understand correctly that the keyboard does not work in the X with the > YaST? Yes, the keyboard of the laptop is completely dead. None of the keys gives a reaction on the screen. When booting from the iso image, only right after the start I can use the keys on the keyboard to do some selections, but as soon as YaST is active on tty7, none of the keys produce an action. When using the upgraded Tumbleweed or upgraded Leap 15.2 only in the boot screen, grub2, the keyboard can be used. As soon as the login screen appears the keyboard is dead. This is active on tty7. > > Or you are in a virtual console. > If you mean by virtual console one of the other tty's, I can't go to any of the terminals, because I have to press Ctrl+Alt+F{1-6} which give no action. > If it is X, does Ctrl+Alt+F1 or double fast press of Ctrl+Alt+Backspace work? No, the keyboard is completely dead. > > Are you able to retrieve logs? Yes I can connect via ssh or even an extra keyboard via USB works. And if you connect the USB keyboard, you are able to do anything, including YaST, Ctrl+Alt+F1 and console? If this is true, then I would guess that it is a problem of the kernel (probably i8042 serio driver). (In reply to Stanislav Brabec from comment #5) > And if you connect the USB keyboard, you are able to do anything, including > YaST, Ctrl+Alt+F1 and console? I tried only on an installed Tumbleweed system and yes with the USB keyboard I can do everything. > If this is true, then I would guess that it is a problem of the kernel > (probably i8042 serio driver). What can I do? I will attach the output of the dmesg command. Maybe it gives a clue. Created attachment 841784 [details]
Output of dmesg
[ 3.061230] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1 [ 3.061231] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp These two lines indicate possible solution. Please check your BIOS settings. Your laptop keyboard seems to be connected to an internal PS/2 port. Maybe it is disabled. If there is no such setting, please edit your boot options and add i8042.nopnp. (In reply to Stanislav Brabec from comment #8) > [ 3.061230] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1 > [ 3.061231] i8042: PNP: PS/2 appears to have AUX port disabled, if this > is incorrect please boot with i8042.nopnp > > These two lines indicate possible solution. > > Please check your BIOS settings. Your laptop keyboard seems to be connected > to an internal PS/2 port. Maybe it is disabled. Should I? The system boots OK with Leap 15.1 and Windows 8.1 and previously also with Leap 15.2 and Tumbleweed. The problem only occurred after an update of Leap 15.2 and an upgrade of Tumbleweed. > If there is no such setting, please edit your boot options and add > i8042.nopnp. Tried this. Got [ 3.058078] i8042: PNP detection disabled [ 3.082843] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 3.082851] serio: i8042 AUX port at 0x60,0x64 irq 12 The keyboard is still dead! Can you still use a USB keyboard? If yes, please try to go to VT1 and test the laptop keyboard there on Linux console. If the problem happens only on X, it can be the problem of libinput stuff. (In reply to Takashi Iwai from comment #10) > Can you still use a USB keyboard? If yes, please try to go to VT1 and test > the laptop keyboard there on Linux console. Yes, and Ctrl+Alt+F1 on the USB keyboard brings me in tty1. In which I can use the laptop keyboard. > > If the problem happens only on X, it can be the problem of libinput stuff. So it happens only on X. Maybe you can trace a change back in it at the end of July, when the problem started. Stefan, it looks like we have the same case again. Closing as duplicate. *** This bug has been marked as a duplicate of bug 1175599 *** |
I updated a week ago the Tumbleweed system on my laptop and today to the latest version 20200731. Since last week I get the Plasma login screen, but I can't input any data from my keyboard. The mouse is working, both the touchpad and when I plugin an USB mouse. I have the same problem when using the Leap 15.2 system. But the Leap 15.1 works normal. I have some additional information from hwinfo: 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 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 The difference is in: /dev/input/by-path/platform-i8042-serio-0-event-kbd