Created attachment 306810 [details] DMESG I am following several bugs for ASUS VivoBook laptops which have a non-working internal keyboard. Adding this model to the quirks list in `drivers/acpi/resource.c` with a match on the board name with my model E1404GA causes the internel keyboard to work again, however I would have to patch my own kernel every update which gets tedious quickly. I would be thankful if this model could be included in the list in future kernel versions. I commented in https://bugzilla.kernel.org/show_bug.cgi?id=216158. @Paul Menzel asked me to file a new issue and CC him (I will try to do that) and to also add the output of dmesg, which I did and attached to this bug.
Created attachment 306843 [details] ACPI: resource: Skip IRQ override on Asus Vivobook Go E1404GA The DMI string is: [ 0.000000] DMI: ASUSTeK COMPUTER INC. Vivobook Go E1404GA_E1404GA/E1404GA, BIOS E1404GA.302 08/23/2023 Please also *attach* the output of `dmidecode` and `dsdt.dat` from the commands below: $ sudo dmidecode > dmidecode.txt $ sudo cat /sys/firmware/acpi/tables/DSDT > dsdt.dat $ iasl -d dsdt.dat $ grep -A 30 PS2K dsdt.dsl | grep IRQ -A 1 Please find a preliminary patch attached.
Created attachment 306847 [details] dmidecode.txt
Created attachment 306848 [details] dsdt.dat
I added these files @PaulMenzel
Thank you. (I am Cc’ed to the report, so no need for comment#4 in the future. ;-)) I sent the patch [1]. The diff is the same to the attached one here, but the commit message is amended. It’d be great if you could test the patch. [1]: https://lore.kernel.org/linux-acpi/20240911081612.3931-1-pmenzel@molgen.mpg.de/T/#u
It’d be also great if you reported the issue to the ASUS. The chances they are going to fix it are low, but if enough reports show up in their issue tracker, they might fix it.
(In reply to Paul Menzel from comment #5) > Thank you. (I am Cc’ed to the report, so no need for comment#4 in the > future. ;-)) > > I sent the patch [1]. The diff is the same to the attached one here, but the > commit message is amended. > > It’d be great if you could test the patch. > > [1]: > https://lore.kernel.org/linux-acpi/20240911081612.3931-1-pmenzel@molgen.mpg. > de/T/#u Tested and the patch fixes the issue! What kernel version do you reckon I can find this fix? Thanks for everything
Thank you for testing. It’d be great if you replied to the patch email I sent yesterday with the tag below: Tested-by: Your Name <your@email> Hopefully it’s going to be picked up for the next merge window, so Linux 6.12. But now promises.
Tom, Thank you for fixing this. Paul, thank you for writing a patch for this. I have submitted an alternative fix for this loosing an existing DMI match instead: https://lore.kernel.org/linux-acpi/20240927141606.66826-2-hdegoede@redhat.com/ The new entry which you submitted would have covered both models anyways (because of DMI_MATCH() substring matching), so just loosing the existing quirk is better.
Hello I have the same problem for dmidecode: System Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: ASUS Vivobook 15 X1504VAP_X1504VA Version: 1.0 Serial Number: S1N0CV02L86302G UUID: cdc508f0-d3f1-f743-bce4-5eb9d4c06fda Wake-up Type: Power Switch SKU Number: Family: ASUS Vivobook 15 Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: X1504VAP Version: 1.0 Serial Number: RC50NBCV00977AMB Asset Tag: ATN12345678901234567 Features: Board is a hosting board Board is replaceable Location In Chassis: Default string Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 sudo grep -A 30 PS2K dsdt.dsl | grep IRQ -A 1 IRQ (Level, ActiveLow, Exclusive, ) {1} Its possible to get this model listed in future kernels? Thanks!
(In reply to gazo11 from comment #10) > Hello I have the same problem for dmidecode: > > > System Information > Manufacturer: ASUSTeK COMPUTER INC. > Product Name: ASUS Vivobook 15 X1504VAP_X1504VA > Version: 1.0 > Serial Number: S1N0CV02L86302G > UUID: cdc508f0-d3f1-f743-bce4-5eb9d4c06fda > Wake-up Type: Power Switch > SKU Number: > Family: ASUS Vivobook 15 > > Its possible to get this model listed in future kernels? Thanks! Thank you for reporting this, I've submitted a patch to add this to the irq1_level_low_skip_override[] list: https://lore.kernel.org/linux-acpi/20241220181352.25974-1-hdegoede@redhat.com/
Super grateful. People like you make Linux the best operating system that exists.
Hello I have the same problem for dmidecode: System Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: ASUS Vivobook 14 X1404VAP_X1404VA Version: 1.0 Serial Number: S1N0CV05H399023 UUID: 4f4adcfd-3666-084c-89a4-f6975a5f2083 Wake-up Type: Power Switch SKU Number: Family: ASUS Vivobook 14 Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: X1404VAP Version: 1.0 Serial Number: S101NBCV003W58MB Asset Tag: ATN12345678901234567 Features: Board is a hosting board Board is replaceable Location In Chassis: Default string Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 sudo grep -A 30 PS2K dsdt.dsl | grep IRQ -A 1 IRQ (Level, ActiveLow, Exclusive, ) {1} uname -a Linux sh-ASUS-Vivobook-14-X1404VAP-X1404VA 6.11.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 12 21:43:43 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux sb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.10 Release: 24.10 Codename: oracular Its possible to get patch for this? Also i will be highly appreciated for explanations (pointing me to some docs or etc.) how i can install this patch?
@mrcold, it’d be great if you created a new issue, as this issue got pretty long already, and is about the ASUS VivoBook E1404GA, and should be closed.
(In reply to Paul Menzel from comment #14) > @mrcold, it’d be great if you created a new issue, as this issue got pretty > long already, and is about the ASUS VivoBook E1404GA, and should be closed. Sure! Done -> https://bugzilla.kernel.org/show_bug.cgi?id=219891 Thank you for your response! p.s. sorry for delay - website return 504 Gateway Time-out constantly for me today :(