http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c2 --- Comment #2 from Luiz Cantarino --- Thanks for the reply, sir. Takashi. Yes I still have the previous kernel, and the laptop's keyboard only works with it. Now using the latest kernel, I have to use a USB keyboard. Could you be so kind as to tell me how to send the requested files. They are too big -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c4 --- Comment #4 from Luiz Cantarino --- Created attachment 840938 --> http://bugzilla.opensuse.org/attachment.cgi?id=840938&action=edit dmesg -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c6 --- Comment #6 from Luiz Cantarino --- Sorry, dmesg was duplicated -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c8 --- Comment #8 from Luiz Cantarino --- I'm sorry Mr. Takashi, the 5.3.18-lp152.19.2 kernel is there, I can see it '$ rpm -qa | grep kernel ', but when I select it it gives this error: "bad shim signature Loading initial ramdisk you need to load the kernel first " And I don't know how to fix this. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c10 --- Comment #10 from Luiz Cantarino --- I did it, I had to downgrade the 'shin' package. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c12 --- Comment #12 from Luiz Cantarino --- Secure boot is disabled, as there was another 'shim' update, and I was unable to start with the previous kernel. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c14 --- Comment #14 from Luiz Cantarino --- Mr. Takashi, I acted as requested. And in this condition, the keyboard will function normally again. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c16 --- Comment #16 from Takashi Iwai --- OK, then it implies that the kernel works more or less as expected, at least. When it works on Linux console, could you start the DE from there? Just run like: sudo /usr/sbin/rcxdm start It'll kick off the X session. Is the keyboard broken on this? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c18 --- Comment #18 from Takashi Iwai --- Well, after booting with "3" option, you're running without GUI, and you can login on Linux console, and the keyboard works, right? Then login as root there, and just run "rcxdm start". This will start the Display Manager service, and you should be able to login or start the graphical session. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c20 --- Comment #20 from Luiz Cantarino --- Created attachment 841093 --> http://bugzilla.opensuse.org/attachment.cgi?id=841093&action=edit TTY3 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c22 --- Comment #22 from Takashi Iwai --- Wait... At the moment you ran "rcxdm start", did you already have the graphical interface, typically on VT7? And while you typed "rcxdm start" on VT3, you could use your keyboard? If both are yes, just go to VT7 (Alt+F7), and you should have the graphical interface, and test the keyboard there. Also, what desktop environment are you using? GNOME, KDE, XFCE or anything else? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c24 --- Comment #24 from Takashi Iwai --- Then this is unlikely a kernel problem. Could you try to log out from the KDE session, choose a different session, preferably a simple one like IceWM, and login there? Do you get the keyboard input on that X11 session? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c26 --- Comment #26 from Takashi Iwai --- What exactly do you mean "old kernel"? Please give the dmesg outputs from both "old" and "new" kernels, to be more exact. Also, running on IceWM, please get the contents of /var/log/Xorg.0.log on both working and broken cases, and upload them as well. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c28 --- Comment #28 from Luiz Cantarino --- Created attachment 841147 --> http://bugzilla.opensuse.org/attachment.cgi?id=841147&action=edit dmesg do kernel 5.3.18-lp152.19.2-sessão IceWM -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c30 --- Comment #30 from Luiz Cantarino --- Created attachment 841149 --> http://bugzilla.opensuse.org/attachment.cgi?id=841149&action=edit dmesg do kernel 5.3.18-lp152.36.1-sessão IceWM -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c32 --- Comment #32 from Takashi Iwai --- Thanks! Unfortunately, those logs don't show any significant difference between working and broken cases. That's strange. It means that X was started properly with the keyboard input device, but it didn't receive events. I checked again hwinfo you gave in the past, and also they showed no relevant difference. So it's not about the missing module or the failed initialization. OK, now let's check what input event is actually delivered. Go to VT1, via ctrl+alt+F1, login there. Install evtest program via "zypper in evtest", and run it as root. You'll be asked to choose the device, and select the PS/2 keyboard (likely "0"). Type something, and see which keycode and event are generated there. You can quit with ctrl+C. Check the above on both working and broken kernels. If you see any difference in the key event behavior, that's the point to take a look. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c34 --- Comment #34 from Luiz Cantarino --- Created attachment 841162 --> http://bugzilla.opensuse.org/attachment.cgi?id=841162&action=edit evtest com kernel 5.3.18-lp152.19.2 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c36 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@suse.com --- Comment #36 from Takashi Iwai --- Thanks. The events look good, so I have no idea why it doesn't work. Possibly some recent changes in X broke casually? Adding Stefan to Cc. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c38 --- Comment #38 from Takashi Iwai --- (In reply to Stefan Dirsch from comment #37)

Well, we had a security update. If this broke keyboard support, we have a serious problem.

FWIW, there is another bug report (bsc#1175581) that shows a very similar symptom but on Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c40 --- Comment #40 from Takashi Iwai --- Yes, that's the mysterious part. From the logs, there are no differences. And in this bug report, both kernels showed the proper key events generated on VT, as it seems. That's why I dragged you here; now we need to step in debugging in X, as everything works fine on Linux console. The issue is reproducible with icewm, hence it's a bit easier than on KDE. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c42 --- Comment #42 from Takashi Iwai --- (In reply to Stefan Dirsch from comment #41)

So we see no keyboard events in xev at all?

We didn't check it yet. Luiz, could you test the keyboard event via xev program? Install xev package, and just run it on icewm session from a terminal. Then type some keys there, and see whether you get any key events.

Well, we could disable the xkb security patches in Xserver to verify this is or is not the culprit.

U_0001-Correct-bounds-checking-in-XkbSetNames.patch U_0003-Fix-XkbSelectEvents-integer-underflow.patch

That'll be helpful, thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c44 --- Comment #44 from Luiz Cantarino --- Mr. Takashi, follows your request for 'xev' in an IceWM session. This package was already installed. Mr.Stefan, follow your request for output 'rpm --changelog -q xorg-x11-server | head -n 10 '. I did not disable the patches mentioned, because I do not know how to do this. But I looked for them with the zypper, and it said that 'no matching item was found' -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c46 --- Comment #46 from Luiz Cantarino --- Created attachment 841185 --> http://bugzilla.opensuse.org/attachment.cgi?id=841185&action=edit xev sessão IceWM kernel 5.3.18-lp152.36.1 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c48 --- Comment #48 from Stefan Dirsch --- (In reply to Luiz Cantarino from comment #47)

Created attachment 841186 [details] output rpm

cantarino@localhost:~> rpm --changelog -q xorg-x11-server | head -n 10 * Wed May 06 2020 Stefan Dirsch - provide/obsoletes cirrus and ast usermode driver also on openSUSE (jsc#SLE-12127) * Thu Feb 27 2020 Stefan Dirsch - specfile: reenabled XFree86-VidModeExtension (boo#1164020) * Fri Nov 29 2019 Frederic Crozat - Build XWayland also on s390. So the security update of this August is not included at all. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c50 --- Comment #50 from Luiz Cantarino --- (In reply to Stefan Dirsch from comment #49)

I see Keypress and Keyrelease events with the newer kernel, but not with the older. I would have expected vice versa. Weird.

A thousand pardons ... I shouldn't have responded, being so tired. Taking care of a mother with Alzheimer's, a puppy, the house, and still working, is very exhausting. Both xev outputs are from the same kernel 5.3.18-lp152.19.2 because I couldn't get xev to work on a VT, or as root. So the output would be the USB keyboard, and I disregarded it. Should I publish the xev output even if it is from a USB keyboard? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c52 --- Comment #52 from Luiz Cantarino --- Mr Stefan, 'xev' does not work on VT1, nor on VT3. So you can't show the laptop's keyboard output. However, I can show the USB keyboard output. Follow the data: -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c54 --- Comment #54 from Luiz Cantarino --- Created attachment 841193 --> http://bugzilla.opensuse.org/attachment.cgi?id=841193&action=edit xev VT3 IceWM kernel 5.3.18-152.36.1 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c56 --- Comment #56 from Luiz Cantarino --- Created attachment 841195 --> http://bugzilla.opensuse.org/attachment.cgi?id=841195&action=edit xev Xterm IceWM kernel 5.3.18-152.36.1 keyboard USB -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c58 --- Comment #58 from Luiz Cantarino --- (In reply to Stefan Dirsch from comment #57)

No, you need to start the xev program from a X terminal.

In this case, there is no event output from 'xev' in the 5.3.18-lp152.36.1 kernel on the laptop's internal keyboard. I can only start it using the USB keyboard. Follow the data. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c60 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(luizcantarino@yah | |oo.com.br) | --- Comment #60 from Stefan Dirsch --- Ok. So indeed no X events with latest kernel and no changes in xserver. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c62 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(luizcantarino@yah | |oo.com.br) --- Comment #62 from Stefan Dirsch --- Thanks. I guess the synaptics X driver is the issue here, but please your current X logfile, so this can be verified. --> /var/log/Xorg.0.log Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c65 --- Comment #65 from Luiz Cantarino --- (In reply to Stefan Dirsch from comment #63)

... but please *attach* your current ...

Ok, follow data from the file /var/log/Xorg.0.log of the 5.3.18-lp152.41 kernel, according to the last update -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c67 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(luizcantarino@yah | |oo.com.br) | --- Comment #67 from Stefan Dirsch --- Ok. Apparently now "evdev" driver took over keyboard support and "synaptics" driver touchpad support. Not sure why they are loaded if you removed everything in /etc/X11/xorg.conf.d. Hmm ... maybe the files for evdev and synaptics are still there ... This also means the "libinput" driver would be the culprit here (or at least *is* together with the updated kernel) and removing xf86-input-libinput package would be a workaround for you. Unfortunately you now removed content in /etc/X11/xorg.conf.d and to bring this back you would need to reinstall some packages, probably these are: systemd xf86-input-evdev xorg-x11-server xf86-input-synaptics Then uninstall xf86-input-libinput Hope this gives you a useful workaround. Why libinput driver no longer works together with updated kernel I have no idea at the moment. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c68 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jengelh@inai.de --- Comment #68 from Stefan Dirsch --- I'm wondering if you get any events when running libinput debug-events on the Linux console. Adding maintainer of libinput package ... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c70 --- Comment #70 from Stefan Dirsch --- libinput command is part of libinput-tools package. In case this isn't installed yet ... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c71 --- Comment #71 from Luiz Cantarino --- (In reply to Stefan Dirsch from comment #70)

libinput command is part of libinput-tools package. In case this isn't installed yet ...

Before answering, I would like to clarify that I did not delete the synaptics file, and when I restarted in the /etc/x11/xorg.conf.d directory, there were two files, the keyboard and the synaptics files. I did as you asked, and the libinput file didn't come back. Follow the data: -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c73 --- Comment #73 from Luiz Cantarino --- Created attachment 841624 --> http://bugzilla.opensuse.org/attachment.cgi?id=841624&action=edit /etc/x11/xorg.conf.d -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c75 --- Comment #75 from Stefan Dirsch --- So did you see events with libinput command when pressing internal keyboard? It doesn't seem so. Compare to what you see when pressing USB external keyboard. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c77 --- Comment #77 from Luiz Cantarino --- Created attachment 841625 --> http://bugzilla.opensuse.org/attachment.cgi?id=841625&action=edit libinput debug-events -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c79 --- Comment #79 from Luiz Cantarino --- (In reply to Stefan Dirsch from comment #67)

Ok. Apparently now "evdev" driver took over keyboard support and "synaptics" driver touchpad support. Not sure why they are loaded if you removed everything in /etc/X11/xorg.conf.d. Hmm ... maybe the files for evdev and synaptics are still there ...

This also means the "libinput" driver would be the culprit here (or at least *is* together with the updated kernel) and removing xf86-input-libinput package would be a workaround for you. Unfortunately you now removed content in /etc/X11/xorg.conf.d and to bring this back you would need to reinstall some packages, probably these are:

systemd xf86-input-evdev xorg-x11-server xf86-input-synaptics

Then uninstall

xf86-input-libinput

Hope this gives you a useful workaround. Why libinput driver no longer works together with updated kernel I have no idea at the moment.

I don't know how to answer ... I think I followed your guidance ... I turned on the laptop, logged in, opened the konsole, did the recommended installations. In the /etc/x11/xorg.conf.d directory, the 'libinput' folder did not appear, as I showed in the print, and the laptop keyboard worked. Then I did the manual installation of xf86-input-libinput by konsole: sudo zypper in -f xf86-input-libinput When I restarted the laptop I had no keyboard ... the libinput debug-events, only had an output for the USB keyboard. Then I performed the uninstallation by konsole, using a USB keyboard: sudo zypper rm xf86-input-libinput When I restarted the laptop, I had the keyboard again, and showed the outputs of libinput debug-events. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c81 --- Comment #81 from Luiz Cantarino --- (In reply to Stefan Dirsch from comment #80)

Ok. Let's assume this happens when libinput X driver is active. For now you can work with synaptics driver for touchpad and evdev driver for internal keyboard when using latest kernel.

Perhaps it is easier to give a history ... At the beginning of the year, tumbleweed was installed on this laptop. With the pandemic, my sister needed it, and as it was a home office, I ended up installing Debian 10. As soon as her work made a machine available for her, I was comfortable, I had no problem with Debian. However, when Debian upgraded from 10.4 to 10.5, I was left without a keyboard and touchpad. I didn't care, and I took the opportunity to try Void ... As soon as I updated, I ran out of keyboard ... I tried to go back to tumbleweed, but there was no keyboard in the installation. I went to Leap, but as soon as I updated, I stayed on keyboard ... That's when I connected you ... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c83 --- Comment #83 from Stefan Dirsch --- Hmm. Not sure what you mean with "it's over" ... could you explain? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c85 --- Comment #85 from Stefan Dirsch --- Ok. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c91 --- Comment #91 from Luiz Cantarino --- (In reply to Stefan Dirsch from comment #89)

It would be good if everybody affected could test again in runlevel 3 without Xserver in place with libinput command (again). See comments 68 and following.

Ok, I would like to help - don't forget that I am noob - so how do I test at runlevel 3 without the Xserver installed? In time, in the openSUSE forum, a member resolves this bug in a different way: https://forums.opensuse.org/showthread.php/544471-HP-Pavillion-x360-Keyboard... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c93 --- Comment #93 from Takashi Iwai --- And, if blacklisting intel-vtn works, it'll explain everything: there has been quite a few changes in this driver between 5.7 and 5.8 about the tablet mode detection. And those have been backported to Leap 15.2 kernel; that's why Leap 15.2 installation worked and later not. Once after confirmed, we'd need to report to the upstream. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c95 --- Comment #95 from Luiz Cantarino --- (In reply to Stefan Dirsch from comment #92)

Thanks. You mean blacklisting intel_vbtn kernel module, right?

https://documentation.suse.com/sled/15-SP1/html/SLED-all/cha-mod.html --> 23.2.2 Blacklisting Kernel Modules with modprobe

Then please give it a try. Thanks!

Then I reinstall the xf86-input-libinput driver: sudo zypper in -f xf86-input-libinput Restart the machine, and send the kernel module to the blacklist: sudo echo blacklist = intel_vbtn >> /etc/modprobe.d/50-blacklist.conf && mkinitrd && reboot Please confirm that the command is correct. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c97 --- Comment #97 from Luiz Cantarino --- (In reply to Takashi Iwai from comment #96)

(In reply to Luiz Cantarino from comment #95)

...

Restart the machine, and send the kernel module to the blacklist: sudo echo blacklist = intel_vbtn >> /etc/modprobe.d/50-blacklist.conf && mkinitrd && reboot

It's better to create a new file. Also don't put '=' at the line.

% su % echo blacklist intel_vbtn > /etc/modprobe.d/90-keyboard-workaround.conf % mkinitrd % reboot

Gentlemen, I am pleased to announce that it works! I installed the xf86-input-libinput driver, restarted the machine, and with a USB keyboard, I sent the intel_vbtn kernel module to the black list ... And I have my internal laptop keyboard again. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c99 --- Comment #99 from Luiz Cantarino --- Created attachment 841991 --> http://bugzilla.opensuse.org/attachment.cgi?id=841991&action=edit /etc/ -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c101 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #101 from Takashi Iwai --- Can all people who suffer from the bug provide the output of dmidecode command please? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c103 --- Comment #103 from Luiz Cantarino --- Created attachment 842039 --> http://bugzilla.opensuse.org/attachment.cgi?id=842039&action=edit dmidcode -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c107 --- Comment #107 from Takashi Iwai --- (In reply to Luiz Cantarino from comment #106)

sudo zypper rm /etc/modprobe.d/90-keyboard-workaround.conf

This must be without zypper sudo rm etc/modprobe.d/90-keyboard-workaround.conf And reboot, choose the newly installed kernel and test. You have to choose the right kernel explicitly in GRUB menu as it'll appear mostly at the bottom of the list even if it was a new kernel. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c109 --- Comment #109 from Luiz Cantarino --- Created attachment 842229 --> http://bugzilla.opensuse.org/attachment.cgi?id=842229&action=edit output of addrepo -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c111 --- Comment #111 from Luiz Cantarino --- (In reply to Takashi Iwai from comment #110)

You seem to have a typo in URL. It must be "standard", not "standart".

Good job, sir. Takashi, it worked! But I had to install the kernel using yast, I don't know why zypper didn't work. Follows output from 'lsmod' -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c113 --- Comment #113 from Luiz Cantarino --- Created attachment 842232 --> http://bugzilla.opensuse.org/attachment.cgi?id=842232&action=edit output of lsmod -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c115 --- Comment #115 from Stefan Dirsch --- "If just a for argument is used, it should be a URI targeting a .repo file..." tells me Google Translate... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 http://bugzilla.opensuse.org/show_bug.cgi?id=1175599#c117 --- Comment #117 from Luiz Cantarino --- (In reply to Takashi Iwai from comment #104)

Now we have a fix patch from the upstream, to be included in either 5.9-final or 5.10-rc1.

Please give it a try later. Install the kernel, remove the blacklist,

reboot with that kernel, and test whether the built-in keyboard still works. If it works, please confirm that intel_vbn module is loaded (shown in lsmod output).

I'm confused about how to proceed now ... Do I continue booting the laptop, with the kernel with the fix patch, or do I go back to the defaut kernel, and send the intel_vbtn kernel module to the blacklist again? What would be better? -- You are receiving this mail because: You are on the CC list for the bug.