E6430 brightness control not working
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Settings Daemon |
Fix Released
|
Medium
|
|||
Nouveau Xorg driver |
Won't Fix
|
Medium
|
|||
OEM Priority Project |
High
|
Unassigned | |||
gnome-settings-daemon (Ubuntu) |
Medium
|
Unassigned | |||
Xenial |
Medium
|
Unassigned | |||
Zesty |
Medium
|
Unassigned | |||
unity-settings-daemon (Ubuntu) |
Medium
|
Unassigned | |||
Xenial |
Medium
|
Unassigned | |||
Zesty |
Medium
|
Unassigned | |||
Bionic |
Medium
|
Unassigned |
Bug Description
Impact
------
It looks like GNOME's brightness control simply used the first backlight device it saw instead of one currently in use. This meant that the brightness control would not work on some computers with multiple GPUs.
Test Case
---------
From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
Restart.
Does the brightness control now work correctly?
Regression Potential
-------
This looks like a minimal fix for this issue. It was accepted as part of gnome-settings-
Original Bug Report
-------------------
The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source Nouveau driver shows the brightness slider moving but does not affect the brightness.
When using the kernel boot option acpi_backlight=
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CurrentDesktop: Unity:Unity7
Date: Mon Apr 17 20:00:56 2017
HibernationDevice: RESUME=
InstallationDate: Installed on 2017-04-10 (7 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
MachineType: Dell Inc. Latitude E6430
ProcFB:
0 nouveaufb
1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A18
dmi.board.name: 0H3MT5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude E6430
dmi.product.
dmi.sys.vendor: Dell Inc.
Related branches
- Robert Ancell: Approve on 2018-06-06
-
Diff: 53 lines (+35/-1)1 file modifiedplugins/power/gsd-backlight-linux.c (+35/-1)
Vincent Gerris (vgerris) wrote : | #1 |
Vincent Gerris (vgerris) wrote : | #2 |
This change was made by a bot.
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Joseph Salisbury (jsalisbury) wrote : | #4 |
Would it be possible for you to test the latest upstream kernel? Refer to https:/
If this bug is fixed in the mainline kernel, please add the following tag 'kernel-
If the mainline kernel does not fix this bug, please add the tag: 'kernel-
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".
Thanks in advance.
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
status: | Confirmed → Incomplete |
Vincent Gerris (vgerris) wrote : | #5 |
Hi Joseph,
Thank you for the quick response.
I tested this with the intel-drm-next kernel and the one you suggested and get the exact same behavior. It seems like a regression, because this was not needed on 16.04/16.10.
I marked it as confirmed and added the tag, thanks you.
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: | added: kernel-bug-exists-upstream |
Po-Hsu Lin (cypressyew) wrote : | #6 |
This issue can be reproduced on another E6430 here, with the same A18 BIOS / 4.10.0-19 kernel. (But the interesting thing is that it cannot be reproduced with its variant, E6430ATG, even if they're all I+N config, and using the same BIOS)
Some debug info with the 4.11rc7 mainline kernel
kernel@
intel_backlight nv_backlight
kernel@
Linux kernel-
tags: | added: 201201-10372 |
Po-Hsu Lin (cypressyew) wrote : | #7 |
The brightness hotkey will change the "brightness" level from /sys/class/
Modify the "brightness" file in /sys/class/
Tested with 4.11rc7
Po-Hsu Lin (cypressyew) wrote : | #8 |
Verified with Kubuntu / Gnome Ubuntu 17.04 LiveUSB, brightness adjustment still not working on them.
Kai-Heng Feng (kaihengfeng) wrote : | #9 |
nvidia_backlight.c thinks the graphics chip is connected to LVDS, hence create a backlight interface, 'nv_backlight'.
This can be somehow 'workaround' in userspace tool, but I think it's not the best way to do it - the backlight interface shouldn't be there if it's not working at all.
I'll file an upstream bug to ask DRM maintainers how to handle this kind of situation.
Changed in linux: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Vincent Gerris (vgerris) wrote : | #10 |
Hi,
Thanks for your feedback. I had a chat with somebody with some experience and he suggested it should be fixed in userspace, here:
https:/
This is what he suggests (if the above is indeed what Ubuntu uses, because it is meant for Fedora):
In the gsd_backlight_
It only looks at the type of backlight and not at the connection between the backlight interface and the connector.
An option is, if the gsd_backlight_
and gsd_backlight_
are unsuccessful, then instead of using gsd_backlight_
Take $PATH as the variable to /sys/class/
and check the content of $PATH/../enabled, it has to be "enabled", that way you can find out which backlight interface is connected to an LVDS interface that actually has a connected LCD.
If no interface is found with:
`cat $PATH/../enabled` == "enabled" then as a fallback, still return the first found interface.
I tried to implement this, but just getting the development environment setup to develop and test took me so much time that I haven't gotten to it.
Perhaps the above is easy to implement for someone with the proper setup.
Please keep us informed, if I make progress I will post too (but that might take a while).
cheers
Kai-Heng Feng (kaihengfeng) wrote : | #11 |
Okay, didn't know the "enabled" part. Originally I was thinking get the value from vgaswitheroo - but "enabled" here will do.
Though I still think nouveau shouldn't expose a backlight interface under /sys with no function at all.
I'll work on GSD/USD as an alternative.
Vincent Gerris (vgerris) wrote : | #12 |
Hi,
Glad that it helps :).
I am not sure if the interface actually doesn't work, because it might if the Optimus mode would switch to use the Nvidia card dedicatedly, but since that is not supported by the nouveau driver, it might not happen. Not sure what happened to the Bumblebee projects and the likes and if it would affect this.
As long as an existing interface that is selected will always work, it could be omitted indeed.
Greetings,
Vincent
Kai-Heng Feng (kaihengfeng) wrote : | #13 |
Please try USD here: http://
I'll send a patch to GSD/USD. It may take some time to backport it to 17.04 though.
Jeremy Bicha (jbicha) wrote : | #15 |
I am closing the 'linux' portion of this bug because this apparently can be fixed in gnome-settings-
Changed in linux (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in gnome-settings-daemon (Ubuntu): | |
status: | New → Fix Committed |
importance: | Undecided → Medium |
Changed in unity-settings-daemon (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in gnome-settings-daemon (Ubuntu Zesty): | |
importance: | Undecided → Medium |
status: | New → Triaged |
no longer affects: | linux (Ubuntu Zesty) |
Changed in unity-settings-daemon (Ubuntu Zesty): | |
status: | New → Triaged |
importance: | Undecided → Medium |
description: | updated |
Changed in gnome-settings-daemon (Ubuntu Zesty): | |
status: | Triaged → In Progress |
Launchpad Janitor (janitor) wrote : | #16 |
This bug was fixed in the package gnome-settings-
---------------
gnome-settings-
* New upstream release (LP: #1689610)
- Fix brightness control in some dual-GPU computers (LP: #1683445)
- Disable GNOME's rfkill handling which basically reverts this to
how it worked or didn't in 16.04 LTS. Hopefully, a more thorough
rework will be done in time for 3.26.
* Drop patches applied in new release:
- git_fix-
- media-keys-
-- Jeremy Bicha <email address hidden> Tue, 09 May 2017 13:17:44 -0400
Changed in gnome-settings-daemon (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in gnome-settings-daemon: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
Changed in linux: | |
status: | Confirmed → Won't Fix |
Hello Vincent, or anyone else affected,
Accepted gnome-settings-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-
Further information regarding the verification process can be found at https:/
Changed in gnome-settings-daemon (Ubuntu Zesty): | |
status: | In Progress → Fix Committed |
tags: | added: verification-needed |
Vincent Gerris (vgerris) wrote : | #18 |
Hi,
This is what I get now when I try the dev package from:
https:/
sudo dpkg -i gnome-settings-
[sudo] password for ubuntu:
(Reading database ... 354908 files and directories currently installed.)
Preparing to unpack gnome-settings-
Unpacking gnome-settings-
dpkg: dependency problems prevent configuration of gnome-settings-
gnome-
Version of gnome-settings-
dpkg: error processing package gnome-settings-
dependency problems - leaving unconfigured
Processing triggers for hicolor-icon-theme (0.15-1) ...
Errors were encountered while processing:
gnome-
so I downloaded that from:
https:/
and installed it.
Then I rebooted but there is not difference in behaviour.
Note that I use Unity, not Gnome.
When I installed these packages:
http://
it worked.
Thank you all!
Jeremy Bicha (jbicha) wrote : | #19 |
Vincent, is it at all possible for you to test Ubuntu GNOME 17.04 before and after this proposed fix? I don't have the hardware to verify your fix and the Ubuntu Stable Release Update team really likes for bugfixes to be verified.
Kai-Heng Feng (kaihengfeng) wrote : | #20 |
I believe @Vicent uses Unity instead of Gnome - but I don't know when will they handle my PR tough.
As for Ubuntu Gnome 17.04, I can confirm GSD in -proposed pocket fixes the issue.
tags: |
added: verification-done removed: verification-needed |
Launchpad Janitor (janitor) wrote : | #21 |
This bug was fixed in the package gnome-settings-
---------------
gnome-settings-
* New upstream release (LP: #1689610)
- Fix gdm starting with no plugins which broke Hi-DPI support
on the login screen (LP: #1685035)
- Fix brightness control in some dual-GPU computers (LP: #1683445)
- Own the D-Bus name that the API documentation tells users of the
multimedia keys API they should use (org.gnome.
in addition to the D-Bus name that they actually use in practice
(
* Add revert-
- Revert commit that disabled GNOME's rfkill handling. Although
this fixes problems for some users, it makes things worse for
other people.
-- Jeremy Bicha <email address hidden> Tue, 09 May 2017 14:05:29 -0400
Changed in gnome-settings-daemon (Ubuntu Zesty): | |
status: | Fix Committed → Fix Released |
The verification of the Stable Release Update for gnome-settings-
no longer affects: | linux (Ubuntu) |
affects: | linux → nouveau |
Changed in oem-priority: | |
importance: | Undecided → Critical |
Launchpad Janitor (janitor) wrote : | #23 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in gnome-settings-daemon (Ubuntu Xenial): | |
status: | New → Confirmed |
Changed in unity-settings-daemon (Ubuntu Xenial): | |
status: | New → Confirmed |
Yuan-Chen Cheng (ycheng-twn) wrote : | #25 |
need fix in xenial.
Changed in oem-priority: | |
status: | New → Confirmed |
Launchpad Janitor (janitor) wrote : | #26 |
This bug was fixed in the package unity-settings-
---------------
unity-settings-
[ Kai-Heng Feng ]
* power: Choose correct backlight device on laptops with hybrid graphics
(LP: #1683445)
Backported from gnome-settings-
-- Sebastien Bacher <email address hidden> Tue, 03 Jul 2018 11:27:01 +0200
Changed in unity-settings-daemon (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in unity-settings-daemon (Ubuntu Zesty): | |
status: | Triaged → Won't Fix |
Hello Vincent, or anyone else affected,
Accepted unity-settings-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
Changed in unity-settings-daemon (Ubuntu Bionic): | |
status: | New → Fix Committed |
tags: |
added: verification-needed verification-needed-bionic removed: verification-done |
Łukasz Zemczak (sil2100) wrote : | #28 |
Hello Vincent, or anyone else affected,
Accepted unity-settings-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
Changed in unity-settings-daemon (Ubuntu Xenial): | |
status: | Confirmed → Fix Committed |
tags: | added: verification-needed-xenial |
Hi,
Unfortunately I'm unable to test, I don't have the laptop anymore.
Kind regards,
Vincent
Den mån 9 juli 2018 14:31Łukasz Zemczak <email address hidden> skrev:
> Hello Vincent, or anyone else affected,
>
> Accepted unity-settings-
> build now and be available at https:/
> /unity-
> <https:/
> in a few hours,
> and then in the -proposed repository.
>
> Please help us by testing this new package. See
> https:/
> to enable and use -proposed.Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-
> fix the bug for you, please add a comment stating that, and change the
> tag to verification-
> your testing we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https:/
> advance!
>
> ** Changed in: unity-settings-
> Status: New => Fix Committed
>
> ** Tags removed: verification-done
> ** Tags added: verification-needed verification-
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> E6430 brightness control not working
>
> Status in GNOME Settings Daemon:
> Fix Released
> Status in Nouveau Xorg driver:
> Won't Fix
> Status in OEM Priority Project:
> Confirmed
> Status in gnome-settings-
> Fix Released
> Status in unity-settings-
> Fix Released
> Status in gnome-settings-
> Confirmed
> Status in unity-settings-
> Confirmed
> Status in gnome-settings-
> Fix Released
> Status in unity-settings-
> Won't Fix
> Status in unity-settings-
> Fix Committed
>
> Bug description:
> Impact
> ------
> It looks like GNOME's brightness control simply used the first backlight
> device it saw instead of one currently in use. This meant that the
> brightness control would not work on some computers with multiple GPUs.
>
> Test Case
> ---------
> From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
> Restart.
> Does the brightness control now work correctly?
>
> Regression Potential
> -------
> This looks like a minimal fix for this issue. It was accepted as part of
> gnome-settings-
> upgrading to.
>
> Original Bug Report
> -------------------
> The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open
> So...
Will Cooke (willcooke) wrote : | #30 |
I've asked our OEM team to look for the hardware to test this on, but they haven't got any.
We're in the position that as far as we can tell nothing is made *worse* by this change, but we can't be sure if it actually fixes the problem or not. I think this is safe to land now, but if anyone has hardware to test this on, please help.
Bartosz Kosiorek (gang65) wrote : | #31 |
After install unity-settings-
Verification done.
tags: |
added: verification-done-bionic removed: verification-needed-bionic |
Launchpad Janitor (janitor) wrote : | #32 |
This bug was fixed in the package unity-settings-
---------------
unity-settings-
[ Kai-Heng Feng ]
* power: Choose correct backlight device on laptops with hybrid graphics
(LP: #1683445)
Backported from gnome-settings-
-- Sebastien Bacher <email address hidden> Tue, 03 Jul 2018 11:27:01 +0200
Changed in unity-settings-daemon (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
Changed in gnome-settings-daemon (Ubuntu Xenial): | |
importance: | Undecided → Medium |
Changed in unity-settings-daemon (Ubuntu Xenial): | |
importance: | Undecided → Medium |
Changed in unity-settings-daemon (Ubuntu Bionic): | |
importance: | Undecided → Medium |
Sebastien Bacher (seb128) wrote : | #33 |
The 15.04.1+
tags: |
added: verification-done verification-done-xenial removed: verification-needed verification-needed-xenial |
Launchpad Janitor (janitor) wrote : | #34 |
This bug was fixed in the package unity-settings-
---------------
unity-settings-
[ Kai-Heng Feng ]
* power: Choose correct backlight device on laptops with hybrid graphics
(LP: #1683445)
Backported from gnome-settings-
-- Sebastien Bacher <email address hidden> Tue, 03 Jul 2018 16:31:09 +0200
Changed in unity-settings-daemon (Ubuntu Xenial): | |
status: | Fix Committed → Fix Released |
Changed in oem-priority: | |
importance: | Critical → High |
So as a wokraround:
sudo vim /etc/default/grub
GRUB_CMDLINE_ LINUX_DEFAULT= "quiet splash acpi_backlight= vendor" LINUX_DEFAULT= "quiet splash"
#GRUB_CMDLINE_
sudo update-grub
reboot
This option adds the dell_backlight: ubuntu- Latitude- E6430:~ $ ls /sys/class/ backlight
ubuntu@
dell_backlight intel_backlight nv_backlight
Note that sending events to the intel_backlight like so: Latitude- E6430:~ # echo 1000 > /sys/class/ backlight/ intel_backlight /brightness
root@ubuntu-
works too.
More info regarding backlight troubleshooting: hansdegoede. livejournal. com/13889. html
http://
I guess we need a kernel patch/quirk.