| 1 | | I had a further look at the logs and the sources. The keyboard device is published {{{ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000}}} but then we never get the {{{ps2: keyboard found}}} from {{{keyboard_open}}}. However we also don't get the "keyboard probing failed" message from there. So either {{{keyboard_open}}} is not called at all, or it deadlocks in its early steps and never gets to probing the keyboard. |
| | 1 | I had a further look at the logs and the sources. The keyboard device is published {{{ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000}}} but then we never get the {{{ps2: keyboard found}}} from {{{keyboard_open}}}. However we also don't get the "keyboard probing failed" message from there. |
| | 2 | |
| | 3 | I rebuilt the ps/2 driver with tracing enabled, and it seems {{{keyboard_open}}} isn't called at all. ps/2 interrupts from the keyboard result in syslog messages: "input/keyboard/at/0 not enabled, data 0xa6 dropped". |
