mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 21:12:08 +00:00
[GH-ISSUE #383] Old hardware, no display for Wolf UI, test ball works #257
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#257
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 @BlackFoxController on GitHub (Apr 3, 2026).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/383
Hi, I have an old processor (i5-3350P) and GPU (AMD Radeon 290X) and cannot get Wolf to work. Not sure if to post here or in gst-wayland-display repo
OS is Ubuntu 24.04.4 LTS
I get a few warnings that seem relevant:
Before an error:
wolf-1 | 15:09:44.795752483 ERROR | [GSTREAMER] Pipeline error: Internal data stream error.It's an issue with gstreamer I think, and I can get Wolf UI to work when I use the following environment flag:
WOLF_USE_ZERO_COPY=FALSEHowever, it is too slow to use.
I have installed Sunshine separately for reference / testing and that works perfectly and fast.
Has anyone encountered this before? I'm using the docker image ( image: ghcr.io/games-on-whales/wolf:stable )
Here is the full log:
@ABeltramo commented on GitHub (Apr 3, 2026):
Have you tried forcing H264 from the encoder settings in your moonlight client?
@BlackFoxController commented on GitHub (Apr 4, 2026):
Hi, just tried it. It doesn't make a difference.
@ABeltramo commented on GitHub (Apr 4, 2026):
It does because your GPU doesn't support anything else than H264 and in the logs you've posted above the client was asking for HEVC. Can you run it again and post the logs with added env variable
WOLF_LOG_LEVEL=DEBUG?@BlackFoxController commented on GitHub (Apr 4, 2026):
Thank you, here is another log with the WOLF_LOG_LEVEL=DEBUG config
Note/ added: I am on Xubuntu, using xfce, maybe the issue is there. It does not have Wayland (but x11 should be available).
@ABeltramo commented on GitHub (Apr 4, 2026):
I guess your HW really is too old to support our zero copy pipeline, have you tried using
WOLF_USE_ZERO_COPY=FALSEwith the H264 encoder though? It should be good enough for some light gaming.@BlackFoxController commented on GitHub (Apr 4, 2026):
I haven't tried any games, but when I enable it that way (h264 with WOLF_USE_ZERO_COPY=FALSE) it's very slow. The cursor moves with crazy lag, and using the keyboard to select apps is also very slow. Same when entering the desktop app. Very low framerate.
It's not the case with Sunshine (very fast). But I'm guessing the architecture is very different (here the hardware is meant to split / distribute the frames to each session), where in Sunshine it's only one render.
@BlackFoxController commented on GitHub (Apr 4, 2026):
Quick update: I switched to Arch Linux with KDE Plasma and Wayland, installed the docker container and it worked out of the box. Using the automatic hardware encoding was still very slow, but forcing it to h264 and it works perfectly. No .env flags are set.
@ABeltramo commented on GitHub (Apr 4, 2026):
Thanks for reporting back your findings, that's quite interesting and good to know. I'm sure I'll help others! Have fun with Wolf! 😉