You are not logged in.

#1 2023-10-26 06:24:49

mikewaggs
Member
Registered: 2023-10-26
Posts: 5

Skipped Frames/Screen Tearing with NVIDIA

Issue Summary: When using a TV as a display with 59.9994hz skipped frames and screen tearing occurs.

Hello All,

Fairly new to Arch and Linux and I've been able to solve most problems but I've been stuck on this one. I'm running KDE (Xorg) with an NVIDIA 4080 and using the proprietary drivers. This has been my only issue with anything related to NVIDIA/display issues.

I run a multi-monitor setup with two monitors (1440p/240hz, 1440p/144hz) and a TV (4k, 60hz). I have no problems with the monitors but when the TV is connected the issues start occurring. This issue occurs whether the TV is the only one connected or if the monitors are connected as well and this issue does not occur in Windows. I've tested this with mpv, VLC, Dragon Player, and Plex HTPC (Plex HTPC being the main reason I would like to get this working). MPV is the only one that does not have this issue and it is the only one where MangoHUD pops up. If I watch something on Plex HTPC it looks like I'm getting half of the frames that MPV is getting. I find it odd that MPV works and Plex doesn't since Plex HTPC uses mpv as the backend and they're both using the same mpv.conf for settings.

Workaround: I've found if I set the TV to 30hz with the NVIDIA Settings then the issues go away.

Possible Cause?: I did notice that when I set my TV to 60hz with the KDE settings, it was actually being set to 59.9994hz. I'm thinking that the issue is the .9994 vs the monitors ending in a full number. Ideally, I'd like to be able to use my TV at 59.9994/60hz for gaming and not have to rely on the workaround.

Open to any advice or ideas!

Offline

#2 2023-10-26 09:06:07

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,232

Re: Skipped Frames/Screen Tearing with NVIDIA

Literally "half the refreshrate" means you're missing a vsync interval. Have you tried suspending/disabling the compositor when running plex (Alt+Shift+F12 by default iirc)/is Vsync enabled in Plex itself/can you disable that? Also are any of these other solutions using accelerated video decoding/e.g. VDPAU and you aren't on your mpv runs/have you tried disabling that?

Last edited by V1del (2023-10-26 09:07:44)

Offline

#3 2023-10-30 23:32:50

mikewaggs
Member
Registered: 2023-10-26
Posts: 5

Re: Skipped Frames/Screen Tearing with NVIDIA

V1del wrote:

Literally "half the refreshrate" means you're missing a vsync interval. Have you tried suspending/disabling the compositor when running plex (Alt+Shift+F12 by default iirc)/is Vsync enabled in Plex itself/can you disable that? Also are any of these other solutions using accelerated video decoding/e.g. VDPAU and you aren't on your mpv runs/have you tried disabling that?

Thanks for taking the time to reply! It looks like the compositor was the culprit. Hitting Alt+Shift+F12 made it run as normal and also fixed an issue in a game that I thought was tied to Wine (game kept refocusing itself and changing as if it was being maximized). I am noticing some slight screen tearing when I'm scrolling inside of my web browser after toggling it.

Now that I have a starting point, I can dive a bit deeper into this. Thank you for the help and open to any suggestions if you have any!

Offline

#4 2023-10-31 07:31:31

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,056

Re: Skipped Frames/Screen Tearing with NVIDIA

qdbus org.kde.KWin /KWin supportInformation # while the compositor is active

Offline

#5 2023-11-06 03:20:33

mikewaggs
Member
Registered: 2023-10-26
Posts: 5

Re: Skipped Frames/Screen Tearing with NVIDIA

seth wrote:
qdbus org.kde.KWin /KWin supportInformation # while the compositor is active

This is the result I get back:

KWin Support Information:
The following information should be used when requesting support on e.g. https://forum.kde.org.
It provides information about the currently running instance, which options are used,
what OpenGL driver and which effects are running.
Please post the information provided underneath this introductory text to a paste bin service
like https://paste.kde.org instead of pasting into support threads.

==========================

Version
=======
KWin version: 5.27.9
Qt Version: 5.15.11
Qt compile version: 5.15.11
XCB compile version: 1.16

Operation Mode: X11 only

Build Options
=============
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 12101009
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==========
Plugin: org.kde.kwin.aurorae
Theme: __aurorae__svg__Layan
Plugin recommends border size: No
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 3
gridUnit: 10
font: Noto Sans,10,-1,0,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Output backend
==============
Name: KWin::X11StandaloneBackend

Cursor
======
themeName: breeze_cursors
themeSize: 24

Options
=======
focusPolicy: 0
xwaylandCrashPolicy: 
xwaylandMaxCrashCount: 3
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
activeMouseScreen: true
placement: 
activationDesktopPolicy: 0
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: false
focusStealingPreventionLevel: 1
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 28
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 28
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 28
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777250
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
compositingMode: 1
useCompositing: true
hiddenPreviews: 1
glSmoothScale: 2
glStrictBinding: false
glStrictBindingFollowsDriver: true
glPreferBufferSwap: 99
glPlatformInterface: 1
windowsBlockCompositing: true
latencyPolicy: 
renderTimeEstimator: 
allowTearing: true

Screen Edges
============
desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
=======
Active screen follows mouse:  yes
Number of Screens: 2

Screen 0:
---------
Name: DP-0
Enabled: 1
Geometry: 0,0,2560x1440
Scale: 1
Refresh Rate: 240000
Adaptive Sync: incapable
Screen 1:
---------
Name: DP-4
Enabled: 1
Geometry: 2560,0,2560x1440
Scale: 1
Refresh Rate: 143998
Adaptive Sync: incapable

Compositing
===========
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 4080/PCIe/SSE2
OpenGL version string: 3.1.0 NVIDIA 545.29.02
OpenGL platform interface: GLX
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 545.29.2
GPU class: Unknown
OpenGL version: 3.1
GLSL version: 1.40
X server version: 1.21.1
Linux kernel version: 6.5.9
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used

Loaded Effects:
---------------
colorpicker
outputlocator
screenshot
screenedge
blur
contrast
kwin4_effect_login
kwin4_effect_logout
kwin4_effect_sessionquit
slidingpopups
kwin4_effect_windowaperture
slide
glide
kwin4_effect_squash
kwin4_effect_maximize
kwin4_effect_frozenapp
kwin4_effect_fullscreen
kwin4_effect_fadingpopups
kwin4_effect_morphingpopups
kwin4_effect_dialogparent
desktopgrid
highlightwindow
overview
tileseditor
windowview
blendchanges
startupfeedback
kscreen

Currently Active Effects:
-------------------------
blur
contrast

Effect Settings:
----------------
colorpicker:

outputlocator:

screenshot:

screenedge:

blur:

contrast:

kwin4_effect_login:
pluginId: kwin4_effect_login
isActiveFullScreenEffect: false

kwin4_effect_logout:
pluginId: kwin4_effect_logout
isActiveFullScreenEffect: false

kwin4_effect_sessionquit:
pluginId: kwin4_effect_sessionquit
isActiveFullScreenEffect: false

slidingpopups:
slideInDuration: 150
slideOutDuration: 250

kwin4_effect_windowaperture:
pluginId: kwin4_effect_windowaperture
isActiveFullScreenEffect: false

slide:
horizontalGap: 45
verticalGap: 20
slideBackground: true

glide:
duration: 160
inRotationEdge: 0
inRotationAngle: 3
inDistance: 30
inOpacity: 0.4
outRotationEdge: 2
outRotationAngle: 3
outDistance: 30
outOpacity: 0

kwin4_effect_squash:
pluginId: kwin4_effect_squash
isActiveFullScreenEffect: false

kwin4_effect_maximize:
pluginId: kwin4_effect_maximize
isActiveFullScreenEffect: false

kwin4_effect_frozenapp:
pluginId: kwin4_effect_frozenapp
isActiveFullScreenEffect: false

kwin4_effect_fullscreen:
pluginId: kwin4_effect_fullscreen
isActiveFullScreenEffect: false

kwin4_effect_fadingpopups:
pluginId: kwin4_effect_fadingpopups
isActiveFullScreenEffect: false

kwin4_effect_morphingpopups:
pluginId: kwin4_effect_morphingpopups
isActiveFullScreenEffect: false

kwin4_effect_dialogparent:
pluginId: kwin4_effect_dialogparent
isActiveFullScreenEffect: false

desktopgrid:
activeView: 
gridRows: 1
gridColumns: 1
animationDuration: 300
layout: 1
partialActivationFactor: 0
gestureInProgress: false
showAddRemove: true
desktopNameAlignment: 0
desktopLayoutMode: 0
customLayoutRows: 2

highlightwindow:

overview:
activeView: 
animationDuration: 300
layout: 1
ignoreMinimized: false
blurBackground: true
partialActivationFactor: 0
gestureInProgress: false
searchText: 

tileseditor:
activeView: 
animationDuration: 200

windowview:
activeView: 
animationDuration: 300
layout: 1
ignoreMinimized: false
mode: -2030306240
partialActivationFactor: 0
gestureInProgress: false
searchText: 

blendchanges:

startupfeedback:
type: 1

kscreen:


Loaded Plugins:
---------------
kwin5_plugin_krunner
kwin5_plugin_nightcolor

Available Plugins:
------------------
kwin5_plugin_buttonrebinds
kwin5_plugin_colord
kwin5_plugin_krunner
kwin5_plugin_nightcolor 

Offline

#6 2023-11-06 08:42:45

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,056

Re: Skipped Frames/Screen Tearing with NVIDIA

That's w/o the TV, isn't?
The output is only interesting for the problematic condition.

Offline

#7 2023-11-06 16:24:52

mikewaggs
Member
Registered: 2023-10-26
Posts: 5

Re: Skipped Frames/Screen Tearing with NVIDIA

seth wrote:

That's w/o the TV, isn't?
The output is only interesting for the problematic condition.

Sorry, this is with the TV. I noticed that I do get screen tearing with the compositor off with my monitors as well but the smoothness issues/skipped frames go away when the compositor is off. Last night I turned on "Force Composition Pipeline" to try to combat the intense screen tearing on my TV and it seemed to make a difference so far.

I also want to apologize for the sporadic responses here, it's been busy for me IRL.

KWin Support Information:
The following information should be used when requesting support on e.g. https://forum.kde.org.
It provides information about the currently running instance, which options are used,
what OpenGL driver and which effects are running.
Please post the information provided underneath this introductory text to a paste bin service
like https://paste.kde.org instead of pasting into support threads.

==========================

Version
=======
KWin version: 5.27.9
Qt Version: 5.15.11
Qt compile version: 5.15.11
XCB compile version: 1.16

Operation Mode: X11 only

Build Options
=============
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 12101009
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==========
Plugin: org.kde.kwin.aurorae
Theme: __aurorae__svg__Layan
Plugin recommends border size: No
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 3
gridUnit: 10
font: Noto Sans,10,-1,0,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Output backend
==============
Name: KWin::X11StandaloneBackend

Cursor
======
themeName: breeze_cursors
themeSize: 24

Options
=======
focusPolicy: 0
xwaylandCrashPolicy: 
xwaylandMaxCrashCount: 3
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
activeMouseScreen: true
placement: 
activationDesktopPolicy: 0
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: false
focusStealingPreventionLevel: 1
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 28
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 28
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 28
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777250
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
compositingMode: 1
useCompositing: true
hiddenPreviews: 1
glSmoothScale: 2
glStrictBinding: false
glStrictBindingFollowsDriver: true
glPreferBufferSwap: 99
glPlatformInterface: 1
windowsBlockCompositing: true
latencyPolicy: 
renderTimeEstimator: 
allowTearing: true

Screen Edges
============
desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
=======
Active screen follows mouse:  yes
Number of Screens: 3

Screen 0:
---------
Name: DP-0
Enabled: 1
Geometry: 3840,0,2560x1440
Scale: 1
Refresh Rate: 240000
Adaptive Sync: incapable
Screen 1:
---------
Name: HDMI-0
Enabled: 1
Geometry: 0,0,3840x2160
Scale: 1
Refresh Rate: 59940
Adaptive Sync: incapable
Screen 2:
---------
Name: DP-4
Enabled: 1
Geometry: 6400,0,2560x1440
Scale: 1
Refresh Rate: 143998
Adaptive Sync: incapable

Compositing
===========
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 4080/PCIe/SSE2
OpenGL version string: 3.1.0 NVIDIA 545.29.02
OpenGL platform interface: GLX
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 545.29.2
GPU class: Unknown
OpenGL version: 3.1
GLSL version: 1.40
X server version: 1.21.1
Linux kernel version: 6.5.9
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used

Loaded Effects:
---------------
colorpicker
outputlocator
screenshot
screenedge
blur
contrast
kwin4_effect_login
kwin4_effect_logout
kwin4_effect_sessionquit
slidingpopups
kwin4_effect_windowaperture
slide
glide
kwin4_effect_squash
kwin4_effect_maximize
kwin4_effect_frozenapp
kwin4_effect_fullscreen
kwin4_effect_fadingpopups
kwin4_effect_morphingpopups
kwin4_effect_dialogparent
desktopgrid
highlightwindow
overview
tileseditor
windowview
blendchanges
startupfeedback
kscreen

Currently Active Effects:
-------------------------
blur
contrast

Effect Settings:
----------------
colorpicker:

outputlocator:

screenshot:

screenedge:

blur:

contrast:

kwin4_effect_login:
pluginId: kwin4_effect_login
isActiveFullScreenEffect: false

kwin4_effect_logout:
pluginId: kwin4_effect_logout
isActiveFullScreenEffect: false

kwin4_effect_sessionquit:
pluginId: kwin4_effect_sessionquit
isActiveFullScreenEffect: false

slidingpopups:
slideInDuration: 150
slideOutDuration: 250

kwin4_effect_windowaperture:
pluginId: kwin4_effect_windowaperture
isActiveFullScreenEffect: false

slide:
horizontalGap: 45
verticalGap: 20
slideBackground: true

glide:
duration: 160
inRotationEdge: 0
inRotationAngle: 3
inDistance: 30
inOpacity: 0.4
outRotationEdge: 2
outRotationAngle: 3
outDistance: 30
outOpacity: 0

kwin4_effect_squash:
pluginId: kwin4_effect_squash
isActiveFullScreenEffect: false

kwin4_effect_maximize:
pluginId: kwin4_effect_maximize
isActiveFullScreenEffect: false

kwin4_effect_frozenapp:
pluginId: kwin4_effect_frozenapp
isActiveFullScreenEffect: false

kwin4_effect_fullscreen:
pluginId: kwin4_effect_fullscreen
isActiveFullScreenEffect: false

kwin4_effect_fadingpopups:
pluginId: kwin4_effect_fadingpopups
isActiveFullScreenEffect: false

kwin4_effect_morphingpopups:
pluginId: kwin4_effect_morphingpopups
isActiveFullScreenEffect: false

kwin4_effect_dialogparent:
pluginId: kwin4_effect_dialogparent
isActiveFullScreenEffect: false

desktopgrid:
activeView: 
gridRows: 1
gridColumns: 1
animationDuration: 300
layout: 1
partialActivationFactor: 0
gestureInProgress: false
showAddRemove: true
desktopNameAlignment: 0
desktopLayoutMode: 0
customLayoutRows: 2

highlightwindow:

overview:
activeView: 
animationDuration: 300
layout: 1
ignoreMinimized: false
blurBackground: true
partialActivationFactor: 0
gestureInProgress: false
searchText: 

tileseditor:
activeView: 
animationDuration: 200

windowview:
activeView: 
animationDuration: 300
layout: 1
ignoreMinimized: false
mode: 0
partialActivationFactor: 0
gestureInProgress: false
searchText: 

blendchanges:

startupfeedback:
type: 1

kscreen:


Loaded Plugins:
---------------
kwin5_plugin_krunner
kwin5_plugin_nightcolor

Available Plugins:
------------------
kwin5_plugin_buttonrebinds
kwin5_plugin_colord
kwin5_plugin_krunner
kwin5_plugin_nightcolor

Offline

#8 2023-11-06 22:13:36

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,056

Re: Skipped Frames/Screen Tearing with NVIDIA

The compositor has a proper idea about the TVs  refresh rate.

If the compositor wasn't relevant, I'd say the HDMI cable is undergraded (does this happen if you keep the refresh rate at 60Hz but run the TV at 1920x1080 ?)
If it wouldn't happen w/ the TV alone, I'd say the  width surpassing 8192px might be an issue.
Does it happen if you don't put the TV into the very left, but the middle or right position?

Offline

#9 2023-11-07 22:45:54

pezz
Member
From: Geelong, Australia
Registered: 2010-05-23
Posts: 100

Re: Skipped Frames/Screen Tearing with NVIDIA

Offline

#10 2023-11-15 04:08:23

mikewaggs
Member
Registered: 2023-10-26
Posts: 5

Re: Skipped Frames/Screen Tearing with NVIDIA

seth wrote:

The compositor has a proper idea about the TVs  refresh rate.

If the compositor wasn't relevant, I'd say the HDMI cable is undergraded (does this happen if you keep the refresh rate at 60Hz but run the TV at 1920x1080 ?)
If it wouldn't happen w/ the TV alone, I'd say the  width surpassing 8192px might be an issue.
Does it happen if you don't put the TV into the very left, but the middle or right position?

I did some more testing and it does happen even without the TV. It looks like the compositor is cutting frames in half when active. I tried out Wayland to see if the same thing happened and as far as I could tell it wasn't. (But I did get a ton of other graphical issues which made me switch back to X11)

As a workaround I have autocomposer running for when I have anything go full screen. Would this be the best route for now or is it worth looking into another compositor (if that's possible)?

Offline

#11 2023-11-15 07:27:08

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,056

Re: Skipped Frames/Screen Tearing with NVIDIA

It looks like the compositor is cutting frames in half when active.

skipped frames and screen tearing … I'm getting half of the frames that MPV is getting

V1del wrote:

Literally "half the refreshrate" means you're missing a vsync interval.

It would be good to narrow down the actual symptoms, esp. wrt what "half" here. Frames or framerate.

As for tearing:
export __GL_SYNC_DISPLAY_DEVICE=DP-0 # select the device which gets synced
But

This issue occurs whether the TV is the only one connected

__GL_SYNC_TO_VBLANK=1 # force vsync
But I'm pretty sure kwin rather defaults to that?

You can test to force the full composition pipeline (notably w/ only one output attached) in nvidia-settings/X server display config/advanced or select the video sync device, nvidia-setttings/x screen/xvideo settings
If the transient changes in nvidia-settings help in any regard, you can automatize them (please don't write a static server config w/ nvidia-settings: it's cruft and likely causes you issues down the road)

Also maybe test the behavior of picom against the uncomposited kwin to see whether it's only the kwin compositor.

Offline

#12 2023-11-15 07:50:13

pezz
Member
From: Geelong, Australia
Registered: 2010-05-23
Posts: 100

Re: Skipped Frames/Screen Tearing with NVIDIA

Forgive me seth, you're a legend.

But is the OP using 545 and getting these issues? Has he reverted to 535 of nvidia, nvidia-utils and and nvidia-settings?

It also needs the 6.5.9 kernel to do this. I've reverted and held off on upgrades on my TV box because of this.

It seems like these elaborate workarounds aren't needed when it is a driver bug.

Offline

#13 2023-11-15 07:59:52

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,056

Re: Skipped Frames/Screen Tearing with NVIDIA

jaja, and bolts of lightning from my arse wink

https://gitlab.archlinux.org/archlinux/ … 2b572fb692 showed up on 1/11, 5 days after the thread was opened.
It might indeed be spoiling recent efforts, though - you can also use the 535xx nvidia-dkms version against recent kernels (unless those cause you troubles as well)

Offline

#14 2023-11-15 08:33:49

pezz
Member
From: Geelong, Australia
Registered: 2010-05-23
Posts: 100

Re: Skipped Frames/Screen Tearing with NVIDIA

Just looking for evidence, the dates certainly throws my idea into doubt (wish I had've noticed this sooner).

I've never used the dkms version of the driver before (never needed to).

Will do some testing (and a lot of reboots).

Offline

#15 2023-11-15 09:22:10

pezz
Member
From: Geelong, Australia
Registered: 2010-05-23
Posts: 100

Re: Skipped Frames/Screen Tearing with NVIDIA

I apologise to the OP here, as given the dates from seth this is unrelated, but it really seems that the 545 driver is bad.

6.5.9 + 545 = regression
6.6.1 + 545 = regression
6.5.9 + 545 dkms = regression
6.6.1 + 545 dkms = regression
6.5.9 + 535 dkms = fine
6.6.1 + 535 dkms = fine

P.S. I will be using the dkms driver from now on, seems like a good way to go, at least I don't have to block a kernel update now.

Last edited by pezz (2023-11-15 09:31:03)

Offline

#16 2023-11-24 03:49:04

pezz
Member
From: Geelong, Australia
Registered: 2010-05-23
Posts: 100

Re: Skipped Frames/Screen Tearing with NVIDIA

Just a quick update on this: 545.29.06-1 with kernel 6.6.2 and I still see the same issue as with the previous 545.29.02 version.

Gone back to 535.113.01-2 again.

Offline

Board footer

Powered by FluxBB