Comment 97 for bug 2034477

> I tried applying your patch but unfortunately it doesn't seem to help.
Curiously I get the message "ACPI: IRQ 1 override to edge(!), high" and not "level(!), low" as you suggested.
Looking at the source code, it doesn't seem that the variables "t" or "p" are ever modified, so I assume it should always show "edge" and "high"?

Ah right my patch neglects to change t and p, but the (!) does show the settings are actually being changed so it does do what it should.

Its unfortunate that the patch does not help. From your description in bug 217873 where you write "This causes an extreme input delay (15 seconds to 1 minute per key press) but at least something happens." I was hoping this would be an IRQ issue, because that sounds a lot like IRQs not working.

I wonder what happens if you mix my patch which manually sets the interrupt trigger type with some of the i8042 options.

E.g. try i8042.nopnp (as suggested in the dmesg) + i8042.dumbkbd + i8042.noloop note using i8042.direct generally speaking is a bad idea on laptops ...

I wonder what the output of "dmesg | grep i8042" is when adding "i8042.nopnp i8042.dumbkbd i8042.noloop" to the kernel commandline ?

And as said try mixing that with overriding the IRQ trigger type for starters I would go with "edge high" since that is the default override (which gets skipped on your laptop because it is AMD Zen based).