#SteamVR cannot detect my Quest 2 : "Please plug in your VR headset" message

125 messages ยท Page 1 of 1 (latest)

tender silo
#
  1. Platform: Linux - Garuda (Arch)
  2. Headset : Quest 2
  3. Installation method: package manager
  4. GPU: Nvidia RTX 3060 driver version: 555
  5. Laptop with iGPU
  6. Alvr logs: - attached
  7. session.json configuration file from alvr folder: - attached
  8. vrserver.txt file: - attached

Notes: ALVR doesn't detect my headset automatically and even when I put in the IP from the quest app manually, they indicate "Disconnected" and "Unknown IP". Firewall rules are supposedly implemented.
The "alvr_server" also doesnt seem to apear in the "manage add-ons" tab, neither in the "vrserver.txt" file.
Someone said to use the command: ls /dev/hidraw* then plug/unplug the headset and run again to see which one is it, and then run some commands:||sudo chmod g+rw /dev/hidraw5 /dev/hidraw6 /dev/hidraw8 /dev/hidraw9 /dev/hidraw10 /dev/hidraw11; sudo chgrp <username> /dev/hidraw5 /dev/hidraw6 /dev/hidraw8 /dev/hidraw9 /dev/hidraw10 /dev/hidraw11|| but the thing is nothing new appears for me, no matter the cable type or the port.

I hope this information suffice, but if not, tell me and I will add what is necessary.

tender silo
#

I thought it was the same trouble shooting from the official site but it turns out this one is for linux specificaly, hmm. I m checking it out rn, but the discrete Hybrid graphics advices section, I have already done that because it was advised by the logs i have also posted.

#

so, i try going to the bios and switch to only discrete GPU and uuhm, reinstaling ALVR from somewhere else?

tender silo
#

I would bet on the drivers but if thats not it idk what else

#

sorry im new to Linux and stuff, can you explain "tdp issues" and "env variables"

#

i think i saw a Vrmonitor folder somewhere when i was thinkering

#

ok

#

yea, ok, sorry ive been doing this all day, and its just too much info ๐Ÿ˜…

#

still no idea about the second one, but thanks a lot!

#

" ~/.local/share/Steam/steamapps/common/SteamVR/bin/vrmonitor.sh %command% " so I place this in the startup arguments

tender silo
#

just slap them next to eachother?

#

or shall I try those with just the discrete GPU on?

#

this way it wont need the first line

tender silo
#

so here they mention a premmision issue

#

i found this pin to be similar

#

oh

#

thats the thing

#

oh

#

no like i meant whenever i plug the headset

#

the result from the ls /dev/hidraw command does not change

#

does this mean its not detecting the headset

#

or is it unrelated

#

i see

#

sorry for the dumb questions

#

alright

#

this changed something

#

but now because i deleted the first argument line for the hybrid compat this shows error

warm cradle
#

This might be a stupid question; you have enabled proton right?

tender silo
#

the forced use in compatability tab?

warm cradle
#

The general steam setting for using proton for steam games

#

I had a buttload of problems when i tried to enable a specific proton layer for steam vr

tender silo
#

I usually check this to run most games and it runs with the experimental proton

#

but when i tried it here it didnt even run so i reverted

warm cradle
#

Yea doing that on steam vr will mess some things up in my experience

#

And just for sanity here; You are trying to run Steamvr through the alvr app?

#

Not just pressing play in steam

tender silo
#

after the 2nd run this changed

tender silo
#

now im gonna run ALVR

warm cradle
#

Yea because running steamvr through alvr is kind of required for it to pick up the simulated headset

tender silo
#

cuz i know its not gonna work from just steam

#

yea

warm cradle
#

Ah good ๐Ÿ™‚

tender silo
#

ik im dumb but im learning ๐Ÿ˜…

warm cradle
#

I mean your doing better than i did when trying this stuff

#

I mean ive had that a few times when my desktop gets screwy. Something about running kde on pop os sometimes makes the whole thing a bit unstable graphics wize

tender silo
#

some stuff worked

warm cradle
#

It looks like mine does before i connect the headset

tender silo
#

it keeps reconecting and disconecting tho

warm cradle
#

Wait yea that error in the bottom of alvr

#

that is not how mine runs

tender silo
#

oh wait

#

im dumb

#

nvm

#

still reconnecting like crazy

warm cradle
#

Sorry this is above my paygrade

tender silo
#

there might be some sensiteve stuff here but meh

#

says broken pipe

warm cradle
#

INah, no sensitve stuff. but above my paygrade, with the handshake errors and os error stuff

tender silo
#

os error 32

#

more reaserch

#

yay...

warm cradle
#

Good luck. Looks like a headache and a half to me

tender silo
#

yeah, sorry ๐Ÿ˜…

#

yeah i had to remove the line that fixes the hybid graphics to add the one for the vrmonitor

#

idk how to keep both

#

but i have added the rules

#

should i try disabling it completely?

#

ok let me try

#

sigh

#

now its the GPU right

#

yeah

#

its using the intel gpu

#

any idea how can i combine those 2 command argument?

#

I feel like this is gona be the end solution

#

ooh so waht u said to me in the beginning

#

i just didnt understand it

#

i still only partialy do tho

#

__GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json ~/.local/share/Steam/steamapps/common/SteamVR/bin/vrmonitor.sh %command%

#

something like that?

#

so it kinda worked

#

no i see mountains and stars on my quest

#

there is still that tho

#

i tought i had CUDA

warm cradle
#

nvidia-smi <- in console to check cuda

tender silo
#

yep

warm cradle
#

plyshka is probably right about this being a hybrid graphics thing ๐Ÿ˜›

tender silo
#

yeah that hybrid thing was sucha pain in the ass when i was just getting into linux

#

which was a month ago but anyway

#

so only the env variables

#

start steam with that argument

#

how exactly

#

its probably simple but i kinda used up all my brain cells today

#

oh

#

wait

#

found it

#

here right

tender silo
#

why would i need to run the steam with it tho?

#

nope, logs are the same

#

it works tho, kinda

#

how do i run a game on it lol

#

i never thought i would go so far XD

tender silo
#

alright, shall we close this as partially solved?

#

let me just put a summary

#

TLDR: put this in SteamVR->properties->General->Launch Options ||GLX_VENDOR_LIBRARY_NAME=nvidia NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json ~/.local/share/Steam/steamapps/common/SteamVR/bin/vrmonitor.sh %command%|| and entirely disable your firewall only until it runs normally for the first time.

#

IDK if "VK_ICD_FILENAMES" is necessary but im just gonna leave it there bec the logs say so
Also its more likely to run without any errors if you switch to "discrete GPU only" from BIOS. I believe this also removes the need for the first half of the argument above.(aka start from ~/.local...)

tender silo
#

try this one

#

try without the VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json if it doesnt work

harsh ocean
#

i appreciate that! its ok though my alvr works now!

tender silo
#

wait

#

i tagged the wrong person XD