need help to make IBM terminal 101 keys work under linux

[dd10]

Hi guys, here goes my first post.

I bought an IBM 1395162 terminal which comes in 101 keys and a rj45 as the connector a few days ago. This is my first model m and wow~~. I have already ordered teensy's usb converter but can't wait to use it on a daily basis. So I followed kishy's post to convert it to ps/2, which turned out great; it works in bios and even in windows xp.

Much to my surprise, I just couldn't make it work in lubuntu. I did some search and found this, and my /proc/cmdline currently looks like this:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic root=/dev/sda1 ro i8042.direct=1 atkbd.set=3 atkbd.terminal=1 atkbd.softrepeat=1
but still no luck.

I don't really think I need to patch libps2.c as the keyboard id is no long 0xbf... ...

Any help would be appreciated, thanks

[dd10]

Well, I've found out why it doesn't work. Somehow by default the keyboard is disable and once enabled, it works like a charm. I am replying this with my new model m. Yay~~~

*****************the above is not the reason why it doesn't work**************

turned out the problem is not being enabled at init, it has something to do with the scancode I guess, will post again once find out

[poxeclipse]

What exactly have you done ? I have the exact same keyboard as yours.

[mich]

What exactly have you done ? I have the exact same keyboard as yours.

I think you might have more luck sending this guy a PM, he hasn't posted here since June.

To debug it yourself, read this (and few posts ahead). Enable serio_raw, start hexdumping incoming data and send the reset command. The keyboad will respond with "aa" and a two byte ID. If the ID doesn't start with one of: ab, ac, 2b, 5d, 60, 47, Linux will be ignoring this keyboard until you patch libps2.

Code: [Select]

aa      # this should be "aa" if keyboard firmware booted successfully
bf      # my 122-key M's ID begins with "bf" so it doesn't work in Linux out of the box
be      # Linux ignores the second byte of ID
When you are at it, press few keys and use this table to find out which scancode set your keyboard uses (I expect 3, but maybe the 101-key ones use 2 instead). If you get "Set 3" or "X(Set 3)", you *must* have "i8042.direct=1 atkbd.set=3 atkbd.terminal=1" in your kernel command line. If you get "Set 2" or "X(Set 2)", you shouldn't have any of these options.

[poxeclipse]

What exactly have you done ? I have the exact same keyboard as yours.

I think you might have more luck sending this guy a PM, he hasn't posted here since June.

I need the pinout for RJ45, for this keyboard. I thought dd10 still might have it.
I have:
pin: 1            2             3        4       5          6         7        8
       Unused  Unused  Black  Red  Yellow  White  Black  Unused

Probably, he used the pinout shown by kishy.

[Soarer]

I need the pinout for RJ45, for this keyboard. I thought dd10 still might have it.
I have:
pin: 1            2             3        4       5          6         7        8
       Unused  Unused  Black  Red  Yellow  White  Black  Unused

Sounds like you need to add kbdbabel to your bookmarks  )

[poxeclipse]

Thank you guys.

[mich]

Yeah, this braindead coloring scheme "case ground - black, ground - white, 5V - black" is common for IBM.

[poxeclipse]

I installed a PS/2 cable, but nothing on Fedora 15. I don't have a Windows box to test.
I'm waiting now for the Teensy, I ordered 2 a few days ago.