On another note, what I initially assumed was that SteamVR detected an irregularity with the firmware on the base station, but what seems to be the case is that the client never completed its process and assumed the base station got soft bricked.
If any intern can confirm that it is the actual behaviour, feel free to close the issue, because it doesn't seem like SVR could connect to them in the first place.
Hello @purplebar0, https://github.com/ValveSoftware/steam-devices/pull/44#issuecomment-1451869694 might be related to this issue.
You might get lucky by checking /lib/udev/rules.d/60-steam-vr.rules for https://github.com/ValveSoftware/steam-devices/commit/0c468922a38e8145c025f3f7cdf11c1b8c666f9d and adding it, but I don't know if that's the only issue blocking you.
After retesting with the udev rules applied and the latest beta, ensuring that Bluetooth is enabled (power management works), I can still not update firmware. The process crashes SteamVR and ends prematurely. Again though, the base station I attempted to update appears to work fine, so it isn't soft bricked or anything.
However, on a slightly unrelated note, it doesn't appear that "standby" works properly, it is not supposed to power down the motors but I could observe them stopping to a halt.
I have the same issue. Since the last update, SteamVR offers to update the base stations, but it crashes right after clicking the button. The logs show:
libpng warning: iCCP: known incorrect sRGB profile
ioctl (GFEATURE): Invalid argument
ioctl (GFEATURE): Invalid argument
ioctl (GFEATURE): Invalid argument
ioctl (GFEATURE): Invalid argument
ioctl (GFEATURE): Invalid argument
ioctl (GFEATURE): Invalid argument
ioctl (GFEATURE): Broken pipe
ioctl (GFEATURE): Broken pipe
ioctl (GFEATURE): Broken pipe
DeleteFBOFreeList: Removing 8 FBO objects, total 0
LuaDbg - Debugging stopped
CSteam3Client::Shutdown
OnContinueBaseStationWirelessUpdate
libpng warning: iCCP: known incorrect sRGB profile
OnNextBaseStationWirelessUpdate
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
crash_20230707221906_2.dmp[151432]: Uploading dump (out-of-process)
Power management works fine (and it's a very welcome feature!)
System Information:
Same issue, 2 of my bases are OK (superold bases), the 3rd which is fairly new is failing to update every time.
SteamVR (silently?) crashes after few seconds when it gives this window with a graphic of a base.
Hello, this problem persists.
(latest everything, kde (currently testing steamvr on wayland, but the same problem is under the x11), steamvr beta)
(Exactly the same like https://github.com/ValveSoftware/SteamVR-for-Linux/issues/589#issuecomment-1626029651)
Since it sounds like a problem with allocating memory - if it is problematic for Valve SteamVR team to reproduce the problem - I can volunteer to run some debug build to help getting that fixed.
// SteamVR Beta 1.26.7 - updating lighthouses crashes StreamVR (issue is still present)
Hi @kisak-valve, do you have any update on this topic?
Half of my bases are unusable because half of them are updated and half are failing to update, and when you have mixed versions on your bases - you will experience extreme drifting issues.
I would accept instructions on how to update/downgrade those lighthouses from command line (there is lighthouse_console binary that looks like a proper thing to use) as a valid solution here.
I’m also facing the same issue, a based station failed the update and is not visible any more (the other I didn’t try after that). Since I have only 2 base stations, I cannot use my Valve Index :slightly_frowning_face:
Waking up/shutting down the base stations through SteamVR still works.
Recovery process also crashes SteamVR once the countdown reaches 0.
Console output from recovery process:
free(): invalid pointer
crash_20240327013456_2.dmp[208166]: Uploading dump (out-of-process)
/tmp/dumps/crash_20240327013456_2.dmp
Aborted (core dumped)
(I must say, considering this ticket has been open for several months now, I’m tempted to just try to get my hands on a Windows machine to fix it…)
Nothing extracted yet.
Describe the bug
On the latest beta, it is possible to initiate a Base Station 2.0 update, however it ends prematurely and interrupts the process.
The problem is that the update was incomplete and I cannot recover from it, since no base stations are detected using "Recover From Incomplete Update".
There is no apparent issue in practice since the base station glows green, but SteamVR complains about incomplete upgrade, so I want to make sure that is taken care of. However, I don't have a Windows install, so I cannot perform the fix.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
SteamVR doesn't offer to update if it clearly cannot.
System Information (please complete the following information):
Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.