You are not logged in.
I'm using the hybrid mode. The issue remains in openbox. I removed both nouveau packages. Xorg log: https://0x0.st/88Ml.txt
❯ xrandr --prop | grep -i PRIME
PRIME Synchronization: 1
~
❯ sudo cat /sys/module/nvidia_drm/parameters/modeset
Y
Last edited by l1ivi1l (2025-01-29 19:06:01)
Offline
All output are on intel, what happens if you disable the prime synchronization?
Offline
❯ xrandr --prop | grep -i PRIME PRIME Synchronization: 1
I'm sorry, using grep here was a mistake
❯ xrandr --prop
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
EDID:
00ffffffffffff0009e5000700000000
011a0104a522137802c9a0955d599429
24505400000001010101010101010101
0101010101019c3b803671383c403020
360058c21000001a0000000000000000
00000000000000000000000000fe0042
4f452043510a202020202020000000fe
004e5631353646484d2d4e34380a007c
Colorspace: Default
supported: Default, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, DCI-P3_RGB_D65, RGB_WIDE_FIXED, RGB_WIDE_FLOAT, BT601_YCC
max bpc: 12
range: (6, 12)
Broadcast RGB: Automatic
supported: Automatic, Full, Limited 16:235
panel orientation: Normal
supported: Normal, Upside Down, Left Side Up, Right Side Up
scaling mode: Full aspect
supported: Full, Center, Full aspect
link-status: Good
supported: Good, Bad
CTM: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
CONNECTOR_ID: 99
supported: 99
non-desktop: 0
range: (0, 1)
1920x1080 60.03*+ 60.01 59.97 59.96 59.93
1680x1050 59.95 59.88
1400x1050 59.98
1600x900 59.99 59.94 59.95 59.82
1280x1024 60.02
1400x900 59.96 59.88
1280x960 60.00
1440x810 60.00 59.97
1368x768 59.88 59.85
1280x800 59.99 59.97 59.81 59.91
1280x720 60.00 59.99 59.86 59.74
1024x768 60.04 60.00
960x720 60.00
928x696 60.05
896x672 60.01
1024x576 59.95 59.96 59.90 59.82
960x600 59.93 60.00
960x540 59.96 59.99 59.63 59.82
800x600 60.00 60.32 56.25
840x525 60.01 59.88
864x486 59.92 59.57
700x525 59.98
800x450 59.95 59.82
640x512 60.02
700x450 59.96 59.88
640x480 60.00 59.94
720x405 59.51 58.99
684x384 59.88 59.85
640x400 59.88 59.98
640x360 59.86 59.83 59.84 59.32
512x384 60.00
512x288 60.00 59.92
480x270 59.63 59.82
400x300 60.32 56.34
432x243 59.92 59.57
320x240 60.05
360x202 59.51 59.13
320x180 59.84 59.32
HDMI-1-0 disconnected (normal left inverted right x axis y axis)
PRIME Synchronization: 1
supported: 0, 1
CTM: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: TMDS
supported: TMDS
ConnectorType: HDMI
ConnectorNumber: 0
_ConnectorLocation: 0
non-desktop: 0
supported: 0, 1There is no PRIME Synchronization option for the primary display, it seems. Although I'm not currently using an external monitor.
I plugged one in and tested. When PRIME Sync is on, the problem occurs just like before; when it is off, the problem just occurs on its own a few seconds after the games launch.
Last edited by l1ivi1l (2025-01-29 21:46:53)
Offline
Have you already tried the 570.86.16 drivers?
https://bbs.archlinux.org/viewtopic.php … 3#p2224493
Offline
Yes, I updated to 570, but it didn't solve my problem
Offline
Anyways, when I run games using iGPU, it appears to be harder to come over the problem and I can fix it by reloading i3 with mod+shift+r. However, with dGPU, reloading i3 doesn't help.
I discovered that running in nvidia mode leads to the same result, so the issue must be connected to the hybrid graphics
Offline
"nvidia mode" means something like envycontrol, not disabling the IGP in the UEFI?
That's just like running everything (incl X11) with prime-run.
game can freeze after you just move the window. This also happens both with and without a compositor.
While running with "PROTON_USE_WINED3D=1 %command%"[, the problem still appears after alt-tabbing for a while, however in this case it isn't as fatal, the games continue running and respond to inputs but all I see is a white screen.
Since it's somehow prime/sync related, let's play w/ that
__GL_SYNC_TO_VBLANK=0 PROTON_USE_WINED3D=1 %command%__GL_SYNC_TO_VBLANK is only interpreted by nvidia and will this way completely disable VSYNC (while "1" will activate it)
Offline
__GL_SYNC_TO_VBLANK=0 PROTON_USE_WINED3D=1 %command%
I can't encounter my issue when using this, so I guess it is solved now. Although using PROTON_USE_WINED3D=1 makes performance worse for me.
Anyways, thanks a lot for the help, I guess this can be marked as [SOLVED] now.
Last edited by l1ivi1l (2025-02-09 17:56:30)
Offline
Although using PROTON_USE_WINED3D=1 makes performance worse for me.
Have you tried w/o?
The primary issue would be the vsync failure?
Anyways, thanks a lot for the help, I guess this can be marked as [SOLVED] now.
Please 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.
Offline
Have you tried w/o?
Yes, the problem was still there unless I ran with PROTON_USE_WINED3D=1
Last edited by l1ivi1l (2025-02-09 18:22:45)
Offline
The _GL parameter likely doesn't impact vulkan and I didn't immediately find an equivlant way to disable VSYNC there (ie. besides selecting VK_PRESENT_MODE_IMMEDIATE_KHR when creating the swapchain, ie. in the game/proton)
Offline