Some progress in research. I remembered how to catch key output using hexdump so I could examine and compare various configurations.
Using the same keyboard where I first saw the bug but connected to a plain old PC.
I use hexdump like this: # hexdump -C tap the problem key, then hit return and then Cntrol-D With numlock off I see: ^[[3~ 00000000 1b 5b 33 7e 0a 00000005 With numlock on: . 00000000 2e 0a 00000002 Using the same keyboard with a ps2-USB adaptor I see the same result as the numlock off test above whether numlock is on or off. This is what I see on the Shuttle also but it has no ps2 sockets so on it I'm stuck with no working dot key on the numpad and of course old habits die hard so I mess up lots of ip addresses. Is there something in wsconsctl or such that would let me patch it? I've been hunting through various related man pages but I have not hit on a hint so far. TIA, oppy On 30/03/2012 11:46, Opera wrote:
dmesg below. This little unit is cool and nearly everything important works on the important OS. I don't care about the funny multi-card thingy as I only use USB sticks. The one bug is very annoying. The numpad key that is "." when numlock is on and Del otherwise is really tricky. When booting, at the boot prompt if the numlock is on, the key produces dots as expected. Once BSD.RD or BSD is running that is not the case. BSD shows all the bugs and I shall skip BSD.RD as it is a subset. At a login: prompt it appears that no chars are being sent BUT if you hit the key 8 times it acts like you hit Enter except the Password: prompt becomes assword: Hit an Enter there and you get a Login failed and a new "login:" prompt. (of course!) At this point hitting the crazy key results in ^[[3~ appearing every time the key is pressed. (until the max length (8 hits) is exceeded.)
