You are not logged in.
Pages: 1
Hello, everyone!
It is the second month that I have fought with mainline Arch Kernel. I'm a user of ASUS S5402ZA Laptop, and there is a problem with the keyboard IRQ. It's not new; there is a topic on bugzilla.kernel.org, and the patch itself.
It's already merged with GitHub ArchLinux Kernel here, and about three revisions passed since that happened, yet even on the last kernel 6.0.10 keyboard doesn't work.
I compile the kernel from kernel.org with this patch, but I'd like to use mainline Arch Kernel without needing to recompile it over and over.
Where can I ask for a patch merge with the last kernel?
Thank you.
Patch:
diff --git a/drivers/acpi/resource.c b/drivers/acpi/resource.c
index 19358a641610..a2c5d1cc3d40 100644
--- a/drivers/acpi/resource.c
+++ b/drivers/acpi/resource.c
@@ -399,6 +399,40 @@ static const struct dmi_system_id medion_laptop[] = {
{ }
};
+static const struct dmi_system_id asus_laptop[] = {
+ {
+ .ident = "Asus Vivobook K3402ZA",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
+ DMI_MATCH(DMI_BOARD_NAME, "K3402ZA"),
+ },
+ },
+ {
+ .ident = "Asus Vivobook K3502ZA",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
+ DMI_MATCH(DMI_BOARD_NAME, "K3502ZA"),
+ },
+ },
+ {
+ .ident = "Asus Vivobook S5402ZA",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
+ DMI_MATCH(DMI_BOARD_NAME, "S5402ZA"),
+ },
+ },
+ {
+ .ident = "Asus Vivobook S5602ZA",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
+ DMI_MATCH(DMI_BOARD_NAME, "S5602ZA"),
+ },
+ },
+ { }
+};
+
+
+
struct irq_override_cmp {
const struct dmi_system_id *system;
unsigned char irq;
@@ -409,6 +443,7 @@ struct irq_override_cmp {
static const struct irq_override_cmp skip_override_table[] = {
{ medion_laptop, 1, ACPI_LEVEL_SENSITIVE, ACPI_ACTIVE_LOW, 0 },
+ { asus_laptop, 1, ACPI_LEVEL_SENSITIVE, ACPI_ACTIVE_LOW, 0 },
};
static bool acpi_dev_irq_override(u32 gsi, u8 triggering, u8 polarity,Last edited by Overbloom (2022-12-04 06:52:06)
Offline
Please edit your post to use [ code ] tags rather than [ quote ] tags.
You could file a bug, but I don't see the point if it is already in the pipeline. You didn't link to a specific commit or give any indication of the timeline, but you have to bear in mind that any commit there must first be released to testing. It may then go through staging. It will only then appear in the main repo. The delay is by design because changes can have unanticipated effects. The more essential the package, the greater the caution.
I don't know what you mean by 'revision' but if you mean a minor release to testing, you can search for bugs on the Arch bug tracker to see what, if anything, may cause delay. I did this earlier for mesa because 22.3 may fix a bug on my system, but 22.3 is wreaking havoc on others' machines - and could easily do so on mine, too - so I doubt it will appear in the main repo imminently and it may need further work upstream before that changes.
If you don't want to wait, you can use testing but then you have to expect things to break. If you prefer things don't break, you have to wait.
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
https://git.kernel.org/pub/scm/linux/ke … c0fcd73ce7
https://git.kernel.org/pub/scm/linux/ke … 692d1435f1
https://git.kernel.org/pub/scm/linux/ke … eaf26c99ed
The default branch of https://github.com/archlinux/linux/ master tracks Linus's mainline kernel. 6.1 will likely be released this week or next and shortly afterwards I would anticipate a 6.1 based release being packaged in testing.
Last edited by loqs (2022-12-04 05:42:10)
Offline
Thanks a lot for your answers! I will wait.
Looks like I just misunderstood how Git works. I found the changes in the code and assumed they would be rolled out in the nearest Arch Kernel revision.
Offline
Pages: 1