VOGONS


First post, by wkjagt

User metadata
Rank Newbie
Rank
Newbie

Hey all. I recently got a WASD Code keyboard, which is one of the few TKL mechanical keyboards that still support PS/2. I have it connected to my P5A-B motherboard using the regular 5-pin keyboard port through a passive USB to PS/2 adapter and then a PS/2 to AT style plug connector. The problem is that on first boot (after turning the PC on) the keyboard doesn't work. The backlight turns off and on, and for some reason I can bypass the memory check during POST by pressing ESC. When I press a key, the backlight turns off. After booting, the keyboard doesn't work, and the backlight stays off. When I unplug and replug the keyboard however, it starts working perfectly, and continues to work perfectly. When I reboot without turning the computer off, the keyboard continues to work fine.

At first I thought it might be a power problem, with the backlight taking too much power, but I turned it off, and tested again, and still the same problem. Also, it works fine with the backlight turned on after plugging the keyboard back in.

Regular PS/2 keyboards work totally fine with this setup by the way.

Does anyone have an idea what might be going on?

Stay at home dad playing around with 286-486. Programming C and assembly. Repairing old stuff.

Reply 1 of 10, by rasz_pl

User metadata
Rank l33t
Rank
l33t

measure 5V rail instead of guessing
this video might be helpful if you have a scope https://hackaday.com/2023/02/07/connecting-a- … t-the-hard-way/

Open Source AT&T Globalyst/NCR/FIC 486-GAC-2 proprietary Cache Module reproduction

Reply 2 of 10, by bogdanpaulb

User metadata
Rank Member
Rank
Member

What tipe of psu are you using AT or ATX ? If it is a ATX psu check how the jumper for power of the keyboard is set up ( you have 2 pos: 1. is taking power from the 5v main rail 2. power from the 5V standby rail (this one can't supply a lot of power/amps and in cheap psu's is poorly regulated). It should be near the keyboard connector.

Reply 3 of 10, by wkjagt

User metadata
Rank Newbie
Rank
Newbie

I am using an AT power supply, which might be getting flaky. It's one of those really old ones, with the power switch on the side. I liked the case it was in, but it doesn't have a power button on the front, so I can't change the PSU for a newer one. I might have to use a different case / power supply. I do have a vague memory of trying out the motherboard with an ATX power supply and it didn't work (or at least, it didn't react to shorting the power button pins on the motherboard). But starting by measuring the 5V is a good idea, and will be my next step. I do have a scope, so I'll also check what is going on with the signals.

I didn't even know there was a jumper for the keyboard power! Very interesting.

Stay at home dad playing around with 286-486. Programming C and assembly. Repairing old stuff.

Reply 4 of 10, by wkjagt

User metadata
Rank Newbie
Rank
Newbie

Quick observation (I haven't measured anything yet), but I just discovered the keyboard clock speed in the BIOS settings, which can be set to 8mhz, 12mhz or 16mhz. When I set the clock to 16mhz, the keyboard works fine, _except_ that it gives a keyboard error during POST. When I press F1 to continue, it's ok after that. Not ideal, but a step closer, and maybe another hint as to what is going on.

Stay at home dad playing around with 286-486. Programming C and assembly. Repairing old stuff.

Reply 5 of 10, by bogdanpaulb

User metadata
Rank Member
Rank
Member

I don't know what keyboard clocks your new keyboard supports , but usually 8 mhz should be just fine. You have the jumper in the pic, If you use a AT power supply it should be on the 2-3 pos (disabled).

Attachments

  • VUeEnY7.jpg
    Filename
    VUeEnY7.jpg
    File size
    1.14 MiB
    Views
    457 views
    File license
    Fair use/fair dealing exception

Reply 6 of 10, by rasz_pl

User metadata
Rank l33t
Rank
l33t
wkjagt wrote on 2023-02-17, 21:51:

Quick observation (I haven't measured anything yet), but I just discovered the keyboard clock speed in the BIOS settings, which can be set to 8mhz, 12mhz or 16mhz. When I set the clock to 16mhz, the keyboard works fine, _except_ that it gives a keyboard error during POST. When I press F1 to continue, it's ok after that. Not ideal, but a step closer, and maybe another hint as to what is going on.

this clock setting is for _keyboard Controller_, not the keyboard itself, and Im very surprised it exists in the bios of P5A-B at all as that board doesnt have external keyboard controller chip - its all integrated into ALi M1533 South Bridge https://bitsavers.org/components/ali/M1541_M1 … orth_Bridge.pdf

Open Source AT&T Globalyst/NCR/FIC 486-GAC-2 proprietary Cache Module reproduction

Reply 7 of 10, by bogdanpaulb

User metadata
Rank Member
Rank
Member

I knew that was the speed for the keyboard controller and that 8 mhz should fine (that is the later adopted ISA bus clock ) but somehow i was always under the impression that when you change the MCU/keyboard controller clock that signal is somehow tied to the keyboard clock also. You learn new things all the time. Thank you.

Last edited by bogdanpaulb on 2023-02-18, 10:37. Edited 1 time in total.

Reply 9 of 10, by wkjagt

User metadata
Rank Newbie
Rank
Newbie

I tried with a different power supply, but that gives the same problematic behaviour.

I just tested this same keyboard on my 486, and it works totally perfect, no problems at all. So the problem seems to be with the P5A-B, or the combination of the motherboard and the keyboard.

By the way, this is the same motherboard I have another problem with (described in PC "waits" for 15 seconds on boot). That problem disappeared while I was trying to figure it out, but since came back. These two problems may even be related. I am saying that because during that 15 second or so pause (as described in the linked post), the keyboard seems to turn itself off (or the PC sends a command to disable it?) or at least, that is when the backlight turns off.

Next step will be measuring voltages (instead of guessing). And I was thinking hooking up an Arduino in parallel with the keyboard and use the PS/2 keyboard library to see if I can see what scan codes and commands are being sent between the motherboard and the keyboard, and see if maybe that could give some hints. If that works, it'll be easier than interpreting clock and data pulses on an oscilloscope.

Stay at home dad playing around with 286-486. Programming C and assembly. Repairing old stuff.

Reply 10 of 10, by wkjagt

User metadata
Rank Newbie
Rank
Newbie
Doornkaat wrote on 2023-02-18, 07:12:

Have you contacted the keyboard manufacturer's support about this issue?

Nope, but good idea! Although in modern keyboards, PS/2 support seems to be implemented for a completely different use case (NKRO) than mine.

Stay at home dad playing around with 286-486. Programming C and assembly. Repairing old stuff.