On Fri, Jul 17, 2015 at 12:55:39AM +0200, Michael van Elst wrote: > In Patrick's case we have: > > >> wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation) > >> wskbd0 at pckbd0: console keyboard, using wsdisplay0 > > - the early console code detected a pckbd keyboard. > - pckbd0 is attached > > But he also sees "pckbdprobe: reset error", which means that the > pckbd driver attached but actually failed to see a keyboard. > > > I guess this is some kind of legacy emulation, where the USB keyboard > is presented as PS/2 hardware, but which is turned off as soon as > something is actually accessing the USB port. > This lets the console probe succeed, and the driver probe fail. > > Maybe this emulation can be turned off in the BIOS. Otherwise, > it's probably necessary to just remove the pckbd driver from > the kernel config.
Today I reproduced this on an old Optiplex GX620 with no PS/2 sockets, and yet another BIOS. With (no PCKBD_CNATTACH_MAY_FAIL) && PCKBC_CNATTACH_SELFTEST pckbc0 at isa0 port 0x60-0x64 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 uhidev1 at uhub0 port 2 configuration 1 interface 0 uhidev1: LITEON Technology USB Multimedia Keyboard, rev 1.10/1.01, addr 3, iclas s 3/1 ukbd0 at uhidev1 wskbd1 at ukbd0 mux 1 wskbd1: connecting to wsdisplay0 So it is necessary to remove pckbc and therefore pckbd, etc.: uhidev1 at uhub0 port 2 configuration 1 interface 0 uhidev1: LITEON Technology USB Multimedia Keyboard, rev 1.10/1.01, addr 3, iclas s 3/1 ukbd0 at uhidev1 wskbd0 at ukbd0: console keyboard, using wsdisplay0 and success! We have ddb! Thanks, Patrick
