Monitor doesn’t wake up after entering the power saving mode. I have to switch to console (ctrl+alt+F3) power off and power on the monitor and then reboot the system to get it working properly. Do you know, what might be wrong?
Graphic card:
VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e1) (prog-if 00 [VGA controller])
Subsystem: Sapphire Technology Limited Nitro+ Radeon RX 570/580 [1da2:e366]
Flags: bus master, fast devsel, latency 0, IRQ 47
Memory at e0000000 (64-bit, prefetchable) [size=256]
Memory at f0000000 (64-bit, prefetchable) [size=2]
I/O ports at f000 [size=256]
Memory at fe900000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at fe940000 [disabled] [size=128]
Capabilities: [48] Vendor Specific Information: Len=08 <?>
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
Kernel
Linux reddwarf 4.20.0-1-default #1 SMP PREEMPT Tue Jan 8 08:38:29 UTC 2019 (34f009a) x86_64 x86_64 x86_64 GNU/Linux
Desktop environment available:
Operating System: openSUSE Tumbleweed 20190121
KDE Plasma Version: 5.14.5
Qt Version: 5.12.0
KDE Frameworks Version: 5.54.0
No, but I do have a theory. (It’s happened to me too.) UEFI was invented. Windows invented fastboot. PCs stopped POSTING in 80x25 text mode. PCs, motherboards and displays began presenting too many permutations of firmware for adequate testing to be performed for manufactuers to discover behavioral defects such as you described for particular hardware combinations. I just try to avoid using that PC with that display or that cable type. If you try to get support for a display that behaves that way, you’ll be assumed to be using Windows, and get no useful support.
There might be a solution for your problem, but it would not surprise me if there isn’t one.
You could try a UEFI BIOS adjustment to a less extreme power saving mode. You could try disabling DPMS, or manually configuring DPMS through xorg.conf*. If possible, try using a different cable type. DP instead of HDMI, or DVI instead of VGA, etc.
What is your output from:
sudo zypper in inxi; inxi -Gxx; hwinfo --monitor; xrandr
The problem occurred when I switched my faulty Nvidia 1060 card to the Radeon. That was the only change that lead to the misbehavior of the power saving.
The inxi output:
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: Sapphire Limited Nitro+ driver: amdgpu v: kernel bus ID: 0a:00.0 chip ID: 1002:67df
Display: x11 server: X.Org 1.20.3 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa compositor: kwin_x11
resolution: 1920x1200~60Hz
OpenGL: renderer: AMD POLARIS10 (DRM 3.27.0 4.20.0-1-default LLVM 7.0.0) v: 4.5 Mesa 18.3.1 direct render: Yes
Absolute path to 'hwinfo' is '/usr/sbin/hwinfo', so running it may require superuser privileges (eg. root).
Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 16384 x 16384
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
HDMI-A-1 disconnected (normal left inverted right x axis y axis)
DVI-D-0 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
1920x1200 59.95*+
1920x1080 60.00
1600x1200 60.00
1680x1050 59.88
1280x1024 60.02
1440x900 59.90
1280x960 60.00
1280x800 59.95
1280x720 59.95
1024x768 60.00
800x600 60.32
640x480 59.94
Your GPU seems to be mere weeks old. Full hardware support may not yet exist. If it’s not yet in kernel 4.20 you may wish to try 4.21git. If that doesn’t help, file a report on bugzilla.opensuse.org.
Are you sure? Exactly how did you do it? If you didn’t use the original script designed for NVidia removal, then likely there is a remnant in /lib that hasn’t been accounted for.
Have you tried, or can you try, using a DisplayPort cable instead of DVI?
The problem seems to be related to the Linux driver, It works fine o[FONT=Noto Sans]n Windows
The monitor has only the VGA and DVI connector. So I tried to connect HDMI cable to graphic card and the other end of the cable was connected to reduction HDMI->DVI and than to monitor DVI connector. And it behave in similar way like if it was connected via DVI cabel. The monitor doesn’t wake up: " Import signal out of range. Change settings to 1920x1200 60Hz.[/FONT]
To expand on my #3 comment, my two most recently manufactured displays don’t like to wake up from sleep either. Both are considerably newer, 2016 and 2018…
The problem seems to be related to the Linux driver, It works fine on Windows
I don’t use Windows anywhere near enough to have any idea if mine are OK if using Windows only, but given the response I got from Dell support about this, it would be no surprise to me if in fact this is a Linux-only problem that is not related to any particular manufacturer of gfx hardware. My two don’t have the same misbehavior. The older Dell (manual input select only) is worse than the Acer (automatic input select). In either case, sometimes a cable disconnect and reconnect solves. Other times only a reboot or even a PC power down is required.
