Bug 1108019 - systemd should save + restore raw backlight interface(s) when there are no firmware interfaces
Summary: systemd should save + restore raw backlight interface(s) when there are no fi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-11 10:13 UTC by Hans de Goede
Modified: 2014-07-20 00:00 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-07-20 00:00:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Hans de Goede 2014-06-11 10:13:29 UTC
Hi,

Judging from the discussion in bug 1090860, it seems that systemd-backlight only saves backlight settings for backlight interfaces with the "firmware" type.

Normally this is the right thing to do since firmware interfaces should be preferred when available. However sometimes there only is a raw interface, and in this case it should be used rather then not saving and restoring backlight settings at all.

Note that only a raw interface becoming available is becoming more and more common as many designed for windows 8 laptops have a broken acpi-video implementation. The kernel currently has a video.use_native_backlight boolean kernel cmdline option which will disable the acpi_video backlight interface when the BIOS is "windows 8  ready". Currently there is an ever growing list of DMI based quirks enabling this options for many many new laptop models, so the plan for 3.16 is to flip this option to on by default.

Regards,

Hans

Comment 1 Lennart Poettering 2014-06-17 00:47:24 UTC
Hmm? current upstream versions of systemd actually save/erstore backlight for all backlight devices, regardless how it is accessed.

Comment 2 Zbigniew Jędrzejewski-Szmek 2014-06-17 03:07:22 UTC
The OP mentions systemd-208. I'll release an update for F20 with commit
http://cgit.freedesktop.org/systemd/systemd/commit/?id=0f4ba83.

Comment 3 Fedora Update System 2014-06-19 13:19:38 UTC
systemd-208-18.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/systemd-208-18.fc20

Comment 4 Fedora Update System 2014-06-19 22:56:23 UTC
Package systemd-208-18.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-208-18.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-7512/systemd-208-18.fc20
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2014-06-22 23:55:45 UTC
Package systemd-208-19.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-208-19.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-7512/systemd-208-19.fc20
then log in and leave karma (feedback).


Note You need to log in before you can comment on or make changes to this bug.