mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 21:12:08 +00:00
[GH-ISSUE #301] Wolf fails to create CUDA/DMA buffers on Arch Linux + NVIDIA + Wayland (Hyprland) #213
Labels
No labels
🧠 1 - 🤖 999
AMD
bug
bug
cannot reproduce
documentation
duplicate
easy
enhancement
enhancement
enhancement
fixed?
fixed?
good first issue
hard
help wanted
Intel
invalid
LXC
medium
moonlight-protocol
Multi GPU
nixos
not a bug
nvidia
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/wolf#213
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @flathead on GitHub (Nov 25, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/301
Description
Wolf fails to start streaming sessions with a black screen, followed by container crashes. The root cause is
waylanddisplaysrcfailing to create GsCUDABuf and DMA buffers.Environment
ghcr.io/games-on-whales/wolf:stableSystem Configuration
Docker Compose Configuration
Steps to Reproduce
nvidia-drm.modeset=1kernel parameterdocker volume create nvidia-driver-volExpected Behavior
Actual Behavior
Error Logs
Critical Errors
Full Stack Trace
GStreamer Pipeline Error
NVIDIA EGL Platform Error
Attempted Solutions
nvidia-drm.modeset=1is set/dev/dri/,/dev/nvidia*devices/run/udev:/run/udev:rwmountnvidia-driver-voland mounted itCreating CUDA context for device /dev/dri/renderD128 (detected CUDA device ID: 0)tmpfs: /usr/share/egl:rw- still read-only error/usr/share/egl- still read-only errorAdditional Context
waylanddisplaysrc Plugin Info
Device Access in Container
Full logs
Questions
/usr/share/eglfilesystem issue a known limitation?Related Issues
Possibly related to:
@ABeltramo commented on GitHub (Nov 25, 2025):
Your compose specification is messed up.
You are mixing the Nvidia container toolkit with the Nvidia manual method from the quickstart guide; you have to pick one of the two options and don't mix the arguments.
We suggest using the Nvidia driver volume method because it's the most reliable, so I suggest you to start with that and see if it works.
Everything else is pretty much all an AI hallucination 😉
@flathead commented on GitHub (Dec 3, 2025):
Yes, I tried to solve the problem through AI, since both standard methods don’t work. GStreamer exits with a critical error:
All I see when launching, regardless of which of the two methods I choose, is a black screen in Moonlight. I haven’t found any solutions in the issues, and I don’t have the expertise to fix it myself. Searching didn’t help, and AI couldn’t help in this situation either.
In the Arch + Wayland configuration, the configs don’t work.
@Greaper88 commented on GitHub (Dec 4, 2025):
Since you've changed methods, try using
docker compose down -vto clear the saved volumes. I've had to do this a couple of times to fix issues.@flathead commented on GitHub (Dec 4, 2025):
The first thing I tried was restarting the containers. Here’s a brief list of what I’ve attempted: restarting, reinstalling Docker and NVIDIA drivers, changing the configuration, trying to fix things from inside the containers, completely reinstalling Wolf. None of the methods or solutions I found on Google or in the Issues have helped. Once, after trying to reinstall Wolf, I managed to get video and audio in the Test Ball, but after reconnecting to Wolf again — black screen, and I couldn’t get even the Test Ball to start anymore.
@ABeltramo commented on GitHub (Dec 4, 2025):
@flathead I was suggesting to change your manually edited
compose.ymlwith the default from the quickstart guide. Since you've first opened this we've also released a few updates. First, make sure that you have the latest image with:After that, can you try running the following
without changing anything and see if that works for you? If it doesn't, can you please post the full Wolf logs when running it with these exact settings?
@flathead commented on GitHub (Dec 4, 2025):
@ABeltramo
Unfortunately, with the updated image and this Compose config the exact same issue remains — a black screen. Below are the logs when launching Test Ball and Wolf UI.
Test Ball logs:
Wolf UI logs:
@ABeltramo commented on GitHub (Dec 4, 2025):
It seems that everything is working fine, Moonlight isn't able to connect to Wolf for some reason.
Which specific Moonlight client are you using? Can you try another one? Is this running over LAN or WAN? Any firewall in between?
@flathead commented on GitHub (Dec 4, 2025):
Thank you for your help! I wrote a long message earlier about the Moonlight clients I’m using, that I added the required ports to iptables, tried disabling it, but nothing helped.
After I ran
sudo systemctl stop iptablesand thensudo systemctl start iptables, streaming suddenly started working for the first time in all my attempts! It wasn’t obvious, and I still don’t understand the connection, since I had already restarted iptables after adding the Wolf ports.Anyway, thank you! :)
@ABeltramo commented on GitHub (Dec 4, 2025):
No worries! Glad that was an easy fix! Have fun with Wolf! 😉