Bug 1085566 - acpi_video1 value is wrong after a couple Win+P
Summary: acpi_video1 value is wrong after a couple Win+P
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-08 23:36 UTC by Pedro Francisco
Modified: 2014-11-24 14:16 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-11-24 14:16:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
logs, no extra params (43.70 KB, application/gzip)
2014-05-14 20:53 UTC, Pedro Francisco
no flags Details
backlight logs as requested (217.16 KB, application/gzip)
2014-05-14 21:12 UTC, Pedro Francisco
no flags Details

Description Pedro Francisco 2014-04-08 23:36:22 UTC
Description of problem:
Monitor doesn't turn on.

How reproducible:
Always.

Steps to Reproduce:
1. Do stuff, update F19 to F20, do random stuff with systemd preset (meaning, not a clean system by chance)
2. Connect HDMI cable
3. Press Win+P a random 
4. Disconnect HDMI cable
5. Reboot system

Actual results:
GDM monitor off, as if output was somewhere else.
Logging in, same thing (but does login judging by disk activity)
VT are with monitor off


Expected results:
Graphics! Color! Brightness!


Additional info:
systemd.unit=multi-user.target -> normal VT
systemctl start gdm.service -> monitor off
sleep 30; systemctl stop gdm.service -> monitor on
systemctl start gdm.service; sleep 10; pm-suspend; -> after resume, monitor on
logging in on Gnome session -> monitor off
sleep 10; pm-suspend; -> after resume, monitor on

This computer's BIOS/UEFI stores some kind of registers between warm reboots.
(proof is: https://bugzilla.kernel.org/show_bug.cgi?id=67711 -- Sound only works after resume from suspend // Sound only works after cold boot )
I haven't tested cold boot because I've written too much on this bug report, but if cold boot works, I'll comment here in 5 minutes.

Other attempts:
rm -rfv /var/lib/gdm.??* ; rm /home/$USER/.config/monitors.xml
did nothing.

Hardware:
8086:0416 (Intel HD Graphics 4600 -- HDMI should be connected to this
one, since NVIDIA is always off on Linux)
10DE:0FE4 (NVIDIA GeForce GT 750M -- always disabled on boot via
manual call on rc.local to bbswitch )

Software:
up-to-date Fedora 20.


(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(==) No Layout section.  Using the first Screen section.
(==) No screen section available. Using defaults.
(**) |-->Screen "Default Screen Section" (0)
(**) |   |-->Monitor "<default monitor>"
(==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(==) Automatically adding GPU devices

Comment 1 Pedro Francisco 2014-04-11 10:35:45 UTC
Clean reinstall fixes it. Closing.

Comment 2 Pedro Francisco 2014-04-23 09:01:37 UTC
Reopened.
Happens on an updated clean install.

From what I remember, here's the procedure to trigger it:
* plug HDMI cable
* update system
* suspend with HDMI cable plugged
* on resume, black screen (makes no sense, but it is what happened, I think)
* on restart, black screen

On further tries, after resume, screen works.

rm /tmp/*
rm /var/lib/gdm/.??*

doesn't fix it.

KDM has the same issue.

Comment 3 Pedro Francisco 2014-05-10 16:47:26 UTC
Fix found!
# echo 100 > /sys/class/backlight/acpi_video1/brightness
solves the issue.

Shall I open a bug report on kernel bugzilla? Or in Gnome's bugzilla?

Short bug description:
Connecting an HDMI cable on an updated Fedora 20 install and doing Win+P a few times sets /sys/class/backlight/acpi_video1/brightness to 0.
Screen will then be black everytime 'something' restores brightness settings (which I would guess was systemd): screen will be black everytime someone starts the computer, even after HDMI cable unplugged.

Comment 4 Hans de Goede 2014-05-14 09:23:00 UTC
Hi Pedro,

Can you please walk through the debugging steps for backlight control issues described here:
http://hansdegoede.livejournal.com/13889.html

And provide *all* of the info requested there?

Thanks,

Hans

Comment 5 Pedro Francisco 2014-05-14 20:53:49 UTC
Created attachment 895629 [details]
logs, no extra params

Comment 6 Pedro Francisco 2014-05-14 21:12:40 UTC
Created attachment 895641 [details]
backlight logs as requested

Only the 06-acpi_osi-EMPTY works and even then, just two levels available (the bar doesn't decrease more than two levels, but the decrease size is 1/10 of the full bar).

Also, I should note that Gnome slider does work on the backlight, just not with the keyboard.

Comment 7 Hans de Goede 2014-05-15 11:34:29 UTC
Hi Pedro,

Thanks for the logs.

(In reply to Pedro Francisco from comment #6)
> Also, I should note that Gnome slider does work on the backlight, just not
> with the keyboard.

Hmm, that seems like a different problem, when you say "Only the 06-acpi_osi-EMPTY works", do you mean that only that one makes the brightness keys work ?

Lets please focus on one problem at a time, your initial complaint was that pressing Win+P a couple of times makes the backlight go to an off state after a reboot / suspend/resume. Then you said it happened when suspend/resuming with the hdmi cable plugged in. Can we focus on that please ?
I'm not saying your keys not working is not a problem, but 1 problem at the time please :)

So none of the options you've tried make the backlight off (under certain circumstances) after suspend/resume go away ?

Note please test the full cycle with the option. IE do the echo 100 > /sys/class/backlight/acpi_video1/brightness to make things work, then reboot with video.use_native_backlight=1, then try to get the backlight into the broken state again. If that does not happen I consider problem 1 fixed. Also please try the brightness slider in gnome for each setting, if a setting fixes the backlight off after suspend/resume, but also breaks the slider we still have a problem.

Regards,

Hans

Comment 8 Pedro Francisco 2014-11-24 14:16:32 UTC
Fixed on F21 current.
I seem to never get a black screen no matter how much Win+P I do.

I think on kernel 3.18 things such as brightness were moved from ACPI to driver-specific code, so that might be the reason.


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