Bug 470455 - volume and brightness keys are not mapped - lenovo x61
Summary: volume and brightness keys are not mapped - lenovo x61
Keywords:
Status: CLOSED DUPLICATE of bug 468448
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: hal
Version: 5.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Richard Hughes
QA Contact: Vladimir Benes
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-07 09:58 UTC by Vladimir Benes
Modified: 2008-12-08 22:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-08 22:47:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Vladimir Benes 2008-11-07 09:58:48 UTC
Description of problem:
volume keys are not mapped, brightness keys are not working and wifi switch (computer with some waves around - but there is another hardware switch which works so this is minor fault) also .. everything else works fine (suspend, hibernate, screen-lock, ext display switch)

Version-Release number of selected component (if applicable):
0.5.8.1

How reproducible:


Steps to Reproduce:
1.press volume down/mute/volume up (the same with brightness buttons)

  
Actual results:
not mapped (volume), not working brightness

Expected results:
volume keys mapped, brightness could be increased/decreased

Additional info:

Comment 1 Vladimir Benes 2008-11-13 10:26:42 UTC
fyi: brightness is working and can be set by adjusting the /sys/class/backlight/thinkpad_screen/brightness flag (from 0 to 15)

Comment 4 Vladimir Benes 2008-11-18 13:31:16 UTC
After moving thinkapd_acpi to kernel/acpi directory brightness regulation is working just fine (because module is autoloaded).
Volume keys can be set up manually via preferences->keyboard shortcuts so I think we can close this bug as WONTFIX

Comment 5 Ben Levenson 2008-12-08 22:47:37 UTC

*** This bug has been marked as a duplicate of bug 468448 ***


Note You need to log in before you can comment on or make changes to this bug.