ukbd0 from dell DRAC5 remote access controller

[Brian A. Seklecki]

>> pe1# cat /var/log/dmesg.today | grep kbd
>> kbd0 at kbdmux0
>> ukbd0: Dell DRAC5, rev 1.10/0.00, addr 3, iclass 3/1
>> kbd1 at ukbd0
>> atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
>>
>> trying to attach only that keyboard to the console:
>> ----
>> pe1# kbdcontrol -k /dev/ukbd0 < /dev/console
>> kbdcontrol: cannot open /dev/ukbd0: Device busy
>>
>> trying to add it to the mux:
>> ----
>> pe1# kbdcontrol -K < /dev/console
>> kbd0
>>     kbdmux0, type:AT 101/102 (2)
>> pe1# kbdcontrol -a kbd0 < /dev/kbdmux0
>> /dev/kbdmux0: Device busy.
>> pe1# kbdcontrol -a kbd1 < /dev/kbdmux0

Actually I'm surprised you were able to get dmesg(8) output.  What did you 
do, boot into the 2nd stage boot-loader and then set the console to serial 
console or just manual copy/paste transcribe?

I have the unfortunate situation of having lots of these machines remotely 
installed and deployed with DRAC setup with which I planned to do the 
remote install of FBSD, but this bug is a serious show stopper.

Moreover, the whole ActiveX client dependency is really absurd.  Does 
anyone have the client working in FreeBSD/Linux/POSIX?  Firefox anything 
even? I could deal with Java for remote console on DRAC4.

With DRAC4's latest firmware, they had even fixed the really annoying "I'm 
going to stop accepting user input and insert a string of 128 of the last 
character in the buffer" bug.

But now this...

~BAS


>> /dev/kbdmux0: Device busy.
>> pe1# kbdcontrol -k /dev/kbdmux0 < /dev/console
>> kbdcontrol: cannot open /dev/kbdmux0: Device busy
>>
>> trying to get info on the keyboards:
>> ----
>> pe1# kbdcontrol -i < /dev/kbdmux0
>> /dev/kbdmux0: Device busy.
>> pe1# kbdcontrol -i < /dev/ukbd0
>> /dev/ukbd0: Device busy.
>> pe1# kbdcontrol -i < /dev/kbd0
>> /dev/kbd0: Device busy.
>> pe1# kbdcontrol -i < /dev/console
>> kbd0:
>>     kbdmux0, type:AT 101/102 (2)
>>