Support in other languages: 
Reply
Community Moderator
zoltanthegypsy
Posts: 2,470
Registered: ‎01-13-2008
Location: Bainbridge Island, WA, USA
0
Accepted Solution

X220 Keyboard partial malfunction (keyboard-combinations don't work)

Moderator Note: there's no way to mark a single/first post as "solved". I've moved belgam JesseCo's to 2nd postition so it can be tagged accordingly.

 

Thanks for the report.

 

Z.

R40 XP Pro + Linux + Solaris, T43 XP Pro + Linux + Solaris, T61 XP Pro + Win 7 + VMs, T400 Win 7 Pro 64 + too many VMs to count, New T420 - a work in progress ... GeezBlog

Blue Screen Again
JesseCo
Posts: 1
Registered: ‎05-06-2012
Location: Finland
0

X220 Keyboard partial malfunction (keyboard-combinations don't work)

[ Edited ]

Setup: I have an X220 on a docking station with a wireless Lenovo USB keyboard and mouse. The receiver is attached to the docking station. The system is running Windows 7 Enterprise

Problem:

  1. When Booting up the device today and reaching the ctrl+alt+del (windows login) -screen, the key-combination didn't work. Tried with the laptop keyboard and the wireless one. The mouse seemed to work on both.
  2. After a few reboots, the ctrl+alt+del worked and when windows started, it said the USB Input devices had their drivers installed.
  3. Now even though ctrl+alt+del works in the login screen, it doesn't do anything when logged in. Also The windows-key and alt+F4 have stopped working.
  4.  On one try, several attempts of ctrl+alt+del at the wireless keyboard also froze the laptop-keyboard.

This is really weird, since you can write with the keyboards just fine, the combinations just don't work. Well after the login screen anyway. And also that the issue is on both external and hardware-keyboards.

 

Everything is up to date and I tried unplugging everything, but no solution there. Nothing special has been done since last use when everything worked fine.

 

EDIT: Also checked the regional settings, everything ok there.

EDIT: Fixed, seems there was something in the keyboard that made it think the Ctrl-key was being pressed continuosly. This happened even though the button in itself seemed to work without issues (going up and down as they do) so maybe it was some kind of a contact-issue or trash between the button and the sensor.