Black Screen and VAAPI error message on linux mint w/ Quest 2

[kind seal]

Steamr vr appears too track the headset fine on desktop but the screen on the headset is completely black. Without attempting the solution in the linux troubleshooting guide the following logs within the attached text file are produced. When attempting the Solution in the linux troubleshooting guide for a black screen the logs in the attached image are produced, and the desktop view of steam vr shows a void instead of the home even when attempting the advice of typing out the filepath based on the primary location shown within steam's storage settings.

1. Platform: Linux Mint Cinnamon Kernel Version 6.8.0-39
2. Quest 2 System version 51062550068500150
3. Installation method: Linux tar.gz
4. GPU: Arc A750 using kisak-mesa PPA
5. PC

[river plinth]

i think i have the same problem too, but on debian with an Intel igpu and an amd discrete gpu.

[kind seal]

probably not important for the current issue, but for context I just remembered it was trying to run of integrated graphics until I disabled them in bios.

[fair tangle]

First line of the log is Couldn't find VA-API runtime on system, what's the output of vainfo on your system ?

[kind seal]

libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit

[gaunt galleon]

I have the same issue, headset tracks fine on the steamVR preview on desktop but in headset shows black screen. I am using an NVIDIA RTX 3060 GPU and a Ryzen 5 2600 CPU on arch linux.

[river plinth]

...i eventually fixed my issue with having a black screen, i think switching from hevc to h.265 was part of it

i also tried two of the things where you put something into the launch options in steam; im not 100% sure if both or even either of them were necessary

specifically i did the DRI_PRIME=1 thing and the "launch the vrmonitor.sh found in xyz directory before you start steamvr" thing

... and for a little more context my laptop seems to have a hybrid gpu setup where the discrete gpu has to go through the igpu to do things

which seemed like it was probably the cause of my issue for a while, and might still be causing other issues

....

and i did the thing where i mix up h.264 and h.265 again

i meant h.264

the older one

the one that's not hevc

[river plinth]

...i tried?

and then it seemed to not work and then honestly idk what happened in between that and switching (back) to h.264 anymore

i put DRI_PRIME=1 in between the vrmonitor thing and %command%

...i didn't really find anything telling me how to use that part of the launch options this way with more than one thing

and it still affects the %command% at the end?

yeah

i figured

huh

i would have thought that it would still work the same the way i did it then probably

idk though

right now what i have to deal with is really bad performance (apparently my gpu is just severely underpowered), the steam menu thing that pops up when you press the menu button on your controller being garbled, and having the same button for the steam menu and the in game menu in the game i wanna play (which is obviously unrelated. probably.)

... is alvr also made to work with anything other than steam vr?

although that's probably not a question for this thread lol

....... and the answer is the literal first thing in the faq

lol

[crimson iron]

replace path here with one that is valid on your own system, this one is for flatpak

the QT_QPA_PLATFORM part is for making wayland work, if u run x11 u dont need

[crimson iron]

resize the steam window and the garbling goes away - its a steam bug with browser and nvida/wayland

[river plinth]

!

like

after i open steamvr?

[crimson iron]

happens with regular steam as well

i dont usually see it in vr, only on desktop

are you using laptop as well?

seems we have problem making alvr use the nvidia gpu

[river plinth]

i am using a laptop, but the laptop had an amd gpu

[crimson iron]

ok maybe not specific nvidia problem - but we haev problem making alvr use the right gpu

other users report it works fine for other steam games, but not with alvr - its using the igpu instead which sucs

[river plinth]

yeah

my laptop has a hybrid gpu

and in the bios there's only the options to use a hybrid gpu or just use the igpu

but under s specific name

"unified memory access" i think but just as an acronym

...i kind of wonder if it would work better to use that and then try to use the discrete gpu from in the operating system, at least since I'm not directly outputting a video signal to a monitor?

and also i kept getting "there is no entry point for (name of video encoding), you might not have hardware video encoding" or something similar

[crimson iron]

i dont think u can disable it on the laptop

file bug report and provide as much info as possible, you are not only person reporting this problem with hybrid graphics

yes you can run with the igpu but teh performance is so poor it counts as not working

[kind seal]

After a fresh install I noticed the vainfo Error starts as soon as I disable integrated graphics in BIOS, I used the steps at https://dgpu-docs.intel.com/driver/client/overview.html to try and install any driver packages i may have been missing and vainfo seems to be working properly now, I have not yet tested whether this changes the outcome on my headset or in the ALVR logs.

Edit: tried installing steam and something I did is causing issues with it.