Weird problem - Enter/Backspace key not working

[SHoTTa35]

Ok, so i got this T42P. The original keyboard that came with it is starting to show it's age, some keys gotta press a bit harder and all that. So i called IBM and got a brand new NMB keyboard (along with some other parts).

Problem is the Enter, Backspace , Spacebarand seems other keys, F10 for sure doesn't work. I called and got another keyboard (NMB) and the same keys doesn't work with that either. The first time i just thought the keyboard was bad, but the second one came and it's the same exact keys. All the other keys work just fine.

This is in the BIOS area as well as Windows. Anyone got any ideas? Just incase you were wondering, the OLD keyboard works fine still, i don't have another T4x system to test the keyboard but i'm almost positive it's not it.

[yak]

You should check the keyboard connector on the system board. Maybe there's some dirt or another reason to break the contact. Just my thoughts, haven't seen such a problem yet.

[SHoTTa35]

i thought of that. I used compressed air cans and blow them out and i also blew off the keyboard's connector too. The funny part is that as soon as i plug in the old one, even WITHOUT rebooting it works right away. I plug the old one in and put in the new one (with windows still running but it doesn't matter if i shut down 100% either) and it doesn't work again.

Does it matter that one seems to be Chicony and the new ones are NMB? I wouldn't think so but it's weird that both new keyboards are NMB (blue rubber under keys) and the old one being Chicony (white rubber) works just fine.

FRU - 39T0643 for the new one.

[Robbyrobot]

This is interesting because I have a similar problem with an A20p I'm working on. Several keys, including F1, F2, F8, F9, Ins, Del, PgUp and Fn are dead, and this applies to two different (internal) keyboards I've tried - as in your case, always the same keys. In contrast, all the keys on an external keyboard (attached via port replicator) work fine. I'm still trying to figure out why this is, and also presume there's some problem with the internal keyboard connection, but have no conclusions as yet.