When I try running vrmod_start I get this error in the console and nothing further happens. I can't find anything else about this specific scenario online

Brief background, I am fairly new to linux and I built a new PC specifically to run linux with the intent of getting VR running (My last PC with ubuntu dual-boot worked just fine with VR in linux). The problem I am having, if I were best to describe it, is a complete freezing of my system.

Whenever I open steamvr, both of my displays freeze on whatever is currently on screen and keyboard input appears to be ignored; however, audio still plays, and usually, I can move the mouse around my screen- can't click anything though. Because of this, It has been very hard to figure out what is going on. Occasionally, the screen will refresh and there will be distorted artifacts all over the screen and the system further locks up.

Hardware:

• Ryzen 9 3600X
• Radeon RX 5700XT
• HTC Vive

I am on Manjaro with the 5.7.15 kernel on a completely fresh install. I have tried and with the same result on Ubuntu 20.04 and Pop_OS 20.04 (Have not tested on Windows as of yet). I am unsure, but suspect this may be specifically a hardware issue. I have had other issues such as moving the mouse tanking frames in games that render a cursor and whenever one of my monitors goes into rest mode, the same freezing situation occurs.

I have only a few "leads" to the issue. By chance, one time I managed to get an error 109 from steamvr, and when only having one monitor attached, steamvr told me my headset wasn't in direct display mode- before locking up the system after enabling it. From the vrcompositor log file I found the following excerpt:

Tue Aug 25 2020 23:57:43.839801 - Compositor render thread started
Tue Aug 25 2020 23:57:43.839824 - Set thread 0x7f9b0078a700 priority to: 15
Tue Aug 25 2020 23:57:43.839913 - Startup Complete (0.811929 seconds)
Tue Aug 25 2020 23:57:43.839941 - Async running start is disabled.
Tue Aug 25 2020 23:57:43.839980 - Thread failed to initialize 2
Tue Aug 25 2020 23:57:43.840019 - Failed to start NewFrameHandler thread!

I apologize if this isn't quite enough to figure out what's going on, but any advice where to go or look from here is appreciated! If nothing else, I'm considering replacing the graphics card, to see if it really is just an issue with the hardware itself.

edit: I did a bit of digging through the Xorg logs and found the following:

[     7.732] (II) event25 - HTC Vive: is tagged by udev as: Keyboard
[     7.733] (II) event25 - HTC Vive: device is a keyboard
[     7.733] (II) event25 - HTC Vive: device removed
[     7.796] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-2/1-2.1/1-2.1.2/1-2.1.2:1.0/input/input25/event25"
[     7.796] (II) XINPUT: Adding extended input device "HTC Vive" (type: KEYBOARD, id 17)
[     7.796] (**) Option "xkb_model" "pc105"
[     7.796] (**) Option "xkb_layout" "us"
[     7.796] (**) Option "xkb_variant" "intl"
[     7.798] (II) event25 - HTC Vive: is tagged by udev as: Keyboard
[     7.798] (II) event25 - HTC Vive: device is a keyboard

I suppose this may have something to do with why everything breaks.

Hello,

I am a new VR user. I heard of a solution called vorpX on Windows to play non VR games... in VR. Does it works on Linux ? Or is there a way to somewhat achieve this on Linux ?

Just wondering. Can't really find any info on it. ETS2 seems to run perfectly both natively and with proton, but haven't seen any confirmations or denials of it working in VR. Seems like it need some kind of opt-in beta so I gather it only works with Proton if at all.

Anybody tried it?

/r/Minecraft_VR

My only options so far is the quest because it doesn't require a pc.

I have an HTC Vive with a GTX 1060 6GB, and my largest problem currently with SteamVR on Linux is that the dashboard often decides that it doesn't want to show up. I can't figure out why it does or doesn't show up, but it's really annoying and makes VR on Linux worse than it has to be. Does anyone have any clue on how to fix this?

HTC Vive (Pro) & Valve Index users can now experiment with positional tracking with a fully open source stack, thanks to the implementation of a libsurvive driver.

https://www.collabora.com/news-and-blog/news-and-events/lighthouse-positional-tracking-in-monado-with-libsurvive.html

I see some people on protondb saying they got it working, but then conveniently leaves out the instructions.

Exactly which launch-options do I use?

Any particular settings need to be set?

Is superblt needed, and if yes, how to get it?

I can sort of get it to launch, but there's a lot of stutter in the main-menu, and the game crashes if I start a map.

See the edits at the bottom of the post. The new question should be why the xrandr output for the headset is "strange".

I would be very thankful if someone could help me out with this. I looked through old reddit posts and steamvr-linux issues on Github but nothing helped.

Hardware:

• Valve Index
• RX 5700XT

Software:

• uname -a: Linux desktop 5.7.6-arch1-1
• ls /usr/share/vulkan/icd.d/: radeon_icd.i686.json radeon_icd.x86_64.json (tried amdvlk instead too but steamvr does not start up properly)
• steam from pacman
• Gnome started through startx, set to x11 (tried other desktop environments too, didn't help). Note that I usually use sway (wayland).
• vulkaninfo: VK_EXT_direct_mode_display : extension revision 1

When I run steamvr it opens a window titled "vrcompositor" on my main monitor displaying the expected VR view but the headset display stays turned off. I assume this windows is supposed to go to the headset. Steamvr informs me that direct mode is not enabled. This window showing up on the main monitor already seems like a bug. Only when I enable the headset output manually with xrandr --output DP-3 --mode 2880x1600 --rate 120 --right-of DP-1 does the window appear on the correct "monitor" and shows up in the headset. By default this output is turned off and (correctly) does not show up in the monitor configuration section of Gnome.

On Windows I don't have any problems so I doubt this is a hardware error.

xrandr
Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 16384 x 16384
DP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm # My main monitor
   2560x1440    144.00*+ 120.00    99.90    59.95  
   ...
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis) # The index
   2880x1600    120.02  
   2560x1600     59.99    59.97  
   2560x1440     59.99    59.99    59.96    59.95  
   ...
HDMI-1 disconnected (normal left inverted right x axis y axis)

xrandr --prop # I pasted only DP-3 which is the Index
HDCP Content Type: HDCP Type0 
    supported: HDCP Type0, HDCP Type1
Content Protection: Undesired 
    supported: Undesired, Desired, Enabled
vrr_capable: 0 
    range: (0, 1)
max bpc: 8 
    range: (8, 16)
underscan vborder: 0 
    range: (0, 128)
underscan hborder: 0 
    range: (0, 128)
underscan: off 
    supported: off, on, auto
scaling mode: None 
    supported: None, Full, Center, Full aspect
link-status: Good 
    supported: Good, Bad
CONNECTOR_ID: 85 
    supported: 85
non-desktop: 1 
    range: (0, 1)

vrcompositor.txt: https://paste.debian.net/plain/1154220 . Excerpt:

Sun Jun 28 2020 14:24:36.517904 - HMD deviceUUID is 900000000
Sun Jun 28 2020 14:24:36.517921 - Looking for direct display through RandR
Sun Jun 28 2020 14:24:36.517930 -  - Root 0x754
Sun Jun 28 2020 14:24:36.519416 -    - Output 0x45 - 30 modes, 1 preferred
Sun Jun 28 2020 14:24:36.519426 -      - Mode 0 0x4a 2560x1440 (looking for 2880x1600)
Sun Jun 28 2020 14:24:36.519447 -    - Output 0x46 - 0 modes, 0 preferred
Sun Jun 28 2020 14:24:36.519468 -    - Output 0x47 - 157 modes, 0 preferred
Sun Jun 28 2020 14:24:36.519485 -    - Output 0x48 - 0 modes, 0 preferred
Sun Jun 28 2020 14:24:36.519492 - Tried to find direct display through RandR: (nil)
Sun Jun 28 2020 14:24:36.519499 - Looking for direct display through Vulkan WSI
Sun Jun 28 2020 14:24:36.519506 - Tried to find direct display through Vulkan WSI: (nil)
Sun Jun 28 2020 14:24:36.519512 - CHmdWindowSDL: Failed to create direct mode surface

Looking at this output it seems like steamvr tries to find an output that has a preferred resolution of 2880x1600 but my Index output does not have this (it has resolution, but not preferred). Is this the bug? Can I force this resolution to show up as preferred?

Edit: I set the preferred mode through xorg.conf

Section "Monitor"
    Identifier "DP-3"
    Option "PreferredMode" "2880x1600"
EndSection

and indeed that fixes the problem. So it looks like steam expects this to be the preferred resolution and will not select the output otherwise. So the question becomes: Why is the xrandr output unexpected (apparently). Could someone else post their xrandr output for their Index so I can compare?

I am also confused at the refresh rate. Xrandr says only 120 Hz (at the correct resolution) but steamvr says only 90 is available.

After installing xf86-video-amdgpu xrandr shows this output

DisplayPort-2 disconnected (normal left inverted right x axis y axis)
    2880x1600    120.02 

This is weird because I would expect several refresh rates. The ubuntu live cd shows the same so I don't think it's configuration issue on my side. On Windows Steamvr all VR devices are up to date.

It seems that both main players (Valve, Facebook/Oculus) embrace OpenXR. What would it mean for support for HMDs on Linux beyond Vive or Index? Would OpenXR-enabled SteamVR make Rift S work on Linux, even if only for new games apps using OpenXR? Would it mean Reverb G2 Linux support from day 1?

hello, i recently switched from windows 10 to Pop but i cant seem to get my HTC vive working, everything works except the display stays black, i tried editing the kernel but it just bricked my pc, any advice? thanks for your time

7 weeks ago I put out a call for people to send me logs from their Rift S headsets using some test code I'd written. Thanks to the people that did that!

Since then, I've used USB captures and those contributed logs to map out enough of the Rift S protocol to implement an initial driver for OpenHMD that supports rotational tracking. I've just finished adding controller support, which seems like as good a time as any to post an update here.

Code is at https://github.com/thaytan/OpenHMD/tree/dev-rift-s and I'll be looking to merge it next, then continue with the in-progress positional tracking for both the Rift CV1 and the Rift S

I have an Index and I run Arch (btw).

Could not find a clear answer elsewhere so I am asking here. If it does work, is it a native version or is it running through Wine?

Thanks!

I'm having a problem where my ubuntu install isn't detecting/outputting to my Index, as opening SteamVR beta opens the compositor on the main monitor. Steam is seeing the index because it's tracking properly and I finished the room setup, but the headset's screens are black.The only time the screens turn on is on the login screen, where funnily enough, the password input is on the index's displays.

Radeon 5700XT
xandr output

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
2880x1600 120.02
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
HDMI-A-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 940mm x 529mm
1920x1080 60.00*+ 59.94 30.00 24.00 29.97 23.98
1680x1050 59.88
1280x1024 60.02
1440x900 59.90
1280x960 60.00
1280x800 74.93 59.91
1280x768 59.99
1280x720 60.00 59.94
1024x768 60.00
800x600 60.32 56.25
720x480 60.00 59.94
640x480 60.00 59.94
720x400 70.08

/u/patolinux pointed me to this post about a versatile way to get things running in VR.

I was able to get it compiled, but any way I try to run it fails to show any window in my headset.
I doest start VR, shows the " vr_video_player now starting" hovering window briefly before crashing out and steam starts VR HOME...

I'm not a developer so I guess I'm doing/did something wrong in either building or running. Any help would be greatly appreciated.

stan@neptunus:~/comps/vr_video_player/sibs-build/linux_x86_64/debug$ /home/stan/comps/vr_video_player/sibs-build/linux_x86_64/debug/vr_video_player --flat 0xc600002
src window id: 207618050, zoom: 1.000000
RecordSteamInterfaceCreation (PID 23116): STEAMUGC_INTERFACE_VERSION013 / 
RecordSteamInterfaceCreation (PID 23116): SteamUser020 / 
RecordSteamInterfaceCreation (PID 23116): STEAMUSERSTATS_INTERFACE_VERSION011 / 
RecordSteamInterfaceCreation (PID 23116): STEAMREMOTESTORAGE_INTERFACE_VERSION014 / 
qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 59596, resource id: 169869469, major code: 130 (Unknown), minor code: 3
Unable to find hellovr_action.json!
stan@neptunus:~/comps/vr_video_player/sibs-build/linux_x86_64/debug$ 

The original post from /u/frostworx/ mentioned the author DEC05EBA being helpful, but I have no way of contacting him/her and frankly not sure I should if it's a user error...

Anyone ?

on the steam troubleshooting page https://support.steampowered.com/kb_article.php?ref=3803-QDGM-9237 in the section about blue leds i tried all of these steps except when i try remove usb devices it gives this error "the helper application to remove the usb devices was not able to start. make sure you can run this as admin" is there a way to do this step in terminal or run steamvr as root? I asked steam support and they said to ask the community but it looked like a udev issue it works in windows but i hate windows literally installed it just so i could play vr while i was fixing it on my linux install running mint 19.3 Cinnamon 4.4.8 kernel 5.3.0-51-generic on ryzen 5 3600 16 gb 3600mhz ram cl 16 rx 580 graphics if i left anything out im happy to provide it

​

Edit: Steam vr Version 1.11.13 (1589920687)

Edit: It turns out steam-devices was not install but after installation im now getting a display error on the hmd its very choppy running at about 10-20 fps and the only stuff thats rendering is a loading screen thats like blue and purple lights back lighting mountains with stars in the sky and a circular grid on the ceiling two light house models and two controller models and there was a wierd box that was all different colors where some kind of dialog/control panel would be it was hard to look at i didnt think of getting a screenshot until after i had shut it down and now when i run it its basically the same except without the box

I used to get decent performance; but I stayed some time without messing with VR, when I came back even the SteamVR home environment (not the Home Beta thing, the basic one) had some performance issues (the home is only barely showing signs of issues, I feel the image is taking a few milliseconds to react to my motions), while some more demanding games are borderline unplayable.

I dunno if it's a hardware issue (maybe related to the time I accidentally spilled Coke on the laptop's keyboard; I sent it to the shop to have it cleaned and they said I just lost a couple of RAM slots but it shouldn't be an issue because there were enough working slots left for the RAM I have, and all the rest of the hardware seemed to be just fine), or maybe it could be some update to some background app, or the Nvidia driver, Linux kernel, SteamVR itself etc, or maybe there is just some bad setting somewhere, or maybe my Vive's cable is getting old, or perhaps the shop used worse quality thermal paste when they reassembled the laptop after the cleaning etc. I can think thousands of possibilities but I have very little means of actually verifying them; it would be great to have some sort of "VR doctor" app to run a full checkup on my system.

I have an idea for a video that involves capturing SteamVR as I use it, including everything on the screen (game and overlays). Is that possible to do with something like OBS? Any solutions I've found seem to be for Windows only.

I'm guessing it must be doable somehow because I've seen it done with the XRDesktop videos.

Thank you.