Gay pirates are the best kinds of pirates 💞
I’m a person who tends to program stuff in Godot and also likes to look at clouds. Sometimes they look really spicy outside.
Gay pirates are the best kinds of pirates 💞
OP is not asking for windows
What exactly do you mean by “press”? In which direction? I have plugged the cable into the headset until it kinda clicked, like a thump, so I thought that would be enough. So yeah, press in which direction? Also I have tried all the steamVR versions, so yeah that’s likely not the issue
I am using the apt version of steam, so that should be fine
You mean I should buy only the headset new, right? I think that makes loads of sense. Unfortunately right now the headset is not available.
… I’ll also be real with you and tell you something terrible. I installed Windows just to test if it works there and it did not. The same red lights, the same error. This seems like either my graphics card has some problems with it, or the headset is simply faulty. Unfortunatly I did not purchase this one new, but used, so no warrenty. It was for “only” 400€, and it came with perfectly functioning base stations and controllers. It’s “just” the headset display which does not work. You think it would make more sense to purchase a new headset specifically or to sell all the base stations and controllers to purchase a simple htc vive 1 ?
Hmm, very interesting. I held down the button when plugging it in, and it resulted in the infamous blinking red lights. Then steamVR indeed told me to enter my password for some sort of setup. I did that, but I stead on installing some firmware or something, it just started StaemVR like usual, but this time not the headset, nor the base stations show up. It has a small error window over it, which says that it could not detect any headset. This is easily resolved by just replugging the index power cable, but that just gets me back to where I started (all devices show up as they should and SteamVR just pretends that everything is working perfectly, while nothing is being displayed in the headset).
Thank you for telling me. When the “display not found” error does not occur, it actaully lists the valve index display as an option as shown here:
Sat Mar 02 2024 23:45:48.724644 [Info] - Looking for direct display through Vulkan WSI
Sat Mar 02 2024 23:45:48.953899 [Info] - - Vulkan output 0: 1280x1024 resolution, 380x300 dimensions - FUS B19-5 (DVI-D-0)
Sat Mar 02 2024 23:45:48.953972 [Info] - - Vulkan output 1: 2880x1600 resolution, 0x0 dimensions - Valve Corporation Index HMD (DP-0)
Sat Mar 02 2024 23:45:48.954003 [Info] - - Vulkan output 2: 1920x1080 resolution, 1210x680 dimensions - GRUNDIG TV (DP-5)
Sat Mar 02 2024 23:45:48.954030 [Info] - Tried to find direct display through Vulkan WSI: 0x56529d5fb9c0
Sat Mar 02 2024 23:45:48.954791 [Info] - Trying to match desired rate of 90.003006Hz.
Sat Mar 02 2024 23:45:48.954814 [Info] - 4 modes on display:
Sat Mar 02 2024 23:45:48.954830 [Info] - - 0: 2880x1600@90.003006Hz
Sat Mar 02 2024 23:45:48.954844 [Info] - - 1: 2880x1600@79.999001Hz
Sat Mar 02 2024 23:45:48.954873 [Info] - - 2: 2880x1600@120.019005Hz
Sat Mar 02 2024 23:45:48.954901 [Info] - - 3: 2880x1600@144.000000Hz
Sat Mar 02 2024 23:45:48.954915 [Info] - Selected mode 0.
Sat Mar 02 2024 23:45:49.417402 [Info] - Acquired xlib display!
Then afterwards, some [Info]s later, I get these errors:
Sat Mar 02 2024 23:45:50.099391 [Info] - HMD driver recommended: 2016x2240 90.0Hz HiddenArea(24.88%) = 610 MP/sec
Sat Mar 02 2024 23:45:50.099411 [Info] - GPU speed being set at first generation HMD resolution 382 MP/sec
Sat Mar 02 2024 23:45:50.099426 [Info] - Raw ideal render target scale = 0.63
Sat Mar 02 2024 23:45:50.099588 [Info] - New result of GetRecommendedRenderTargetSize for current app: 900x1000
Sat Mar 02 2024 23:45:50.099625 [Info] - Creating samplers
Sat Mar 02 2024 23:45:50.099723 [Info] - Creating util resources
Sat Mar 02 2024 23:45:50.100647 [Info] - Creating constant buffers
Sat Mar 02 2024 23:45:50.105007 [Info] - Creating systemlayer textures (w=1592,h=1772)
Sat Mar 02 2024 23:45:50.106200 [Info] - Creating/Updating distortion surfaces (mesh resolution 49)
Sat Mar 02 2024 23:45:50.167374 [Info] - Warp mesh (left eye) covers 82.12% of its viewport (shrink wrap saved 1.87%)
Sat Mar 02 2024 23:45:50.167774 [Error] - ASSERT: "unSize < 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.226694 [Error] - ASSERT: "unSize < 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.294548 [Info] - Warp mesh (right eye) covers 81.97% of its viewport (shrink wrap saved 1.97%)
Sat Mar 02 2024 23:45:50.295023 [Error] - ASSERT: "unSize < 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.295504 [Error] - ASSERT: "unSize < 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.396356 [Error] - ASSERT: "unSize < 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.400858 [Error] - ASSERT: "unSize < 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.401612 [Error] - ASSERT: "unSize < 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.402094 [Error] - ASSERT: "unSize < 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.405972 [Error] - ASSERT: "unSize < 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.407084 [Error] - ASSERT: "unSize < 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.407499 [Error] - ASSERT: "unSize < 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.408178 [Error] - ASSERT: "unSize < 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.408412 [Error] - ASSERT: "unSize < 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.408676 [Error] - ASSERT: "unSize < 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
Sat Mar 02 2024 23:45:50.408907 [Error] - ASSERT: "unSize < 65536" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5110.
They seem to target one specific line in some vulkan renderer c++ script. Then this is the very last error I get before it just keeps on printinig infos:
Sat Mar 02 2024 23:45:50.643309 [Error] - Unflushed events requested in CGpuTiming::GetDeltas!
So it really does detect the display, it just seems to have some undefined software issue… This would be the full files contents, in case there is some stuff which is vitally important. The SteamVR window itself does not even mention anything being wrong. It just sits there, happily rendering that image meant for the hmd. Do you see something in these logs? I am unfortunatly still at a loss…
The output of the xrandr command is this:
Screen 0: minimum 8 x 8, current 3200 x 1080, maximum 32767 x 32767
DVI-D-0 connected 1280x1024+1920+0 (normal left inverted right x axis y axis) 376mm x 301mm
1280x1024 60.02*+ 75.02
1024x768 75.03 60.00
800x600 75.00 60.32
640x480 75.00 59.94
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 160mm x 90mm
1920x1080 50.00*+ 60.00 59.94 29.97 25.00 23.98 60.00 50.04
1600x1200 60.00
1360x850 60.00
1360x768 59.80
1280x1024 75.02 60.02
1280x960 60.00
1280x768 59.87
1280x720 59.94 50.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
720x576 50.00
720x480 59.94
640x480 75.00 59.94 59.93
Where can I find that vrcompositor log?
Unfortunately I don’t have a multimeter. As I said, the tracking works perfectly and even the IPD adjustment works. It’s just the display which does not seem to work The headset also gets warm while in “use” even though it doesn’t display stuff. How would I got about resetting the firmware?
The lighthouses I only have plugged in to the wall. They magically connected to steam VR, and both appear as green. As said before, the tracking works perfectly, even for the knuckles controllers. I have a GTX 1060 with 6GB of VRAM. I’m using the latest version of the Nvidia-driver package (It’s something like 525 or somethin). I don’t think I need to plug the lighthouses right into the PC…
Yes exactly that. I got a new cable, the one which goes from headset into the graphics card. I am using the latest Nvidia-driver package from apt, so yes the proprietary one. No extension cables anywhere.
I actually got it to work. I ran these commands: sudo apt remove --purge nvidia sudo reboot #(Reboots the system) sudo apt install nvidia-tesla-470-driver sudo reboot #(Reboots the system)
And BAM! I got the right driver for the job! Version 470 obtained!
Turns out that the repository one is broken. This is an issue with a specific version of the nights driver, which has just been fixed. If you want more info, have a look at the solved content I made on this post.
SOLUTION:
This is a problem not with the operating system, but rather the nvidia DKMS. It can easily be fixed by replacing some lines in the apt sources located here: /etc/apt/sources.list
.
The line update-security has to be replaced by these two:
deb http://deb.debian.org/debian/ bookworm-updates main non-free contrib non-free-firmware
deb-src http://deb.debian.org/debian/ bookworm-updates main non-free contrib non-free-firmware
Here is a link to where this solution was found: https://forums.developer.nvidia.com/t/debian-12-and-nvidia-driver-nvidia-linux-x86-64-470-223-02-run/282473/2
After updating the sources there, simple run sudo apt
update and sudo apt upgrade
. Then it should finally compile the drivers for your kernel, the extra kernel in the grub menu (if it appeared on your machine) should disappear, and your original kernel (in my case 6.1.0-18-amd64) will have the module in it. So your monitors and stuff should work as they did before.
Oh yeah, I completely missed the DKMS. I just installed the nvidia-kernel-dkms package, and it seemed to try to build the module, but then failed:
Building for 6.1.0-18-amd64
Building initial module for 6.1.0-18-amd64
Error! Bad return status for module build on kernel: 6.1.0-18-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/525.147.05/build/make.log for more information.
dpkg: error processing package nvidia-kernel-dkms (--configure):
installed nvidia-kernel-dkms package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-driver:
nvidia-driver depends on nvidia-kernel-dkms (= 525.147.05-4~deb12u1) | nvidia-kernel-525.147.05 | nvidia-open-kernel-525.147.05 | nvidia-open-kernel-525.147.05; however:
Package nvidia-kernel-dkms is not configured yet.
Package nvidia-kernel-525.147.05 is not installed.
Package nvidia-kernel-dkms which provides nvidia-kernel-525.147.05 is not configured yet.
Package nvidia-open-kernel-525.147.05 is not installed.
Package nvidia-open-kernel-525.147.05 is not installed.
dpkg: error processing package nvidia-driver (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
nvidia-kernel-dkms
nvidia-driver
E: Sub-process /usr/bin/dpkg returned an error code (1)
It says that something hasn’t been configured yet, even though I am just installing it…
Is there a way to download older driver versions? I’ve heard that output to VR displays tends to get blocked by the new drivers.
Oh really? That’s quite odd, I thought it’d be a me problem. Guess I’ll get the drivers from nvidias website…
Go use NewPipe! Its Foss!