[SOLVED] atkbd spamming the logs, stating unknown key
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Since the recent -current updates, I've noticed a few issues in my /var/log/{syslog,messages}. System is Slackware64-current multilib, 3.18.11 kernel, ZaReason Strata 7440 laptop. This was not a problem prior to the update.
The log spamming did not exist before the update. I am assuming all I need to do is assign the key on my keyboard to the operation. The weird thing is that KDE seems to be adjusting the screen brightness just fine though. My main concern is that my logs are being spammed constantly when I change the screen brightness.
Not really sure about how to fix this since I've found many different solutions after searching LQ and google.
This is what shows up when I press the brightness keys.
Code:
Aug 11 20:24:00 mothership kernel: [ 2102.120830] atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0).
Aug 11 20:24:00 mothership kernel: [ 2102.120840] atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.
Aug 11 20:24:00 mothership kernel: [ 2102.266520] atkbd serio0: Unknown key released (translated set 2, code 0xf8 on isa0060/serio0).
Aug 11 20:24:00 mothership kernel: [ 2102.266524] atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.
Aug 11 20:24:01 mothership kernel: [ 2102.823543] atkbd serio0: Unknown key pressed (translated set 2, code 0xf7 on isa0060/serio0).
Aug 11 20:24:01 mothership kernel: [ 2102.823547] atkbd serio0: Use 'setkeycodes e077 <keycode>' to make it known.
Aug 11 20:24:01 mothership kernel: [ 2102.937668] atkbd serio0: Unknown key released (translated set 2, code 0xf7 on isa0060/serio0).
Aug 11 20:24:01 mothership kernel: [ 2102.937673] atkbd serio0: Use 'setkeycodes e077 <keycode>' to make it known.
This is what shows up right after I let go of the brightness keys.
Code:
Aug 11 20:14:12 mothership root: ACPI group video / action brightnessdown is not defined
Aug 11 20:14:13 mothership root: ACPI group video / action brightnessup is not defined
Aug 11 20:14:13 mothership root: ACPI group video / action brightnessdown is not defined
Aug 11 20:14:15 mothership last message repeated 3 times
Aug 11 20:17:58 mothership root: ACPI group video / action brightnessdown is not defined
Aug 11 20:17:59 mothership root: ACPI group video / action brightnessup is not defined
Aug 11 20:23:38 mothership root: ACPI group video / action brightnessup is not defined
Aug 11 20:23:39 mothership root: ACPI group video / action brightnessdown is not defined
Aug 11 20:24:00 mothership root: ACPI group video / action brightnessup is not defined
Aug 11 20:24:01 mothership root: ACPI group video / action brightnessdown is not defined
I had the same problem in an old Dell laptop, but the actual code appearing in the logs was different. In my case, similar to what was answered in the askubuntu site, it was solved by replacing the battery.
If the messages appear only when pressing the keys, I'd just ignore it In my case I had 6-8 messages appearing every second, and that was not only filling the logs but also causing me to lose "real" messages in all the noise.
If the "action" is not defined, as the logs say, maybe your problem can be solved by creating a handler for it, as described here https://wiki.archlinux.org/index.php/Acpid
I had the same problem in an old Dell laptop, but the actual code appearing in the logs was different. In my case, similar to what was answered in the askubuntu site, it was solved by replacing the battery.
If the messages appear only when pressing the keys, I'd just ignore it In my case I had 6-8 messages appearing every second, and that was not only filling the logs but also causing me to lose "real" messages in all the noise.
If the "action" is not defined, as the logs say, maybe your problem can be solved by creating a handler for it, as described here https://wiki.archlinux.org/index.php/Acpid
I am pretty close to just saying "screw it" and leaving it be. It isn't spamming my logs unless I press the keys. Which leads me to believe the problem is that I do not have a handler for ACPI. In addition, I found this after looking into the logs further up and noticing the words "No Handler." It seems like I have a bit of research to do if I want to fix this.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
In my case I had 6-8 messages appearing every second, and that was not only filling the logs but also causing me to lose "real" messages in all the noise.
