[SOLVED]Dual monitor freeze

Sudoha · 2021-05-05 14:09:39

Hello! I have a particular problem with linux. I have installed arch mate at the moment, but it also occurred with ubuntu kde/cinnamon/mate and arch kde/cinnamon.
Simply, the system freezes due to the second monitor. If I turn it on, all system freezes. Any solution?
Right now I have installed nvidia 465 driver, but I also tried 460. One monitor is fhd 144hz and the other one is uhd 120hz. I have an nvidia 3080 + ryzen 3600.
I tried all the solutions I found with google, but it did not help

i'm pretty sure that the problem is related to xorg configuration, because if i generate a configuration file with nvidia-settings, there is only one monitor

config generated with nvidia-settings and both monitor connected

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 460.56

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "LG Electronics LG TV SSCR"
    HorizSync       30.0 - 255.0
    VertRefresh     24.0 - 120.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce RTX 3080"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-3"
    Option         "metamodes" "HDMI-0: 3840x2160_120 +0+0, DP-2: 1920x1080_144 +960+2160"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

config generated with nvidia-settings with only 1 monitor connected

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 460.56

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "AOC 24G2W1G4"
    HorizSync       160.0 - 160.0
    VertRefresh     48.0 - 144.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce RTX 3080"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-3"
    Option         "metamodes" "1920x1080_144 +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

I'm trying to create a working config file

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "AOC 24G2W1G4"
    HorizSync       160.0 - 160.0
    VertRefresh     48.0 - 144.0
    Option         "DPMS"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "LG Electronics LG TV SSCR"
    HorizSync       30.0 - 255.0
    VertRefresh     24.0 - 120.0
    Option         "DPMS"
EndSection

if I create multiple X screen, no freeze, but the other monitor is black

Last edited by Sudoha (2021-05-07 11:07:19)

seth · 2021-05-05 14:33:37

Stay w/ the 460 driver because the 465 one has a known related problem.
Then investigate on the nature of the "freeze", eg. whether it's related to a compositor (try an openbox session) and whether you still can interact w/ the system from a remote terminal (eg. via ssh)
Then check for errors in the old xorg log and the old system journal (try to reboot cleanly - if you can access via ssh, you can monitor "demsg -w" while it's happening)

Next: you should™ not use a static server layout at all.
How did you create the config for both outputs if this causes the server to freeze?
If you want to configure the outputs (w/ your last config file as a drop-in to xorg.conf.d) use the output names (HDMI-0, DP-2) as "Identifier" to apply them to that output.

Also: which is the troublesome output or do either cause this as soon as they're both active?
Multiscreen will make the driver to use the full composition pipeline - at this point the GPU will draw more power. If "just using two outputs" makes the system freeze, chances are that the GPU is underpowred - either because of a weak PSU or, more likely, because you forgot to connect the 6/8-pin dedicated power supply.

Sudoha · 2021-05-05 15:00:29

well I managed to stop the freezes
I re-generated the config file with nvidia-settings and both monitors connected

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 465.27

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "AOC 24G2W1G4"
    HorizSync       160.0 - 160.0
    VertRefresh     48.0 - 144.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "NVIDIA GeForce RTX 3080"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-3"
    Option         "metamodes" "DP-2: nvidia-auto-select +960+2160, HDMI-0: nvidia-auto-select +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

And I added

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "LG Electronics LG TV SSCR"
    HorizSync       30.0 - 255.0
    VertRefresh     24.0 - 120.0
    Option         "DPMS"
EndSection

but there are still some problems:
the desktop icons have disappeared
the main monitor, 24' fhd, has the writing too small
if I boot arch with the second monitor disabled, the main screen is all black and returns visible after login. The login screen is visible on the second screen, even if it is turned off.

edit: ok freeze are back. I don't know why. I probably give up.

Last edited by Sudoha (2021-05-05 15:21:15)

seth · 2021-05-05 15:31:35

And I added

Nothing, because that identifier isn't referenced in the server config…

I probably give up.

Whatever, but if you don't please bother to read my previous post…

Sudoha · 2021-05-05 16:00:33

And I added

seth wrote:

Nothing, because that identifier isn't referenced in the server config…

This is the first thing I tried

Section "Monitor"
    Identifier  "DP-2"
    Option      "Primary" "true"
EndSection

Section "Monitor"
    Identifier  "HDMI-2"
    Option      "LeftOf" "DP-2"
EndSection

I probably give up.

seth wrote:

Whatever, but if you don't please bother to read my previous post…

I have read it but it is a bit technical.

seth wrote:

Then investigate on the nature of the "freeze", eg. whether it's related to a compositor (try an openbox session) and whether you still can interact w/ the system from a remote terminal (eg. via ssh)
Then check for errors in the old xorg log and the old system journal (try to reboot cleanly - if you can access via ssh, you can monitor "demsg -w" while it's happening)

I can try with awesomewm.
What you mean via ssh? edit: Okay, I think I got it, I'm trying.
Now I try to look for errors in the logs.

seth wrote:

How did you create the config for both outputs if this causes the server to freeze?

I disconnected a monitor

seth wrote:

Also: which is the troublesome output or do either cause this as soon as they're both active?
Multiscreen will make the driver to use the full composition pipeline - at this point the GPU will draw more power. If "just using two outputs" makes the system freeze, chances are that the GPU is underpowred - either because of a weak PSU or, more likely, because you forgot to connect the 6/8-pin dedicated power supply.

If I start arch with the two monitors on, no freeze. II turn off the monitor after boot and turn it back on, it freezes. If I start arch with 1 monitor on and after booting I turn on the second one, it freezes.
I have a 3080 with a good PSU, no problem playing on windows.

update:
I'm connected via ssh. I can confirm that ssh works after freeze.
but how I need to use dmesg -w ? I used before the freeze, then I forced it, but nothing happened on ssh console.

Last edited by Sudoha (2021-05-05 16:58:56)

seth · 2021-05-05 19:53:17

Can you run "dmesg" (and ideally also "sudo journalctl -b") in the ssh console after the freeze?

Sudoha · 2021-05-05 21:43:17

yes, but journalctl -b is infinite, do I have to copy it?

Last edited by Sudoha (2021-05-07 11:07:49)

seth · 2021-05-06 07:15:45

do I have to copy it?

No. See the tip in the first link in my signature.

But

[    3.394387] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  465.27  Thu Apr 22 23:21:03 UTC 2021
[    3.520700] EDAC amd64: F17h_M70h detected (node 0).
[    3.520754] EDAC amd64: Node 0: DRAM ECC disabled.
[    3.521952] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  465.27  Thu Apr 22 23:12:47 UTC 2021
[    3.526442] [drm] [nvidia-drm] [GPU ID 0x00002600] Loading driver
[    3.526444] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:26:00.0 on minor 0
…
[15502.613809] BUG: kernel NULL pointer dereference, address: 0000000000000000
[15502.613815] #PF: supervisor read access in kernel mode
[15502.613817] #PF: error_code(0x0000) - not-present page
[15502.613819] PGD 0 P4D 0 
[15502.613822] Oops: 0000 [#1] PREEMPT SMP NOPTI
[15502.613825] CPU: 1 PID: 512 Comm: Xorg Tainted: P           OE     5.11.16-arch1-1 #1
[15502.613829] Hardware name: Micro-Star International Co., Ltd MS-7B86/B450-A PRO MAX (MS-7B86), BIOS M.60 04/18/2020
[15502.613831] RIP: 0010:_nv002197kms+0x12/0x30 [nvidia_modeset]
[15502.613870] Code: c7 47 08 18 b4 eb c0 48 89 77 10 c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8b 87 20 7f 00 00 40 84 f6 40 0f 95 c6 40 0f b6 f6 <48> 8b 38 48 8b 07 48 8b 80 10 01 00 00 e9 6c 57 be ec 66 2e 0f 1f
[15502.613873] RSP: 0018:ffffa40e01e6fc90 EFLAGS: 00010246
[15502.613876] RAX: 0000000000000000 RBX: ffffa40e01f1e008 RCX: 0000000000000001
[15502.613878] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffffa40e01f1e008
[15502.613880] RBP: ffffa40e00549f98 R08: 0000000000000000 R09: ffff9271110376e0
[15502.613882] R10: ffff927111e20008 R11: 0000000000000001 R12: ffff927102487008
[15502.613883] R13: 0000000000000001 R14: ffffa40e00549008 R15: ffffa40e005497c8
[15502.613885] FS:  00007fba5be44940(0000) GS:ffff92740e840000(0000) knlGS:0000000000000000
[15502.613888] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[15502.613890] CR2: 0000000000000000 CR3: 000000010def6000 CR4: 0000000000350ee0
[15502.613892] Call Trace:
[15502.613895]  ? _nv002206kms+0x1dd/0x210 [nvidia_modeset]
[15502.613931]  ? _nv002576kms+0x122d/0x1af0 [nvidia_modeset]
[15502.613966]  ? _nv000559kms+0x50/0x50 [nvidia_modeset]
[15502.613994]  ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset]
[15502.614022]  ? nvkms_ioctl+0x10f/0x180 [nvidia_modeset]
[15502.614049]  ? nvidia_frontend_unlocked_ioctl+0x37/0x50 [nvidia]
[15502.614407]  ? __x64_sys_ioctl+0x83/0xb0
[15502.614412]  ? do_syscall_64+0x33/0x40
[15502.614416]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[15502.614421] Modules linked in: snd_seq_dummy snd_hrtimer snd_seq mousedev joydev nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) usbhid snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg soundwire_intel rfkill soundwire_generic_allocation soundwire_cadence snd_hda_codec snd_usb_audio snd_hda_core soundwire_bus intel_rapl_msr intel_rapl_common vfat fat snd_soc_core snd_usbmidi_lib edac_mce_amd snd_hwdep kvm_amd snd_rawmidi snd_seq_device ppdev snd_compress mc wmi_bmof ac97_bus kvm drm_kms_helper r8169 snd_pcm_dmaengine irqbypass crct10dif_pclmul sp5100_tco realtek snd_pcm crc32_pclmul ghash_clmulni_intel aesni_intel ccp cec snd_timer mdio_devres crypto_simd snd syscopyarea cryptd sysfillrect glue_helper sysimgblt rapl i2c_piix4 libphy pcspkr soundcore k10temp fb_sys_fops rng_core parport_pc parport wmi gpio_amdpt pinctrl_amd gpio_generic mac_hid acpi_cpufreq drm fuse pkcs8_key_parser agpgart bpf_preload ip_tables x_tables ext4
[15502.614483]  crc32c_generic crc16 mbcache jbd2 xhci_pci crc32c_intel xhci_pci_renesas
[15502.614491] CR2: 0000000000000000
[15502.614494] ---[ end trace f69cf34a533a09af ]---
[15502.614496] RIP: 0010:_nv002197kms+0x12/0x30 [nvidia_modeset]
[15502.614528] Code: c7 47 08 18 b4 eb c0 48 89 77 10 c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8b 87 20 7f 00 00 40 84 f6 40 0f 95 c6 40 0f b6 f6 <48> 8b 38 48 8b 07 48 8b 80 10 01 00 00 e9 6c 57 be ec 66 2e 0f 1f
[15502.614531] RSP: 0018:ffffa40e01e6fc90 EFLAGS: 00010246
[15502.614533] RAX: 0000000000000000 RBX: ffffa40e01f1e008 RCX: 0000000000000001
[15502.614535] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffffa40e01f1e008
[15502.614536] RBP: ffffa40e00549f98 R08: 0000000000000000 R09: ffff9271110376e0
[15502.614538] R10: ffff927111e20008 R11: 0000000000000001 R12: ffff927102487008
[15502.614540] R13: 0000000000000001 R14: ffffa40e00549008 R15: ffffa40e005497c8
[15502.614541] FS:  00007fba5be44940(0000) GS:ffff92740e840000(0000) knlGS:0000000000000000
[15502.614544] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[15502.614545] CR2: 0000000000000000 CR3: 000000010def6000 CR4: 0000000000350ee0

seth wrote:

Stay w/ the 460 driver because the 465 one has a known related problem.

Despite the different backtrace and RIP code, this could just be caused by https://bbs.archlinux.org/viewtopic.php?id=265563 (esp. because of the discussed symptoms) to please make sure to test whether this and the same/similar backtrace occurs w/ the 460 module.

Sudoha · 2021-05-06 11:41:42

Yesterday i noticed the same kernel bug, and after googling i found the same topic
I have downgraded nvidia and nvidia-utils to version 460.67-1, but the system won't boot. I only see "-" flashing
I tried the 460 drivers on ubuntu, where they are installed by default, but with the same freezes.

I also did a memtest, no error. Both hard drive 100% health.

Last edited by Sudoha (2021-05-07 11:07:56)

seth · 2021-05-06 14:14:16

Did you try whether this happens w/ openbox or awesome (don't run picom/xcompmgr on top of them - no fancy shadows tfor this test)

Edit:

but the system won't boot. I only see "-" flashing

Likely a botched downgrade because either the old drivers are in the initramfs or you only downgraded to nvidia 460xx (but not the kernel - however, keep the kernel and use nvidia-dkms 460xx instead)

Last edited by seth (2021-05-06 14:17:16)

Sudoha · 2021-05-06 15:20:53

I formatted and installed awesomewm,no freeze
so the problem is related to a compositor?
I can use awesomewm, I've used it in the past. But if I remember correctly, I used it with compton installed, maybe for fix the tearing

Last edited by Sudoha (2021-05-06 15:32:10)

seth · 2021-05-06 15:36:09

I formatted

You did what???

There's no reason to even uninstall mate to use awesome - let alone completely resetting the system.
What archlinux version is this exactly? Are you even still using the nvidia blob or maybe now nouveau?
And does mate still cause the original problem?

Sudoha · 2021-05-06 16:15:24

I used the latest official iso and installed with archinstall
nvidia 465
I don't know if mate still cause the original problem, I have only awesomewm right now.
Should I have installed awesomewm together with mate? I've always used awesomewm alone, so I didn't think about it. And I preferred to format because I had changed too many things.

seth · 2021-05-06 16:17:17

Should I have installed awesomewm together with mate?

Yes.

And I preferred to format because I had changed too many things.

The problem with that is that you completely changed the situation - right now we don't even know whether the original problem is still reproducible or whether it might only cook up later when you replicate previous changes…

Sudoha · 2021-05-06 16:22:10

well as i said in the first post, the problem occurred with ubuntu kde / cinnamon / mate with nvidia 460, without change or install anything. and on arch mate/cinnamon/kde with nvidia 465, without change or install anything.
right now no freeze on arch with nvidia 465 and awesomewm. so the problem is related to a desktop environment, no?

seth · 2021-05-06 19:56:27

There're many ways to believe that and one to know: you try.

Sudoha · 2021-05-06 20:22:50

I installed mate and freeze shows up. if instead I choose awesome with lightdm, no freeze

Last edited by Sudoha (2021-05-06 20:28:58)

seth · 2021-05-06 20:28:34

So it's most likely the compositor. Does it happen w/ picom?
If so, does it happen w/ the xrender or the GL backend or either?

Sudoha · 2021-05-06 21:04:14

seth wrote:

So it's most likely the compositor. Does it happen w/ picom?

no freeze. I get 2 error with picom, but it seems to work well

[ 05/07/2021 01:00:58.386 x_fence_sync ERROR ] Failed to trigger the fence (X error 136 XSyncBadFence request 134 minor 15 serial 1828)
[ 05/07/2021 01:00:58.386 paint_all ERROR ] x_fence_sync failed, xrender-sync-fence will be disabled from now on.

seth wrote:

If so, does it happen w/ the xrender or the GL backend or either?

how can switch on mate? o.o I tried to google it
edit: I also tried to disable compositing on mate from general option, but still freeze
thank you for your help, I appreciate it very much

Last edited by Sudoha (2021-05-06 21:12:00)

seth · 2021-05-06 21:15:29

You can try to https://wiki.archlinux.org/title/MATE#D … ompositing and run picom as compositor if you want and alternatively https://wiki.archlinux.org/title/MATE#U … ow_manager
This will also reveal whether this is an issue w/ the mate compositor or a different element of the DE.

Sudoha · 2021-05-06 21:36:31

seth wrote:

You can try to https://wiki.archlinux.org/title/MATE#D … ompositing and run picom as compositor if you want and alternatively https://wiki.archlinux.org/title/MATE#U … ow_manager
This will also reveal whether this is an issue w/ the mate compositor or a different element of the DE.

freeze with mate compositing disable and also with picom active
freeze with marco replaced with i3 or awesome

seth · 2021-05-06 21:44:16

xrandr component of the mate settings-daemon?
(I've never used mate, I'm just eyeballing where things could fall apart)

Sudoha · 2021-05-06 22:34:19

seth wrote:

xrandr component of the mate settings-daemon?
(I've never used mate, I'm just eyeballing where things could fall apart)

I don't know exactly what you were asking me lol
I installed dconf-editor and disabled mates xrandr plugin, it worked! no freeze

now I have to figure out how to set up the monitors, because the secondary monitor is seen as the primary one
edit: I used nvidia-settings and for now, no freeze.
edit2: I preferred to create a conf file, it works better than nvidia-settings. But i don't understand why it doesn't save monitor position with absolute coordinates

  GNU nano 5.7          /etc/X11/xorg.conf.d/10-monitor.conf                    
Section "Monitor"
    Identifier  "DP-2"
    Option      "Primary" "true"
    Option      "Position" "960 2160"
    Option      "PreferredMode" "1920x1080"
EndSection

Section "Monitor"
    Identifier  "HDMI-0"
    Option      "Position" "0 0"
    Option      "PreferredMode" "3840x2160"
EndSection

however, it seems the problem is solved!

Last edited by Sudoha (2021-05-06 22:59:57)

seth · 2021-05-07 05:20:22

If the primary output is the only one it'll be positioned at 0,0 - you could use https://aur.archlinux.org/packages/x-on-resize/ as dynamic config daemon.
And best file a bug, https://github.com/mate-desktop/mate-se … mon/issues

Edit: Also please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Last edited by seth (2021-05-07 05:20:53)

Sudoha · 2021-05-07 14:41:54

seth wrote:

If the primary output is the only one it'll be positioned at 0,0 - you could use https://aur.archlinux.org/packages/x-on-resize/ as dynamic config daemon

I don't know how to use it, but I will find another way
edit: i am using ~ / .xprofile and it works fine

 xrandr --output HDMI-0 --mode 3840x2160 --rate 120 --pos 0x0 --rotate normal --output DP-2 --primary --mode 1920x1080 --rate 144 --pos 960x2160 --rotate normal

seth wrote:

Edit: Also please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Done!
I switched to KDE and fixed the freezes by disabling the Kscreen 2 service
thanks again for your help!

Last edited by Sudoha (2021-05-07 15:34:33)

Arch Linux

#1 2021-05-05 14:09:39

[SOLVED]Dual monitor freeze

#2 2021-05-05 14:33:37

Re: [SOLVED]Dual monitor freeze

#3 2021-05-05 15:00:29

Re: [SOLVED]Dual monitor freeze

#4 2021-05-05 15:31:35

Re: [SOLVED]Dual monitor freeze

#5 2021-05-05 16:00:33

Re: [SOLVED]Dual monitor freeze

#6 2021-05-05 19:53:17

Re: [SOLVED]Dual monitor freeze

#7 2021-05-05 21:43:17

Re: [SOLVED]Dual monitor freeze

#8 2021-05-06 07:15:45

Re: [SOLVED]Dual monitor freeze

#9 2021-05-06 11:41:42

Re: [SOLVED]Dual monitor freeze

#10 2021-05-06 14:14:16

Re: [SOLVED]Dual monitor freeze

#11 2021-05-06 15:20:53

Re: [SOLVED]Dual monitor freeze

#12 2021-05-06 15:36:09

Re: [SOLVED]Dual monitor freeze

#13 2021-05-06 16:15:24

Re: [SOLVED]Dual monitor freeze

#14 2021-05-06 16:17:17

Re: [SOLVED]Dual monitor freeze

#15 2021-05-06 16:22:10

Re: [SOLVED]Dual monitor freeze

#16 2021-05-06 19:56:27

Re: [SOLVED]Dual monitor freeze

#17 2021-05-06 20:22:50

Re: [SOLVED]Dual monitor freeze

#18 2021-05-06 20:28:34

Re: [SOLVED]Dual monitor freeze

#19 2021-05-06 21:04:14

Re: [SOLVED]Dual monitor freeze

#20 2021-05-06 21:15:29

Re: [SOLVED]Dual monitor freeze

#21 2021-05-06 21:36:31

Re: [SOLVED]Dual monitor freeze

#22 2021-05-06 21:44:16

Re: [SOLVED]Dual monitor freeze

#23 2021-05-06 22:34:19

Re: [SOLVED]Dual monitor freeze

#24 2021-05-07 05:20:22

Re: [SOLVED]Dual monitor freeze

#25 2021-05-07 14:41:54

Re: [SOLVED]Dual monitor freeze

Board footer