I would also be interested to know if this will be officially support.

So far I've only found this reddit post that said it works on Linux:
https://www.reddit.com/r/virtualreality_linux/comments/1welkhs/steam_frame_confirmed_by_linustechtips_to_not

Asking the real questions. I've signed up for the waiting list lotto myself, data point 2:

Environment
Distro: Arch Linux x86_64 (systemd, KDE Plasma 6.7.5)
Kernel: 7.2.4-zen1-1-zen
Display: KWin (Wayland)
Audio: PipeWire + WirePlumber
GPU (render/encode): AMD Radeon RX 9070 XT, Mesa: 26.2.3-arch1.1, Vulkan
Other GPUs present: AMD Radeon Graphics [Integrated - Ryzen 9 9950X3D]
Steam Beta Branch: Steam Beta Update
Steam Version: 1789606022
Steam Client Build Date: Wed, Sep 16, 2026 20:23 UTC -04:00
Steam Web Build Date: Wed, Sep 16, 2026 17:01 UTC -04:00
Steam API Version: SteamClient023
Wi-Fi: Linksys EA6350 AC1200+ Dual-Band

I have a Steam Frame and have been unable to get the wireless dongle working on either my Manjaro desktop or Bazzite unofficial "steam machine." WiFi streaming technically works, but I've been experiencing consistent quality drops where it literally goes from "excellent" to "poor" every 10 to 15 seconds, causing severe stuttering. The only decent VR gaming I've been able to do on it is with locally-installed games.

I did try both Wayland and X, and it doesn't seem to be an issue with that. I've also successfully streamed to the Quest 3, so I don't think it's anything to do with my home network.

@tajeraich i'm also struggling getting the dongle working, also had the same problems with the quality drops you're experiencing with the normal wifi, for those what i did was disable the "reserve Wifi 6E for the dongle" option in the connected wifi settings on the frame. it was enabled for me even though the dongle was not connected, making the connection insanely slow. after that i got no connection problems, and could get stable streams.

edit: forgot to mention i had to reconnect the wifi to apply the changes

I have been able to get the dongle to work.

1. power on the Frame
2. plug in the dongle
3. profit

having the dongle plugged in before the frame is looking for it results in a cascade of disconnected errors
I haven't been able to get VR streaming to work on Fedora even with the dongle tho.

@tajeraich @4ndrs I would be interested in getting some info on your machines to see if there is some reason I'm not able to get a VR stream at all, even if a bad one.

I'm running a Fedora 44 system with a 7800xt
Steam beta client with SteamVR beta on KDE (wayland session)

@november781

I would be interested in getting some info on your machines to see if there is some reason I'm not able to get a VR stream at all, even if a bad one.

i'm running gentoo, kernel 7.2.6, RX9070
steam beta client with steam vr beta on bspwm (X11)

i have the experimental steamrt3 client disabled since with that my steam vr fails

CachyOS
Kernel: 7.2.7-1-cachyos
GPU: RTX 5070
DE: KDE Plasma 6.7.5 (Wayland)

Was able to play Beat Saber over the adapter by starting Steam (Native, but not beta), going to Big Picture Mode, and then starting Steam VR. Frame connected right away and then I was able to start Beat Saber.
That said, the experience was okay, but not usable for Beat Saber. I initially had the adapter plugged into the back of my PC, which put it at maybe shin-level about 10 feet from the Frame. Packet loss would fluctuate between 15-90% on the adapter. Swapped to the front panel USB port and moved my desk out of the way, so it was at thigh-level about 6 feet from the Frame, and packet loss would be 0-4% typically, but there would still be random drop outs every 30 seconds or so. Not great for Beat Saber. Usable for other stuff though.

WiFi streaming is entirely unusable because when using that, the packet loss was consistently 99% with 200+ms of latency. My router is through about three walls and about 30 feet away.

Another issue I had was with the room settings. Beat Saber would seemingly place the player in a random spot and a random orientation on each boot, and I couldn't figure out how to reset the room from SteamVR (didn't look too hard though), so I had to spend a couple minutes adjusting the room settings within Beat Saber every time I started the game.

i finally got the dongle working today

i have a fairly minimal setup, so i don't have network manager (i think steam uses it in some way. what i have is openrc + netifrc). i saw that in remote play options, inside the frame, you can configure the dongle and use a custom configuration instead of leaving steam to manage it. i enabled the custom config, and in my gentoo box configured the dongle to get it up with openrc

# /etc/wpa_supplicant/wpa_supplicant.conf
network={
    ssid="frame_hostname"
    scan_ssid=1

    key_mgmt=SAE
    sae_password="password_generated_in_the_frame"
    ieee80211w=2
}

# /etc/conf.d/net
modules_wlp5s0f1u3="wpa_supplicant"
wpa_supplicant_wlp5s0f1u3="-Dnl80211"
config_wlp5s0f1u3="dhcp"
dhcp_wlp5s0f1u3="nodns nogateway" # frame link must not touch normal dns/default routing

so far multilink is working, and don't see any other network issues

Ok I'm an idiot... I was missing the mesa-vulkan-drivers-freeworld swap...

the rest of the mesa-freeworld packages let me use VAAPI just fine but SteamVR hard locks to the vulkan encoder and not vaapi.

I have gotten pcvr working, however it has some bugs. On archlinux, I have to run 'steam -pipewire' I then get a dialogue to select what I want to share. If i try to share full desktop with dual monitors it takes both monitors and smashes them together into a single 16:9, so each monitor is essentially half width. If i try to stream a single monitor it works fine, but the cursor control from the steam frame controllers gets an offset. The solution to the offset is to disable your second monitor AND disable display scaling. So I had to set my 4k monitor to 1080p + 100% scaling instead of my typical 4k 150%. This fixes the offset issue, although clicking things at the very edge of the screen top when the browser is max is still difficult. Currently I see no way to stream both monitors as separate windows within the steamframe.

Replying to https://github.com/ValveSoftware/SteamVR-for-Linux/issues/946#issuecomment-5840998298

when you are getting the desktop display, are you selecting the desktop from the headset dashboard while streaming or are you using some other way to see your desktop? I'm just getting a black screen, sometimes with a cursor.

Fedora 44
KWin
steam -pipewire

I have gotten pcvr working

@michaelkavsak I'm confused by this since your description seems only to describe getting traditional 2D streaming working with the frame, considering your talk of desktop resolutions and traditional aspect ratios like 16:9.

To clarify, have you actually managed to get streaming of PCVR games to the Steam Frame working (Eg; Half Life Alyx) from your system, or only desktop/2D game streaming?

Confirming PCVR works for me on a non-SteamOS Linux desktop, including the wireless adapter. I only did short tests, but ran alyx (sound issues however!) , Beatsaber (working fine), Skyrim VR (needs controller remapping i think)

Setup:

• CachyOS , KDE Plasma 6 on Wayland, no gamescope session
• RTX 5080, proprietary NVIDIA driver
• Steam Frame 256GB

What works:

• PC VR streaming over regular Wi-Fi
• PC VR streaming via the 6 GHz wireless adapter + WIFI — recognised and working out of the box, no manual driver install

One gotcha that cost me a while, and I suspect it will bite others:

My existing ufw rules were scoped to my LAN subnet, so they did not cover the adapter traffic at all, and the headset simply reported that it could not reach the host. Disabling ufw made it work immediately.

After plugging in the adapter, check which interface and subnet it brought up:

ip -br a

After allowing the subnet everything "just worked".
I did not use any launch params for SteamVR.

My experience is awful.
Streaming Half-Life: Alyx (linux version, no Proton) from my desktop to the frame is basically impossible.

Setup:

• CPU: AMD Ryzen 7 7800X3D (integrated graphics disabled in the BIOS)
• GPU: NVIDIA GeForce RTX 5070 Ti
• Motherboard: MSI PRO B650-P WIFI (BIOS 1.L7)
• Headset: Steam Frame
• Ubuntu 24.04.5 LTS, kernel 7.0.0-34, GNOME on X11
• NVIDIA driver 595.91.07 (nvidia-driver-595-open)
• NetworkManager with wpa_supplicant (iwd removed)
• SteamVR stable (2.17.x)
• WIFI is off, running wired.

Problems Encountered & Fixed:

• The firewall blocked the Frame. UFW dropped Steam discovery (UDP 27036) and the VR stream (UDP 10400). Fixed with rules.
• VRInitError_Compositor_UnableToCreateDevice (405). Driver 580 lacked a Vulkan extension (-7). Fixed with a newer driver though.
• The compositor ran on the AMD integrated GPU (CreateDriverDirectModeResolveTextures) causing errors. Fixed by turning off the integrated graphics.

Continued Problems:

• The Steam VR UI sometimes appeared twice in my VR view.
• The Wireless Adapter never connects.
• Half-Life Alyx crashes or freezes when killing barnacles. (crash libscenesystem.so (a null pointer) with nvidia driver 610, freeze with driver 595)
• Steam VR on PC randomly crashes
• When starting a VR stream from the Frame without first starting SteamVR on the PC everything breaks.
• The Steam PC client crashes whenever starting a desktop stream from within the Frame (in libnvidia-glcore).

Not sure how helpful this will be, but this is my experience so far.

x86_64 Linux 7.2.7-arch1-1
KDE Plasma on Wayland
NVIDIA Corporation NVIDIA GeForce GTX 1660/PCIe/SSE2
4.6.0 NVIDIA 615.71.09

Edit: Forgot to mention I'm using the beta Steam client and SteamVR on PC and stable on the headset.

When the headset reports only "2D-Streaming: Ready", 2D streaming works. Adding the firewall rules below causes it to report "Streaming: Ready" and "Local Wi-Fi: Ready". Now, 2D streaming no longer works. It launches the game on the host, but disconnects / will not display on the headset. I've also tested with the firewall disabled with the same result.

ufw allow proto udp from 192.168.1.0/24 to 192.168.1.0/24
ufw allow proto udp from 162.254.192.0/21 to 192.168.1.0/24

In this state, SteamVR will connect to it. When a VR game (Superhot VR) is launched from the headset on the PC, the game is displayed on the PC but never comes up on the headset. The headset displays appear to change modes twice. They flash and a message comes up with 90Hz and then 120Hz. At least once I noticed through the pass-through while wearing the headset that the game displayed on the PC was tracking the headset movement.

Looking at dmesg after, I've seen various segfaults in vrcompositor:

[10293.333135] vrcompositor[36792]: segfault at 7f893c407030 ip 00007f893c407030 sp 00007fff81ef93f8 error 15 likely on CPU 8 (core 2, socket 0)
[10293.333175] Code: 00 00 50 16 3d 3c 89 7f 00 00 a0 55 3d 3c 89 7f 00 00 a0 97 3d 3c 89 7f 00 00 b8 8f 00 00 1c 00 00 00 80 fe 43 3c 89 7f 00 00 <70> fe 43 3c 89 7f 00 00 81 00 00 00 00 00 00 00 40 78 40 3c 89 7f

[10369.450571] vrcompositor[38895]: segfault at 64 ip 0000555f006959cc sp 00007ffe6dd138e0 error 4 in vrcompositor[2389cc,555f005ab000+37d000] likely on CPU 7 (core 1, socket 0)
[10369.450586] Code: 48 8d 83 c8 01 00 00 48 89 45 c8 49 39 c4 0f 84 da 00 00 00 4c 8d 3d db 07 f0 ff eb 62 90 f0 41 83 45 08 01 48 8b 3b 48 8b 07 <ff> 50 18 89 c2 4c 89 f1 4c 89 fe bf 02 00 00 00 31 c0 e8 3d 49 08

[ 1772.601148] vrcompositor[9082]: segfault at 7f4d9c41bc90 ip 00007f4d9c41bc90 sp 00007ffec978f248 error 15 likely on CPU 6 (core 0, socket 0)
[ 1772.601161] Code: 00 00 6a 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 67 00 00 00 0c 00 00 00 02 00 00 00 00 00 00 00 6a 00 00 00 14 00 00 00 <64> 75 6c 65 00 39 32 00 61 00 00 00 00 00 00 00 b0 c2 5b 9c 4d 7f

@rbrauer

I get exactly the same compositor crashes

So my experience has been, that everything worked correctly!

My PC

• Distro: CachyOS
• Kernel: 7.2.8-1-cachyos
• GPU: AMD Radeon RX 9070 XT
• DE: KDE Plasma Wayland 6.7.5
• Steam client: beta
• SteamVR 2.18.1

Tested VRChat and some other games, no crashes for me. Overall I am pretty happy with the experience.
I had to enable WiFi in my system, otherwise SteamVR cannot manage the dongle via NetworkManager.
I was streaming with 120Hz and all of the other settings on auto.

When in game, the streamed SteamVR dashboards/overlays are pretty wobbly and janky, but I guess this is still WIP and not a big dealbreaker.

I'm having a lot of trouble with the wifi. I've set the AP on the frame to custom (ssid=frame). I have seen the network show up in scans before from various devices who can connect just fine to other 6GHz networks (phone, intel laptop, dongle). I've been able to connect to it from my phone, but only intermittently.

[steamos@frame ~]$ iw dev
phy#0
	Unnamed/non-netdev interface
		wdev 0x4
		addr [...]
		type P2P-device
	Interface wlanap
		ifindex 14
		wdev 0x3
		addr [...]
		ssid frame
		type AP
		channel 37 (6135 MHz), width: 160 MHz, center1: 6185 MHz
		txpower 5.00 dBm
		multicast TXQ:
			qsz-byt	qsz-pkt	flows	drops	marks	overlmt	hashcol	tx-bytes	tx-packets
			0	0	21	0	0	0	0	3768		21
	Interface wlan0
		ifindex 12
		wdev 0x1
		addr [...]
		ssid [...]
		type managed
		channel 36 (5180 MHz), width: 80 MHz, center1: 5210 MHz
		txpower 5.00 dBm
		multicast TXQ:
			qsz-byt	qsz-pkt	flows	drops	marks	overlmt	hashcol	tx-bytes	tx-packets
			0	0	0	0	0	0	0	0		0

Most people here seem to be having no problem with this. @GijsBellaard you mentioned "The Wireless Adapter never connects.". Is that consistent with what I'm seeing?

Edit: of course as soon as I post I make some progress.

I switched back to 'steam' AP mode, connected the dongle, did a scan and found 'frame_*' SSID. Starting steam still failed to connect, so I did a nmcli conn delete 'Steam Frame Wireless Adapter', and then restarted steam. Now it's connecting.

Here's my experience troubleshooting and ultimately getting HL:A streaming to work with the dongle on Linux. I'm on Arch Linux with CachyOS packages, 7950X3D & 7900XTX.

Any attempt to start streaming Half-Life: Alyx directly from the Steam Frame would only get you to the menu, but "Continue" or "New Game" would only get you in the gray rocky loading environment before locking up with a pop-up on the desktop:

SteamVR runtime failure!
Timed out waiting for response from Mongoose.
SteamVR needs to be restarted.

An interesting detail here is that the gray rocky loading environment did not have the "LOADING" text it is meant to show, so if you're not seeing it either, my following findings may apply to you too.

Streaming purely SteamVR directly via "Streaming Status" -> <my-pc> -> "Advanced" -> "Stream VR Without Game" gave me a choppy feed of broken lines:

This turned out to be due to launch options I'd set for SteamVR in my Steam library previously when setting up ALVR. After removing these and launching SteamVR manually I was prompted to grant it superuser privileges for some sort of additional system configuration. After which its been working fine.

Now if I enter SteamVR first via "Stream VR Without Game", and then begin streaming HL:A from the same UI, I get proper "LOADING" text in the loading screens, and the game appears to start and run properly.

This still feels like a workaround and so I hope we'll see this addressed in the near future, especially considering this being effectively a launch title.

if I enter SteamVR first

My experience has been mixed, but one thing that's been consistent is that launching games which should launch SteamVR (e.g. BeatSaber), simply doesn't launch SteamVR, meaning they launch without the necessary SteamVR bits, which apparently includes the necessary OpenXR components. Launching SteamVR first and then launching the game always fixes this particular issue for me. I'm sure this will get fixed eventually.

Personally I have other issues. I can't get the dongle to connect to the headset at all in Mint, but my guess is that's due to the older (7.0) kernel.

In Nobara with a 7.2.6 kernel I can get the dongle to connect (usually after a raindance restarting SteamVR on both the PC and headset), and it will even work flawlessly in multistreaming mode for a while. But after a while, I will lose audio entirely. Also taking the headset off will frequently cause it to lose either the Wifi or the dongle connection, or both. On top of that SteamVR like to crash randomly.

Pretty much all of these things are resolved by restarting SteamVR on the PC, or on the headset, or restarting the headset entirely. But even then sometimes the headset will just never get a wifi connection and/or dongle connection back. It's an entirely unpredictable buggy mess.

I've tried various combinations of the SteamVR beta on PC, beta client on the headset, etc. But nothing has improved the inconsistency.

I will say that on both OSes I had almost no issues with wifi-only streaming (or flatscreen remote play for that matter). And the headset works flawlessly standalone as well. It's only after throwing the dongle into the mix that things go crazy.

Update: today I was able to multistream BeatSaber for a good couple hours with zero issues. However it did take a handful of SteamVR restarts on both the PC and headset to make that stable in the first place. And then SteamVR on the PC crashed immediately when I manually closed it afterward. So the functionality is clearly possible, it's just not consistent. With that said, today I moved my dongle from a front port on my PC (for which I don't really know the specs offhand) to an active, powered 16ft USB extension plugged into a known fast port on my motherboard backplane. The extension placed the dongle squarely above where I stand to play VR. Whether this change actively helped eliminate the various issues and disconnects is debatable. Either way there are clearly still big issues.

P.S. Also I'm sorry to the originator of this issue, who put together such a lovely info request and got exactly nothing except for a bunch of technically-off-topic anecdotes from users. To be fair I think there's some good info in here.

I'm going to assume this is the place to put this, but I am also having issues with the dongle on Arch Linux, Kernel 7.2.7-zen1-1-zen

I can see the adapter with lsusb

Bus 004 Device 010: ID 28de:2432 Valve Software 802.11ax WLAN Adapter

and frame-dongle-troubleshoot.sh reports no errors after I set my regulatory domain.

➜  ~ sudo ~/Downloads/frame-dongle-troubleshoot.sh
[sudo] password for orangestar: 
-- Steam Frame Wireless Dongle Troubleshooting script v0.4
--
-- Lines beginning with PROBLEM are issues which will prevent the dongle from working.
-- Lines beginning with INFO may not prevent the dongle from working, but are worth looking into.

which: no firewall-cmd in ([my $PATH])
SUCCESS: None of the most obvious/common problems seem to have turned up!

Despite this, connecting the dongle to my computer does nothing. I've tried multiple ports, but there's nothing onscreen and the frame says no adapter is connected.

Other people have been saying Steam needs to be able to do something with NetworkManager in order to add the hotspot... should my user be in a specific group or should I give Steam access to modify some file in order to grant this access?

Other people have been saying Steam needs to be able to do something with NetworkManager in order to add the hotspot... should my user be in a specific group or should I give Steam access to modify some file in order to grant this access?

It depends on how polkit is setup. On my nixos/gnome laptop I just got an OS prompt asking to allow the process to change network stuff.

On my more barebones desktop machine (nixos/sway), I had to add myself to the networkmanager group, but that's because of a nixos specific polkit config:

    polkit.addRule(function(action, subject) {
      if (
        subject.isInGroup("networkmanager")
        && action.id.indexOf("org.freedesktop.NetworkManager.") == 0
        )
          { return polkit.Result.YES; }
    });

Perhaps that's a standard thing?

today I moved my dongle from a front port on my PC (for which I don't really know the specs offhand) to an active, powered 16ft USB extension plugged into a known fast port on my motherboard backplane.

I didn't use an extension, but moving to a USB3 backplane port seemed to solve a lot of problems for me with the driver freezing and failing to connect.

+1, same situation here: Steam Frame on a non-SteamOS desktop (Debian 13, kernel 7.1.13, KDE Plasma Wayland), and nothing official covers this setup.

System: Ryzen 9 9950X, RX 9070 XT (RADV), Frame on the SteamOS 0.4.2 preview channel, SteamVR 2.17.10.

What I ran into, in case it helps:

• Adapter driver: Debian's kernel doesn't build rtw89_8852cu (CONFIG_RTW89_8852CU not set), so the wireless adapter has no driver. I had to backport rtw89 from 7.2.8 via DKMS. Steam also expects a holo-realtek-firmware-toggles helper that only exists on SteamOS ("low latency mode unavailable").
• SteamVR startup on Linux: Proton titles fail with VRInitError_Init_InterfaceNotFound unless SteamVR is already running and the HMD is connected before launch (same as #962).
• Stream quality: frequent stutter and stream-reset storms. The PC side is clean (0 late frames in SteamVR frame timing), but under game load 1–4% of the video packets sent to the adapter never reach the headset's radio, measured by counting packets at both ends. At idle nothing is lost. I also hit the pFrame->ulVideoTimeline == ulTimelineSequence assert from #965.
• Shared radio: taking the headset off home Wi-Fi (so its single ath12k radio stays on the 6 GHz link) cut resets by about 75% but didn't eliminate them.

It would really help to know which host distros, kernels and driver versions are supported or tested for the Frame and its adapter on Linux.

It would really help to know which host distros, kernels and driver versions are supported or tested for the Frame and its adapter on Linux.

This is basically the crux, and actually relevant to the OP. With this information we could at least have a target to shoot for to bring all our various systems into alignment. However I suspect we won't see something official until it's officially supported on SteamOS. Taking a step back, we're all here trying to break into something that even Valve hasn't officially cracked yet. Releasing the product without this support is lame of course, but that's beside the point here.

Personally I'd just like to hear an official statement on WHERE (let alone WHEN) we can expect to see an announcement that there's some form of support officially released, and documentation of the details. Currently this crowd is all over the place (GitHub, Steam forums, Reddit, Steam Support, etc.). Bringing us (and the relevant information) together in a more coherent and orderly fashion would probably be quite useful for a lot of folks going forward, even after official support is announced, for troubleshooting purposes.

FWIW:

My system

OS: Xubuntu 24.04.5 LTS x86_64
Kernel: 7.2.8 (self-compiled)
GPU: AMD ATI Radeon RX 7900 XTX
GFX Driver: 26.2.3~kisak1~n
Steam: latest beta
Steam Frame: latest beta (though doesn't matter I guess)

I also had issues with lsusb showing the dongle, but neither Steam nor the Frame recognized the dongle.
Turns out by default only the PCIe of the driver required for the dongle is built-in. So I had to compile a kernel module for usb.
If you are a developer and have a lot of local networks, that can be an issue as well, as Steam only broadcasts to the first 16 networks - if you boot with the dongle you should be okay, but if you plug it in and already have 16+ networks (hello docker), it won't work.
I've also disabled my onboard wifi, as I usually don't use that, but wifi needs to be active for the dongle to work.

tl;dr: When I made the dongle and streaming work, I've compiled a file that contains what we did, along with a script to toggle on/off my onboard wifi - maybe it is of use to someone.

For me it works, since recently also without starting steam with the previously required -vrlinkforceenable. It still has its usual SteamVR quirks here and there (right now it only shows a black screen, will be fixed soon), network switches on and off, but overall it works pretty good. Remember to start SteamVR before you start to stream. I have not yet fiddled with the powersaving, wasn't necessary yet.

README.md

onboard-wifi.sh

My Environment

My issue was after plugging in the dongle, the network manager would do an infinite loop of losing the connection and re-attempting the connection. There was also a problem where steam would never make the connection to the frame.

I was able to get the dongle connecting by loading in a different driver than what was on the Nobara 44 kernel also using a different USB port. This hasn't resolved all issues, since now streaming from the PC to Frame is unreliable due to it rendering the game on PC, but not to the frame. Alternatively it will render on the frame, but inputs are ignored (controller and head movement).

Driver that worked for me — morrownr/rtw89

https://github.com/morrownr/rtw89.git

Steam Support Answer

This was the steam support response to my troubles:

Hello,

Thank you for contacting Steam Support.

SteamVR on desktop Linux isn't fully supported at this time. While many games may work, you may run into performance or compatibility issues.

With that said, Steam Support's ability to provide in-depth support for issues that may arise from using the wireless adapter on Linux PCs is limited.

If you're using the Steam Frame wireless adapter, Linux PCs require Linux kernel 7.2+.

We're working on expanding support following the launch of the Steam Frame.

streaming from the PC to Frame is unreliable due to it rendering the game on PC, but not to the frame. Alternatively it will render on the frame, but inputs are ignored (controller and head movement).

That's about where I'm at as well. With enough SteamVR restarts on the PC and headset I can get eventually get it to randomly work and then it will be stable for a session, or until I take the headset off and let it go idle. After that I have to do the raindance again.

P.S. Also I'm sorry to the originator of this issue, who put together such a lovely info request and got exactly nothing except for a bunch of technically-off-topic anecdotes from users. To be fair I think there's some good info in here.

This kind of info dump is probably the best we're gonna get until the Steam Frame is successfully released fully and Valve can reallocate devs to the treadmill work of getting this working on multiple distros 😭. Also, like @mmseng says, there is no central spot for this kind of info anyway so might as well do it right on top of SteamVR repo lol.

1. Many Linux configurations already support streaming to Steam Frame and other headsets using Steam Link, and we hope you'll find your configuration also works too. If you're already using Steam Link with a Quest, we expect streaming to a Frame would also work just fine. If either streaming to a Quest or Frame don't work, that's something we'd want to look at resolving.

2. The dongle is supported on SteamOS 3.9+, or Linux kernel 7.2+. There are also additional patches currently working their way through various packages to better support the dongle, so we expect that your experience streaming with the dongle to improve in the future.

3. Similar to Quest, WiFi streaming is supported on it's own but you'll want to make sure you're using a 5GHz router plugged directly into your PC. Multi-Link is also supported on Quest, and sends packets over multiple interfaces to ensure that you're using an optimal connection at any given time. If one were to drop, the other interface would still be streaming packets just fine and the stream shouldn't drop.

4. We use vulkan video to encode HEVC video on the host PC. We prefer discrete GPUs, and prefer a nvidia card if available. The GPU that steam link chooses will also be the one used by SteamVR too.

5. The audio system on the host is the same as when streaming from a Quest using Steam Link.

6. When permission is explicitly granted in Steam Link's VR settings to send eye tracking data to other apps, XR_EXT_eye_gaze_interaction is supported on the host PC.

7. We pay attention to issues reported on this GitHub page, as well as the SteamVR community forums. A number of issues reported here have been fixed in recent SteamVR updates - so thanks to those who have reported issues.

If you are reporting an issue, please do use the issue template and include logs/dumps as requested. A simple and concise hand-written message describing the problem you're running into, and a description of your system/configuration, goes a long way to helping us diagnose and fix the problem.

I want to know the intended operation of the link adapter, I think there's userspace software conflicts with programs that control the radio.

I will post my testing here, fwiw:
PC is my existing VR rig that normally uses WiVRn + quest. It runs CachyOS with KDE Plasma, and steamVR has never worked on any of my systems-- hence wivrn.
Headset is 1TB Steam Frame.

Traditional game streaming works to this PC
XR standalone environment works for HL:A

Immediately on plugging the dongle in, there's notification spam informing me that the adapter connects and reconnects repeatedly. I think it's some conflict between networkmanager and steam trying to use the same device.
Whatever driver makes this work, it isn't kernel level because the adapter doesn't appear anywhere in lspci. Swapping networkmanager for iwd stops the usb connection loop (the adapter is now recognized as wlan199). I've also confirmed using another computer that you can just use this adapter to surf the web by itself and it's actually decent lol.

Anyways, it's possible both IWD and NetworkManager take control of the adapter (and can use it) when steam is supposed to take control and do... something with it?

The troubleshooting script by valve reports no major issues other than maybe the firewall, after updating the rules no change was observed. The firewall was also disabled completely, as suggested by RudidasRentier, but this must not have been the issue with my setup.

Replying to https://github.com/ValveSoftware/SteamVR-for-Linux/issues/946#issuecomment-5985267737

I think the notification spam is a conflict with NetworkManager trying to query 2.4ghz networks with the adapter. I've heard mentions of a driver update in a future kernel roll-out that should solve that problem, but we will have to wait and see.

For now, having the headset on and ready to connect before plugging in the adapter seems to let you occasionally win a race condition and get connected before NetworkManager throws the error.

I've been compiling various issues with using frame with Linux, mostly to do with the desktop view (Wayland, multi-monitor, pipewire flag, etc.) but would there be an appropriate place to submit feedback relating to the frame's OS itself?

For example, MPRIS works but not for Bluetooth sources, likely due to missing packages. The frame's version of steamOS is strangely sparse in terms of packages, missing stuff like that, Kate, KDE Connect, etc. Also, the current version of beta SteamOS inverts colors for steam windows including games (but not floating windows of other apps?) when sharing your view through the virtual camera with applications like Discord.

Immediately on plugging the dongle in, there's notification spam informing me that the adapter connects and reconnects repeatedly. I think it's some conflict between networkmanager and steam trying to use the same device.

This is a known issue we are looking into addressing.

would there be an appropriate place to submit feedback relating to the frame's OS itself?

There is a community forums page for Steam Frame specifically where you can report issues: https://steamcommunity.com/app/4165890/discussions/

I believe many of the comments in the original post have been resolved, so I'm going to close this. Feel free to open a new issue if you encounter any problems.

Replying to https://github.com/ValveSoftware/SteamVR-for-Linux/issues/946#issuecomment-5825776747

steamrt3 kills steam VR for me had to turn it off