Submitted 1 month ago by swooosh@lemmy.world to selfhosted@lemmy.world
I try to follow the docs but somehow it doesn’t work as expected. How does your cpose file look and what to choose in the settins?
I believe you want to use QSV (VAAPI is there for older processors IIRC).
For running as rootless, you could try adding group-add keep-groups (an explanation from Redhat about keep-groups).
group-add keep-groups
thx, it does not change anything.,
I have found that VAAPI works better and doesn’t have issues.
VAAPI is the “standard” interface for hardware en-/decoding on Linux. It should work with any GPU using the open source drivers and mesa.
I don’t know how QSV can be installed; AMF, the AMD equivalent, is limited to their proprietary driver.
I think VAAPI is still how the gpu is accessed but you can use the intel libva driver (vaapi) or the intel media driver (QSV) (arch wiki page). If I’m interpreting this all correctly.
First add your user to the video and render groups. Additionally, set the pass through to /dev/dri/renderD128:/dev/DRI/renderD128
Another thing, I do not believe that podman compose is well maintained or stable. I would use podman from the command line.
In order for me to get transcoding working I had to have a window manager running. I also had to set Jellyfin to only try to transcode in supported formats.
Have you tried verifying it’s not the group permissions? You could preliminarily set permissions with chmod 666 /dev/dri/render128
My older Skylake processor has a bit worse video quality (occasional artifacts) with QuicSync.
chmod 666 /dev/dri/render128
thx, it does not change anything.
Hmm. I mean niw reading your first outpot in privileged mode, I don’t see any errors, or am I missing something… Seems it loaded vaapi sucessfully?!
Do not use 666 as that is completely open permissions. The proper way is to add your user to the render group.
New Lemmy Post: how to set up jellyfin with podman and selinux and an intel gpu (a380) for transcoding? (https://lemmyverse.link/lemmy.world/post/15511371)
Tagging: #SelfHosted
(Replying in the OP of this thread (NOT THIS BOT!) will appear as a comment in the lemmy discussion.)
I am a FOSS bot. Check my README: https://github.com/db0/lemmy-tagginator/blob/main/README.md
Kekin@lemy.lol 1 month ago
I can speak at least for rootless podman, I spent some hours on it and different ways I tried all ended in permission issues.
I gave up on trying to do it properly and just set the permissions of the /dev/dri device to 666, so that my podman container can use the gpu for transcoding.
Part of the issue with the container images that I tried is that they create a new user with whatever uid:gid I pass to the container, and so even if my nonroot user is part of the render group, the new user inside the container is not and so it can’t write to the /dev/dri/renderD128 (gpu), and so transcode wouldn’t work.
That’s where I left the troubleshooting at cause it was being a headache
herrfrutti@lemmy.world 1 month ago
I recommend this: https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html#method-1-give-your-user-permissions-on-every-reboot with that and aösp read the tipp after that I was troubleshooting my permission issues.
This should apply to gpu too.
possiblylinux127@lemmy.zip 1 month ago
Just add your local user to the render group.
swooosh@lemmy.world 1 month ago
thx for sharing your experience with it