RESOLVED – Trying to install Slowroll on an AMD Ryzen 5 8600g APU
I’ve been juggling the installation of Linux on three different Linux PCs and, at the same time, I’m also trying to use Linux to rescue some files from a friend’s Windows 11 PC that won’t boot, so It’s taken me a while to update the information on the process of installing Slowroll on my new AMD Ryzen 5 8600g APU.
The good news is that Slowroll is now working correctly on the AMD Ryzen 5 8600g integrated gpu and will now support the entire range of screen resolutions available on the monitor instead of only being able to display 800x600. Now I can utilize the full 1920x1080 resolution that my HDMI monitor can display.
The Info Center is now correctly reporting that the graphics processor is “AMD Radeon Graphics integrated” instead of llvmpipe as it did previously. The processor is reported as AMD Ryzen 5 8600G w/ Radeon 760M Graphics.
There were two keys to the success of finally getting this working correctly.
I tried the suggestion of deano_ferrari, Global Moderator, on May 25th:
“Ok, this is the first account I’ve read of such troubles. Anyway, assuming that you have internet connectivity, try to install KDE Plasma (from a root console) with
zypper install -t pattern kde kde_plasma”
This did get me much closer to having the correct screen resolution and a working installation. It looked like it would eventually work but I deciding to try what deano_ferrari had also recommended, which was to try installing Slowroll using the new Agama installer.
The Agama installer worked like a charm and I now had a functioning Slowroll using the correct driver amdgpu for the AMD Ryzen 5 8600g APU.
I have tried using the Agama installer to do several subsequent Slowroll installations and it has worked correctly on a range of older AMD and Intel cpus as well as the latest AMD Ryzen gpus with integrated Radeon graphics.
A few days ago I used the Agama installer to install Slowroll on my new Framework 13 notebook computer which has a very new AMD Ryzen AI 5 340 APU with Radeon 840 integrated graphics. The Agama installer correctly installed the amdgpu driver to utilize the 2880x1920 120Hz resolution of the Framework 13 screen.
If you’re in the market for a new computer, I would encourage you to take a look at the Framework notebook and desktop computers. Unlike other notebook computers, users can upgrade and repair Framework notebooks as easily as you can a desktop computer. Several friends of mine have also bought Framework notebooks and are very happy with them. And Slowroll runs great on them.
So, thanks very much for the help from deano_ferrari and others on the openSUSE forums which was of great help in getting Slowroll running on my Ryzen 5 8600g desktop as well as my brand new Framework 13 with its Ryzen AI 5 340 APU.
The information below might be related to the problem I had, where llvmpipe prevented Slowroll from being able to determine the correct 1920x1080 resolution for my HDMI monitor? This information refers to problems with NVIDIA drivers but perhaps it also affects the AMD amdgpu driver?
“17 June 2025, 04:37 PM
Likely these pieces of information are useful for KDE developers about the communication between Kwin_Wayland and Nvidia drivers:
Why it doesn’t work on Wayland (kwin_wayland) after the Plasma 6.4 update:
As discussed, KWin on Wayland (kwin_wayland) has undergone a significant restructuring and gained greater independence. This has led to:
Increased Reliance on GBM: KWin_wayland in Plasma 6.4 is likely more tightly coupled with and optimized for the use of GBM (Generic Buffer Management) for graphical buffer handling.
New Initialization Requirements: For NVIDIA drivers to interact correctly with this new GBM-based approach (and Wayland in general), specific environment variables are necessary. If these are not correctly set at the start of the Wayland session, KWin cannot “see” your GPU in the way it expects and, as a fallback, resorts to llvmpipe (the Mesa software driver).
EGL/GLVND Interface: Even if the drivers are installed, the “dispatching” (the process that decides which OpenGL/EGL implementation to use) must be correctly directed towards the NVIDIA libraries. The environment variables __GL_EGL_DEVICE_INTEGRATED=nvidia and __GL_VENDOR_LIBRARY_NAME=nvidia serve precisely this purpose.
Conclusion and Recommended Solution:
The problem is not a general malfunction of your NVIDIA drivers, but a specific disconnection in the initialization between kwin_wayland and the NVIDIA libraries on Wayland, likely due to more stringent requirements introduced in Plasma 6.4.
EDIT: the issue is much more complicated and not solvable. Consider this note: Nvidia proprietary drivers worked flawlessly before Kernel 5.8.50. After the 5.8.49 Kernel release, something has gone worst and Nvidia users adopted a workaround to have the possibility to enter Wayland session providing a file in modeprob.d folder in which to write fbdev=1 so to enter Wayland session.
I don’t know what happened but now kwin uses Nvidia drivers for desktop tasks, unlike some other programs such as the browsers (firefox, chromium…) which use MESA drivers.
Last edited by MorrisS.; 17 June 2025, 06:32 PM.”