You are not logged in.
two days ago, I updated all my packages (cca a week after a previous update). After a restart sway with vulkan would crash saying it found a device, yet failed. But this issue persisted even when I downgraded all packages to some date from the previous month, even with kernel 6.14. But when I boot with the lts kernel everything works fine.
I have just an AMD iGPU, but I still tried installing
amdvlk vulkan-validation-layers linux-firmware-radeon
which didn't solve the issue either.
Any ideas what could've started this and why does it persist even after downgrading my system to package versions which used to work?
Last edited by Kepis (Yesterday 07:35:12)
Offline
Sorry to ask but any reason not to use Mesa instead?
Online
I am actually using mesa, that's why I didn't expect the extra packages to do anything, but tried it just to be sure.
Offline
You're running on the simpledrm device rather than an actual GPU driver it seems. You most likely don't have linux-firmware-amdgpu which is what you want on anything remotely modern. You should be able to remove linux-firmware-radeon and you really don't want amdvlk in the majority of cases.
If this doesn't solve it post the complete journal for the boot with the issue
sudo journalctl -b | curl -F 'file=@-' 0x0.st
and maybe throw in a pacman log from the transaction where you noticed this failing. This might be a plain kernel regression if LTS works fine, or a mismatch between running and installed kernel.
Last edited by V1del (2025-07-26 14:03:45)
Offline
After installing the amdgpu driver, it does write something to the the journal, but other than that everything is the same. However, since it used to be working just fine even when I didn't have the driver and stil is when using lts it doesn't feel like the driver was at fault. Neither could've the kernel been, since downgrading my packages back to as far as the previous month didn't change anythin.
Unfortunately I don't have any pacman logs. I feel like the update must have overwritten some weird file, but I don't know anything more about it other than the update contained changes from the period not larger than 5.7.-24.7.
Last edited by Kepis (2025-07-26 14:40:51)
Offline
/var/log/pacman.log - if you don't have that file you'r either not running archlinux or fucked up the system. "bigly".
If this doesn't solve it post the complete journal for the boot with the issue
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Offline
This is really weird. After I downgraded linux and linux-api-headers to 6.14, everything started working, and now it works even after I upgraded it back to the latest versions. But I suppose it is solved, so we will never know what caused it.
Offline