Screen won't turn off

Support Graphics & Display
,
1

Hello, friends.

Previously, I had an nVidia graphics card and had no problems. However, after updating the graphics card and drivers for the AMD card, my screen does not turn off after the specified time in the power manager.

For example, before, I had it set to turn off after 3 minutes. Now, I set any time and it turns off, then turns on (only on x11). That is, it should turn off and not turn on without mouse or keyboard movement, but it turns on immediately after the screen displays a message that there is no video signal.

I would prefer not to completely reinstall the system to test how it behaves on a clean installation of the system and AMD drivers. Therefore, perhaps you can suggest something. I have tried different kernels (5.15, 6.1, 6.2, 6.3), but there is no effect.

Also, since I installed the AMD card, I hoped that open source drivers would give smoother performance for the entire system. However, when working on Wayland, the screen also does not turn off at all. It only turns off on x11, but immediately turns on.

At the same time, my peripheral devices are working properly and I have not changed them. That is, the same mouse and keyboard were used with the nVidia card. I have no other devices that could be waking up the screen.

===========

Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.3.0-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™2 Quad CPU Q9550 @ 2.83GHz
Memory: 5,8 GiB of RAM
Graphics Processor: AMD Radeon RX 470 Graphics
Manufacturer: MICRO-STAR INTERNATIONAL CO.,LTD
Product Name: MS-7360
System Version: 1.0
1 Like
2

Friends, do you have any ideas?
I updated my computer hardware. I reinstalled the operating system, but the problem is still relevant.
On X11, the monitor turns off, but then immediately turns on.
On Wayland it doesn’t turn off at all

3

This might be your problem.
https://bbs.archlinux.org/viewtopic.php?id=282293&p=3
You can try linux60-rt , this works on my ryzen 7 6850u notebook, while linux61 ,linux62 and linux63-rc5 will not suspend (x11 here).
The first sugestion in this thread, appending
amd_iommu=off
to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub is also partially working on my machine, so I can wait for a fix (hopefully) in the next update.

And if you have not seen yet,

1 Like
4

On 6.0 my system won’t start at all.
But thanks for the advice.

5

Does this command work?

xset dpms force off

If so, somebody reported it was an issue with his webcam:
https://bbs.archlinux.org/viewtopic.php?pid=1992258#p1992258

1 Like
6

Unfortunately, apart from the keyboard and mouse, I have no other third-party devices connected (except for monitors, of course).

xset dpms force off                                                                            ✔ 
server does not have extension for dpms option
xset:  unknown option force
7

Screenshot_20230504_110444
Screenshot_20230504_110444699Ă—214 31.2 KB

Friends, is there any point in trying to install other drivers (modesetting, vesa)?

1 Like
8

If I understood you correctly, then among other things, you advised adding such a setting to the bootloader configuration. I tried. It didn’t fix the screen behavior. It still turns off and on again, immediately.

GRUB_CMDLINE_LINUX_DEFAULT="quiet cryptdevice=UUID=0000-00-00000:luks-0000-0000 root=/dev/mapper/luks-0000-000-0000 splash resume=UUID=000-000-000 udev.log_priority=3 !!! amd_iommu=off !!!"
1 Like
9

As you can read in the arch forum link, various users with various amd systems have various workarounds. This is no advice, this is “try and error”. As long as this is not fixed, we have to get around that somehow. My best option on my notebook is linux60-rt.

10

For programmers, this is called a “crutch” )

For some reason, when I use Wayland, those programs that were open are not remembered when I exit and enter a session or restart the PC. For example kate, dolphin. Do you also?
Although at x11 they open at login.

11

I have 2 monitors installed. First is Philips 246e.
Second - Samsung 223BW.
If I turn off the first one (Philips), and set the monitor to turn off after 1 minute (when only Samsung is working), then it works. Samsung turns off and turns on only when I move the mouse or press keys on the keyboard.
But, if I turn off Philips or use it together with Samsung, then the Philips monitor turns off, writes that there is no input signal and turns on again…
Perhaps there is some solution.

12

Hello my friend, I am glad I found someone who’s is facing the very same issue. (All my screens are BenQ)
I have tried this and it is the very same on KDE Plasma of:
MX Linux KDE 5.25
Solus OS KDE 5.27 iso
Endeavor OS KDE 6.1 iso
Debian Live KDE 5.25 iso
Manjaro too :wink: KDE 6.0.5

I have tried all 6.X kernels but 6.10 on sysvinit and systemd.

I originally thought I have misconfigured something in BIOS or physically made a booboo while putting it in.
I get all info (no fan speed) in radeontop and in the System Monitor (with a downladed GPU page), but not on widgets.

Shown-below widgets are System Load Viewer and Aesthetic Clock (no info at all on Simple Monitor as well), but this is on MX Linux right now. These widgets do not work in Plasma 6.

Screenshot_20240722_100306
Screenshot_20240722_1003062568Ă—1661 648 KB

inxi -G
Graphics:
  Device-1: Intel RocketLake-S GT1 [UHD Graphics 750] driver: i915 v: kernel
  Device-2: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX] driver: amdgpu
    v: kernel
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X:
    loaded: amdgpu,modesetting unloaded: fbdev,radeon,vesa dri: radeonsi
    gpu: amdgpu resolution: 1: 1920x1080~60Hz 2: 3840x2160~60Hz
    3: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: AMD Radeon Graphics
    (gfx1100 LLVM 15.0.6 DRM 3.57 6.9.7-1-liquorix-amd64)

My setup is HD+4K+HD and sometimes the last HD stays black and is cast on top of the 4K, but not off (but this is an X11 issue I think and negligible since it was the same for Nvidia in the past).

I do confirm, software can not turn off the screen, it turns right back on. And so it is with the above xset command
( that of course does only work on X11 so hence nothing at all happens on Wayland. Unsure how KDE implements auto-turn screens off on Wayland.)

Maybe some kernel parameter must be set or we can ask on AMD support forums?

1 Like
13

Try also reading my posts from here ^
I was able to turn off the monitor over time only by turning off one of the monitors. Namely, the one connected via DVI.
At the moment I only have one monitor connected and it is turning off. I’d rather be without the second old monitor (additional) than to constantly turn off the new (main) monitor with a button.
Perhaps the problem lies precisely in DVI. I tried to leave only the old DVI monitor, it turned off over time. But together with the new monitor via HDMI it did not turn off.
I turned off the old monitor using the monitor widget near the clock in the lower corner of the screen, on the taskbar. And I turned off the second monitor with a button.

1 Like
14

Ok I will try w/o DVI later. Problem is, there is 2 HD and 2 DVI outlets, I want to be able to use them all.

Might be worth to sign up here and ask too?
https://community.amd.com/

Also I haven’t tried Kubuntu yet… for Ubuntu has an officially supported closed source driver.

15

I don’t know how, but now I have both monitors connected and, lo and behold, they both turn off. This is very pleasing. Although, maybe it’s until the reboot or something like that.
And how are you?

16

I found that when two monitors are turned on, they are now turned off. If I turn off one of them using the monitor control widget (I have it near the clock), then turning off does not work.

17

It worked once when I manually switched off the DVI 4k (still connected) though. I still have to test with disconnecting.
However all of this is just for tracing the bug, I just have to use all 4 ports of my graphics card. Which is 2xHDMI and 2xDVI.
An option of a switcher DVItoHDMI would mean possible quality loss and even if I had those converters just to trace the bug as well.
Right now I am not on Manjaro with the said desktop, so I can not seek help here!
Although I know there is the same issue on Manjaro. As far as I can see we do not even have the option to software-switch off on Wayland in general?

18

The screen does auto turn off and stay off on SDDM login screen, DVI and HDMI.

19

This thread was started in April 2023, and doesn’t seem to be going anywhere generally.

Perhaps it needs some closure. :door:

(or at least a summary)