UB
Universal Blue•10mo ago
Rumble

VRR Issues after waking from sleep.

Hello I'm running bazzite-deck on my HTPC. It's connected via a certified HDMI 2.1 cable to a LGC3 (that doesn't have a displayport). I run in game mode pretty much full-time. The system is a AMD 7600 cpu and a AMD 6650XT. I generally "turn off" they system by holding down the xbox button on my controller and picking sleep from the steam menu that pops up. When the computer wakes back up, the TV constantly flickers black each time a menu item moves for about a second or so. My TV reports that the framerate is "40fps" for some reason. I can struggle through it to get to the QAS menu and disable and re-enable VRR, and then everything goes right back to normal. I'd love some help solving this as its quite annoying. I'll be happy to send some logs or more information, but I'm not sure exactly what would be useful.
40 Replies
Kyle Gospo
Kyle Gospo•10mo ago
There's a huge DRM refactor coming to gamescope here soon may resolve this issue youir gamescope logs (saved to ~/ as a dotfile) would also be helpful there's two of them
Rumble
RumbleOP•10mo ago
hopefully these are what you are looking for
antheas
antheas•10mo ago
I was told Jan's HDR patch causes issues with vrr @Jan whereas the chimera one doesnt
antheas
antheas•10mo ago
antheas
antheas•10mo ago
On the ally at least
Jan
Jan•10mo ago
Chimera dropped their HDR patches some time ago AFAIK the ones I currently use are based from nobara, with are baed on the CachyOS patch and I don't really see anything vrr related in the patch can you perhaps point me at an upstream I should consider
antheas
antheas•10mo ago
i was told that swapping to this patch fixes it thats all i know
Jan
Jan•10mo ago
GitHub
AMDGPU HDR patch causes issues, possibly involving my VRR display ·...
I have a Radeon RX 6700-XT, and two monitors: An LG 24UD58-B, which is 3840x2160 panel that supports up to 60Hz and supports optional VRR range of 40-60Hz, and a Dell P2414H, a 1920x1080 panel that...
Kyle Gospo
Kyle Gospo•10mo ago
that would break the LGO again though lol
Jan
Jan•10mo ago
so, removing it fixes it but... its not just part of the HDR patch
Kyle Gospo
Kyle Gospo•10mo ago
and probably the SD OLED
Jan
Jan•10mo ago
its also part of the steamdeck quirks fix
No description
Jan
Jan•10mo ago
well, unless I find out more I can't really act I'll talk to GE regardless
Kyle Gospo
Kyle Gospo•10mo ago
could always make this a DMI check true should only apply to Galileo/Jupiter/LGO, otherwise call the old func I can look into that later today
Jan
Jan•10mo ago
indeed, but I sadly lack enough info to make a decision
Kyle Gospo
Kyle Gospo•10mo ago
iirc the VRR = true thing is a hack for gamescope to manage frame timings which it does when it has full refresh rate control of a display that is otherwise not a VRR display
Jan
Jan•10mo ago
so outside of gamescope its probably broken
Kyle Gospo
Kyle Gospo•10mo ago
works fine for me, but maybe there's some edge cases gamescope only does this for specific hardware, hence my DMI check concept
antheas
antheas•10mo ago
i think i tested the patch and it was fine? but maybe not
Jan
Jan•10mo ago
do you perhaps know anyone I could talk to to get more info on this
antheas
antheas•10mo ago
you have common servers with neither of them _neroreflex_ adolfotregosa adolfos legion go is on order so he will be able to confirm if the patch messes with the go in a couple of days all of their testing was done on the ally so if you wonder about the go they wont be much help
Jan
Jan•10mo ago
I thought a bit about the issue and think the current approach of just forcing vrr on is broken especially on systems without vrr support and compositors that aren't intended for it the steam deck hw quirks patch appears to include it for gamescope specifically, but is not a suitable solution for Bazzite where running anything but gamescope is an expected use-case I am unsure what the best solution would be without also modifying gamescope
antheas
antheas•10mo ago
forcing vrr on was done for the go and the sd oled, not the ally in kernel
Jan
Jan•10mo ago
no, it was done everywhere
antheas
antheas•10mo ago
because the displays have some weird timing requirements yes but it was done specifically for those 2 devices
Jan
Jan•10mo ago
yeah and since the Deck is only expected to run SteamOS, where you either run gamescope or KDE nested in gamescope, its not an issue, since gamescope supports VRR just fine but for other compositors this would cause problems yknow what, I know how to go forward with this...
antheas
antheas•10mo ago
If you think that this has to do with vrr you don't understand the issue Also desktop mode on the deck is not nested I think
Jan
Jan•10mo ago
I recall hearing that they switched Desktop mode from just being a raw KDE instance to being KDE nested in gamescope to allow for overlays and what not
antheas
antheas•10mo ago
Both should be available Nested does not allow for multi monitor and has stupid docking bugs
Kyle Gospo
Kyle Gospo•10mo ago
both are offered nested KDE & normal as far as what you mentioned -- my patch I sent should be enough since it only applies this VRR tweak to hardwre we know needs it
Jan
Jan•10mo ago
I looked at the patch again the oled hw quirks patch also reverts all but one segment of the vrr stuff so nothing is doing VRR
bouhaa
bouhaa•10mo ago
Not true That was for debugging at the time. It got added later again
Jan
Jan•10mo ago
Then please help me find it
Jan
Jan•10mo ago
Its not on master
No description
bouhaa
bouhaa•10mo ago
It's just GE's patch from nobara That is just kept in sync with torvalds tree
Jan
Jan•10mo ago
Ah Well, it can't be an up to date patch from nobara because nobara uses 6.7 And 6.7 had HDR partially upstreamed so the patch doesn't apply
bouhaa
bouhaa•10mo ago
Older version then 😉 Indeed, but rebasing should not be too bad right? Anyway, 6.8 has almost everything in anyway so I just decided to skip 6.7
Midas06
Midas06•5w ago
I think im seeing this issue currently. Was this resolved?
Want results from more Discord servers?
Add your server