[Asus G53JW] Cannot change keyboard backlight brightness

[SonWon]

When pressing function key plus F3 or F4 the backlight on the keyboard does not change. This was working on a Ubuntu 13.10. No longer works in ubuntu 14.04.

---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: sonwon 2028 F.... pulseaudio
 /dev/snd/controlC1: sonwon 2028 F.... pulseaudio
 /dev/snd/controlC0: sonwon 2028 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=4d6d29f4-40a8-44cf-80ea-f0fd044e7f80
InstallationDate: Installed on 2014-06-08 (1 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
MachineType: ASUSTeK Computer Inc. G53JW
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=7eb10043-4463-42ac-bef7-723d8c108f94 ro quiet splash
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-29-generic N/A
 linux-backports-modules-3.13.0-29-generic N/A
 linux-firmware 1.127.2
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/28/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G53JW.211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G53JW
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG53JW.211:bd01/28/2011:svnASUSTeKComputerInc.:pnG53JW:pvr1.0:rvnASUSTeKComputerInc.:rnG53JW:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: G53JW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1327828

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[SonWon (sonwon-1)]

apport information

[SonWon (sonwon-1)]

apport information

[SonWon (sonwon-1)]

apport information

[SonWon (sonwon-1)]

apport information

[SonWon (sonwon-1)]

apport information

[SonWon (sonwon-1)]

apport information

[SonWon (sonwon-1)]

apport information

[SonWon (sonwon-1)]

apport information

[SonWon (sonwon-1)]

apport information

[SonWon (sonwon-1)]

apport information

[SonWon (sonwon-1)]

apport information

[SonWon (sonwon-1)]

apport information

[SonWon (sonwon-1)]

apport information

[SonWon (sonwon-1)]

apport information

[SonWon (sonwon-1)]

apport information

[SonWon (sonwon-1)]

apport information

[penalvch (penalvch)]

SonWon, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available (the one all the way at the top, and not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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-3.15

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.

[SonWon (sonwon-1)]

Could not complete kernel testing since the video card driver didn't like the new kernel.
The resolution was incorrect.
I am a nub and didn't know how to correct.
Going back to old kernel fixed the problem.
linux-image-3.15.0-031500-generic_3.15.0-031500.201406081435_amd64
linux-headers-3.15.0-031500-generic_3.15.0-031500.201406081435_amd64

I should add I had to do the following to fix the screen back light on 13.10 and 14.04:

1) Go to Nvidia settings and save config into xorg.conf (the file will be at /etc/X11)
2) In xorg.conf in the "Device" section for your GPU add (use sudo to edit with your favorite editor)
 Option "RegistryDwords" "EnableBrightnessControl=1"
3) restart X and brightness works or reboot

[SonWon (sonwon-1)]

I've been doing some investigation and have discovered the following. If I perform these commands the back-light changes:

echo 0 | sudo tee /sys/class/leds/asus::kbd_backlight/brightness
echo 1 | sudo tee /sys/class/leds/asus::kbd_backlight/brightness
echo 2 | sudo tee /sys/class/leds/asus::kbd_backlight/brightness
echo 3 | sudo tee /sys/class/leds/asus::kbd_backlight/brightness

Also there is a script called /etc/acpi/asus-keyboard-backlight.sh

I thought maybe this script wasn't being called and remapped the keys to the script and it still would not work. So I manually entered each script line and tested which worked fine accept I couldn't test this line:

if [ "$1" = down ]; then

I assume the $1 variable is only passed when called by the keyboard handler or is it possible this is the problem? How do I discover if this is being passed? How do I figured out if the script is even being called by the keyboard handler?

I have enough information now to make a workaround but would like to see this fixed in future versions.

[penalvch (penalvch)]

SonWon, you would need to uninstall the nvidia drivers first then test the mainline kernel.

[SonWon (sonwon-1)]

The fix for this issue is to change the keyboard scan codes in the asus-keyboard-backlight-down and asus-keyboard-backlight-up scripts located at /etc/acpi/events/ from:

event=hotkey ATKD 000000c5
event=hotkey ATKD 000000c4

To:

event=hotkey ATK0100:00 000000c5
event=hotkey ATK0100:00 000000c4

In there respective scripts.

And restart the acpi server,

sudo service acpid restart

I used acpi_listen to find the correct codes.

All thanks and credit goes to TOZ over at forum.xfce.org

Someone here needs to place this fix into the upstream.

[SonWon (sonwon-1)]

It is fixed, I posted the how to in the bug report. How does it get moved
into production so it says fixed?

On Sun, Jun 15, 2014 at 11:01 AM, Christopher M. Penalver <
<email address hidden>> wrote:

> SonWon, you would need to uninstall the nvidia drivers first then test
> the mainline kernel.
>
> ** Tags added: needs-upstream-testing
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1327828
>
> Title:
> [Asus G53JW] Cannot change keyboard backlight brightness
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> When pressing function key plus F3 or F4 the backlight on the keyboard
> does not change. This was working on a Ubuntu 13.10. No longer works
> in ubuntu 14.04.
>
> ---
> ApportVersion: 2.14.1-0ubuntu3.2
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC2: sonwon 2028 F.... pulseaudio
> /dev/snd/controlC1: sonwon 2028 F.... pulseaudio
> /dev/snd/controlC0: sonwon 2028 F.... pulseaudio
> CurrentDesktop: XFCE
> DistroRelease: Ubuntu 14.04
> HibernationDevice: RESUME=UUID=4d6d29f4-40a8-44cf-80ea-f0fd044e7f80
> InstallationDate: Installed on 2014-06-08 (1 days ago)
> InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64
> (20140416.2)
> MachineType: ASUSTeK Computer Inc. G53JW
> NonfreeKernelModules: nvidia
> Package: linux (not installed)
> ProcFB:
>
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic
> root=UUID=7eb10043-4463-42ac-bef7-723d8c108f94 ro quiet splash
> ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
> RelatedPackageVersions:
> linux-restricted-modules-3.13.0-29-generic N/A
> linux-backports-modules-3.13.0-29-generic N/A
> linux-firmware 1.127.2
> Tags: trusty
> Uname: Linux 3.13.0-29-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> _MarkForUpload: True
> dmi.bios.date: 01/28/2011
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: G53JW.211
> dmi.board.asset.tag: ATN12345678901234567
> dmi.board.name: G53JW
> dmi.board.vendor: ASUSTeK Computer Inc.
> dmi.board.version: 1.0
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: ASUSTeK Computer Inc.
> dmi.chassis.version: 1.0
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrG53JW.211:bd01/28/2011:svnASUSTeKComputerInc.:pnG53JW:pvr1.0:rvnASUSTeKComputerInc.:rnG53JW:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
> dmi.product.name: G53JW
> dmi.product.version: 1.0
> dmi.sys.vendor: ASUSTeK Computer Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327828/+subscriptions
>

[Launchpad Janitor (janitor)]

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

[SonWon (sonwon-1)]

Well this is disappointing, I don't have much hope this gets moved into production, sigh.