You are not logged in.
Pages: 1
I've recently upgraded from an R9 270 to a Nvidia 3080 and have been having slight stuttering in Gnome a few times a minute.
lspci -k | grep -A 2 -E "(VGA|3D)"
0a:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] (rev a1)
Subsystem: NVIDIA Corporation Device 1539
Kernel driver in use: nvidiajournalctl -b
https://pastebin.com/K14NmrzvThank you
Offline
Did you previously run gnome on wayland?
Add "nvidia_drm.modeset=1" to the kernel parameters.
Offline
Hi Seth thanks for the reply. I've been on x11 since installing as far as I'm aware.
I've set parameters in /etc/default/grub to
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet nvidia_drm.modeset=1"then pushed changes using
sudo grub-mkconfig -o /boot/grub/grub.cfgand rebooted. I still have the same issue, any ideas?
Last edited by Sesame4673 (2023-03-08 16:57:28)
Offline
"nvidia_drm.modeset=1" would esp. have been relevant to run gnome on wayland.
Since gnome defaults to wayland, you might want to check your journal whether you've really been running on X11.
Do you get the same "stutter" with an openbox session?
How does it manifest? Are all windows affected?
Also post the output of "xrandr -q"
Offline
It's affecting all windows (from text editors to web browsers and video players) The audio isn't affected when the "stuttering" is taking place.
X11 is running:
echo $XDG_SESSION_TYPE
x11xrandr -q
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 32767 x 32767
HDMI-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 697mm x 393mm
2560x1440 59.95 + 74.97*
1920x1080 119.98 119.88 99.93 60.00 59.94 50.00
1280x1440 59.91
1280x1024 75.02 60.02
1280x720 59.94 50.00
1024x768 119.99 100.00 75.03 70.07 60.00
800x600 119.97 100.00 75.00 72.19 60.32 56.25
720x576 50.00
720x480 59.94
640x480 120.01 99.99 75.00 72.81 59.94 59.93
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)Offline
Try to run the output at 60Hz, iirc mutter has the rate "fixed" (it might be configurable) and w/ a 75Hz vblank, you'll get judder.
xrandr --output HDMI-0 --rate 60Offline
I've stepped down the refresh rate to 60hz and ran:
xrandr --output HDMI-0 --rate 60
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 32767 x 32767
HDMI-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 697mm x 393mm
2560x1440 59.95*+ 74.97
1920x1080 119.98 119.88 99.93 60.00 59.94 50.00
1280x1440 59.91
1280x1024 75.02 60.02
1280x720 59.94 50.00
1024x768 119.99 100.00 75.03 70.07 60.00
800x600 119.97 100.00 75.00 72.19 60.32 56.25
720x576 50.00
720x480 59.94
640x480 120.01 99.99 75.00 72.81 59.94 59.93
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)It does seem to have eliminated a bit of the stutter/judder, which is great. It's probably reduced it by about 50% from what I can see.
Offline
Does it completely go away when you
export __GL_SYNC_TO_VBLANK=0 to the session (or globally)?
Dince the default rate is 60Hz, what did set the 75Hz? You? After gnome started?
Edit: https://gitlab.gnome.org/GNOME/mutter/-/issues/2230
Last edited by seth (2023-03-08 21:09:19)
Offline
Does it completely go away when you
export __GL_SYNC_TO_VBLANK=0to the session (or globally)?
Dince the default rate is 60Hz, what did set the 75Hz? You? After gnome started?
I set the refresh rate to 75hz in display options.
export __GL_SYNC_TO_VBLANK=0Isn't having any real effect on reducing the dropped frames
Offline
What does "glxgears" report about the fps?
Offline
What does "glxgears" report about the fps?
Hi Seth, it's output this, which I don't think is an appropriate output to describe the situation
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
300 frames in 5.0 seconds = 59.864 FPS
300 frames in 5.0 seconds = 59.948 FPS
300 frames in 5.0 seconds = 59.947 FPS
300 frames in 5.0 seconds = 59.944 FPS
300 frames in 5.0 seconds = 59.968 FPS
300 frames in 5.0 seconds = 59.949 FPS
300 frames in 5.0 seconds = 59.951 FPS
300 frames in 5.0 seconds = 59.952 FPS
300 frames in 5.0 seconds = 59.945 FPS
300 frames in 5.0 seconds = 59.950 FPS
300 frames in 5.0 seconds = 59.956 FPS
296 frames in 5.0 seconds = 59.160 FPS
300 frames in 5.0 seconds = 59.928 FPS
300 frames in 5.0 seconds = 59.952 FPS
300 frames in 5.0 seconds = 59.961 FPS
300 frames in 5.0 seconds = 59.932 FPS
300 frames in 5.0 seconds = 59.950 FPSSo I have taken a screencast that describes the issue.
https://i.imgur.com/AQRSTmJ.mp4
Hope this helps bring clarity to the situation, not sure how to embed it so apologies ![]()
Offline
That's not judder. The update completely stalls - and rather infrequently.
If you run multiple instances of glxgears (w/ 1-2 seconds delay inbetween), do they all stall at the same moment?
Offline
That's not judder. The update completely stalls - and rather infrequently.
If you run multiple instances of glxgears (w/ 1-2 seconds delay inbetween), do they all stall at the same moment?
Yeah, it's a complete freeze across all glxgears instances and they stop at the same time
Thanks
Offline
So it's the compositor and I don't think it's related to the refresh rate, notably b/c if exporting __GL_SYNC_TO_VBLANK=0 to the session had no impact.
Are the stalls reflected in
sudo journalctl -f ?
Do you get the same behavior w/ eg. openbox+picom (latter w/ the glx backend)?
You should also try gnome/wayland as I'm not sure this is even GL related at all.
Edit: nevertheless triple buffering might get you smoother behavior overall, https://wiki.archlinux.org/title/NVIDIA … en_tearing
Edit #2
nb. that "AllowIndirectGLXProtocol" defaults to "off" anyway and "ForceFullCompositionPipeline" will increase the power usage of the GPU (and is probably not relevant here)
Last edited by seth (2023-03-10 08:34:41)
Offline
Pages: 1