(In reply to Mateusz Jończyk from comment #136)
>
> Mysteriously, the device responded with:
>
> [ 1.789711] i8042: [537] ff -> i8042 (command)
> [ 1.789773] i8042: [537] ff -> i8042 (parameter)
> [ 1.895570] i8042: [537] fa <- i8042 (return)
> [ 1.898595] i8042: [537] aa <- i8042 (return)
>
The 8042 was not waiting for any parameter so the second "ff" went straight to the keyboard controller and told it to reset.
The keyboard controller (even though it probably was disabled - I won't analyse it further now) answered with fa aa - according to the spec the "fa" should not be there, but it is probably just a mistake in the embedded controller.
(In reply to Mateusz Jończyk from comment #136)
>
> Mysteriously, the device responded with:
>
> [ 1.789711] i8042: [537] ff -> i8042 (command)
> [ 1.789773] i8042: [537] ff -> i8042 (parameter)
> [ 1.895570] i8042: [537] fa <- i8042 (return)
> [ 1.898595] i8042: [537] aa <- i8042 (return)
>
The 8042 was not waiting for any parameter so the second "ff" went straight to the keyboard controller and told it to reset.
The keyboard controller (even though it probably was disabled - I won't analyse it further now) answered with fa aa - according to the spec the "fa" should not be there, but it is probably just a mistake in the embedded controller.