mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 21:12:08 +00:00
[GH-ISSUE #221] Fail to stream on older Intel GPUs (11th Gen Rocket Lake and older) #150
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#150
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 @Squid1917 on GitHub (Jul 3, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/221
Run the container get black screen when load any app. docs say its expected but it doesnt disapear even after 30 mins
Docker Compose
Docker Container Logs
@Squid1917 commented on GitHub (Jul 3, 2025):
Server is running ubuntu with intel intergrated graphics
@ABeltramo commented on GitHub (Jul 3, 2025):
Which CPU have you got? It might be "too old" to support the latest DMA buffer capabilities in our latest zero copy pipeline. You could try setting the env variable
WOLF_USE_ZERO_COPY=FALSEand see if that helps@Squid1917 commented on GitHub (Jul 3, 2025):
I have a Celeron 3865U. Its old I know.
Edit: still black screen but im getting audio with the test ball application
@DanCardin commented on GitHub (Jul 6, 2025):
I'm seeing the same with an i5-8500T. with/without WOLF_USE_ZERO_COPY makes no difference. And i get audio and input (at least steam is outputting audio when i hit the arrow keys)
Error seems exactly the same, but i get a ton of lines of
gst_element_send_event: assertion 'GST_IS_ELEMENT (element)' failedfwiw@Squid1917 commented on GitHub (Jul 6, 2025):
Same, did you find any fix
@ABeltramo commented on GitHub (Jul 6, 2025):
Right, so I think that the issue here is related to the upgrade of the base images to Ubuntu 25.04 which doesn't seem to bundle
libmfxwhich is the discontinued library needed for older Intel GPUs.I'll see if and how we can bring that back so that we continue to support them with future releases..
@Squid1917 commented on GitHub (Jul 6, 2025):
Any temporary fix in the meantime
@DanCardin commented on GitHub (Jul 6, 2025):
I swapped my image to
ghcr.io/games-on-whales/wolf:sha-b98d1c4(the latest published version before that rebase afaict) and that does appear to fix the video issue! so issue confirmed.@Squid1917 commented on GitHub (Jul 6, 2025):
Wonderful, thanks so much.
Couple of other questions anyway to put behind a reverse proxy so I can have friends use it and how is the game library stored. Also can I run something like playnite on wolf if so how. Thanks again awesome work.
@ABeltramo commented on GitHub (Jul 7, 2025):
Just pushed a fix for this, you can test it out by switching to
I've tested it on an
i5-8500Tmyself, and I can correctly use the latest zero copy pipeline there. Got some surprisingly good results too: 1440p@100 or 4K@40. Let me know if that fixes it for you too guys!Moonlight doesn't work like that, it needs raw access to a bunch of TCP/UDP ports so you can't just put it behind a proxy. We discourage users to open up the required ports to the outside word for security reasons. You should consider setting up a VPN/Wireguard/Tailscale to provide secure access to stuff on your LAN to the outside world.
See the docs. FYI this is also going to change a lot with https://github.com/games-on-whales/wolf/pull/179 which introduces support for profiles and lobbies which will open a lot of new possibilities.
We don't have a pre-made image for Playnite on GOW yet, but it's possible to build your own images if you want to get your hands dirty, you can read more about it here
@DanCardin commented on GitHub (Jul 7, 2025):
Idk if this is unrelated or not, but after getting it to work with the aforementioned tag, i tried your above test fix and now get:
But now switching back to the original tag does nothing either. 😬
@ABeltramo commented on GitHub (Jul 7, 2025):
@DanCardin the Steam container is failing to start for some reason, I would suggest pulling the latest
and if that persists, you can see the logs of the dying container by adding the env variable
WOLF_LOG_LEVEL=DEBUGto Wolf.