![]() As an experiment I left Beat Saber at the health and safety warning screen for about 5min, and couldn’t produce a crash with repeatedly opening and closing the SteamVR dashboard. I reverted to 430.09 just for the sake of running code that’s considered “stable”. I collected some notes on it, but I’m inclined to write it off as “beta being beta”. ![]() That one actually crashed when starting SteamVR, dmesg looked a bit different like it was a different bug. Just for the sake of argument, I tried the developer Vulkan beta 418.52.05. It’s not 100%, but trying to close the system menu will usually immediately produce a nasty orange and green pattern in the left eye and all displays going completely unresponsive. I’ve found the most consistent way to produce the crash is to launch Beat Saber (in Proton), start a song, and open the SteamVR system menu after about 30sec or so. Adding an NBR log from that as well, why not. But then I went on and reproduced one of the crashes that happened on 430, exactly, right down to the circumstances leading up to the crash and the precise corrupt pattern displayed in the HMD. Initially got a hang just starting SteamVR, physically disconnecting my second monitor seemed to fix this. I’m attaching the partial NBR log regardless.ģ90 booted fine, but exhibits the same problem. I was able to reinstall 430 via the remote shell, system would not shut down for a reboot but was back to normal after a forced reset. nvidia-bug-report hung during vulkaninfo, which did not respond to signals, not even SIGKILL. It looks like X wouldn’t even start, or even gdm3 wouldn’t get to the point of spawning X before getting hung up on something. ![]() Thankfully I was able to SSH in and inspect the system remotely. Local console just showed a frozen Ubuntu splash, completely unresponsive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |