8086:0116 [Lenovo IdeaPad Z570] LCD brightness control keys and widget do not work on Intel Graphics

[Shriramana Sharma]

After upgrading to Saucy, on my Lenovo IdeaPad Z570 with Intel HD Graphics 3000, it is no longer possible to control the LCD brightness using the hardware brightness control keys. Likewise for the KDE power management settings or the battery icon on my Kubuntu Plasma tray. (I don't use GNOME/Unity.) Until Raring I did not have this problem.

WORKAROUND: At a terminal:
echo 150 | sudo tee /sys/class/backlight/intel_backlight/brightness

where 150 is on the scale of 0 to whatever is given within /sys/class/backlight/intel_backlight/max_brightness. Based on this I wrote a GUI which however needs to be run using sudo/kdesudo/gksudo. I have attached it.

---
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
DistroRelease: Ubuntu 13.10
InstallationDate: Installed on 2013-10-19 (38 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
Package: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Tags: saucy
Uname: Linux 3.11.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
---
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: samjnaa 1717 F.... pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=ba00d992-e43e-4bce-8689-9647370add15
InstallationDate: Installed on 2013-10-19 (117 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: LENOVO HuronRiver Platform
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=(hd0,msdos9)/vmlinuz root=/dev/sda9 ro quiet splash
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-15-generic N/A
 linux-backports-modules-3.11.0-15-generic N/A
 linux-firmware 1.116
StagingDrivers: rts5139
Tags: saucy staging
Uname: Linux 3.11.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 02/22/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 45CN28WW
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Emerald Lake
dmi.board.vendor: LENOVO
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnLENOVO:bvr45CN28WW:bd02/22/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
dmi.product.name: HuronRiver Platform
dmi.product.version: Ideapad Z570
dmi.sys.vendor: LENOVO

[N1ck 7h0m4d4k15 (nicktux)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:

apport-collect 1255428

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

This is a known problem. Please see here on how to debugging blacklight:
https://wiki.ubuntu.com/Kernel/Debugging/Backlight

Your slider works for me also :-)

Here is a thread on ubuntuforums.org . See another workaround related to ACPI events.
http://ubuntuforums.org/showthread.php?t=2156192&p=12701188#post12701188

Best Regards
    NikTh

[Shriramana Sharma (jamadagni)]

Hi thanks for your feedback [esp re my slider ;-)].

I tried doing what you asked but I got the following errors:

Traceback (most recent call last):
  File "/usr/share/apport/apport-kde", line 522, in <module>
    sys.exit(UserInterface.run_argv())
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 656, in run_argv
    return self.run_update_report()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 540, in run_update_report
    apport.packaging.get_version(p)
  File "/usr/lib/python2.7/dist-packages/apport/packaging_impl.py", line 120, in get_version
    pkg = self._apt_pkg(package)
  File "/usr/lib/python2.7/dist-packages/apport/packaging_impl.py", line 113, in _apt_pkg
    return self._cache()[package]
  File "/usr/lib/python2.7/dist-packages/apport/packaging_impl.py", line 81, in _cache
    self._apt_cache = apt.Cache(progress, rootdir='/')
  File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 101, in __init__
    self._check_and_create_required_dirs(rootdir)
  File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 131, in _check_and_create_required_dirs
    open(rootdir + f, "w").close()
IOError: [Errno 13] Permission denied: '//etc/apt/sources.list'

Note that I do not have a /etc/apt/sources.list on my system since I put in individual .list for my local repos, my preferred net repos etc files under /etc/apt/sources.list.d/.

Please tell me how to go ahead. Do you want me to temporarily rename one of them to /etc/apt/sources.list?

[N1ck 7h0m4d4k15 (nicktux)]

Probably apport expects the /etc/apt/sources.list file to exist. I would suggest to create one and try again.
Also it would be a good idea to open a new bug about this behavior of apport and see what developers have to say.

Best Regards
    NikTh

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[penalvch (penalvch)]

Shriramana Sharma, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, 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 (not the daily folder, but the one at the top) 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-v3.13-rc4

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.

[Shriramana Sharma (jamadagni)]

Hello Christopher. Sorry for the delay. I am having problems downloading the daily images but I trusted with Alpha 2, and the bug persists there.

And I did not test the mainline kernels since as noted earlier, even with the Saucy kernel, if we directly write to /sys/class/backlight/intel_backlight/brightness then the brightness does change, so even the default Saucy kernel is clearly capable of telling the hardware to change its brightness.

The problem lies probably in that the GUI as in the power management applet popup and the keyboard hook which should handle the pressing of the physical brightness keys on keyboard are somehow not able to modify the /sys/class/backlight/* file or so.

With the existing setup, I have having to sudo to modify the /sys/class/* file, so perhaps the process running the GUI popup or the keyboard hook does not have the relevant permissions to change the /sys/class/* file.

[penalvch (penalvch)]

Shriramana Sharma, please execute the following in a terminal:
apport-collect 1255428

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

apport information

[Shriramana Sharma (jamadagni)]

Hello Christopher. I did the update just now and nothing has changed. Here's the output you asked for:

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
45CN38WW
10/21/2011

BTW as I already mentioned, I wonder if you are looking for the problem in the wrong place. I filed this bug against the kernel since I did not know where exactly else to file it and the hardware hotkey is not working.

But as I said, if I manually adjust the contents of /sys/class/backlight/intel_backlight/brightness the actual display brightness does change.

The problem is only that I am not able to change the brightness via the keyboard hotkey as well as the power applet.

[taj (othertaj)]

I also have Intel graphics in a HP laptop

This fix also works in 14.04:
http://askubuntu.com/questions/362894/changing-the-brightness-stopped-working-in-13-10-saucy-salamander

If you're using intel video card do:

sudo gedit /usr/share/X11/xorg.conf.d/20-intel.conf

Add the following in the empty file then log out and log in again or reboot. That should fix your problem.

Section "Device"
    Identifier "card0"
    Driver "intel"
    Option "Backlight" "intel_backlight"
    BusID "PCI:0:2:0"

EndSection

Thanks Tatakai Wasumi for that solution!

[penalvch (penalvch)]

taj, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[penalvch (penalvch)]

Shriramana Sharma, could you please test the latest upstream kernel available (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-rc1

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.

[Shriramana Sharma (jamadagni)]

Hello. Sorry for the delay. I've now installed Trusty and the problem persists. However the solution provided by http://askubuntu.com/a/395442/170127 works. (The command line option detailed at http://askubuntu.com/a/382833/170127 works as well.)

[penalvch (penalvch)]

Pending https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255428/comments/31 .

[Launchpad Janitor (janitor)]

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

[Shriramana Sharma (jamadagni)]

Hello. I downloaded the latest kernel 4.1.1 for the Trusty LTS that I am using and even there the behaviour is the same. Again the workarounds I previously mentioned still work.

Now I'm not an expert but I really don't think this is a kernel bug at all because if the Xorg conf entry is there then the kernel seems to be perfectly capable of sending the requisite commands to the LCD firmware to adjust its brightness upon user hitting the hardware key. I don't have any pre-Saucy installations to test whether those versions automatically had the entry, or whether some change in the kernel or Xorg or elsewhere started requiring the existence of this conf file in order for the desired behaviour to be restored. So possibly you should be investigating why the Xorg conf file is no longer put in there by default by the installer or such...

[Shriramana Sharma (jamadagni)]

Confirmed on 4.2-RC1. Same workarounds still work. BTW I also checked on Fedora 22 which has kernel 4.0.4 (admittedly lesser version but) which means it's not Ubuntu specific anyhow.

[penalvch (penalvch)]

Shriramana Sharma, to see if this already resolved upstream, could you please test the latest mainline kernel (4.4) and advise to the results?

[Shriramana Sharma (jamadagni)]

I'm sorry but I'm still running Trusty LTS waiting for the next LTS to install. It seems the 4.4 kernel is only available for Wily but Wily comes with 4.2 and I'll have to install Wily and the kernel. Is it sufficient for me to test a recent daily image from http://cdimage.ubuntu.com/kubuntu/daily-live/current/ and tell you?

[penalvch (penalvch)]

Shriramana Sharma, that would be fine for now.

[Launchpad Janitor (janitor)]

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

[Nisheet Lall (nisheet-lall)]

Fixed following Arch-Wiki.

Details in:
https://nisheetlall.wordpress.com/2016/07/12/solved-brightness-fix-in-linux-1for-optimus-laptops/

[penalvch (penalvch)]

Nisheet Lall, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Pie Bald (piebald.laptop)]

On 16.04 (and 14.04), the following link fixed it for me: https://itsfoss.com/fix-brightness-ubuntu-1310/