enricobuehlerandClaude Opus 5
d383161723
ci / rust (push) Failing after 2m31s
ci / docs-site (push) Successful in 1m22s
ci / web (push) Successful in 1m48s
docker / builders (--build-arg FEDORA_VERSION=44, ci/fedora-rpm.Dockerfile, punktfunk-fedora44-rpm, -f44) (push) Successful in 1m1s
ci / rust-arm64 (push) Successful in 2m2s
docker / builders (ci/android-ci.Dockerfile, punktfunk-android-ci) (push) Successful in 11s
docker / builders (ci/arch-ci.Dockerfile, punktfunk-arch-ci) (push) Successful in 9s
docker / builders (ci/fedora-rpm.Dockerfile, punktfunk-fedora-rpm) (push) Successful in 9s
docker / builders (ci/rust-ci-noble.Dockerfile, punktfunk-rust-ci-noble) (push) Successful in 9s
docker / builders (ci/rust-ci.Dockerfile, punktfunk-rust-ci) (push) Successful in 9s
docker / builders-arm64cross (push) Successful in 20s
docker / apps (., web/Dockerfile, punktfunk-web) (push) Canceled after 36s
docker / apps (docs-site, docs-site/Dockerfile, punktfunk-docs) (push) Canceled after 36s
docker / deploy-docs (push) Canceled after 0s
~1150 feat/fix commits landed since v0.19 and the docs drifted badly. This is a full sweep of every page against the code as shipped: ~280 verified corrections, nine new pages, and one deletion. The worst of what was wrong: the quickstart's five-minute path could not work (`serve` never started the web console, so step 3 had no PIN to read); every packaged Linux host runs `serve --gamestream` while security.md told readers to leave GameStream off; HDR was documented as Windows-only; `PUNKTFUNK_SECURE_DDA` was documented as a working knob that nothing reads; `PUNKTFUNK_INPUT_BACKEND` listed a `uinput` value that does not exist and named libei for KDE instead of kwin; README linked three pages deleted on 2026-07-05; and the rpm-ostree update command pointed at a script no package installs. Completeness: about half of what shipped since v0.19 had no page at all. New: support-matrix (what works where, from 217 verified capability cells), input (mouse/touch/pen — and the in-stream chords, so the docs finally say how to get your mouse back), client-settings, profiles-and-links, game-library, clipboard, wake-on-lan, hdr, uninstall. Updating existed but had zero inbound links. status.md is gone: its facts moved into the support matrix, its shell stays as a redirect so the public URL does not 404. roadmap.md is themes now, not a feature checklist — checkboxes are what rotted. Debian is no longer claimed. The .deb's Depends resolve against Ubuntu images, nothing in CI builds or tests Debian, and Debian 12 is below the glibc 2.39 floor. The `debian` in the repo URL is the package format. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
224 lines
10 KiB
Markdown
224 lines
10 KiB
Markdown
---
|
||
title: Fedora
|
||
description: Install the Punktfunk host on Fedora from the RPM registry.
|
||
---
|
||
|
||
Install a Punktfunk host on **Fedora** from the self-hosted RPM registry. The host installs as an
|
||
RPM-managed systemd **`--user`** service and updates with `dnf upgrade` like the rest of your
|
||
system — no building required. It works with either **KDE Plasma** or **GNOME**; the
|
||
desktop-specific setup (which compositor captures, headless sessions, quirks) lives on the
|
||
[desktop configure pages](#5-configure-your-desktop). Host encode is **NVENC on NVIDIA**; on
|
||
**AMD/Intel** HEVC and AV1 go through **Vulkan Video**, with **VAAPI** for H.264 and as the fallback
|
||
(`PUNKTFUNK_ENCODER=auto` picks per GPU).
|
||
|
||
> New here? Read [Security & Safe Use](/docs/security) first — a streaming host is remote control of
|
||
> the machine, so keep it on a trusted LAN or VPN and require pairing.
|
||
|
||
Install is two parts: **GPU driver** → **host RPM**. Then open the firewall and point the host at
|
||
your desktop from the [desktop configure pages](#5-configure-your-desktop).
|
||
|
||
## 1. NVIDIA driver (RPM Fusion akmod)
|
||
|
||
Enable RPM Fusion (free + nonfree), then install the akmod driver + CUDA. RPM Fusion's nonfree
|
||
NVIDIA repo is sometimes pre-enabled on some spins; the full free/nonfree repos below are still
|
||
needed (they carry the NVENC ffmpeg in the next step).
|
||
|
||
```sh
|
||
sudo dnf install \
|
||
https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm \
|
||
https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
|
||
sudo dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda
|
||
```
|
||
|
||
**NVENC ffmpeg.** Fedora ships `ffmpeg-free`, which is built **without** NVENC — the host can't
|
||
encode with it. Swap to RPM Fusion's ffmpeg:
|
||
|
||
```sh
|
||
sudo dnf install --allowerasing ffmpeg ffmpeg-libs
|
||
ffmpeg -hide_banner -encoders | grep nvenc # expect hevc_nvenc / av1_nvenc / h264_nvenc
|
||
```
|
||
|
||
**Secure Boot.** If `mokutil --sb-state` says *enabled*, the akmod module is signed with a
|
||
locally-generated key that must be enrolled once:
|
||
|
||
```sh
|
||
sudo akmods --force # build + sign the module
|
||
sudo mokutil --import /etc/pki/akmods/certs/public_key.der # set a one-time password
|
||
sudo reboot
|
||
```
|
||
|
||
On the next boot a blue **MOK Manager** screen appears **on the machine's console** (not over
|
||
SSH): *Enroll MOK → Continue → Yes → (the password) → Reboot*. Then verify:
|
||
|
||
```sh
|
||
nvidia-smi # driver loads
|
||
ffmpeg -hide_banner -encoders | grep nvenc
|
||
```
|
||
|
||
(Or disable Secure Boot in firmware to skip the MOK step — fine for a dedicated test box.)
|
||
|
||
**AMD / Intel.** No akmod needed — the Mesa stack carries both encode paths. HEVC and AV1 go through
|
||
**Vulkan Video** by default (the Mesa Vulkan driver, present on any normal Fedora desktop), and
|
||
**VAAPI** is the H.264 path and the fallback. Install the freeworld VAAPI drivers for full codec
|
||
support (`mesa-va-drivers-freeworld` for AMD from RPM Fusion, `intel-media-driver` for Intel); on a
|
||
desktop these are usually already present.
|
||
|
||
## 2. Install the host (RPM)
|
||
|
||
The host is published to the self-hosted Gitea RPM registry, in a per-release group (an RPM is
|
||
soname-coupled to its base, so each Fedora release gets its own group). Pick the one matching your
|
||
release — `rpm -E %fedora` prints the number you're on:
|
||
|
||
- **Fedora 44** → `fedora-44`
|
||
- **Fedora 43** → `bazzite` — that group is a plain Fedora 43 build of the same `punktfunk` package,
|
||
so it's the right one for a regular Fedora 43 box too
|
||
|
||
Put your group in the `baseurl` below, then add the repo and install:
|
||
|
||
```sh
|
||
sudo tee /etc/yum.repos.d/punktfunk.repo >/dev/null <<'REPO'
|
||
[punktfunk]
|
||
name=punktfunk
|
||
# The group for your release: fedora-44 on Fedora 44, bazzite on Fedora 43.
|
||
baseurl=https://git.unom.io/api/packages/unom/rpm/fedora-44
|
||
enabled=1
|
||
# Packages are GPG-signed (gpgcheck=1) AND the repo metadata is Gitea-signed (repo_gpgcheck=1).
|
||
gpgcheck=1
|
||
repo_gpgcheck=1
|
||
gpgkey=https://git.unom.io/api/packages/unom/rpm/repository.key
|
||
https://git.unom.io/api/packages/unom/generic/punktfunk-keys/1/RPM-GPG-KEY-punktfunk
|
||
REPO
|
||
|
||
sudo dnf install punktfunk
|
||
sudo usermod -aG input "$USER" # /dev/uinput access for virtual gamepads (re-login to apply)
|
||
```
|
||
|
||
Updates later are just `sudo dnf upgrade punktfunk`, followed by
|
||
`systemctl --user restart punktfunk-host` so the running host picks up the new binary. The package
|
||
ships the systemd user units, the udev rule, the UDP socket-buffer sysctl tuning, and example
|
||
configs.
|
||
|
||
The group you picked above is the **stable** channel. For the latest `main` build, point `baseurl` at
|
||
`fedora-44-canary` (or `bazzite-canary`) instead — see [Release Channels](/docs/channels). Updating
|
||
in general, including the opt-in one-click button in the web console, is covered in
|
||
[Updating the Host](/docs/updating).
|
||
|
||
> `fedora-44` and `bazzite` are the only stable groups published, so on Fedora 42 or older — or on a
|
||
> release newer than 44 — there's nothing matching yet. Build one with the same toolchain CI uses —
|
||
> `docker build --build-arg FEDORA_VERSION=NN -f ci/fedora-rpm.Dockerfile -t pf-rpm ci` then run
|
||
> `packaging/rpm/build-rpm.sh` inside it — or build from source (appendix below).
|
||
|
||
## 3. Check it installed
|
||
|
||
Before moving on, confirm the binary is there and nothing else is competing for the same job:
|
||
|
||
```sh
|
||
punktfunk-host --version # the binary is on PATH
|
||
punktfunk-host detect-conflicts # exits 1 if Sunshine/Apollo is also installed
|
||
```
|
||
|
||
If `detect-conflicts` reports another streaming host, remove it before going further — two hosts on
|
||
one machine is the most common reason a clean install never streams. See
|
||
[Troubleshooting → another streaming host is installed](/docs/troubleshooting#another-streaming-host-sunshine-apollo--is-installed).
|
||
|
||
Once you've enabled the service on your desktop page below, these are how you watch it:
|
||
|
||
```sh
|
||
systemctl --user status punktfunk-host # active
|
||
journalctl --user -u punktfunk-host -f # watch a client connect
|
||
```
|
||
|
||
## 4. Open the firewall
|
||
|
||
Fedora runs **firewalld** by default and the package never edits your firewall, so the host stays
|
||
unreachable until you allow it. The RPM installs the service definitions — enable them once.
|
||
|
||
The packaged unit runs `serve --gamestream` — the RPM installs it as it ships and only rewrites the
|
||
binary path — so a host you enabled with `systemctl --user enable --now punktfunk-host` serves
|
||
**both** the native `punktfunk/1` plane and stock [Moonlight](/docs/moonlight) clients, and needs
|
||
**both** services:
|
||
|
||
```sh
|
||
sudo firewall-cmd --reload # load the installed definitions
|
||
sudo firewall-cmd --permanent --add-service=punktfunk-native
|
||
sudo firewall-cmd --permanent --add-service=punktfunk-gamestream
|
||
sudo firewall-cmd --reload
|
||
```
|
||
|
||
`punktfunk-native` opens UDP 9777 (QUIC control), UDP 5353 (mDNS discovery) and TCP 47990 (the
|
||
mgmt/library API — HTTPS + mTLS, read-only off loopback). `punktfunk-gamestream` opens the fixed
|
||
Moonlight ports — TCP 47984, 47989 and 48010, UDP 47998–48000 — plus the same mDNS. The media
|
||
**data plane** uses an ephemeral UDP port the client opens with a hole-punch, so there is nothing
|
||
fixed to open for video.
|
||
|
||
Switched the host to **native-only** — dropped `--gamestream` with a
|
||
`systemctl --user edit punktfunk-host` drop-in, or you run `punktfunk-host serve` by hand? Then add
|
||
`punktfunk-native` alone and leave `punktfunk-gamestream` out. `systemctl --user cat punktfunk-host`
|
||
shows which one yours is.
|
||
|
||
And if you want the web console reachable from another device, open **TCP 47992**:
|
||
|
||
```sh
|
||
sudo firewall-cmd --permanent --add-service=punktfunk-web && sudo firewall-cmd --reload
|
||
```
|
||
|
||
## 5. Configure your desktop
|
||
|
||
How the host creates its virtual display and injects input depends on your desktop, not your distro.
|
||
Continue on the page for the desktop you run — it covers your `host.env`, any compositor quirks, and
|
||
starting the host:
|
||
|
||
- [KDE Plasma (KWin)](/docs/kde)
|
||
- [GNOME (Mutter)](/docs/gnome)
|
||
- [Steam / gamescope](/docs/gamescope)
|
||
- [Hyprland](/docs/hyprland)
|
||
- [Sway / wlroots](/docs/sway)
|
||
|
||
Enable the browser management console (status, paired devices, arm pairing) — see
|
||
[Web Console](/docs/web-console).
|
||
|
||
For a headless KWin appliance that streams at boot with no graphical login, see
|
||
[KDE → Headless session](/docs/kde#headless-session).
|
||
|
||
Full config reference: [Configuration](/docs/configuration). Service model:
|
||
[Running as a Service](/docs/running-as-a-service).
|
||
|
||
## 6. Connect a client
|
||
|
||
From any [client](/docs/clients), `--discover` finds the host on the LAN. On first connect, complete
|
||
the **PIN pairing** — arm it from the host's [web console](/docs/web-console#arm-pairing), which
|
||
displays a 4-digit PIN to type into the client. See [Clients](/docs/clients) and
|
||
[Pairing](/docs/pairing).
|
||
|
||
## Next steps
|
||
|
||
- **Keep it current** — [Updating the Host](/docs/updating).
|
||
- **Remove it again** — [Uninstalling](/docs/uninstall).
|
||
- **Something not working?** — [Troubleshooting](/docs/troubleshooting).
|
||
|
||
## Appendix — build from source
|
||
|
||
If there's no RPM for your Fedora release and you don't want to build one, compile the host directly
|
||
(no clean updates / no packaged units — you wire those up by hand):
|
||
|
||
```sh
|
||
sudo dnf install gcc gcc-c++ make cmake clang clang-devel nasm git pkgconf-pkg-config \
|
||
pipewire-devel wayland-devel wayland-protocols-devel libxkbcommon-devel opus-devel \
|
||
libdrm-devel mesa-libgbm-devel mesa-libGL-devel mesa-libEGL-devel mesa-libGLES-devel libva-devel \
|
||
ffmpeg-devel libei-devel
|
||
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
|
||
git clone https://git.unom.io/unom/punktfunk.git && cd punktfunk
|
||
cargo build --release --locked \
|
||
--features punktfunk-host/nvenc,punktfunk-host/vulkan-encode \
|
||
-p punktfunk-host
|
||
```
|
||
|
||
`mesa-libGL-devel` isn't optional — the zero-copy GPU path links `libGL`, and without it the build
|
||
fails at the link step with `cannot find -lGL`. The two `--features` are what the packaged builds
|
||
use: leave them off and the host has no direct NVENC (NVIDIA) and no Vulkan Video encode
|
||
(AMD/Intel), and quietly falls back to the slower libav backends.
|
||
|
||
Then write `~/.config/punktfunk/host.env` (as in `/usr/share/punktfunk/host.env.kde`, but the host
|
||
binary is `target/release/punktfunk-host`) and run it inside your desktop session — for a headless
|
||
KWin appliance see [KDE → Headless session](/docs/kde#headless-session).
|