mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-16 05:22:03 +00:00
[GH-ISSUE #225] Unable to use second GPU for encoding (Intel + AMD) #153
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#153
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 @HeiyuEP on GitHub (Jul 8, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/225
There are Internal data stream error when moonlight connect to steam.
graphics card:
docker-compose config:
wolf debug log:
@HeiyuEP commented on GitHub (Jul 8, 2025):
set the env variable WOLF_USE_ZERO_COPY=FALSE, and there wouldn't be this error. But I hope to use the zero copy version.
@ABeltramo commented on GitHub (Jul 8, 2025):
Our custom compositor is erroring out when trying to create a DMABuffer for the zero copy pipeline, these are the relevant lines
Could you provide me a couple more info?
/dev/dri/renderD129what are the other GPUs plugged into the system? Specifically what's/dev/dri/renderD128?RUST_LOG=INFOand post the full logs?I'm afraid that for that specific GPU you would have to use Wolf with the zero copy pipeline disabled until https://github.com/games-on-whales/gst-wayland-display/issues/7 is implemented..
@HeiyuEP commented on GitHub (Jul 9, 2025):
/dev/dri/renderD128is Intel's integrated graphics cardthe new log:
@ABeltramo commented on GitHub (Jul 16, 2025):
Sorry this has taken me this long to reply. I can see that the issue is that since you have multiple
VAAPIcapable devicesvapostprocis defaulting to the Intel GPU whilst the wayland compositor will try to render on the AMD card, so they end up disagreeing on the format used.Could you try adding the env variableGST_VAAPI_DRM_DEVICE=/dev/dri/renderD129and see if that fixes it for you? If it doesn't, can you post the logs again with that added?@ABeltramo commented on GitHub (Jul 16, 2025):
Discard what I proposed above. Can you try replacing in your
config.tomlthe defaultvah265encwithvarenderD129h265encso that it becomes:(assuming Moonlight asks for a HEVC video, that's the most common format. If not, you'll have to update all the other
va*encblocks)@ABeltramo commented on GitHub (Nov 27, 2025):
There's been a lot of work on this lately. For a dual Intel/AMD GPU setup you'll still have to manually exclude the render device from the mount points, but something like
has been reported https://github.com/games-on-whales/wolf/issues/297#issuecomment-3567587676 working