Bug 216579
| Summary: | Laptop Internal keyboard not working on ASUS VivoBook S5602ZA on ubuntu 22.04. | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Dzmitry (wrkedm) |
| Component: | Input Devices | Assignee: | drivers_input-devices |
| Status: | RESOLVED CODE_FIX | ||
| Severity: | normal | CC: | examiner, renato.lochetti, tamim |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 5.15.0-48-generic | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
Fix IRQ issues on keyboard for S5602ZA for linux kernel 6.1+
Fix IRQ issues on keyboard for all vivbook on linux 5.15+ |
||
Created attachment 302997 [details]
Fix IRQ issues on keyboard for S5602ZA for linux kernel 6.1+
@Dzmitry I have attached a patch that should fix this the issue on the 6.1+ kernels and also another that fix all the vivobook laptops we have found so far for 5.15+ kernels. I will get this sent over the mailing list and update the bug report when I have details about what version of the kernel this will get merged into
Let me know if you continue to have issues with your laptop after applying the patch.
Thanks,
Tamim
Created attachment 302998 [details]
Fix IRQ issues on keyboard for all vivbook on linux 5.15+
@Tamim After applying the patch I'v got the working keyboard. Highly appreciate your help, thanks a lot! Looks like this issue should be fixed in the 6.1 kernel: https://lore.kernel.org/linux-acpi/CAJZ5v0hgm2REg6cxy3cdnETpt0G-cnH5JH0X8FqS8XtTzttZyg@mail.gmail.com/T/#t Comment on attachment 302998 [details] Fix IRQ issues on keyboard for all vivbook on linux 5.15+ This patch doesn't work on M5402RA vivobook Refer to the following bug for details: https://bugzilla.kernel.org/show_bug.cgi?id=216649 |
ASUS VivoBook S5602ZA laptop keyboard is not working with Ubuntu 22.04. Please find the result of the execution of following commands: cat /sys/firmware/acpi/tables/DSDT > dsdt.dat iasl -d dsdt.dat grep -A 30 PS2K dsdt.dsl | grep IRQ -A 1 Result: IRQ (Level, ActiveLow, Exclusive, ) {1} Seems that this is the same issue as mentioned here https://bugzilla.kernel.org/show_bug.cgi?id=216158