Nope, both didn't help. It was mentioned above.
The controller does not have mux. Even when the mouse is working, it does not use it. I have made diffs of the i8042 output in both states. Analyzed the i8042 output extensively and found not much interesting except for that:
at 0x60,0x64 irq 1,12 //start of i8042 initialization d1 -> i8042 (command) df -> i8042 (parameter) ff -> i8042 (command) c4 <- i8042 (flush, kbd) 20 -> i8042 (command) 65 <- i8042 (return) 20 -> i8042 (command) + fa <- i8042 (return) + 20 -> i8042 (command) + 65 <- i8042 (return) + 20 -> i8042 (command) 65 <- i8042 (return) 60 -> i8042 (command) 74 -> i8042 (parameter) d3 -> i8042 (command) 5a -> i8042 (parameter)
It happened when it worked. I have seen this only on this one log.
AUX interrupts are delivered, it was checked separately.
Nope, both didn't help. It was mentioned above.
The controller does not have mux. Even when the mouse is working, it does not use it.
I have made diffs of the i8042 output in both states.
Analyzed the i8042 output extensively and found not much interesting except for that:
at 0x60,0x64 irq 1,12 //start of i8042 initialization
d1 -> i8042 (command)
df -> i8042 (parameter)
ff -> i8042 (command)
c4 <- i8042 (flush, kbd)
20 -> i8042 (command)
65 <- i8042 (return)
20 -> i8042 (command)
+ fa <- i8042 (return)
+ 20 -> i8042 (command)
+ 65 <- i8042 (return)
+ 20 -> i8042 (command)
65 <- i8042 (return)
60 -> i8042 (command)
74 -> i8042 (parameter)
d3 -> i8042 (command)
5a -> i8042 (parameter)
It happened when it worked. I have seen this only on this one log.
AUX interrupts are delivered, it was checked separately.