My model m died and the terminal spare one doenst work 100%

[blubb]

Hello everyone,
first off: im really glad and amazed about how much nerdyness i found in this forum...

back to topic:
I killed my model m (chipset 1394079 and model 1386716) some days ago by spilling water in it. Since i was drunk that night, the keyboard remained wet & plugged for 1 whole night. Dry again some keys misbehaved (backspace typed +, etc)..

Since i had a spare model m 1394416 (terminal with rj45, chipset 1394073) i first tried just to switch chipsets/platinas (which didnt work for me), but went on to give the terminal model m a ps2 cable, which actually worked (was able to move up & down in grub)! here i followed the tutorial postet in this board...

Until now i unfortunately havent understood how to fix the software side, so my os recognizes the outputs of the keyboard (running both win7 and ubuntu 10.04).

So my first question is how to implement the http://www.kbdbabel.org/ keymappings into both ubuntu and windows 7 or how to get my terminal model m to work. If i would succeed i would have a fully operational model m again! (i really miss it when typing...)

second question:
Since my old model m is misbehaving when typing, i suspect that the contatcs/membranes beneath the plastic plate somehow dont work properly. Got smeared or corrodet, dunno.
Is opening the keyboard and cleaning the membranes gonna help ? (thinking of http://geekhack.org/showwiki.php?title=Island:12093)

I am looking foreward to hearing from you and am glad that i found such an awesome ressource.
greetings,
blubb.

[fohat.digs]

You can take the Model M completely apart, if you are willing to do a bolt mod to put it back together. There are several wikis here with great instructions. I like Sandy's. Be forewarned that you will have to order some very small screws. McMaster-Carr is the best source, in my opinion.

Pretty much everything can be separated and cleaned, and if you are lucky that will be it.

If contacts are corroded or scratched, you will have to do some sort of electrical repair.

There is a good chance that you will end up with something "better than new" but it will take a few hours at the kitchen sink and workbench.

[blubb]

I am more than willing to rescue my model m. I just wanted to hear what you think would be the cause for the problem i described...

keys misbehaves ("backspace" types "+" when prssed, etc)..

also, anyone who can help me along with the software issues ? -> point me to a wiki ? ive been reading some of the wikis describing how to get the sofwar running. unfortunately i dindt got how to do this in ubuntu... in windows its managed by some program, easy enough...

But thanks for the encouragement - im defenitely going to try to revive my good old model m

McMaster-Carr is the best source, in my opinion.

what would that be outside of the us ? ( i live in flensburg, northern germany)

[fohat.digs]

They would probably ship to you for very little, but I don't know for sure.

Seriously, an entire set of 50 nuts and bolts would fit in a teaspoon and weigh just a couple of grams.

[blubb]

probably, yes...

I still hope to hear something regarding the other two problems though.

[mich]

Terminal Ms have weird ID, speak scancode set 3 and don't send break codes by default.

If Linux completely ignores the board, you need to patch the kernel with proper ID (sorry, I still didn't get my lazy ass to send this upstream):

Code: [Select]

diff --git a/drivers/input/serio/libps2.c b/drivers/input/serio/libps2.c
index 07a8363..e2489fb 100644
--- a/drivers/input/serio/libps2.c
+++ b/drivers/input/serio/libps2.c
@@ -114,6 +114,7 @@ int ps2_is_keyboard_id(char id_byte)
                0x5d,   /* Trust keyboard               */
                0x60,   /* NMB SGI keyboard, translated */
                0x47,   /* NMB SGI keyboard             */
+               0xbf,   /* IBM terminal keyboards       */
        };
 
        return memchr(keyboard_ids, id_byte, sizeof(keyboard_ids)) != NULL;
To tell Linux to decode scancode set 3, add this to the kernel command line: i8042.direct=1 atkbd.set=3

To tell Linux to program the keyboard to send break codes, add also: atkbd.terminal=1

If you want key repetition generated in software (the keyboard doesn't do it by itself), add: atkbd.softrepeat=1
Note that this is meaningful only in VTs, X always repeats keys in software.


Windows requires special driver, available somewhere in wikis.

[blubb]

thx for the rply mich. unfortunately ive never touchd my kernel... is there any good tutorial on how to do this ?
some very scarce research suggests to add the cmds to grub... is that correct ?

also what do i do with the code you supplied ? feed it to the terminal ?

also: cant i "just" implement any of th scancodes provided by http://www.kbdbabel.org/ ?