Failed to load vulkan loader?

[Boldsama]

so im attempting to run league of legends via lutris and while i can get it to boot, i cant get anything above choppy, stuttering gameplay using nvidias proprietary option in the vulkan ICD loader. im a bit new with lutris and all this so i did lots of digging and i can't find any way to point the ICD loader too the proper thing? ive used the following command to try and force it but saw zero changes.

export VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.i686.json:/usr/share/vulkan/icd.d/nvidia_icd.x86_64.json

im stumped on how to get vulkan to use the right ICD. heres my inxi output

System:
Kernel: 5.15.70-1-lts arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
root=UUID=3b256a22-dfc4-4368-b2cd-a07dceb3840a rw [email protected]
splash amd_iommu_on rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3 vfio-pci.ids= 10de:1b80,10de:10f0
Desktop: sway v: 1.7 info: waybar vt: 1 dm: greetd Distro: Garuda Linux
base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME X370-PRO v: Rev X.0x
serial: UEFI: American Megatrends v: 5220
date: 09/12/2019
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Gaming Mouse
serial: charge: 55% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: AMD Ryzen 7 1800X bits: 64 type: MT MCP arch: Zen level: v3
built: 2017-19 process: GF 14nm family: 0x17 (23) model-id: 1 stepping: 1
microcode: 0x8001138
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 768 KiB desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB desc: 8x512 KiB
L3: 16 MiB desc: 2x8 MiB
Speed (MHz): avg: 3247 high: 3843 min/max: 2200/3850 boost: disabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3081 2: 3079
3: 3084 4: 3075 5: 3077 6: 3231 7: 3080 8: 3843 9: 3078 10: 3089 11: 3076
12: 3229 13: 3080 14: 3172 15: 3843 16: 3843 bogomips: 122973
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT vulnerable
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
disabled, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1080] driver: nouveau v: kernel
non-free: 515.xx+ status: current (as of 2022-08) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-21 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
link-max: gen: 3 speed: 8 GT/s ports: active: DP-3,DVI-D-1
empty: DP-1,DP-2,HDMI-A-1 bus-ID: 0a:00.0 chip-ID: 10de:1b80
class-ID: 0300
Display: wayland server: [X.org](http://X.org) v: 1.21.1.4 with: Xwayland v: 22.1.3
compositor: sway v: 1.7 driver: gpu: nouveau d-rect: 5360x2520
display-ID: 1
Monitor-1: DP-3 pos: primary,top-left model: Acer Z35P serial:
built: 2017 res: 3440x1440 hz: 60 dpi: 107 gamma: 1.2 scale: 1
size: 819x346mm (32.24x13.62") diag: 889mm (35") modes: max: 3440x1440
min: 640x480
Monitor-2: DVI-D-1 pos: bottom-r model: ViewSonic VA2246 SERIES
serial: built: 2014 res: 1920x1080 hz: 60 dpi: 102 gamma: 1.2
scale: 1 size: 477x268mm (18.78x10.55") diag: 547mm (21.5") ratio: 16:9
modes: max: 1920x1080 min: 720x400
OpenGL: renderer: NV134 v: 4.3 Mesa 22.1.7 direct render: Yes
Audio:
Device-1: NVIDIA GP104 High Definition Audio driver: snd_hda_intel
v: kernel pcie: bus-ID: 3-1.3:9 gen: 1 chip-ID: 0d8c:0005 class-ID: 0300
speed: 2.5 GT/s serial: lanes: 16 link-max: gen: 3 speed: 8 GT/s
bus-ID: 0a:00.1 chip-ID: 10de:10f0 class-ID: 0403
Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 0c:00.3
chip-ID: 1022:1457 class-ID: 0403
Device-3: C-Media Blue Snowball type: USB
driver: hid-generic,snd-usb-audio,usbhid
Sound Server-1: ALSA v: k5.15.70-1-lts running: yes
Sound Server-2: sndio v: N/A running: no
Sound Server-3: PulseAudio v: 16.1 running: no
Sound Server-4: PipeWire v: 0.3.58 running: yes
Network:
Device-1: Broadcom BCM4360 802.11ac Wireless Network Adapter
vendor: ASUSTeK driver: wl v: kernel modules: bcma pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 14e4:43a0
class-ID: 0280
IF: wlp6s0 state: up mac:
Device-2: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 08:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp8s0 state: down mac:
Bluetooth:
Device-1: Broadcom BCM20702A0 Bluetooth 4.0 type: USB driver: btusb v: 0.8
bus-ID: 3-1.2:8 chip-ID: 0a5c:21e8 class-ID: fe01 serial:
Report: bt-adapter ID: hci0 rfk-id: 1 state: up address:
Drives:
Local Storage: total: 3.64 TiB used: 586.79 GiB (15.7%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO Plus
1TB size: 931.51 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: rev: 2B2QEXM7
temp: 41.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: rev: 2B6Q scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000LX001-1RG174
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 5400 serial: rev: SDM1 scheme: GPT
Partition:
ID-1: / raw-size: 914.11 GiB size: 914.11 GiB (100.00%) used: 298.6 GiB
(32.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 27.2 MiB
(9.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 914.11 GiB size: 914.11 GiB (100.00%) used: 298.6
GiB (32.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 914.11 GiB size: 914.11 GiB (100.00%) used: 298.6
GiB (32.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 914.11 GiB size: 914.11 GiB (100.00%) used: 298.6
GiB (32.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.55 GiB used: 2.5 MiB (0.0%)
priority: 100 dev: /dev/zram0
ID-2: swap-2 type: partition size: 17.11 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
System Temperatures: cpu: 34.9 C mobo: N/A gpu: nouveau temp: 38.0 C
Fan Speeds (RPM): N/A gpu: nouveau fan: 1192
Info:
Processes: 317 Uptime: 7m wakeups: 2 Memory: 15.55 GiB used: 2.05 GiB
(13.2%) Init: systemd v: 251 default: graphical tool: systemctl
Compilers: gcc: 12.2.0 Packages: pm: pacman pkgs: 1475 libs: 453
tools: pamac,paru Shell: fish v: 3.5.1 default: Bash v: 5.1.16
running-in: alacritty inxi: 3.3.21
Garuda (2.6.7-1):
System install date: 2022-09-22
Last full system update: 2022-09-27
Is partially upgraded: No
Relevant software: NetworkManager
Windows dual boot: Probably (Run as root to verify)
Snapshots: Snapper
Failed units:

[filo]

@Boldsama

using nvidias proprietary option in the vulkan ICD loader

@Boldsama

Device-1: NVIDIA GP104 [GeForce GTX 1080] driver: nouveau v: kernel

I'm not able to help with gaming, but for sure at the moment you're using the kernel module not the proprietary driver for the Nvidia GPU, although It seems to be available, but not loaded.
How did you install it?
Maybe you could try reinstalling with the HW assistant (Garuda Welcome - > Garuda Settings Manager - > Hardware Configuration) and provide any error messages that might be given.

[Boldsama]

sorry for the late reply i had a nightmare using the dkms install, i couldnt get the driver too launch no matter what i did which caused the display manager to not work. i just tried the nvidia-lts package and while i did get that too boot, i still have the issue of no vulkan loader. i still appear to be loading in with the nouveau driver.

[Boldsama]

how could i make sure im loading the correct up to date nvidia driver? dkms seems too mess up somewhere in the install but still succeed.

[Boldsama]

Update, I installed nvidia-dkms and now the systems DM won’t start. I logged into a tty and started sddm and was able to be greeted and logged in, but it still sits on a black screen. I’m starting to give up on nvidia and wayland. What can I do to get sway to use the nvidia drivers or should I just stick with open source and dual boot for games I get poor performance on.

i have since restored too before i installed the dkms package.

[BluishHumility]

@Boldsama

I logged into a tty and started sddm

Wait, whaaat? You started SDDM on your Sway install?

@Boldsama

I’m starting to give up on nvidia and wayland.

Actually, Nvidia+Wayland has come a long way compatibility-wise. At least some of the grief you are experiencing is due to how incompatible Nvidia is with Sway, not Wayland. Nvidia is beyond unsupported; they are borderline hostile toward proprietary driver use. From the Sway GitHub page:

Before installing

Nvidia users

All proprietary graphics drivers are unsupported. This includes the Nvidia proprietary driver. The open source Nouveau driver can be used instead. Tip: buy your hardware with open source support in mind.

It is still possible to get Sway working on certain Nvidia hardware, but it requires extra legwork and you need to pass intentional flags when you launch the session. This is from the Sway ArchWiki page:

Note: All proprietary graphics drivers are not supported, including NVIDIA. After NVIDIA driver version 495, sway works if you enable kernel mode setting and run sway with --unsupported-gpu.

The --unsupported-gpu flag used to be --my-next-gpu-wont-be-nvidia. I guess they have decided to tone it down some.

To enable kernel mode setting, add nvidia_drm.modeset=1 to the GRUB_CMDLINE_LINUX_DEFAULT= line in /etc/default/grub.

To launch Sway with the special Nvidia flag of shame, add it to your greetd config.

sudo micro /etc/greetd/config.toml

It should look something like this:

[terminal]
vt = 1
[default_session]
command = "tuigreet --r --cmd 'sway --unsupported-gpu'"
user = "greeter"

I just copied mine as an example, and I'm realizing I switched from qtgreet to tuigreet a while ago, so yours likely looks a little different. The important thing is to change "sway" to "'sway --unsupported-gpu'"--make sure it is enclosed in single-quotes. You can leave the rest of the file alone.

Hopefully that will get you up and running. I honestly can't say if that will be the end of your grief or not because you are trying to run a very unsupported hardware/software combination.

[Boldsama]

I’ll make some back ups tonight and certainly try dabbling in black magic, I just wanna play league without switching OS, if I had a dual GPU system I would just black list the Beefier one for the VM.