[BUG] SteamVR Display Output goes to Monitor instead of Index

[openyk]

Describe the bug Upon starting SteamVR, the VR scene is rendered in a window on the monitor instead of the HMD. The Valve Index HMD display remains black.

To Reproduce Steps to reproduce the behavior:

1. Open SteamVR

Expected behavior The SteamVR default 3D visual scene outputs to the Valve Index HMD.

System Information (please complete the following information):

• Distribution: Debian Testing with Linux Kernel 5.10.0-4-amd64
• SteamVR version: 1.16.10
• Steam client version: 2021-02-12
• Opted into Steam client beta?: No
• Graphics driver version: Mesa 20.3.4
• Gist for SteamVR System Information: https://gist.github.com/openyk/6ab284b7f69d7218c803949b9835c164

Screenshots

https://imgur.com/a/nIBUP9V

FYI, the window I've moved to the bottom of the screen is the room setup program popup. Also, I've tried doing it and the default SteamVR 3D room scene with the wooden floors comes up on the monitor as expected.

Additional context This PC is using a fresh install of Debian Testing (dist-upgraded from Stable, as recommended). It didn't work on my main Debian Testing drive so installed the OS again to a separate drive to troubleshoot.

On this PC the HMD display outputs correctly on Windows SteamVR.

On this PC the HMD is not listed under "Settings > Displays".

The HMD display outputs correctly as an extended display on an AMD APU mini-PC.

The HMD display outputted correctly on an older Linux PC when using the same GPU (that PC used Debian Testing, Linux kernel 5.10.0-2-amd64)

The same bug happens when I start SteamVR without the HMD displayport cable plugged in. When I start SteamVR then plug displayport in, no change. When I start SteamVR with displayport in, then unplug it, no change. Of course each time I plug in or out the monitor goes briefly black due to the display IO change. HMD remains continuously black.

Feels like the issue is GPU graphics-driver-related but the fact that it works on Windows and LinuxAPU plus that it worked on the older Linux PC with the same GPU (so this bug is a regressive event in my eyes)... it's strange. I tried to use AMD's GPU driver install script to bolster Mesa (though Mesa should be fine because it worked before on that older PC) but doesn't work for the 5.10+ kernel (https://amdgpu-install.readthedocs.io/en/latest/install-overview.html).

Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.

[kisak-valve]

Hello @openyk, you might be seeing the behavior I see on my VR test box when vrcompositor wrongly uses the Intel chipset to render instead of the AMD chipset that the HMD is attached to. As a quick test, you can check if you have intel_icd.x86_64.json and move it aside with something like sudo mv /usr/share/vulkan/icd.d/intel_icd.x86_64.json /usr/share/vulkan/icd.d/intel_icd.x86_64.json.disabled.

[openyk]

Hey @kisak-valve that makes sense because my old Linux PC used an Intel CPU/chipset (current PC has AMD CPU). Unfortunately disabling the intel json config files did not work.

On the plus side, before I had 3 vulkaninfo errors and now only 1 comes up:

vulkaninfo | grep vulkan
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32

Does that filepath/error seem familiar to you?

[kisak-valve]

That error message is just telling you that the vulkan loader couldn't use the 32 bit radv driver with 64 bit vulkaninfo, which is expected and harmless.

Maybe give #334 a read and see if your experience lines up with the older issue report.

[HadetTheUndying]

I had this issue earlier today and i just ended up unhooking everything and plugging it back in and it resolved the issue.

[melvyn2]

I had this issue since I re-enabled my iGPU, removing the intel-vulkan package solved it.

[cmdrogogov]

I have this issue.

There is no video output to the Index headset whatsoever, and all display output on steamVR goes directly to a non resizable window on the monitor.

Currently running Kernel 5.10.22-200.fc33.x86_64 with mesa 20.3.5-1.fc33 installed. I am using Wayland/Mutter under Gnome however, so most of the X-specific stuff listed in other threads isn't applicable it would seem.

Running on a vega-based AMD card with no problem on traditional monitor apps -

[drm] Initialized amdgpu 3.40.0 20150101 for 0000:04:00.0 on minor 1

When launching Steam VR I get the error message regarding Direct Display mode, then clicking it again results in a crash;

qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Fatal : VkResult is "UNKNOWN_ERROR" in /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp at line 3678
crash_20210331131826_1.dmp[271346]: Uploading dump (out-of-process)

[melvyn2]

Last time I tried SteamVR on Wayland the same issue occured (Plasma/KWin however), so I think that steamvr simply does not support wayland for now.

[HadetTheUndying]

If you're running multiple monitors try unplugging all but one display and the HMD. Also try unplugging and replugging both the DP and USB cables on the headset.

[cmdrogogov]

No joy. I did try signing into an xorg session, and after generating a new xorg configuration it seems insistent on utilizing a different video device, and not amdgpu.

To complicate matters I am running everything in a VM with devices passed through from a hypervisor.

[HadetTheUndying]

To complicate matters I am running everything in a VM with devices passed through from a hypervisor.

You're positive the USB devices passed through correctly?

[cmdrogogov]

Yep - it's something I apparently need to take special care for because if everything is passed through and connected then the hypervisor hardlocks. But that's an issue vmware are utterly disinterested in resolving, and not relevant to this issue.

I managed to get a baremetal installation up and running after a little while and it works more reliably there. I think we must put this down to the difficulty of determining output devices in linux.

I suppose my next step will be to try and get everything in the VM up without the virtualized svga adapter which I think is what is causing the problem here.

[melvyn2]

When running linux directly, did steamvr work during a wayland session?

[HadetTheUndying]

When running linux directly, did steamvr work during a wayland session?

I did not try SteamVR directly because I can't capture Windows in OBS on Wayland right now, but I did try OpenXR with Monado while running a Wayland Gnome session and it was working fine.

[cmdrogogov]

@melvyn2 - no it did not.

[DomiStyle]

Is there any way to resolve this by now? I'm using an AMD GPU without any integrated graphics and I have the same issue.

[melvyn2]

Is there any way to resolve this by now? I'm using an AMD GPU without any integrated graphics and I have the same issue.

are you on wayland?

[DomiStyle]

@melvyn2 Nope, X11.

[HadetTheUndying]

@melvyn2 Nope, X11.

What distribution? Kernel? Druver and Firmware versions?

[DomiStyle]

@HadetTheUndying Ubuntu 21.04, 5.12.0-9.1-liquorix-amd64, Mesa 21.1.2 - kisak-mesa PPA.

Which firmware? GPU or Index? Index is on latest firmware that SteamVR offered me but I updated a long time ago, nothing new since then. GPU firmware is taken from linux-firmware 1.197 package on Ubuntu.

[Scrumplex]

For the people running Wayland. SteamVR itself is running via XWayland there. Currently drm-lease is not supported with XWayland or Wayland in general. There are some ongoing efforts to get this working though. The changes are not ready for prime time yet but if you want to play around see this merge request for official Wayland protocols: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/67

You will need to get a patched version of your Wayland compositor (currently only Sway/wlroots and KWin) and a patched version of XWayland. All of them are linked in the merge request.

[yaomtc]

Does anyone have a PKGBUILD for the patched version of XWayland? I found this, but while XWayland is mentioned in the README here:

https://gitlab.freedesktop.org/lubosz/wlxr-pkgbuilds

I don't see a PKGBUILD for it.

[michaelnew]

@yaomtc try this. I'm not sure how to set the pkver correctly here, because yay always wants to update to the latest commit from the master branch, but otherwise this works for me. I've been able to get SteamVR running with this along with wlroots-git and sway-git.

pkgname=xorg-xwayland-git
pkgver=xorg.server.1.20.0.r1103.g667e180af
pkgrel=1
arch=('x86_64')
license=('custom')
groups=('xorg')
url="https://xorg.freedesktop.org"
pkgdesc="Run X clients under Wayland (git version)"
depends=('nettle' 'libegl' 'libepoxy' 'systemd-libs' 'libxfont2'
         'pixman' 'xorg-server-common' 'libxcvt')
makedepends=('meson' 'git'
             'xorgproto-git' 'xtrans'
             'pixman' 'libxkbfile' 'libxfont2' 'dbus'
             'xorg-font-util'
             'wayland' 'wayland-protocols'
             'libdrm' 'libepoxy'
             'systemd'
             'egl-wayland'
)
source=("xserver::git+https://gitlab.freedesktop.org/Zamundaaa/xserver.git#branch=drm-lease")
sha256sums=('SKIP')
provides=('xorg-xwayland' 'xorg-server-xwayland' 'xorg-server-xwayland-git')
conflicts=('xorg-xwayland' 'xorg-server-xwayland' 'xorg-server-xwayland-git')
replaces=('xorg-server-xwayland-git')

pkgver() {
  cd xserver
  git describe --long 2>/dev/null | sed 's/\([^-]*-g\)/r\1/;s/-/./g' ||
  printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
}

build() {
  arch-meson xserver build \
    -D ipv6=true \
    -D xvfb=false \
    -D xnest=false \
    -D xcsecurity=true \
    -D xorg=false \
    -D xephyr=false \
    -D xwayland=true \
    -D xwayland_eglstream=true \
    -D xwin=false \
    -D xquartz=false \
    -D glamor=true \
    -D udev=true \
    -D systemd_logind=true \
    -D suid_wrapper=true \
    -D xkb_dir=/usr/share/X11/xkb \
    -D xkb_output_dir=/var/lib/xkb

  # Print config
  meson configure build
  ninja -C build
}

package() {

  # bin + manpage + .pc file
  install -m755 -Dt "${pkgdir}"/usr/bin build/hw/xwayland/Xwayland
  install -m644 -Dt "${pkgdir}"/usr/share/man/man1 build/hw/xwayland/Xwayland.1
  install -m644 -Dt "${pkgdir}"/usr/lib/pkgconfig build/hw/xwayland/xwayland.pc

  # license
  install -m644 -Dt "${pkgdir}/usr/share/licenses/${pkgname}" xserver/COPYING
}

[yaomtc]

Installs just fine manually, thanks @michaelnew! I'll test it out once I can get some other *-git packages to install, waiting on a fix for a patch atm so I can use it with Plasma/kwin

[cmdrogogov]

Tested briefly again today. This is still an issue. I am not sure when Fedora will be folding these changes into their distro if ever, and I'm a little reluctant to hose my installation attempting to build the patched version as i'm somewhat out of my depth here.

[AlexRamallo]

This might not that helpful, but I was encountering the exact same symptoms described here, including the message about switching to direct display mode (on a Vive instead of an Index), and it turned out that the HDMI part of the 3-in-1 cable was faulty. Connecting a different HDMI cable bypassed the issue and it worked perfectly on Plasma.

[Bloodninj]

I am also having this issue on a fresh install of Pop!_OS 21.10 with a Radeon 6700XT, although it also happened on the previous 21.04 distro, both with my current card and with a Radeon Vega 56. Both of the cards worked perfectly under Windows 10 2004 onwards. As far as I know, Pop!_OS 21.10 does not use Wayland unless it is specifically enabled in a config file and enabled as a login session, which hasn't been done in my case.

system_report.txt

[asiantuntija]

I've been running sway-git and wlroots-git a long time, occasionally trying to start SteamVR and usually seeing crashing or VR view on monitor. After 1.7-RC1 I figured to try again since release notes say VR should be working now, well it didn't. Found this issue and tried installing xorg-xwayland-git, rebooted and as a big surprise VR was working with my Index. I played around for a while and pretty much everything worked except overlay menus which seems to be another issue.

Later today I figured to try playing again, VR doesn't work again at all. Rebooting, changing display and USB ports, disabling and enabling Direct Display Mode, restarting headset, different versions of SteamVR, reinstalling whole Steam and SteamVR, nothing brings the picture back.

Is there something obvious I'm missing or is the stack still so immature it can't be made work reliably?

edit: Disconnecting HMD from breaker seems to work a lot better, getting picture pretty much every second restart of SteamVR. Checking dmesg when SteamVR fails to get picture I see vrcompositor[70554]: segfault at 10 ip 00007ff55aa6a424 sp 00007ffcc459f168 error 4 in libpthread-2.33.so[7ff55aa66000+f000] consistently. Another thing I noticed is game Until You Fall sometimes reports failing to get cursor and has to be killed. After that Steam Home doesn't start and any game that tries to start prints VKRenderThread[93530]: segfault at 7f6b1496f918 ip 00007f79b62e0ed8 sp 00007f7967ab4d90 error 6 in vrclient.so[7f79b60a9000+6ac000] and crashes.

[ZarathustraDK]

I just started getting this bug out of nowhere. I was playing VRChat when suddenly SteamVR just crashed on me. Subsequently restarting SteamVR now pipes the headset output to a X11-window on my desktop with the SteamVR-client visible. It suggests to enable Direct Mode and wants a restart, if I do that then the same thing happens again, though the steamvr-client window is now absent. Only way to exit is to close/kill steam. Restarting steam afterwards resets the behavior to the initial state.

Running vulkaninfo | grep vulkan I get:

ERROR: [Loader Message] Code 0 : loader_scanned_icd_add: Driver /usr/lib/libvulkan_radeon.so supports Vulkan 1.2, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)
WARNING: radv is not a conformant Vulkan implementation, testing use only.
        VK_KHR_vulkan_memory_model                  : extension revision 3
        vulkanMemoryModel                                  = true
        vulkanMemoryModelDeviceScope                       = true
        vulkanMemoryModelAvailabilityVisibilityChains      = false
        vulkanMemoryModel                             = true
        vulkanMemoryModelDeviceScope                  = true
        vulkanMemoryModelAvailabilityVisibilityChains = false

I tried renaming /usr/share/vulkan/icd.d/amd_icd32.json to something else, didn't help. Tried using SteamVR beta, no dice. It's strange, I wasn't updating anything, and had been gaming for a solid 3 hours when it just decided to crap its pants out of nowhere.

Steam System Information gist

[melvyn2]

For a late update, KDE Plasma beta 5.24 (aka 5.23.90) along with xwayland from git master works great for VR on wayland.

[ZarathustraDK]

For a late update, KDE Plasma beta 5.24 (aka 5.23.90) along with xwayland from git master works great for VR on wayland.

I think I'll just wait the 3 days for 5.24 to drop and not go about mucking it up any further ;)