ChimeraOS
After recovering from suspension, shared graphics memory will become invalid
It should be a common problem with archLinux, both Holloiso and ChimeraOS have this issue. After recovering from suspension, shared graphics memory no longer takes effect, and the GPU can only use the dedicated graphics memory set in the bios. This will cause a significant decrease in GPU performance after suspension recovery, especially in handheld devices where 16GB RAM machines default to allocating 3G dedicated graphics memory, and some large games often use graphics memory exceeding 3G, After the failure of shared memory, the FPS of these games will significantly decrease, often only reaching about half of the maximum FPS. This issue has been identified and can only be recovered by restarting the system.
I have not provided any feedback to AMDGPU developers. I am just an ordinary user and do not understand the technology. However, in a Windows handheld player group, some people have reported that Steamdeck may experience performance degradation after recovering from suspension. However, Steamdeck will automatically recover performance in a short period of time. I hope this is helpful to you.
I have not provided any feedback to AMDGPU developers. I am just an ordinary user and do not understand the technology. However, in a Windows handheld player group, some people have reported that Steamdeck may experience performance degradation after recovering from suspension. However, Steamdeck will automatically recover performance in a short period of time. I hope this is helpful to you.
This is indeed very valuable information. Thanks for sharing!
I posted some udev rules from the latest Jupiter hw support package that might have a positive effect here
~~I am also seeing this issue on my OneXPlayer Mini Pro 6800u on ChimeraOS 43.1 stable. Testing with Armored Core 6, which will use approximately 5.4GB of VRAM in the assembly menu, after sleeping and resuming it is limited to using 5GB of VRAM and fps drops from locked 30 to <22. Doesn't seem to fix it itself after a few minutes of waiting, only on restart.~~
~~I unlocked the file system and updated device quirks to see if that might fix the issue, but it hasn't. Let me know what I can do to help diagnose the problem.~~
Edit: With some further diagonising my issue is not the same, vram and gtt are unchanged with my issue.
