[email protected] (Patrick Welche) writes:
>uc> diskable pckbc
>[125] pckbc0 disabled
>but no change:
>wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation)
>wsmux1: connecting to wsdisplay0
>ukbd0 at uhidev0: 8 modifier keys, 6 key codes
>wskbd0 at ukbd0 mux 1
>wskbd0: connecting to wsdisplay0
>So can lack of "console" be the reason I can't break into ddb?
Sure. Only the console keyboard checks for magic input.
When wskbd is attached from a console keyboard, you see the "console keyboard"
message. The first USB keyboard should be the 'console keyboard' unless
pckbc_cnattach finds a PC keyboard.
The problem is, pckbc finds a PC keyboard even when you disable the driver
because it just maps the hardware (and that a long time before autoconfig
would attach the driver) and sends a simple enable command. Sending
the command doesn't require any complex response from the hardware
and it doesn't require a working keyboard.
There is a kernel option PCKBC_CNATTACH_SELFTEST which sends a selftest
command to the PC keyboard and waits for a successful response. Maybe
this helps in your case to really skip the PC keyboard for the console.
The alternative is of course to remove pckbd from the kernel configuration.
--
--
Michael van Elst
Internet: [email protected]
"A potential Snark may lurk in every tree."
