Bug 1069027 - Cannot turn on Screen with radeon drivers after resume of suspend.
Summary: Cannot turn on Screen with radeon drivers after resume of suspend.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-24 01:33 UTC by Álvaro Castillo
Modified: 2015-04-07 07:29 UTC (History)
11 users (show)

Fixed In Version: kernel-3.19.3-100.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-21 05:00:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg, lsusb, lspci logs... (30.02 KB, application/gzip)
2014-02-24 01:33 UTC, Álvaro Castillo
no flags Details
pm-utils.log with AMD Catalyst (11.44 KB, text/x-log)
2014-02-24 01:34 UTC, Álvaro Castillo
no flags Details
Contains some information get of pm-utils-bugreport.sh script. (11.71 KB, application/x-text)
2014-02-24 15:35 UTC, Álvaro Castillo
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Linux Kernel 71051 0 None None None Never

Internal Links: 1090128

Description Álvaro Castillo 2014-02-24 01:33:03 UTC
Created attachment 866832 [details]
dmesg, lsusb, lspci logs...

I have a HP laptop g6-2145ss with Fedora 20 installed into my HDD.

But, I have to add this problem persist at openSUSE 13.1 and Tumbleweed too.  

Fedora or openSUSE does not suspend system properly. When It's going to suspend. This works OK. But wake up does not work. Screen does not turn on. I have to force reboot machine push AC powe button. It's not good idea.

However, when I use AMD Catalyst drivers. I can perform suspends awesome. I guess is a kernel bug, or AMD haven't released source code of suspend graphics card yet.

Log attached is of AMD Catalyst driver installed and how to works fine suspend operation.

Note: I don't interested use AMD Catalyst driver, because I'm using GNOME 3.10 and It's does not work with it. Because AMD does not included libGLES into privative driver.

Comment 1 Álvaro Castillo 2014-02-24 01:34:25 UTC
Created attachment 866833 [details]
pm-utils.log with AMD Catalyst

Comment 2 Álvaro Castillo 2014-02-24 14:29:11 UTC
I tried to listen to music with VLC player. So I was surprised... system works 100% after resume but Screen is off LOL. I can swtich into different ttys and X11 desktop without Screen turned on LOL.

Comment 3 Álvaro Castillo 2014-02-24 15:35:05 UTC
Created attachment 867010 [details]
Contains some information get of pm-utils-bugreport.sh script.

Comment 4 Álvaro Castillo 2014-02-24 15:35:19 UTC
Add information:

I've tried some options to going into suspend system with pm-suspend --*

All options tried was not turn on laptop screen after resume:
--quirk-dpms-on
--quirk-dpms-suspend
--quirk-radeon-off
--quirk-s3-bios
--quirk-s3-mode
--quirk-vbe-post
--quirk-vbemode-restore
--quirk-vbestate-restore
--quirk-vga-mode-3
--quirk-save-pci
--store-quirks-as-lkw
--quirk-none

Comment 5 Álvaro Castillo 2014-02-24 15:46:49 UTC
systemctl suspend does not work too.

systemd-python-208-9.fc20.x86_64
systemd-208-9.fc20.x86_64
systemd-libs-208-9.fc20.x86_64

Comment 6 n0000b.n000b 2014-04-24 16:52:37 UTC
Hello, it seems that  i have a similar bug. Have you tested suspend this way?

sudo pm-suspend --quirk-test --quirk-s3-bios

also check https://bugs.freedesktop.org/show_bug.cgi?id=42960

Comment 7 Hin-Tak Leung 2014-09-18 08:25:53 UTC
From previous experience with backlights (screen blanking in vt after a while),
there are a few other things to try:

- the dpms option of xset
- cat some values in to /sys/class/backlight/radeon_bl0/*

Comment 8 Chester 2015-03-10 00:55:46 UTC
This seems to be fixed by:
66c2b84ba6256bc5399eed45582af9ebb3ba2c15

Can this patch be included in Fedora's kernel?

Comment 9 Josh Boyer 2015-03-11 17:48:46 UTC
(In reply to somethingsome2000+redhat from comment #8)
> This seems to be fixed by:
> 66c2b84ba6256bc5399eed45582af9ebb3ba2c15
> 
> Can this patch be included in Fedora's kernel?

I added it to F20 and F21 in Fedora git today.

Comment 10 Chester 2015-03-13 18:16:50 UTC
When would this reach the repos?

Comment 11 Fedora Update System 2015-03-17 04:16:06 UTC
kernel-3.19.1-200.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/kernel-3.19.1-200.fc21

Comment 12 Fedora Update System 2015-03-18 10:27:05 UTC
Package kernel-3.19.1-200.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.19.1-200.fc21'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-4059/kernel-3.19.1-200.fc21
then log in and leave karma (feedback).

Comment 13 Fedora Update System 2015-03-19 18:37:59 UTC
Package kernel-3.19.1-201.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.19.1-201.fc21'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-4059/kernel-3.19.1-201.fc21
then log in and leave karma (feedback).

Comment 14 Fedora Update System 2015-03-21 05:00:44 UTC
kernel-3.19.1-201.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 15 Fedora Update System 2015-03-27 23:16:24 UTC
kernel-3.19.3-100.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/kernel-3.19.3-100.fc20

Comment 16 Fedora Update System 2015-04-07 07:29:22 UTC
kernel-3.19.3-100.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


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