Hello @Kuro-Maii, looking at your system information, you have a Sea Islands (CIK) generation video card. The linux kernel uses the radeon kernel module by default with this generation of video card. The radeon kernel module is incompatible with Vulkan. Please give https://github.com/ValveSoftware/Proton/wiki/For-AMD-users-having-issues-with-non-OpenGL-games a read.
The extended system information tool tries to use both the 32 bit and 64 bit variants of those libraries, one which silently works and the other is expected to harmlessly fail.
I would like to give it a try, but I am running into the problem that the file /etc/default/grub does not exist.
I ran the following to see if grub would be in a different location, but I don't know if this would be a valid file to edit:
$ sudo find / -iname grub
/usr/lib/recovery-mode/options/grub
it looks like Pop OS does not use GRUB, instead it uses systemd-boot. so the linked guide would need to be updated for that.
The extended system information tool tries to use both the 32 bit and 64 bit variants of those libraries, one which silently works and the other is expected to harmlessly fail.
In my case it isn't one or the other failing, it is both failing.
As the 32 bit lib is addressed by the 64bit system and the 64bit lib being addressed by the 32bit systems.
After a sleep I searched for systemd-boot amdgpu.cik_support=1 I found the following post giving me enough hints to find the file I needed to edit.
$ sudo -s
# cat /boot/efi/loader/loader.conf
default Pop_OS-current
#
This made me dig around a bit more until I found: /boot/efi/loader/entries/Pop_OS-current.conf
I amended this file from:
title Pop!_OS
linux /EFI/Pop_OS-d0bab141-8c68-4922-b302-d6e51d180f2c/vmlinuz.efi
initrd /EFI/Pop_OS-d0bab141-8c68-4922-b302-d6e51d180f2c/initrd.img
options root=UUID=d0bab141-8c68-4922-b302-d6e51d180f2c ro quiet loglevel=0 systemd.show_status=false splash
to
title Pop!_OS
linux /EFI/Pop_OS-d0bab141-8c68-4922-b302-d6e51d180f2c/vmlinuz.efi
initrd /EFI/Pop_OS-d0bab141-8c68-4922-b302-d6e51d180f2c/initrd.img
options root=UUID=d0bab141-8c68-4922-b302-d6e51d180f2c ro radeon.cik_support=0 amdgpu.cik_support=1 quiet loglevel=0 systemd.show_status=false splash
Just altering this file fixes the rendering issues I was experiencing. It would be nice if this could be updated in the article, linked by @kisak-valve in their reply above, to accommodate those who are using systemd-boot instead of GRUB.
However this did not fix steam system information telling me it is mixing up the the 32 and 64 bit vulkan libraries. and thus I see this issue for now as unresolved.
Digging into the issue steam system information shows that "wrong ELFCLASS" errors for both 32 and 64bit vulkan libraries.
This is https://github.com/KhronosGroup/Vulkan-Loader/issues/262. It's harmless.
Closing as fixed in the 1.2.176 vulkan loader.
Your system information
Please describe your issue in as much detail as possible:
Several games seem to run sub-optimal and some windows games run via proton fail to render anything other then the UI (E.G. Taur) or the game is really dark unless ingame items are actively highlighted (E.G. VRChat (desktop mode) having an active mirror in view also allows correct rendering)
Digging into the issue steam system information shows that "wrong ELFCLASS" errors for both 32 and 64bit vulkan libraries.
I expected the correct path for 32bit and for 64bit versions of vulkan libraries to be addressed, this clearly does not happen with an out of the box steam installation.
I had the same issue under Debian 10 just last week.
Steam System Information included: Github Gist
Steps for reproducing this issue: