I seem to be having the same issue, IE freezing after 30 seconds or so. On a fresh reboot, the HMD powers on when I start SteamVR. However, after a crash, the HMD video stops working. I have to reboot to get it back to the state.
Did you do anything other than disable reprojection? That didn't seem to have an effect on my system.
Disabling reprojection was all I did... re-enabling it brings the freezes back, too.
Same issue here. I disabled reprojection and rebooted SteamVR and it still ended up crashing my system. This was found in my system journal:
Apr 12 13:17:50 vashnix kernel: NVRM: GPU Board Serial Number:
Apr 12 13:17:50 vashnix kernel: NVRM: Xid (PCI:0000:0c:00): 13, Graphics Exception on GPC 0: 3D-C MEMLAYOUT Violation. Coordinates: (0x0, 0x0)
Apr 12 13:17:50 vashnix kernel: NVRM: Xid (PCI:0000:0c:00): 13, Graphics Exception: ESR 0x500420=0x80000400 0x500434=0x0 0x500438=0x1900 0x50043c=0x10000
Apr 12 13:17:50 vashnix kernel: NVRM: Xid (PCI:0000:0c:00): 13, Graphics Exception on GPC 1: 3D-C MEMLAYOUT Violation. Coordinates: (0x8, 0x0)
Apr 12 13:17:50 vashnix kernel: NVRM: Xid (PCI:0000:0c:00): 13, Graphics Exception: ESR 0x508420=0x80000400 0x508434=0x8 0x508438=0x1900 0x50843c=0x10000
Apr 12 13:17:50 vashnix kernel: NVRM: Xid (PCI:0000:0c:00): 13, Graphics Exception on GPC 2: 3D-C MEMLAYOUT Violation. Coordinates: (0x10, 0x0)
Apr 12 13:17:50 vashnix kernel: NVRM: Xid (PCI:0000:0c:00): 13, Graphics Exception: ESR 0x510420=0x80000400 0x510434=0x10 0x510438=0x1900 0x51043c=0x10000
Apr 12 13:17:50 vashnix kernel: NVRM: Xid (PCI:0000:0c:00): 13, Graphics Exception on GPC 3: 3D-C MEMLAYOUT Violation. Coordinates: (0x18, 0x0)
Apr 12 13:17:50 vashnix kernel: NVRM: Xid (PCI:0000:0c:00): 13, Graphics Exception: ESR 0x518420=0x80000400 0x518434=0x18 0x518438=0x1900 0x51843c=0x10000
Apr 12 13:17:50 vashnix kernel: NVRM: Xid (PCI:0000:0c:00): 13, Graphics Exception: ChID 005e, Class 0000c197, Offset 000015cc, Data 00010000
And a bunch of random errors like:
Apr 12 13:19:13 vashnix kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000927c:1:0
Is there some Discord or IRC we can all join? GOL maybe? Really wish Valve were more responsive :(
Updating NVIDIA driver to 396.54.09 from 396.24 resolved some of these crashes (375.27.13 is quite old for Vulkan support let alone VR). Until they resolve two of the core issues in #143 we're going to continue chasing ghosts. The updated driver is now causing the vive control box to keep rebooting at random times. At least I was able to get the environments working again through steam. Granted that was with dedicated cores to vrcompositor, steam, vrserver and X.
@Plagman is Valve even tracking ANY of these??
We have an IRC channel that is mostly about SteamVR at #vronlinux on freenode.
0x80000400x1 2018-04
System information
Issue Details:
Starting SteamVR yields the "vrclient shared lib not found" error. However, SteamVR and SteamVR Home start. One can look around, interact with the control tutorial (inside the Home) etc. at good framerates.
After ~3 - 30 seconds, everything attached to the same GPU as the Vive freezes (i.e. the Home App, the desktop).
SSHing in from another machine and killing all vr-related processes makes the system usable again. When I start SteamVR afterwards (without a full reboot of the computer), tracking works fine, but the Vive only shows a pattern of very dim red and black blocks (which are not affected by tracking).
VR-related logs at https://gist.github.com/CarpeNecopinum/fbd9979859e1881c9fe20b8d1cc3420a
No similar issues occur with self-written (Vulkan) VR-Apps.
Steps for reproducing this issue:
Update 1: The "vrclient shared lib not found" error does not occur with the SteamVR beta build of May 26. The freezing issues however are not fixed.
Update 2: Opting into Steam client beta prevents freezing of other applications on the same GPU. The screen inside the Vive remains useless until reboot, though.
Update 3: This appears to be related to #1 disabling reprojection as danginsburg suggested fixes the freeze issues.