Maybe we should stop relying only on the open firmware to determine the 
console, since newer open firmwares don't seem to provide enough 
information in this respect. In particular, if we have an akbd, we 
should use it as console no matter what the openfirmware says.

Currently, I suspect the wsmux trick doesn't let the adb keyboard be 
recognized as the proper console and doesn't let you drop into DDB if 
you hit Cmd-Opt-Power. I had to hack my kernel to hardcode that my 
console is akbd.

  Aymeric

Krister Walfridsson wrote:

> As a work around, you can get a working keyboard by adding
>
>    pseudo-device wsmux
>
> to your kernel config file: