No brightness for Fn keys on ASUS X555L.

Bug #1653559 reported by hotellina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Hi,

The FN keys Fn + F5 and Fn + F6 don't work for the brightness with any version of Ubuntu/Kubuntu/Lubuntu etc...

Even if I run acpi_listen the events are not detected at all.

Cheers,

Aldo

1)
john@john-X555LAB:~$ lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04
2) no clue about it.
3) Decrease the brightness by pressing Fn + F5 and increasing by Fn + F6
4) Same brightness, no difference after pressing the keys.
---
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: john 1706 F.... pulseaudio
 /dev/snd/controlC0: john 1706 F.... pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=30b021e6-b5af-4de8-af81-71108e2d8381
InstallationDate: Installed on 2016-12-28 (6 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
 Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp.
 Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X555LAB
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_IE:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_IE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=aa44a294-fde3-45eb-b84f-98b998f29eef ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-57-generic N/A
 linux-backports-modules-4.4.0-57-generic N/A
 linux-firmware 1.157.6
Tags: xenial
Uname: Linux 4.4.0-57-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 05/05/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X555LAB.601
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X555LAB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.601:bd05/05/2016:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X555LAB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 1653559

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
hotellina (hotellinaweb) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
hotellina (hotellinaweb) wrote : CRDA.txt

apport information

Revision history for this message
hotellina (hotellinaweb) wrote : CurrentDmesg.txt

apport information

Revision history for this message
hotellina (hotellinaweb) wrote : IwConfig.txt

apport information

Revision history for this message
hotellina (hotellinaweb) wrote : JournalErrors.txt

apport information

Revision history for this message
hotellina (hotellinaweb) wrote : Lspci.txt

apport information

Revision history for this message
hotellina (hotellinaweb) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
hotellina (hotellinaweb) wrote : ProcInterrupts.txt

apport information

Revision history for this message
hotellina (hotellinaweb) wrote : ProcModules.txt

apport information

Revision history for this message
hotellina (hotellinaweb) wrote : RfKill.txt

apport information

Revision history for this message
hotellina (hotellinaweb) wrote : UdevDb.txt

apport information

Revision history for this message
hotellina (hotellinaweb) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc2

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
hotellina (hotellinaweb) wrote :

Tried with the mainline kernel[0] v4.10-rc2 as suggested.
It fixed the problem, thanks a million.

Cheers,

hotellina

hotellina (hotellinaweb)
tags: added: kernel-fixed-upstream
removed: apport-collected xenial
tags: added: apport-collected xenial
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
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.