Comment 102 for bug 1949394

(In reply to Mateusz Jończyk from comment #96)
> 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)
>

this does not seems to be very important. The function i8042_controller_init() waits for receiving twice the same answer to its I8042_CMD_CTL_RCTR before continuing.

The problem comes that psmouse_probe() is not called at all (it should be called by psmouse_connect()). There are no traces of psmouse trying to ping the touchpad to guess its protocol.

My suggestion would be to add some debug information to check that psmouse_connect() and psmouse_probe() are actually called. And if they are not, try to debug where they are cut short.