Red Hat Bugzilla – Bug 702154
Brightness controls on Acer Timeline
Last modified: 2013-04-23 13:28:15 EDT
Created attachment 496933 [details]
Simple script to set the brightness on the Acer Timeline series
Description of problem:
Brightness controls (via Fn + [Left|Right] arrow keys) do not function as expected and backlight is held on full brightness, irrespective of gnome settings/physical controls
Version-Release number of selected component (if applicable):
Unknown, happy to discover under advice
Steps to Reproduce:
1. Try and set brightness via either function keys or gnome settings.
2. Observe the onscreen overlay show the changes and note that value in /sys/class/backlight/acpi_video0/brightness reflects the changes.
Brightness is held at maximum regardless of settings
Brightness to change in accordance with power settings & physical brightness controls.
I wrote a script to workaround this on Ubuntu and it can be found under 'Alternative Fix for 10.10' on https://help.ubuntu.com/community/AspireTimeline/Fixes.
Essentially I grepped the value set from the /sys fs and used it to set the value via setpci which was hooked into acpid.
I'd love to get a fix into the right place and am happy to work with someone to accomplish it via a Kernel module (I have developed these before for in-house projects) or tweaking the script to work on Fedora.
Is the acer-wmi driver loaded?
Yes it would seems so from an lsmod:
[nick@zeus ~]$ lsmod | grep wmi
acer_wmi 15532 0
sparse_keymap 2650 1 acer_wmi
rfkill 13096 5 bluetooth,acer_wmi,cfg80211
wmi 7722 1 acer_wmi
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
Is this still an issue with the 3.9 kernels in F19?
This bug is being closed with INSUFFICIENT_DATA as there has not been a
response in 2 weeks. If you are still experiencing this issue,
please reopen and attach the relevant data from the latest kernel you are
running and any data that might have been requested previously.