[...]
The only thing is, and I'm not certain whether I'm alone in this problem, or whether this is a standard glitch: the ctrl and alt combination doesn't register. Left ctrl and alt fire individually, but not together.
I'm connecting the keyboard via an adapter that I got from Ebay, it looks like the ones I've seen touted as working.
[...]
I wonder if anyone else has had this problem?
One the plus side, the keyboard is close to fantastic: but I'm a programmer for a living and need the ctrl_alt combo working.
Best wishes from UK!
Paul
I don't have the problem.
I have an IBM Model M made in 1995 by lexmark. Its model number is 82G2384 (the same as 82G2383 but with spanish ISO layout (though I prefer ANSI layout, this is the one I could find)). It is a buckling spring KB, has removeable keycaps, drainage channels, non-detachable PS/2 cable, blue label, and the speaker holes at the bottom.
Though I can connect it directly to PS/2 in my motherboard, I choose to connect it through a USB adapter so that I don't have to worry about plugging in the PS/2 port while the computer is ON.
I tried a terrible adapter before I found the one in the attached images. My previous adapter would drop keystrokes and suddenly repeat keys too.
The one I'm using works perfectly.
I have several shortcuts on CTRL+ALT and I just retested them and they work with both the left side keys and the right side CTRL+ALT keys.
Such as CTRL+ALT+M to mute, up/down arrows to increase decrease volume, CTRL+ALT+L to lock the screen, CTRL+ALT+K to switch between Dvorak and qwerty (qwerty only used for guests :-) ).
Linux reports that my USB converter requests 400mA of max current (doesn't mean it uses the full 400mA all the time, just that it is the max).
With 'lsusb -v' I see the following:
# lsusb -v
[.... other devices ....]
Bus 003 Device 018: ID 13ba:0018 PCPlay Barcode PCP-BCG4209
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x13ba PCPlay
idProduct 0x0018 Barcode PCP-BCG4209
bcdDevice 0.01
iManufacturer 0
iProduct 1
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 59
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 400mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
[...]
Note the line where it says:
MaxPower 400mA
The VID:PID of the converter I'm using is this, as seen above: 13ba:0018 (you might find it branded differently, but with that same chip, by VID:PID).
For some reason, the converter description says Bar Code Reader. I guess it makes sense since the bar code readers actually input the code as keystrokes to the computer. Someone was lazy not updating the description of the device for that chip. But it works wonderfully, and requests the 400mA from the USB port (more than enough for the IBM Model M).
My previous converter was reported to only request 100mA of current from USB, which might have been causing it to reset and eat keypresses and keyreleases.
I have also attached a picture of a spare converter still in the blister, maybe you can find it by the picture.
ALSO, first and foremost: have you tried connecting the keyboard directly to a PS/2 port on a desktop PC that has it? Even new some ones have it. My gigabyte motherboard came out in 2013 and still has a PS/2 port.
I hope this was of some help,
anything to help a fellow programmer,
Cheers!!
.KeyHopper.