The OS floor is now enforced at install time (MinVersion=10.0.22621 with an explanatory [Messages] override): pf-vdisplay is built against IddCx 1.10, and on Windows 10 (incl. LTSC) / Win11 21H2 the device fails start with Code 10 STATUS_DEVICE_POWER_FAILURE (field-reported). Docs (site requirements/install/ windows-host pages + README) state the floor; new docs-site Security page. Installer also gains the trayicon task (punktfunk-tray.exe file + HKLM Run key, post-install launch as the signed-in user, upgrade taskkill + uninstall --quit/taskkill choreography before file deletion), and the wizard/cleanup text/port sweeps move off the stale :3000 web-console references to :47992 (cleanups sweep both for upgrades from old installs). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
4.2 KiB
title, description
| title | description |
|---|---|
| Troubleshooting | Common problems setting up or using a punktfunk host, and how to fix them. |
The host isn't found on the network
- Make sure the host is actually running (
systemctl --user status punktfunk-host, or you see it listening in the terminal). - Host and client must be on the same network/subnet. Discovery uses mDNS, which doesn't cross routed subnets or most VPNs-without-multicast. As a fallback, add the host by IP address in your client.
- A firewall on the host can block it. The native protocol's control plane uses UDP port 9777. The per-session data plane uses an ephemeral UDP port negotiated at connect time (currently random) — for a strict firewall, open a UDP range or move the data port. GameStream/Moonlight uses TCP 47984/47989/48010 + UDP 47998–48010 + ENet UDP 47999. Allow them on the host's firewall.
nvidia-smi says it can't communicate with the driver
- The NVIDIA kernel module didn't load. With Secure Boot enabled, enrol the module's signing key:
sudo mokutil --import /var/lib/shim-signed/mok/MOK.der, reboot, Enrol MOK at the blue screen (or disable Secure Boot). On Fedora, follow RPM Fusion's Secure Boot steps. - After a kernel update the module may need a rebuild — reinstall the driver package.
The desktop won't start, or "GPU … not supported by EGL"
The NVIDIA GL/EGL userspace is missing — the base driver package doesn't always include it.
- Ubuntu:
sudo apt install libnvidia-gl-<version>(matching your driver). - Confirm
/usr/share/glvnd/egl_vendor.d/10_nvidia.jsonexists andnvidia-drm modesetisY.
Black screen / no picture, but the client connects
- You must be on a Wayland session, not X11 (check the login-screen session picker).
- KWin must be ≥ 6.5.6 (
kwin_wayland --version); GNOME ≥ 48; gamescope ≥ 3.16.22. - Confirm
PUNKTFUNK_COMPOSITORinhost.envmatches your desktop.
Capture fails: "Session creation inhibited" (GNOME)
A locked GNOME session blocks screen capture. On an always-on/headless host, disable the lock:
gsettings set org.gnome.desktop.screensaver lock-enabled false
gsettings set org.gnome.desktop.session idle-delay 0
See Running as a Service.
A controller is detected but does nothing (Bazzite)
The host user needs to be in the input group. On Bazzite:
ujust add-user-to-input-group
Then log out and back in. On other distros this is sudo usermod -aG input $USER + re-login.
Pairing is rejected / the client can't connect
- The host requires pairing by default. Arm pairing from the web console, then enter the PIN on the client. See Pairing & Trust.
- If you re-installed the host, its identity changed — re-pair the client.
Stutter, drops, or high latency
- Lower the bitrate. On a busy or Wi-Fi link, the requested bitrate may be too high — the native clients' speed test picks a safe value; with Moonlight, set it manually.
- Prefer a wired connection or 5 GHz Wi-Fi between host and client.
- Streaming to many devices at once shares the GPU encoder. The host serves several concurrent native sessions (up to 4 by default); heavy load is usually bitrate-bound, so lower the bitrate first.
Windows: "punktfunk Virtual Display" shows Code 10 in Device Manager
Sessions end with "pf-vdisplay driver interface not found" and Device Manager shows the
punktfunk Virtual Display device failed with Code 10 (STATUS_DEVICE_POWER_FAILURE).
This means your Windows version is too old. The virtual-display driver requires the IddCx 1.10 driver framework, which first shipped in Windows 11 22H2 (build 22621) — on Windows 10 (including LTSC) and Windows 11 21H2 the driver installs but cannot start. Reinstalling won't help; the fix is updating to Windows 11 22H2 or newer. (Current installers refuse to run on older Windows for this reason; if you see this, the host was likely installed with an older installer.)
Still stuck?
Run the host with RUST_LOG=info (or debug) and check journalctl --user -u punktfunk-host for the
error around the failed connect or capture.