You are not logged in.
Recently I was going through my Lutris game configs and I realized it said "Error: Vulkan is not installed or is not supported by your system." This came completely out of nowhere and it had not said that before. On top of that, other games which used to run no problem now started to crash or have serious FPS issues. I ran vulkaninfo to check what was happening and got:
SOLUTION: The solution for me was adding myself to the vglusers group. Not sure why I wasn't in this group, not sure what the group even is, and I'm not sure why it became an issue out of nowhere, but it's fixed. Thanks to everyone for the help
$ vulkaninfo
ERROR: [../mesa-24.1.2/src/amd/vulkan/radv_physical_device.c:1929] Code 0 : Could not open device /dev/dri/renderD128: Permission denied (VK_ERROR_INCOMPATIBLE_DRIVER)
ERROR: [Loader Message] Code 0 : setup_loader_term_phys_devs: Failed to detect any valid GPUs in the current config
ERROR at /usr/src/debug/vulkan-tools/Vulkan-Tools-1.3.269/vulkaninfo/./vulkaninfo.h:237:vkEnumeratePhysicalDevices failed with ERROR_INITIALIZATION_FAILED
I saw it said "permission denied," so I ran it with sudo and it worked as intended. vkcube also threw an error when I ran it as myself, but worked perfectly fine as sudo. Same with the other games that stopped working.
EDIT: Programs launched as sudo also have the sound come out of my monitor? Which has never happened before and I didn't even know my monitor had speakers.
Is there any way to fix this?
I have a Radeon Pro WX 3200 with (lib32-)vulkan-radeon and amdgpu using Xorg. My kernel is 6.9.7-arch1-1
lspci -k output:
61:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 3200] (rev 10)
Subsystem: Lenovo Device 104c
Kernel driver in use: amdgpu
Kernel modules: amdgpu
61:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X]
Subsystem: Lenovo Device aae0
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
ls /usr/share/vulkan/icd.d :
$ ls /usr/share/vulkan/icd.d
intel_hasvk_icd.i686.json intel_icd.i686.json radeon_icd.i686.json
intel_hasvk_icd.x86_64.json intel_icd.x86_64.json radeon_icd.x86_64.json
pacman -Q | grep vulkan :
$ pacman -Q | grep vulkan:
lib32-vulkan-icd-loader 1.3.279-1
lib32-vulkan-intel 1:24.1.2-1
lib32-vulkan-mesa-layers 1:24.1.2-1
lib32-vulkan-radeon 1:24.1.2-1
vulkan-extra-layers 1.3.250.0-1
vulkan-extra-tools 1.3.250.0-1
vulkan-headers 1:1.3.285-1
vulkan-html-docs 1:1.3.279-1
vulkan-icd-loader 1.3.285-1
vulkan-intel 1:24.1.2-1
vulkan-mesa-layers 1:24.1.2-1
vulkan-radeon 1:24.1.2-1
vulkan-tools 1.3.269-1
vulkan-utility-libraries 1.3.273-1
vulkan-validation-layers 1.3.275-1
pacman -Q | grep video:
$ pacman -Q | grep video
xf86-video-amdgpu 23.0.0-2
xf86-video-ati 1:22.0.0-2
Last edited by tibamita (2024-07-03 18:44:45)
there is beauty and magic in the air
Offline
The importart part of the error is likely not permission denied, but VK_ERROR_INCOMPATIBLE_DRIVER .
vulkan-intel 1:24.1.2-1
Is there an intel gpu in your system ?
If not, remove vulkan-intel and lib32-vulkan-intel .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
No I don't have any intel cards I'm honestly not sure why I have the drivers lol. After uninstalling them I'm still having the same issue though.
The importart part of the error is likely not permission denied, but VK_ERROR_INCOMPATIBLE_DRIVER .
The thing is, I only get that error when not root. If I run with sudo it detects my GPU no problem. Here's the vkcube output with and without sudo:
Without:
$ vkcube
vkEnumeratePhysicalDevices reported zero accessible devices.
Do you have a compatible Vulkan installable client driver (ICD) installed?
Please look at the Getting Started guide for additional information.
With:
$ sudo vkcube
Selected GPU 0: AMD Radeon Pro WX 3200 Series (RADV POLARIS12), type: DiscreteGpu
there is beauty and magic in the air
Offline
That suggest the permissions on your /dev/dri folder may be wrong, (which is surprising as the entries there are supposed to be recreated at every boot)
Please post the output of
$ ls -l /dev/dri
$ stat /dev/dri/renderD128
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
ls -l /dev/dri
$ ls -l /dev/dri
drwxr-xr-x 2 root root 80 Jul 2 03:13 by-path
crw-rw----+ 1 root vglusers 226, 1 Jul 2 03:13 card1
crw-rw---- 1 root vglusers 226, 128 Jul 2 03:13 renderD128
stat /dev/dri/renderD128:
$ stat /dev/dri/renderD128
File: /dev/dri/renderD128
Size: 0 Blocks: 0 IO Block: 4096 character special file
Device: 0,6 Inode: 575 Links: 1 Device type: 226,128
Access: (0660/crw-rw----) Uid: ( 0/ root) Gid: ( 1003/vglusers)
Access: 2024-07-02 03:13:35.741328137 -0400
Modify: 2024-07-02 03:13:35.741328137 -0400
Change: 2024-07-02 03:13:35.741328137 -0400
Birth: 2024-07-02 03:13:33.927994817 -0400
there is beauty and magic in the air
Offline
Why did you install https://wiki.archlinux.org/title/VirtualGL ?
What's the context here? Is this a virtual machine?
Offline
This is my main bare metal machine. I honestly have no clue what VirtualGL is and after checking pacman -Q it seems I don't have it installed on my system. But, I have tried to use programs like NoMachine to try and set up X forwarding to my laptop, though I uninstalled it and now just use ssh -X. Should I be a member of the vglusers group? I never even knew that group existed.
In case it matters, here are the groups that I'm in:
$ groups ruby
sys network power wheel optical rfkill video storage audio users scanner lp informant ruby
EDIT: after adding myself to the vglusers group everything went back to normal. I don't understand why and would love an explanation if anyone has one. Hopefully anyone else having this issue is able to find this
Last edited by tibamita (2024-07-03 18:42:45)
there is beauty and magic in the air
Offline
NoMachine sets up an udev rule that forces the permissions and doesn't clean it up if you uninstall, there was a case with this a few months ago: https://bbs.archlinux.org/viewtopic.php … 6#p2153376
Offline
Ohhh, thank you! It's all making sense now. Can't believe NoMachine doesn't clean up after itself when you uninstall that's some bs.
there is beauty and magic in the air
Offline