Hello, since upgading to the 6.17 kernel I am having the issue that I cannot get vulkan anymore due to the system no longer booting with amdgpu.
my primary boot line is normally
linux /boot/vmlinuz-6.12-x86_64 root=UUID=460d69d4-7793-42aa-b048-9b9cf560c702 rw radeon.si_support=0 amdgpu.si_support=1 quiet splash resume=UUID=6096ac4d-7157-4398-9f2f-14f6bf99776f udev.log_priority=3
but since the update to the 6.17 kernel I get stuck when booting with a bunch of messages, which while it did have way too much going on way too fast, and I have no idea if that is written somewhere (if someone tells me where I can find that) but long story short it says it has an issue with amdgpu and effectively stops booting.
I can either hop back to the 6.12 kernel, where everything boots normal or I can just swap radeon_si and amdgpu in the boot line but then I get the issue that I can no longer use Vulkan on the AMD gpu due to there being something with the other driver, and apparently Mesa not being compatible for some reason.
vulkaninfo | grep "AMD"
WARNING: [../mesa-25.3.1/src/amd/vulkan/radv_physical_device.c:2183] Code 0 : Could not open device /dev/dri/renderD128: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)
VK_LAYER_MESA_anti_lag (Open-source implementation of the VK_AMD_anti_lag extension.) Vulkan version 1.4.303, layer version 1:
VK_AMD_anti_lag : extension revision 1
VK_AMD_buffer_marker : extension revision 1
is there some trick to get amdgpu back to work or making Mesa work with the Radeon 520?
if there’s any other info I can provide, I’ll gladly do so.
you can use this to see the boot messages from your actually boot:
journalctl -b0
The “0” after the “-b” switch is a ID. If you use “-1” insteed of “0” you can see the messages from your last boot.
Kernel 6.17 gets EOL soon, so its better to try 6.18 to get the problem solved. I dont use a radeon gpu and no further ideas, but you should provide more system information, so that others can help you.
This is due to AMD ending AMDVLK development, and moving all Vulkan support into the AMD Radeon Vulkan driver:
So, as long as you have the vulkan-radeon package installed (it replaces the out-of-date amdvlk package), your linux617 kernel should automatically load the correct amdgpu drivers without any need for them to be included in the boot parameters. If it doesn’t, try linux618, which has recently been announced as the next LTS kernel. You can install it with:
sudo mhwd-kernel -i linux618
Added note: after removing radeon.si_support=0 amdgpu.si_support=1 from /etc/default/grub, make sure you run the sudo update-grub command before rebooting.
You wouldnt find it there … as an update. You can install it through the “Manjaro Settings Manager → Kernel” or in the way @scotty65 described above. Non LTS-Kernel normally gets EOL in 3-4 mounth, so you have to take a look at this topic if you use them.
Hm, you can try to use the “-S” (since) switch, which will show you all entries since that date (and time).
journalctl -S 2025-12-20
… for example shows you every entry since December 20th this year.
thanks, just redirected the logs into a file, and as it luckily logs the boot line, it was easy to see that none of the lines where it tried to boot 6.17 with AMDGPU.
oh okay. 6.17 came kinda out of nowhere too (and an update removing x11 on my KDE) but now I suddenly need to manually choose it? lol. well I can try loading that.
Edit: 6.18 doesnt boot with amdgpu too. and a kernel update likely isnt gonna make mesa suddenly work with vulkan.
It varies – typically, 1-3 months, is a fair guess.
The LTS kernels are around much longer - see the EOL site linked (above) - 6.18 (LTS) is expected to reach EOL in December 2027, 6.12 (LTS) in December 2026.
If kernel 6.12 (LTS) is working for you, there’s probably no pressing need to change from that.
Although if it goes eol next year already that’s gonna be fun.
While i am aware that the 520 isn’t exactly new or specifically high powered but i do like some semi light gaming and went to Linux because the laptop isn’t w11 compatible (one gen too old) and i don’t wanna throw it away (aside from the other junk ms does)
That’s fine - often an older kernel can be more suitable for older hardware. And linux612 will be fully supported for another year.
Having done a bit more research this morning, it looks like the radeon.si_support=0 amdgpu.si_support=1 boot parameters may still be required for running your card on older kernels. Even though the Arch Wiki instructions mention only Southern Islands & Sea Islands generation cards, the newer Radeon 520 card (generation: Polaris) was built using the GCN 1.0 architecture, which is the same as the Southern Islands card: AMD Radeon 520 OEM Specs | TechPowerUp GPU Database
This article may also interest you:
If you want to give linux619 a test run, release candidate version 6.19.0rc1-1 is available in all 3 Manjaro branches: Branch compare for Manjaro - linux619. It can be installed via the Manjaro Settings Manager or with the following command:
sudo mhwd-kernel -i linux619
Note that the radeon.si_support=0 amdgpu.si_support=1 boot parameters should probably be removed for linux619 due it now defaulting to the modern AMDGPU kernel driver for GCN 1.0/1.1 GPUs.
Ah, the modern AMDGPU driver – I wonder if that suggests the previous driver isn’t modern, but legacy, and therefore is different and likely not backward-compatible