Also, suspend doesn't seem to work well, so going to rollback to previous release
Also, suspend doesn't seem to work well, so going to rollback to previous release
FSingle GPU and dual GPU passthrough are very different beasts. I researched single GPU for a couple months before deciding to just save up for a used second GPU. So much easier.
Jrolling back did fix the suspend issue, so there's that, at least
TIs anyone else here running VRR-patched Gnome with an AMD GPU? I think I might be narrowing in on a bug but it would be nice if someone else could test and verify, too
Hi do both single and dual gpu, i also develop 2 tools to specifically help with gpu passthrough (mainly dual but one of the tools is useful for both)
testers are few and far between (especially since i dont use the main tool myself anymore since most my stuff is now ostree based)
testers are few and far between (especially since i dont use the main tool myself anymore since most my stuff is now ostree based)
TAnd to clarify a bit more, I think VRR does not function properly when running games with high GPU utilization unless you disable KMS modifiers by setting MUTTER_DEBUG_SEND_KMS_MODIFIERS=0
TI believe in both Xorg and Wayland but most noticably in Wayland.
VUnfortunately, removing the args was definitely not the fix, but I expected that anyway. Regardless, good to remove args I won't actually be using lol
TI've been trying to figure out what's going on with VRR on Wayland for a while now and the other day I finally put together this theory from several different issue tickets in different window managers. Many of these WMs and DEs just use VRRTest or something to test that VRR works, but the issue only pops up when you're running an actual game. If you start up VRRTest, then start a demanding game on another workspace and switch back to VRRTest, you should see that VRRTest starts to stutter and skip. When I disabled KMS Modifiers, VRRTest no longer stuttered and skipped--it's also noticable in game of course, but checking VRRTest with high GPU load is a more consistent and obvious way to see if VRR is still working.
TI'm not really sure where to put this information--since it's happening in every WM I've tried, I think it's probably an AMD bug? But if disabling modifiers fixes it, then it's also something that WM/DEs could work around, so...
TAnd also something bazzite could work around, if it's found this really is affecting other AMD users
Jso what you are saying is that the GPU can't keep up the frametime and so starts stuttering when expected to spew out as many frames as possible
JI dont think this is a bug unless you can verify this on games that aren't very demanding
TIt appears to be a frametime issue, yeah. But the point of VRR is that your frames are synced to the refresh rate, which is only useful when you're playing a demanding game that can't hit your max refresh rate, right? So if VRR "works" for low GPU usage situations but not high GPU usage ones... isn't it pretty much not working?
TI did find a ticket from I think a year ago, I can find it in a sec, where previously Gnome disabled modifiers on AMD because of some issue with xwayland. This wasn't VRR related but it at least shows there's a history of this being an issue for functionality I guess
TThis is the revert for that, looks like modifiers were preventing direct scanout for DRI3 clients in xwayland: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3030
TAlso seems this was an issue people found 3 years ago: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4308
TLots of discussion in this issue as well on sway, some of the testing people did in here seems to indicate disabling direct scanout can fix it as well: https://github.com/swaywm/sway/issues/5601
VDid you change the power profile to 3d_fullscreen?
VBecause that's a known issue with AMD and has been for like two years
VYou need to change the power profile to 3d_fullscreen
TYes, I've had that fix in place for a long time
TFor a long time I didn't think the issue was with VRR itself so I was running down other known issues like that power profile one
VAh so it is a gnome-vrr bug?
TThat's what I'm not sure about. It could be? But it seems there's similar issues in sway and hyprland
Tand also I'm not completely confident that it's a generalized issue for everyone with amd on wayland, that's what I'm trying to figure out. it could be some specific setting or something
VI can try it out on plasma
J
Jbazzite is on GoL this morning!
O@Kyle Gospo Fresh boot, still getting that update error in game mode, so let me know what logs you’d like
DGoL?
Jhttps://www.gamingonlinux.com/2024/02/pc-and-handheld-gaming-with-linux-levels-up-with-bazzite-v230/
GamingOnLinux
Bazzite version 2.3.0 has been released, and it should make installing it a whole lot easier across different devices from PCs to handhelds. The developers think it's the next generation of Linux Gaming.
EGeeks3DJeGX
FurMark 2 has been released. The new major version of FurMark is available for Windows and Linux with OpenGL and Vulkan stress tests and benchmarks.
ENeed to benchmark vs stock Kinoite -.-
KYes please! It should have made ~/.steamos-update.log
OIs that Home or root?
Khome
OI have a .steam folder but no .steamos
Knot a folder, just a file
Kshould also be various .gamescope ones
OYup see those
OOK lemme install the flatpak discord on this machine so I can upload them
Kalso ~/.steam*
OLet me know if I missed any
Kty!
OIt looks like it might be upset because I disabled the Deck BIOS checks? Because I'm not running on a Deck?
Kmight be related, but others are experiencing this without that
KKThis is very helpful, looks like it's not properly returning the "no update" code to steam
Kthank you
OHappy to help!
