LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook
User Name
Password
Linux - Laptop and Netbook Having a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).

Notices

Reply
 
Search this Thread
Old 10-05-2007, 02:05 PM   #1
flsomerv
LQ Newbie
 
Registered: Jun 2007
Location: Chilhowie, VA
Distribution: Fedora 11 (2.6.30.9-96.fc11.i586)
Posts: 12

Rep: Reputation: 0
Question Laptop key press/release events question


On my new Dell Inspiron 1501, I dumped Windows Visa Home Premium and installed Fedora 7. Everything was working fine. I preformed some updates and installed some software (thunderbird, realplayer, etc.) and then I noticed some error messages when I shut down the system.

These messages show up in virtual consoles and during shutdown:

atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0).
atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.

These messages repeat over and over. I have also noticed that sometimes it is a different code. Sometimes it is e055 instead of e00d.

I can stop the error messages from happening via:

setkeycodes e00d 122

however, the events are still occuring. I can run xev from a terminal and see that the key press release errors are still happening. Not only are the events still happening, but they now interfere with things like the screensaver. If I activate the screensaver, it detects a key press after about 1 second and asks for the password. And if I wait for the screensaver to activate on its own, it never does activate because it is getting the key events.

I can fix the screensaver and everything is functional again with:

setkeycodes e00d 0

but this takes me back to the original situation of having the error messages constantly filling the logs. I don't use the text-based console that often, but with these messages popping up every second, it is hard to use the text console for anything. The other annoyance with these events is that the cpu light flashes each time the event occurs. Basically, my cpu light flashes once every second.

These events weren't happening at all when I first installed Fedora 7. I tried doing a fresh install of Fedora 7 to see if that would fix things, but it didn't. I saw the error messages as early as the inital stages of the anaconda installer.

My question is what is causing these key press/release events and how do I stop the event from happening?

Any help is greatly appreciated.
Thanks.

NOTE: This question is also posted on the Linux On Laptops forum, but I wasn't getting any responses there.
 
Old 10-07-2007, 12:52 PM   #2
osor
HCL Maintainer
 
Registered: Jan 2006
Distribution: (H)LFS, Gentoo
Posts: 2,450

Rep: Reputation: 70
Perhaps the problem can somehow be resolved in the BIOS. Did you change any BIOS settings when you noticed the problem? Another possible culprit is that your your software update messed up your keymaps. There are a few ways to remedy the situation from within fedora (as opposed to from within the BIOS):
  1. Reinstall or upgrade the kbd package.
  2. Add a few setkeycodes commands to the startup scripts (sometime after the keymaps have been loaded).
  3. Figure out what keymap is being loaded by your init scripts. Either change which keymap gets loaded, or edit the keymap file and add the relevant keycodes.
 
Old 10-08-2007, 10:59 AM   #3
flsomerv
LQ Newbie
 
Registered: Jun 2007
Location: Chilhowie, VA
Distribution: Fedora 11 (2.6.30.9-96.fc11.i586)
Posts: 12

Original Poster
Rep: Reputation: 0
Question choosing to not run syslog at startup?

Hello and thanks for the reply. I tried reinstalling the kbd package--no luck. I tried adding the setkeycodes commands to the /etc/rc.local file--no luck. I double checked the keymap that was getting loaded--no luck.

I tried doing an interactive startup and choosing to not load anything. When the desktop came up, my problem was gone--no key press/release messages, no events happening in xev, screensaver comes up fine. In fact, everything on my system seems to be working the way it should. So, for the next step, I went through the start up services one at a time and disabled one while starting the other usual services. It turns out that syslog is the one causing the problem. When I start my computer and don't start syslog, everything works.

My question now is: Is is OK or safe or acceptable to run my machine with syslog turned off?

Thanks.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
How to get key press and release events on kernel 2.6 for a application in C? abhijeet Programming 2 04-24-2007 12:37 AM
Key press Majestros Programming 2 02-14-2007 03:42 AM
Key press simulation in FC kiruxa Linux - General 1 11-24-2006 10:00 PM
scripting question press any key to continue Mr.McCormick Programming 3 02-04-2005 03:47 AM
latest M$ press release? or just illiterate boob? bulliver General 11 12-11-2002 02:51 PM


All times are GMT -5. The time now is 03:11 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration