Display randomly freezes and 2nd monitor goes unresponsive

Wolfyxon · 2023-04-02 14:35:03

So boot with the LTS kernel and try downgrading packages on it?

seth · 2023-04-02 14:37:19

No, build the dkms modules for (also/only) the lts kernel and boot that.

Wolfyxon · 2023-05-08 10:41:52

Sorry again for long time of inactivity but this seems to have helped. Thank you so much!

Steps:
1. Install the linux-lts-515-git kernel
2. Downgrade all packages related to NVIDIA
2. DKMS build will fail for the latest kernel but will succeed for the LTS one
3. Update grub config and boot the LTS kernel
4. Tadaa!

PS: My compositor, picom seems to be slowing down my system and my system boots and shuts down a bit slower on this kernel/older nvidia packages. Is there something I can do about it?

Last edited by Wolfyxon (2023-05-08 12:32:31)

seth · 2023-05-08 12:11:50

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General
Also your picom config.

Wolfyxon · 2023-05-08 12:20:28

Xorg log: http://0x0.st/HZwg.txt
Picom config: http://0x0.st/HZwE.txt

I also tested multiple backends
glx - low performance
xrender - horrible performance
xr_glx_hybrid - better performance but still slow
When running picom with the prime-run script, all screens just turn black.

Last edited by Wolfyxon (2023-05-08 12:21:51)

seth · 2023-05-08 12:34:10

You're currently running on the intel chip, reverse priming one output on the nvidia chip.
If you want to run (picom and everything) on the nvidia chip, see https://wiki.archlinux.org/title/NVIDIA … phics_only

As for picom, looks like you've gaussian blurring enabled "blur-strength = 20;"
That's horrible, look into the "--experimental-backends" and

blur-method = "dual_kawase"
blur-strength = 2 # 2-5 is likely sufficient

Wolfyxon · 2024-03-28 16:09:52

It's been a while and I really need to use the latest kernel due to `CVE-2024-1086` (also I love how fast the latest kernel boots), but this issue still persists. What do I do?

Here's my updated system info:
compositor: xcompmgr (picom was slow)
kernel: 6.8.2-arch1-1
nvidia-dkms: 550.67-1

I noticed that it often freezes when a new window is opened on the external screen.
Also often when switching windows or workspaces, both screens freeze for 1-3 seconds but then recover.

Another issue, the latest linux-firmware causes wifi to stop working entirely, ethernet works.

Last edited by Wolfyxon (2024-03-28 16:51:48)

seth · 2024-03-28 17:00:42

We've been there, but https://wiki.archlinux.org/title/PRIME# … erse_PRIME

xrandr --prop

Edit: for wifi please open a new thread and post your system journal after losing the wifi there.

Last edited by seth (2024-03-28 17:01:20)

Wolfyxon · 2024-03-28 17:19:34

Running the xrandr prime sync command causes the 2nd monitor to slowly fade into darkness.
EDIT: This seems to have only happened once, but it doesn't fix the freezing.

Output of

xrandr --prop

Latest kernel & drivers: http://0x0.st/Xskh.txt
Old: http://0x0.st/XskR.txt

Edit: for wifi please open a new thread and post your system journal after losing the wifi there.

Ok I might do it later, but it's only an issue on the old LTS kernel.

Last edited by Wolfyxon (2024-03-28 17:41:35)

Wolfyxon · 2024-03-28 21:20:53

Welp, if there's no fix I guess I have to either use my system in a very annoying way or never download any software

seth · 2024-03-28 21:45:24

(I'm not here 24/7)

Latest kernel & drivers:
PRIME Synchronization: 1

Old:
PRIME Synchronization: 0

And the plan was to disable that (ie. get the "Old" value) - this rather looks promising?

Wolfyxon · 2024-03-28 22:29:04

(I'm not here 24/7)

I was just assuming since I couldn't really find anyone else having this problem. Anyways.

Latest kernel & drivers:
PRIME Synchronization: 1
Old:
PRIME Synchronization: 0
And the plan was to disable that (ie. get the "Old" value) - this rather looks promising?

I was testing that command on the old kernel, that's why it's 0
I think I also uploaded xrandr --prop after a reboot and I set the prime sync to 0 before that reboot.
I guess I should set it to 0 then do xrandr --prop?

Also I noticed that after disabling it, the 2nd monitor recovers after a freeze (I might need to test it a bit more to truly confirm), but the random freezes still happen.

Last edited by Wolfyxon (2024-03-28 22:46:37)

seth · 2024-03-28 23:00:26

What exactly did "old" mean here? I was under the impression it was the functional system (515 LTS kernel)?
For more clarification: the "2nd monitor" is the HDMI one?
Before it "recovers", can you still change xrandr gamma or brightness while it's frozen?

And while it's not default for your GPU, did you maybe configure https://wiki.archlinux.org/title/PRIME# … Management ?

Wolfyxon · 2024-03-29 09:21:49

What exactly did "old" mean here? I was under the impression it was the functional system (515 LTS kernel)?

Yes you're correct, maybe I explained something wrong somewhere.

For more clarification: the "2nd monitor" is the HDMI one?

Yes.

Before it "recovers", can you still change xrandr gamma or brightness while it's frozen?

Yes, all xrandr settings work. However rotating the display or setting prime sync unfreezes it.

And while it's not default for your GPU, did you maybe configure https://wiki.archlinux.org/title/PRIME# … Management ?

I haven't ever touched that. Should I?

Last edited by Wolfyxon (2024-03-29 09:22:03)

seth · 2024-03-29 11:39:23

I haven't ever touched that. Should I?

No, the idea was that that might kick in and power down the GPU.

I think I also uploaded xrandr --prop after a reboot and I set the prime sync to 0 before that reboot.
I guess I should set it to 0 then do xrandr --prop?

The setting is transient, the idea is to boot the malfunctioning setup (current kernel and driver) and set prim sync to "0" there (you'll have to do this every time the X11 server starts - at least for testing purposes) and see whether that stabilizes the system.

Wolfyxon · 2024-03-29 11:54:21

That's what I did. As I said the 2nd monitor recovers after a freeze, but the freezes still happen when prime sync is set to 0. That is somewhat a fix, but I can't use my system normally if it freezes like that.

Oh also, I'm not very sure, but my HDMI port could be a bit damaged (I spilled cola in that area a few years ago) since a slight cable move causes the display to shut off for a few seconds (I tried different cables).
Maybe the new drivers can't handle properly such an unstable connection?

Last edited by Wolfyxon (2024-03-29 12:05:10)

seth · 2024-03-29 18:32:16

Wrt the cola incident:

◉ cvt12 1920 1080 60 -b
# 1920x1080 @ 60.000 Hz Reduced Blank (CVT) field rate 60.000 Hz; hsync: 66.660 kHz; pclk: 133.32 MHz
Modeline "1920x1080_60.00_rb2"  133.32  1920 1928 1960 2000  1080 1097 1105 1111 +hsync -vsync

Try to use that modeline, https://wiki.archlinux.org/title/Xrandr … esolutions
It has a slightly lower pixelclock than the currently used CVT1 reduced blanking modeline - maybe that helps…

Wolfyxon · 2024-03-29 19:07:41

I'm not able to add that mode

[wolfyxon@WolfArch ~]$ xrandr --addmode HDMI-1-0 "1920x1080_60.00_rb2"
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  18 (RRAddOutputMode)
  Serial number of failed request:  42
  Current serial number in output stream:  43

seth · 2024-03-29 19:11:13

Add

Option  "ModeValidation"        " AllowNonEdidModes"

to your nvidia xorg configlet, eg. /etc/X11/xorg.conf.d/20-nvidia.conf

Section "Device"
    Identifier "GeForce"
    Driver  "nvidia"
    Option  "ModeValidation"        " AllowNonEdidModes"
EndSection

Wolfyxon · 2024-03-29 22:30:47

That makes Xorg only use the HDMI screen and the laptop screen works only for TTY.

seth · 2024-03-29 22:34:04

… and probably runs the server on the nvidia chip as it's now explicitly referenced.
[Edit: sorry, should have thought of that]

Try whether it gets picked up in /usr/share/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf (OutputClass Section) - otherwise we'll have to add an actual screen config.

Last edited by seth (2024-03-29 22:34:25)

Arch Linux

#76 2023-04-02 14:35:03

Re: Display randomly freezes and 2nd monitor goes unresponsive

#77 2023-04-02 14:37:19

Re: Display randomly freezes and 2nd monitor goes unresponsive

#78 2023-05-08 10:41:52

Re: Display randomly freezes and 2nd monitor goes unresponsive

#79 2023-05-08 12:11:50

Re: Display randomly freezes and 2nd monitor goes unresponsive

#80 2023-05-08 12:20:28

Re: Display randomly freezes and 2nd monitor goes unresponsive

#81 2023-05-08 12:34:10

Re: Display randomly freezes and 2nd monitor goes unresponsive

#82 2024-03-28 16:09:52

Re: Display randomly freezes and 2nd monitor goes unresponsive

#83 2024-03-28 17:00:42

Re: Display randomly freezes and 2nd monitor goes unresponsive

#84 2024-03-28 17:19:34

Re: Display randomly freezes and 2nd monitor goes unresponsive

#85 2024-03-28 21:20:53

Re: Display randomly freezes and 2nd monitor goes unresponsive

#86 2024-03-28 21:45:24

Re: Display randomly freezes and 2nd monitor goes unresponsive

#87 2024-03-28 22:29:04

Re: Display randomly freezes and 2nd monitor goes unresponsive

#88 2024-03-28 23:00:26

Re: Display randomly freezes and 2nd monitor goes unresponsive

#89 2024-03-29 09:21:49

Re: Display randomly freezes and 2nd monitor goes unresponsive

#90 2024-03-29 11:39:23

Re: Display randomly freezes and 2nd monitor goes unresponsive

#91 2024-03-29 11:54:21

Re: Display randomly freezes and 2nd monitor goes unresponsive

#92 2024-03-29 18:32:16

Re: Display randomly freezes and 2nd monitor goes unresponsive

#93 2024-03-29 19:07:41

Re: Display randomly freezes and 2nd monitor goes unresponsive

#94 2024-03-29 19:11:13

Re: Display randomly freezes and 2nd monitor goes unresponsive

#95 2024-03-29 22:30:47

Re: Display randomly freezes and 2nd monitor goes unresponsive

#96 2024-03-29 22:34:04

Re: Display randomly freezes and 2nd monitor goes unresponsive

Board footer