LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Issue with laptop using ATI Radeon RX 580. (https://www.linuxquestions.org/questions/linux-hardware-18/issue-with-laptop-using-ati-radeon-rx-580-a-4175643233/)

alex14641 11-27-2018 07:42 PM

Issue with laptop using ATI Radeon RX 580.
 
Working with an HP laptop containing a Radeon RX 580 video card, I encountered an issue wherein the screen would not turn back on when the laptop lid is closed and reopened. I have opened a bug report with the kernel folks. I can work around the issue by blacklisting the amdgpu video driver. I am currently running Linux 4.19.5. I will update this thread with any new developments.

rogan 11-30-2018 01:46 PM

I suspect that the new amd display code (in amdgpu) loads upon booting your machine.
It has various problems. One of them is when /sbin/setterm is switching on consoleblanking
in /etc/rc.d/rc.M. I changed it to /sbin/setterm -blank 0. Everything seem to work okay with
my AMD Vega64 now. Before the system chrashed whenever the console or desktop blanked the monitor.
I also could not reboot or shut down normally, it would stay on until i pressed reset.
This might be the same problem as yours.

I'm not sure if the new display code is even needed for your card.
If it's not, you can just pass amdgpu.dc=0 to the kernel and everything should work just fine.

alex14641 11-30-2018 04:59 PM

setterm -blank 0 didn't work. Nor does dc=0.

mrmazda 12-02-2018 01:50 AM

try consoleblank=0

alex14641 12-02-2018 06:12 PM

Quote:

Originally Posted by mrmazda (Post 5932417)

It didn't work.

rogan 12-02-2018 10:35 PM

A little more information might be very helpful...
Output of /sbin/lspci -v and dmesg is a start.

alex14641 12-03-2018 06:22 PM

Quote:

Originally Posted by rogan (Post 5932695)
A little more information might be very helpful...
Output of /sbin/lspci -v and dmesg is a start.

https://bugzilla.kernel.org/show_bug.cgi?id=201535

rogan 12-03-2018 10:49 PM

Regardless of hardware; I have tested this on three different machines with three
different graphics cards, I get the same amdgpu warnings and chrash trace from the
new display code as you if I let line 25 in rc.M run.

alex14641 12-14-2018 06:19 PM

Quote:

Originally Posted by alex14641 (Post 5932976)

If anyone has experienced this issue, please add yourself to the bug report via the link above.

alex14641 12-19-2018 07:21 PM

Update: with the kernel built from drm-next-4.21-wip, loading the amdgpu module with dc=1, and the latest kernel firmware from git, the display wakes up on resume. I'll test this for a few days: if it still works, I'll mark this as solved.

Just tried with 4.19.11: does not work. When loading the module, the screen goes blank.

alex14641 12-23-2018 04:42 PM

On further thought, I will wait until a fix appears in a released kernel before I mark this as solved.

alex14641 12-28-2018 04:46 PM

Turns out passing dc=1 to the module is not necessary.

alex14641 01-13-2019 03:51 PM

The screen wakes up on resume with 4.20.2. Marking this solved.


All times are GMT -5. The time now is 02:21 PM.