ASUS Vivobook Go E1504GA_E1504GA's internal keyboard doesn't work on Linux (Linux Mint 21.1, also observed in live boots of Fedora 38 and EndeavourOS Cassini Nova). Typing has no effect. I saw that this has happened in other laptops including other Vivobooks (see bug 216158), and after running: cat /sys/firmware/acpi/tables/DSDT > dsdt.dat iasl -d dsdt.dat grep -A 40 PS2K dsdt.dsl | grep IRQ -A 1 I got the output: IRQ (Level, ActiveLow, Exclusive, ) {1} This seems to be the same bug as the one linked above.
I have the same model, and the same issue (testing on Fedora 38, kernel 6.4.9-200.fc38.x86_64). I will attach the output of dmesg, dmidecode, libinput list-devices and lsmod.
Created attachment 304818 [details] dmesg output
Created attachment 304819 [details] dmidecode output
Created attachment 304820 [details] libinput list-devices output
Created attachment 304821 [details] lsmod output
Typing in the BIOS (and in Windows) works as expected on the same machine.
Created attachment 304988 [details] Patch for Asus Vivobook Go E1504GA keyboard I have the same model, and I tried to rewrite patch from bug 216158. So, there is patch for 6.1.49 it work fine for me, tested on Ubuntu 23.04, but Mint and KDE Neon (both based on Ubuntu 22.04) just crash on boot into emergency shell and don't see disk when I upgrade kernel (any kernel from 5.19). And I really don't know is it necessary to add constant to every new notebook model? But I'm not developer and can't answer this question.
(In reply to Maxim Sokolovskii from comment #7) > Created attachment 304988 [details] > Patch for Asus Vivobook Go E1504GA keyboard > > I have the same model, and I tried to rewrite patch from bug 216158. So, > there is patch for 6.1.49 it work fine for me, tested on Ubuntu 23.04, but > Mint and KDE Neon (both based on Ubuntu 22.04) just crash on boot into > emergency shell and don't see disk when I upgrade kernel (any kernel from > 5.19). And I really don't know is it necessary to add constant to every new > notebook model? But I'm not developer and can't answer this question. The disk not being recognized is also a problem on Fedora 38 but not EndeavourOS Cassini Nova or Debian 12, so I think it's likely a regression that's already been patched. When I searched for an explanation I came across https://bbs.archlinux.org/viewtopic.php?id=283906 which sounds like the same issue and says that it was already fixed back in the 6.2 series. Not sure why Fedora was outdated (did they reject the patch for some reason? I thought 38 was past 6.2) or when Mint will catch up, but that's something to take up with the distro maintainers. The end of the thread does have some links which should be enough for you to track down the patch if you want to try it on older kernels, though. Also from what I remember reading in the other topics on this keyboard issue it was caused by a fix for a different issue affecting other devices, and so the solution has been patching exceptions for the devices affected by this keyboard issue on a case-by-case basis so as to not reintroduce the old bug to any devices.
I can confirm the keyboard doesn't work on laptop model ASUS Vivobook 15 Go E1504GA in Ubuntu Linux 23.04 and 23.10 beta exactly as described. I have also tried on these mainline kernels with no change: linux-image-6.5.0-5-generic 6.5.0-5.5 amd64 linux-image-unsigned-6.5.0-060500-generic 6.5.0-060500.202308271831 amd64 linux-image-unsigned-6.5.5-060505-generic 6.5.5-060505.202309230703 amd64 linux-image-unsigned-6.6.0-060600rc3-generic 6.6.0-060600rc3.202309242231 amd64 I think this model needs adding to the quirks list for the keyboard IRQ fix along with other models as per bug 216158, https://bugzilla.kernel.org/show_bug.cgi?id=216158
I have a Vivobook E1404GA and the internal keyboard doesn't work either, any solution ??
I built a custom patched kernel 6.5.0-5-generic (#5, 6.5.0-5.5) on this hardware, on Ubuntu 23.10 mantic (development branch), and from this I can confirm that the same patch used on https://bugzilla.kernel.org/show_bug.cgi?id=216158 makes the internal keyboard work as expected on this model. I have also created a Ubuntu-specific report for this issue here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037768
Can you reproduce this in 6.8.7?