LinuxQuestions.org - Scancode Error

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - Scancode Error (https://www.linuxquestions.org/questions/debian-26/scancode-error-450394/)

Not sure if this would belong in the Hardware section or here...but I'm putting it in both places (my apologies in advance Mods)

Hi guys,
I just installed Debian on my machine. I am using a MS wireless keyboard and mouse. I'm not interested in the "fancy" buttons (I can't stand those things).

My issue is I'm getting an error at random times (I'm sure if I timed it its at a particular frequency) at the console. The error is:

Code:

keyboard: unknown scancode e0 01

I can hit ANY key and will get a similar error to the one above. Enter, any letter key, any number. I can type for a few seconds, then the error comes up. Its REALLY annoying. The odd thing is this never happened during the installation process. If I can get it to work like it did when it was installing, that would be great.

I've read about these errors, but usually they're in log files...not popping up constantly on the screen. I'd be happy if I can get them to log to a file and not my screen :)

The keyboard and mouse are USB, but I use the USB to PS/2 adapter for the mouse.

Any help would be really appreciated.

Thanks
:newbie:

In general you can redirect from standard output (your screen) to a file with the >> switch. Usage like: [commandname+options] >> {filename with extension} As extension the .txt (plain textfile) is quite suitable. Open the textfile (located in the current directory) with the editor you prefer. If you want to redirect the output to a specific directory, specify the full path, like "/home/<user>/temp" or where-ever you want.

Quote:

Originally Posted by Dutch Master

Thanks Dutch Master, I'm going to ask a really ignorant question now (please forgive my new-ness).....what would the " commandname+options " be for my situation?

Good question... I'm not familiar with wireless keyboards, but errors should appear in the output of the dmesg command. No garantees, but you might want to try the following commands, all done as root:

Code:

dmesg >> dmesg.txt

cat /var/log/messages >> messages.txt

chmod 644 dmesg.txt messages.txt

The last step allows you to access these files as normal (non-root) user. Again: I don't know what exactly you'll need to look for, but it's a start... ;)

Thanks DM!

Here's what I did....

Code:

dmesg -n 1

I researched your suggestion (the dmesg), and found this (excerpt from here )

Set the level at which logging of messages is done to the console. For example, -n 1 prevents all messages, expect panic messages, from appearing on the console. All levels of messages are still written to /proc/kmsg, so syslogd(8) can still be used to control exactly where kernel messages appear. When the -n option is used, dmesg will not print or clear the kernel ring buffer.

Granted, this doesn't cure the problem (the keyboard sending the error...but I really don't mind it since its not popping up in my face)

Thanks again!! :)

Please do not post the same thread in more than one forum. Picking the most relevant forum and posting it once there makes it easier for other members to help you and keeps the discussion all in one place.

http://www.linuxquestions.org/rules.php