8086:0116 [Lenovo B570] backlight control acpi_video0 instead intel_backlight

[Тимофей]

After upgrading to new release (13.10), when i control brightness, system change value in file /sys/class/backlight/acpi_video0/brightness instead of /sys/class/backlight/intel_backlight/brightness by default. On 13.04 or older brightness works good.

---
ApportVersion: 2.12.6-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: timofey 2907 F.... pulseaudio
CurrentDmesg:
 Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
 dmesg: write failed: Broken pipe
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2013-05-28 (169 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: LENOVO HuronRiver Platform
MarkForUpload: True
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.12.0-2-generic root=UUID=5f54dc08-5f0f-4ab1-bdf2-844517b2419b ro rootflags=subvol=@ acpi_backlight=vendor
ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
Tags: trusty
Uname: Linux 3.12.0-2-generic x86_64
UpgradeStatus: Upgraded to trusty on 2013-07-08 (127 days ago)
UserGroups: audio autopilot libvirtd sudo video
WifiSyslog:

dmi.bios.date: 10/27/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 44CN43WW
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:bvr44CN43WW:bd10/27/2011:svnLENOVO:pnHuronRiverPlatform:pvrLenovoB570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
dmi.product.name: HuronRiver Platform
dmi.product.version: Lenovo B570
dmi.sys.vendor: LENOVO

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1249219/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Quinn Balazs (qbalazs)]

Please run "apport-collect 1249219" in order to collect some useful logs.

I think adding the boot flag of "acpi_backlight=vendor" on your next boot should make the values change in /sys/class/backlight/intel_backlight/brightness.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.12-trusty/

[Тимофей (nefelim4ag)]

apport information

[Тимофей (nefelim4ag)]

apport information

[Тимофей (nefelim4ag)]

apport information

[Тимофей (nefelim4ag)]

apport information

[Тимофей (nefelim4ag)]

apport information

[Тимофей (nefelim4ag)]

apport information

[Тимофей (nefelim4ag)]

apport information

[Тимофей (nefelim4ag)]

apport information

[Тимофей (nefelim4ag)]

apport information

[Тимофей (nefelim4ag)]

apport information

[Тимофей (nefelim4ag)]

> I think adding the boot flag of "acpi_backlight=vendor" on your next boot should make the values change in
> /sys/class/backlight/intel_backlight/brightness.

I trying this, this no effect.

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

I always using dev distribution, cause i already using 3.12

On 12.10 or older distrs brightness work good.

Any way, thanks.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Quinn Balazs (qbalazs)]

Please link either the upstream bug number or a link to the upstream bug so we can add a tracker for it.

Thanks

[Тимофей (nefelim4ag)]

I guarantee it does not depend on the kernel version. If install new kernel in 13.04 (for example 3.13), the bug does not appear.
I think in backlight control (in gnome-system-settings) can be added switcher to video outputs
As Notebook screen and VGA, HDMI external output and other.
This fix, can avoid this problem.

[Тимофей (nefelim4ag)]

Yes, when i install 3.13rc2 to Raring the problem not occur.

[Тимофей (nefelim4ag)]

Christopher M. Penalver (penalver), this problem exist only on new releases, with out any dependencies with kernel.

[Тимофей (nefelim4ag)]

Christopher this problem also have in all live cd, which released after 13.04

[Тимофей (nefelim4ag)]

Christopher, on 13.04 all work fine.

[penalvch (penalvch)]

Тимофей, thank you for providing the requested information. In Saucy/Trusty, if you remove all non-default kernel parameters (ex. acpi_backlight=vendor) does this change anything?

[Тимофей (nefelim4ag)]

Christopher, i havn't this option and acpi_backlight=vendor no effect to this problem. I try add this after second comment
Quinn Balazs (qbalazs) wrote on 2013-11-12: #2
Please run "apport-collect 1249219" in order to collect some useful logs.

I think adding the boot flag of "acpi_backlight=vendor" on your next boot should make the values change in /sys/class/backlight/intel_backlight/brightness.

[penalvch (penalvch)]

Тимофей, thank you for your response. Unfortunately, while I'm usually pretty good on triaging backlight bugs that have a clear kernel cause relationship, I'm stumped on this one. I'm marking back to Confirmed for someone else to check into or I come back with a better idea.

Thank you for your understanding.

[Jeremie Tamburini (jeremie2)]

On my Fujitsu Lifebook A512 I should be able to adjust the brightness pressing Fn+F6 or Fn+F7. The brightness-indicator pop-up works but the brightness doesn't change. This should be related to the cpi_video0 / intel_backlight issue.

I found a workaround here http://ubuntuforums.org/showthread.php?t=2192471

Basically it works creating the /usr/share/X11/xorg.conf.d/20-intel.conf file with the following lines:

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

This makes the brightness shortcuts Fn+F6 and Fn+F7 work.

[penalvch (penalvch)]

Jeremie Tamburini, 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

[Jeremie Tamburini (jeremie2)]

Here the new bug related to Fujitsu Lifebook A512: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318299

[Joseph Salisbury (jsalisbury)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

  With the recent release of this Ubuntu release, would like to confirm if this bug is still present. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Launchpad Janitor (janitor)]

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