Description of problem: Keyboard is not working on Asus ExpertBook B2502 Version-Release number of selected component (if applicable): kernel-5.19.15-201.fc36.x86_64 kernel-6.0.5-200.fc36.x86_64 How reproducible: After installation Fedora 36 Live x86_64 ISO on an Asus ExpertBook B2502 laptop, its built-in keyboard is not working. The same problem is experienced with the newest Fedora 37 Live x86_64 ISO Beta release. Steps to Reproduce: 1. Install the Fedora 36 x86_64 version using the official Live ISO file. 2. Install the Fedora 37 x86_64 Beta version using the official Live ISO file. 3. Actual results: Built-in keyboard is not working (dead) Expected results: Working built-in keyboard Additional info: The problem is very similar to that reported here: https://www.linux.org/threads/keyboard-not-working-asus-vivobook-s5402za.41986/
This indeed sounds like it is the same issue as: https://bugzilla.kernel.org/show_bug.cgi?id=216158 Assuming this is indeed the same issue, then I can build a Fedora kernel with your laptop model added to this list of models which need a special workaround: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/acpi/resource.c#n406 But to do that I need you to gather the model strings used by this list first, there are 2 ways to do this: 1. Under Windows using: https://gnuwin32.sourceforge.net/packages/dmidecode.htm Note I have never used this, I don't know if it works, at all. It could also be some virus or trojan software. I don't think so, but I want to make clear that this is just something which I found on duckduckgo after a 5 seconds search. 2. Install Fedora using an external USB keyboard, you are going to need to do that anyway to then later install the fixed kernel. And then under Fedora run: sudo dnf install dmidecode sudo dmidecode > dmidecode.txt And then attach dmidecode.txt as an attachment to this bug. Once I have the dmidecode output I can write a patch to add your model to the: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/acpi/resource.c#n406 list and then build a custom Fedora kernel for you, which you can then download as rpms, install and test. Since the results of me building a custom kernel for you will be just a set of kernel packages (rpms) you will still need to install Fedora first, which as I mentioned before will hopefully be possible using an external USB keyboard and you will also use the USB keyboard to install the kernel packages. Once you have booted the custom kernel your laptop's keyboard will hopefully work and then you won't need the USB keyboard anymore. p.s. This all assumes the problem on your laptop is indeed the same as the one from: https://bugzilla.kernel.org/show_bug.cgi?id=216158 which seems likely, but there is no guarantee it actually is the same problem.
Created attachment 1924466 [details] The generated dmidecode.txt
(In reply to Edgar Bertoti from comment #2) > Created attachment 1924466 [details] > The generated dmidecode.txt Thanks. Here is a link to a custom kernel build with a patch which will hopefully fix things on your model (koji is the Fedora buildsystem) : https://koji.fedoraproject.org/koji/taskinfo?taskID=94236809 Note this is still building atm, it should be finished in a couple of hours and then that page should show links to rpm-s for you to download. Here are some generic instructions for installing a kernel directly from koji: https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt
The custom kernel build which I have done for you is finished now. Note since this is a custom / test build the buildsystem will remove the rpms after approx. a week to reclaim the disk-space used. So even if you don't have time to test soon, please at least download the rpms. Please let me know if this custom kernel fixes your keyboard issue, then I submit the patch upstream for inclusion into the official kernel sources.
Created attachment 1924718 [details] [PATCH] ACPI: resource: Add Asus ExpertBook B2502 to Asus quirks Here is the patch included in the custom kernel.
Thank you for the custom kernel, I have installed the generated kernel packages, according to the instructions: cat /proc/cmdline BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.0.8-300.rh2142574.fc37.x86_64 root=UUID=d7f8ffb7-4f15-40c7-887b-26d979768928 ro rootflags=subvol=root rhgb quiet Unfortunately, the indicated problem with the built-in keyboard is still present.
(In reply to Edgar Bertoti from comment #6) > Thank you for the custom kernel, I have installed the generated kernel > packages, according to the instructions: > > cat /proc/cmdline > BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.0.8-300.rh2142574.fc37.x86_64 > root=UUID=d7f8ffb7-4f15-40c7-887b-26d979768928 ro rootflags=subvol=root rhgb > quiet > > Unfortunately, the indicated problem with the built-in keyboard is still > present. Thank you for testing. Unfortunately I have been completely swamped with work, so I have not been able to find the time to take another look at this and I don't know when I will find the time... One thing which you could try is adding the following to the kernel commandline (of any recent kernel): i8042.nomux=1 i8042.reset=1 If that does not help you can also try adding (on top of the above): i8042.nopnp=1 and/or atkbd.reset=1 Note if this helps, please try finding the minimal combination which helps, e.g. if "i8042.nomux=1 i8042.reset=1" fixes things you could try using only i8042.nomux=1 or only i8042.reset=1 If this helps and you can let me know the minimum combination necessary, then I can add a DMI quirk to automatically enable this behavior on your model laptop going forward. If this does not help, I guess you could also try this in combination with the test kernel build I did for you. Maybe we got unlucky and your model needs both types of workaround ?
Thank you for your help and suggestions. I supplemented the kernel commandline (the /etc/default/grub file) as seen below and tried the custom, as well as the newest kernel: cat /proc/cmdline BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.0.8-300.rh2142574.fc37.x86_64 root=UUID=d7f8ffb7-4f15-40c7-887b-26d979768928 ro rootflags=subvol=root rhgb quiet atkbd.reset=1 i8042.nopnp=1 i8042.nomux=1 i8042.reset=1 cat /proc/cmdline BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.0.11-300.fc37.x86_64 root=UUID=d7f8ffb7-4f15-40c7-887b-26d979768928 ro rootflags=subvol=root rhgb quiet atkbd.reset=1 i8042.nopnp=1 i8042.nomux=1 i8042.reset=1 Unfortunately, the buil-in keyboard is still dead.
I am afraid that I'm pretty much out of ideas how to fix this then. But I see that there is no dmesg attached here. Can you (re)boot the laptop and then shortly after the boot run: dmesg > dmesg.txt in a terminal and then attach the generated dmesg.txt file here? Then I can take a look and see if anything stands out, but no promises.
Created attachment 1932148 [details] The generated dmesg.txt file. Thank you for your help. Attached please find the dmesg.txt file. Some additional information if it helps: The built-in keyboard works when I enter BIOS at booting, and I have just recognized that it also works when I enter the GRUB menu at booting. The keyboard is dead in both multi-user text mode (runlevel 3) and multi-user GUI mode(runlevel 6). I have no other operating system installed on this laptop, only Fedora 37.
Ok, good news, your dmesg shows: [ 1.116566] ACPI: IRQ 1 override to edge, high Which means that your original hunch that this seems to be similar to: https://www.linux.org/threads/keyboard-not-working-asus-vivobook-s5402za.41986/ https://bugzilla.kernel.org/show_bug.cgi?id=216158 seems to be correct, but for some reason my first attempt at fixing this by adding the DMI info for your laptop to the list of Asus laptops needing special work here did not work? I have started a new Fedora test kernel build now: https://koji.fedoraproject.org/koji/taskinfo?taskID=95277765 With a patch which avoids the "IRQ 1 override" with a quick and dirty hack; and which logs some extra debugging to help figure out why the original patch did not help. Note this kernel is still building atm, it should be finished in a couple of hours. The generic instructions for installing a kernel directly from koji are still here: https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt Please give this kernel a try, with all the other i8042 / atkbd options removed from the commandline. Once you have booted this new kernel please check if your keyboard works now. Independent of if your keyboard works or not, please collect a new dmesg with this kernel and attach it here.
Note the new test kernel is done building and RPMs are now available here: https://koji.fedoraproject.org/koji/taskinfo?taskID=95277765
Created attachment 1932388 [details] The new dmesg file.
Great kernel and great job! I am typing this message on my built-in keyboard. Attached please find the new dmesg file. Please let me know if you need any more information. Thank you very much for all your help.
Good to hear that the test kernel helps. However that kernel has a quick and dirty fix, not something which can be added to the official upstream / Fedora kernels. Upon double checking my initial patch it seems I made an error with that patch, sorry. Here is a new test kernel build with a fixed version of a proper patch fixing this. If you can confirm that this indeed fixes things, then I can submit the proper fix upstream: https://koji.fedoraproject.org/koji/taskinfo?taskID=95323442 As before this kernel is still building atm, it should be finished in a couple of hours. The generic instructions for installing a kernel directly from koji are still here: https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt
Created attachment 1932692 [details] The latest dmesg file with a proper patch. Thank you, the built-in keyboard works after installing the newest test kernel with a fixed version of a proper patch. I am sending the new dmesg file. Only a rather small problem exists that I discovered yesterday: the sensepoint on the keyboard with the two touchpad buttons does not work. But the touchpad itself works (it always worked) with all its functionalities.
(In reply to Edgar Bertoti from comment #16) > Created attachment 1932692 [details] > The latest dmesg file with a proper patch. > > Thank you, the built-in keyboard works after installing the newest test > kernel with a fixed version of a proper patch. I am sending the new dmesg > file. Thanks, that is good to hear. I have submitted the fix upstream now. > Only a rather small problem exists that I discovered yesterday: the > sensepoint on the keyboard with the two touchpad buttons does not work. But > the touchpad itself works (it always worked) with all its functionalities. Ok, I assume this also does not work with the kernels where the keyboard is broken? Can you please open a new bug report for this issue? And let me know the number of the new bug here ? Then I will ask a colleague who specializes in touchpads + pointing-sticks to take a look.
> Ok, I assume this also does not work with the kernels where the keyboard is broken? The sensepoint has never worked, independently of which kernel is booted. I opened a new bug report, its number is Bug 2154204. Thank you once more for all your help. I am happy with my working keyboard.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.