[Hardy] Backlight low on Asus x57 laptop (M50sa)

Bug is related to kernel module asus_laptop.

By disabling it video brightness is set to maximum, fn+f5/fn+f6 controls don't work but other fn+fX contols work.
When on battery brightness is not reduced...

sudo su
echo 10 > /sys/devices/platform/asus-laptop/ls_level

Solves the issue. Issue is related to improperly set ls_level for light sensor on asus laptop.
Light sensor could be disabled by entering
echo 0 > /sys/devices/platform/asus-laptop/ls_switch

Unfortunately this must be done every restart.

I scripted it and added it to modprobe.d default level.

To have the fn+F5 and fn+F4 keys back working simply edit:
sudo gedit /usr/share/hotkey-setup/asus.hk and paste the following:

setkeycodes e005 $KEY_BRIGHTNESSDOWN # Brightness down button
setkeycodes e006 $KEY_BRIGHTNESSUP # Brightness up button
setkeycodes 6f $KEY_MUTE # Mute key
setkeycodes 6d $KEY_VOLUMEUP # Volume up
setkeycodes 6e $KEY_VOLUMEDOWN # Volume down
setkeycodes e007 $KEY_SWITCHVIDEOMODE # Fn+F7 (backlight on/off)
setkeycodes e00b $KEY_VIDEOOUT # Fn+F8 (display switch)

I have an M50Sv-A1 and have the same problem. I use these commands to get the display to where I want it.

cd /sys/devices/platform/asus-laptop

chmod 755 ls_level

chmod 755 ls_switch

echo "5" > ls_level

How can I put this into a script to run at Startup on my Ubuntu 8.08 machine?
Also, I can only run this when in root / sudo- how can I enter these commands without having to enter there? (Changing file permissions is denied otherwise)

Refers to this to create scripts:
http://bbs.archlinux.org/viewtopic.php?id=38935

To have the scripts starting at boot simply write:
$ update-rc.d YOURSCRIPT defaults

I have the same problem with my Asus M70. The fix given by Kame works, although the

setkeycodes e005 $KEY_BRIGHTNESSDOWN # Brightness down button
setkeycodes e006 $KEY_BRIGHTNESSUP # Brightness up button

buttons make the brightness meter show up and the progressbar moves, but the brightness doesn't actually change.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Sorry to report that it's not fixed in 8.10 alpha 5 release.
Actually, I can't even see a single thing on this laptop, since the video driver is not working (monitor seems out of sync).

Haven't try the alpha yet but with 2.6.26 kernel it's exactly the same.

@ Giacomo Magnini: I doubt ATi drivers will compile on 2.6.27 kernel right now.
(Serve pazienza con ATI... penso si arriverà ai catalyst 8.10 prima di un buon supporto col kernel 2.6.27)

Just installed Intrepid Ibex final and everything is still the same.

Seems to me that an year as passed and nothing was changed.

Gutsy was working flawlessy although... :(

identical problem with Asus z71vp.

I had to use a simlar script fix for either hardy or edgy, i don't recall which.

Knock Knock

Is anyone there.

I am in Intrepid now, kernel 2.6.27-8, everything is warking flawlessy but the brightness.

I had to put a script in default runlevel and map my keys as I have told before.
Unfortunatly it has been 4 month that the keys don't work.
I can see a nice applet showing that I am changing brightness but nothing is changing.

It has been 7 months now any solution yet?

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

This issue is still present in Ubuntu 9.10, Karmic Koala. I have implemented the following workaround on my system, which is a persistent version of that in update 4 above.

ian@dash:~$ cat /etc/modprobe.d/asus-backlight-workaround.conf
# Got this from Ubuntu bug 222171.
install asus-laptop /sbin/modprobe --ignore-install asus-laptop; sleep 2; echo 5 > /sys/devices/platform/asus_laptop/ls_level

This is a bug in the asus-laptop kernel module.

Guys, will this EVER be fixed?
After a recent Karmic update (you know, the usual update manager one) ambient sensor once more turned on, only this time no workarounds help. I will now try what Ian Turner suggested but it is really a bad bug which has been creating problems for people literally for years.
Is it really difficult to fix? Whom should this be reported to? I am ready to pay!

Ian, your fix did not work for me. I tried adding a savior line:
echo 0 > /sys/devices/platform/asus_laptop/ls_switch to shut down the sensor, but it also does not work.

Where can this bug be reported? All the devs should do is ONE thing - in devices/platforms/asus_laptop in file ls_switch there should be a 0 by default - and that's it. Years and years this cannot be done.

I;ve read the kernel wiki, it is tough. I can't understand where to report.

Okay, there were a couple of mistakes in mr. Turner's script.

ian@dash:~$ cat > /etc/modprobe.d/asus-backlight-workaround.conf
# Got this from Ubuntu bug 222171.
install asus_laptop /sbin/modprobe --ignore-install asus_laptop; sleep 2; echo 5 > /sys/devices/platform/asus_laptop/ls_level

I have an M51Vseries Asus, where I also made ls level 10, not 5 (full light) and also switched the ambient sensor completely off by adding this line to the above script.
echo 0 > /sys/devices/platform/asus_laptop/ls_switch

However, the funny thing about it is that while I was writing this message the screen suddenly went dim. For some reason the ambient sensor just turned on without warning, although yesterday I've worked for a long time and it was fine.

Something is definitely wrong with this module and, tbh, I am a bit tired of this problem.

Okay, so the script worked yesterday, but today the system ignores it and no matter what I write there - it does not do anything, so I have to turn off the light sensor manually each time.

The problem was in the new version of upstart, which made the system ignore init scripts at boot. By downgrading from upstart I was able to solve my problem.

Kame, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]