Posts Tagged RedHat
kernel atkbd.c: Unknown key released messages on Linux
Posted by MB in Uncategorized on April 24, 2011
I just installed Ubuntu 10.10 (Maverick Meerkat) on to a Dell Vostro 1000. (Yea, yea, I know Natty is just around the corner). During the installation I dropped the terminal box down — ‘cus I’m like that — and noticed the following messages spamming the terminal log:
Apr 20 14:17:59 Vostro-1000 kernel: [ 2.814838] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). Apr 20 14:17:59 Vostro-1000 kernel: [ 2.814844] atkbd serio0: Use 'setkeycodes e00d ' to make it known.
Unplugging the laptop’s AC adapter caused it to throw the same event, this time with code e06e.
After some research, it looks like various model laptops throw odd keycodes in response to AC adapter/battery events. The Dell Vostro 1000 seems to be the one that comes up the most in searches, but the Dell Latitude 131L (which is based on the same design / hardware) is mentioned in Launchpad bug #549741, which is specific to this issue. The Inspiron 1501 is mentioned in Redhat bug #454131.
There’s also the issue of the specific keycodes that are thrown. Myself, I saw e00d and e06e. The author at DezzaNet mentions e055 as well.
So how to get rid of these messages?
The two bug reports referenced above mention removing and replacing the battery while the system is on. However, that may not work in all cases. There’s another way to get rid of the messages, and that’s mapping the keycode to the NULL character.
To do this at every bootup, edit the /etc/rc.local file and add lines like the following above the exit 0 statement:
setkeycodes 255
For example:
setkeycodes e00d 255
Repeat for each keycode you will to null out.
Questions, comments, feedback regarding this? Feel free to share in the comments below. Thank you!
Logitech Devices on Ubuntu Linux (and others)
Posted by MB in Uncategorized on June 27, 2010
A friend presented me with an issue a while back where certain buttons on his Logitech keyboard, specifically the zoom bar, didn’t work properly under Ubuntu. After some searching, I found a site that codes Linux drivers for these devices, and directed him to it. They have drivers for Debian, CentOS, Fedora, Mandriva, Mint, RedHat, Suse, and Ubuntu. The full list of supported devices is below.
After testing, he came up with a set of instructions (originally posted at another site) and I have rewritten them here in a [hopefully] more accurate process.
- Head over to HIDPoint
- Fill in the requested information on the download page (mouse/keyboard/OS/etc…), you can ignore the email field if you wish and select download. Make sure you select correctly if you’re using a 64-bit or non-64-bit OS.
- On the next screen, select the link “Download Now“, and save the file to your hard drive.
- Navigate to wherever you downloaded the file to.
- Right click on the file, and go to Properties > Permissions and check the box for execute.
- Double click on the file and select “Run In Terminal“. Type “Y” then hit “Enter”.
- Follow all on screen prompts.
- After Installation is complete, you will need to reboot.
Supported devices:
| Keyboards: | Mice: | Mice: |
|
|
|
Bug in Fedora : Cannot change number of workspaces via workspace switcher properties
Posted by MB in Uncategorized on February 26, 2010
This occurs when Compiz is enabled — you need to change the number of desktops through the Compiz Config Settings Manager (CCSM)
Bug : https://bugzilla.redhat.com/show_bug.cgi?id=481275
To work around the issue, install ‘ccsm’, then under System->Preferences->Look
& Feel choose “CompizConfig Settings Manager”. In the new window choose
“General Options” and from the tab list choose “Desktop Size” and change the
top slider to how many workspaces you need. This may not change the number of
workspaces immediately – you may need to log out and log in again.
