[ASUS X200MA] Brightness keys do not work

Bug #1400068 reported by Pilot6
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Linux
Unknown
Unknown
linux (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Brightnes keys Fn+F5 and F6 do not work.

WORKAROUND: Add kernel boot parameter: acpi_osi=

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.16.0-25-generic 3.16.0-25.33~14.04.2
ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Dec 7 15:22:27 2014
InstallationDate: Installed on 2014-10-31 (37 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pilot6 1930 F.... pulseaudio
CurrentDesktop: Unity
CurrentDmesg:
 [ 35.096232] init: plymouth-upstart-bridge main process ended, respawning
 [ 41.464895] init: anacron main process (1153) killed by TERM signal
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=2f501090-6091-423c-abb1-a09f9c524fc3
InstallationDate: Installed on 2014-10-31 (38 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Lsusb:
 Bus 001 Device 005: ID 13d3:3408 IMC Networks
 Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
 Bus 001 Device 003: ID 0bda:5603 Realtek Semiconductor Corp.
 Bus 001 Device 002: ID 8087:07e6 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X200MA
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=8b0c6000-31d7-4e41-bfbf-4149ad0122d4 ro quiet splash acpi_osi= acpi.debug_layer=0x10000000 acpi.debug_level=4 vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-25-generic N/A
 linux-backports-modules-3.16.0-25-generic N/A
 linux-firmware 1.127.10
Tags: trusty
Uname: Linux 3.16.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X200MA.502
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X200MA
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.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X200MA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Pilot6 (hanipouspilot) wrote :
Revision history for this message
Pilot6 (hanipouspilot) wrote :
Revision history for this message
Pilot6 (hanipouspilot) wrote :

Here is the upstream patch
https://lkml.org/lkml/2014/12/7/42

Why apport-collect does not work against linux-lts-utopic?

Revision history for this message
penalvch (penalvch) wrote :

Pilot6, please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1400068

affects: linux-lts-utopic (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Pilot6 (hanipouspilot) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Pilot6 (hanipouspilot) wrote : BootDmesg.txt

apport information

Revision history for this message
Pilot6 (hanipouspilot) wrote : CRDA.txt

apport information

Revision history for this message
Pilot6 (hanipouspilot) wrote : IwConfig.txt

apport information

Revision history for this message
Pilot6 (hanipouspilot) wrote : Lspci.txt

apport information

Revision history for this message
Pilot6 (hanipouspilot) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Pilot6 (hanipouspilot) wrote : ProcEnviron.txt

apport information

Revision history for this message
Pilot6 (hanipouspilot) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Pilot6 (hanipouspilot) wrote : ProcModules.txt

apport information

Revision history for this message
Pilot6 (hanipouspilot) wrote : PulseList.txt

apport information

Revision history for this message
Pilot6 (hanipouspilot) wrote : RfKill.txt

apport information

Revision history for this message
Pilot6 (hanipouspilot) wrote : UdevDb.txt

apport information

Revision history for this message
Pilot6 (hanipouspilot) wrote : UdevLog.txt

apport information

Revision history for this message
Pilot6 (hanipouspilot) wrote : WifiSyslog.txt

apport information

Revision history for this message
penalvch (penalvch) wrote :

Pilot6, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to 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 exactly shown as:
kernel-fixed-upstream-3.18

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.

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

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.

tags: added: latest-bios-502
Revision history for this message
Pilot6 (hanipouspilot) wrote :

@Christop

The bug exists in 3.18.
See the kernel bug report.

https://bugzilla.kernel.org/show_bug.cgi?id=89401

tags: added: kernel-bug-exists-upstream-3.18
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Plot6, just to clarify, are you the original reporter (Dmitry Tunin) of https://bugzilla.kernel.org/show_bug.cgi?id=89401 ?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Pilot6 (hanipouspilot) wrote :

Yes, I am the original reporter. The problem is a bit complex.

My "acpi_osi=" solution used to work, until Aaron made that DOD commit.
Now the brightness keys do not create events at all in 3.18 kernel.

He needs to fix that first. Regarding Ubuntu kernel, the patch works.

You can see commits in my tiny fork.

https://github.com/hanipouspilot/ubuntu-fixes/tree/pilot6

Revision history for this message
Pilot6 (hanipouspilot) wrote :

@Christopher

And also it would be helpful for everyone if that commit

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/acpi/video.c?id=0b8db271f1592e118feef7300f6da85bea9366da

is not backported to Ubuntu, until the issue is fixed. Because now there is a workaround with "acpi_osi=" boot parameter for some Asus models, but after that it is competely blocked.

penalvch (penalvch)
description: updated
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Bagus Farisa (bagusfarisa) wrote :

In Ubuntu 15.10 the fn brightness key problem is still persistent.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.