[ASUS UX305FA] Some Fn+ Keys Not Working

Bug #1458351 reported by Carlo Abelli
40
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Brightness control keys on my laptop not being recognized (including no output from acpi_listen). Running Ubuntu 14.04.2 LTS. Other function keys do work and are recognized ex. volume.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
Uname: Linux 3.16.0-38-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun May 24 12:59:49 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-05-23 (0 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 064e:9700 Suyin Corp.
 Bus 001 Device 002: ID 8087:0a2a Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX305FA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic.efi.signed root=UUID=246981b4-9b06-41f9-ac18-1e5ba27d4247 ro quiet splash acpi_osi=Linux vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/26/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX305FA.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX305FA
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.:bvrUX305FA.208:bd03/26/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX305FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sun May 24 12:07:13 2015
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 8493
 vendor AUO
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

Revision history for this message
Carlo Abelli (carloabelli) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Carlo Abelli, thank you for reporting this and helping make Ubuntu better. To see if this is already fixed in a later version of Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

tags: added: latest-bios-208
Changed in xorg (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Carlo Abelli (carloabelli) wrote :

After fresh install of 15.04 the problem persists. Seems to be same result for acpi_listen with no output appearing. Volume buttons and others still functional but no brightness function keys.

Revision history for this message
penalvch (penalvch) wrote :

Carlo Abelli, 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/Kernel/MainlineBuilds ? 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 by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

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: vivid
affects: xorg (Ubuntu) → linux (Ubuntu)
Revision history for this message
Carlo Abelli (carloabelli) wrote :

Tested with 4.1.0-040100rc6-generic #201506010235. Problem persists. Please let me know if there is anything else I can do!

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

Carlo Abelli, the issue you are reporting is an upstream one. Could you please report this problem to the appropriate mailing list (linux-input) by following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked via http://vger.kernel.org/vger-lists.html . It can take a day for the new e-mail to show up in the respective archive.

Thank you for your understanding.

summary: - Some Fn+ Keys Not Working
+ [ASUS UX305FA] Some Fn+ Keys Not Working
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Carlo Abelli (carloabelli) wrote :

Forgot to add a subject line but here is the thread:

http://www.spinics.net/lists/linux-input/msg38966.html

Revision history for this message
ishbalai (ishbalai) wrote :

Sounds like you have the same problem as me. (Asus UX501JW)

I was given a workaround from linux-input. It enables brightness keys and airplane key.

Set boot parameter to "acpi_osi="

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460088

Revision history for this message
Carlo Abelli (carloabelli) wrote :

I saw your report and I had tested this with my previous version 14.04 to no avail. It appears that in the new version 15.04 this option added to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub does enable the airplane mode button but the brightness controls still remain inactive (including using acpi_listen). Thank you for your suggestion though!

Revision history for this message
Carlo Abelli (carloabelli) wrote :

I will also mention that I have tried acpi_osi=Linux and acpi_backlight=vendor which both do nothing. In addition a side effect of acpi_osi= is that while it enables my airplane mode button it renders the brightness slider in System Settings useless so for now the tradeoff is not worth it as brightness control for me is more important.

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.