Same issue,
happens only with vulkan-radeon, using amdvlk doesn't crash (although I can't tell if the output is full 144Hz).
https://github.com/ValveSoftware/SteamVR-for-Linux/issues/532 seems like the same issue.

Differences:
latest Arch with X11 gnome
steamvr beta 1.25.3
steam build Dec 15 2022
5950X cpu

(EDIT: it is out of scope)

you have very close stack to mine, do you get artifacts on the "border" of right eye (and artifacted 2d surfaces in steamvr overlays (but not in 3d scenes))?
(it happens regardless if I use amdvlk or vulkan-radeon)

The artifacting is random, usually it is pure white with random distorted gpu memory trash(?).
In the headset the artifact is visible only if your eye is very close to the lens, but since it is very bright white - it is a bit unpleasant to play.

~~Maybe worth noting - I use vulkan-radeon and amdvlk from repository extra and lib32 variants of them from multilib.
https://archlinux.org/packages/extra/x86_64/vulkan-radeon/
https://archlinux.org/packages/multilib/x86_64/lib32-vulkan-radeon/~~

Hello @Danielduel, please give #480 a read.

Wow, I didn't knew how to look for that issue, thank you a ton <3

I also have this problem with my 7900xtx. The 144hz one

If you want to get the fix early, this kernel branch tag has it fixed: https://gitlab.freedesktop.org/agd5f/linux/-/tags/amd-drm-next-6.3-2023-02-17
The fix does not seem to be merged in as of kernel 6.2.

Just chiming in with the same experience. Upgraded from a 6800XT that had the 144Hz option to a 7900 XTX that seems to be lacking it.

I'm guessing it should be merged in when we get 6.3.

Had this issue with vive randomly not getting into direct mode for a while
Just tested 6.3 kernel on fedora silverblue (see here how to do it https://coreos.github.io/rpm-ostree/ex-replace) on arch container with steam and it worked perfectly, vive now can be detected every time

On my 7900XT I can't even select any refresh rate. It just says "Additional refresh rates are supported by your HMD, but were not detected by the graphics driver.". Running mesa-git and the amd-drm-next tree.

EDIT: This stopped happening after unplugging the headset and reconnecting it.

Fix has been merged as of kernel 6.3+.

Yeah, it works for me too now

(after updating local packages (including kernel, mesa, DE, ...)) Headset doesn't crash anymore in 144Hz mode, will check if it's stable today.

Seems stable, 3h of (proton) Beat Saber on 144Hz index ran without any problems, the difference to 120Hz is hard to spot, but I would argue it correctly pushed frames.

Another 2h session - everything was fine.
@kisak-valve I think this can be marked as fixed.