Red Hat Bugzilla – Bug 435539
the special keys of my asus notebook don't work..
Last modified: 2008-10-20 17:25:26 EDT
i've an Asus A4K,
the multimedia keys don't work at all. i searched for a module or something, but
i found nothing useful by myself.
the same keys worked well with other linux version.
if i launch xev the pression of those keys produce no effect.
thanks for attention.
This isn't a keyutils problem. keyutils deals with encryption keys not
keyboard keys. I think this probably belongs to one of the Xorg components.
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Created attachment 296713 [details]
xorg.conf, i've to send you the log too...
Created attachment 296725 [details]
Can you please compile up evtest.c  and run it on your keyboard device (when the X server is not running). Then hit some of the multimedia keys and post the output here.
I would wager a guess that they keycodes are > 255, in which case the server will silently ignore it. The X Protocol doesn't support high keycodes.
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.
Closing as INSUFFICIENT_DATA.