I don't think that can be the case.  That's pretty durn inconsistent
with "S.O.P." on keyboards...  Said reset command, comes in via the
clock AND DATA lines - and REQUIRES the data line to be open collector
so (non-zero) data can be sent to the keyboard!  This is like having a
Dallas 1-wire device which pulls the single line low, then expects a
command to somehow manage to arrive in over that same line...
Something's broke or latched up or ???  (<EG>  This is also rather akin
to supergluing someone's hands to a Rhino, then criticizing them *when*
they don't wave goodbye <EG> but that's getting somewhat OT!)

I'm thinking to check the rise time on your 5V power for the keyboard
while waiting for me to get there (If it's too slow, perhaps the
keyboards are locking up - On a PC, the rise time's pretty fast IIRC.)

If that's not it, I'd try toggling the clock line to see if that happens
to unlatch things, is all I can come up with at this hour.  I should go
look at all the info I've notebooked together tomorrow.  A look at the
POST code in an AT's BIOS would be the first place I look, now where'd I
lose THAT at?  <G>

It's 2 AM and I'm rather "wiped", so maybe I'm forgetting something, of
course...

  Mark

Alan B Pearce wrote:
> Your keyboards that keep the data line low are probably awaiting a reset command
> from the PC before coming alive on the interface. Check the documentation
> available on the web for how the PC resets these.