QSV not working after restart

[TheDreadPirate]

Step 4.

https://jellyfin.org/docs/general/admini...untu-linux

[Ergo]

I tried setting up HW acceleration today, after installing an i7-7700 in place of the i5-6400t that i had. I don't know anything about computers but got it working. After a necessary reboot (had to install a chassis fan) HW acceleration doesn't work anymore. I cannot play videos on my smartphone (I could before) and I absolutely don't know how to fix it

[TheDreadPirate]

What OS and what settings are you using in Jellyfin. Share screenshots of Dashboard > Playback.

[Ergo]

Jellyfin 10.9.8 runs on a Debian OS CT, has a mount to a NAS (guess it doesn't matter)

I have to clarify something first: I am basically illiterate about this stuff, so, if you don't want to explain stuff like you'd have to at a 4yo I won't blame you. That said...

To initially set HW acc. I followed this tutorial: https://www.youtube.com/watch?v=XAa_qpNmzZs&t=965s (hope i can post this link)

Now HW acceleration is working again. I suspect it's because I retyped the command "chmod -R 777 /dev/dri/*" (I don't even know what it means) on the Host, because that is the only thing I did except for typing "ls /dev/dri" and "intel_gpu_top" again in the container shell.

Is there a way to make it that I don't need to do that everytime it boots?

jellyfin config
https://ibb.co/fCx20LN

(i'll post dashboard playback settings if needed. I figured, since I didn't change anything in there before it worked again, it might be irrelevant)

PC Config:
HP Elitedesk Mini 800 G3
I7-7700
16 GB ram
256GB nvme m.2 + 500gb HDD

[TheDreadPirate]

Giving yourself permissions to the GPU with "chmod -R 777 /dev/dri/*" is only temporary. When you reboot it will reset. Follow our directions at the link below to permanently give jellyfin permissions to access the GPU.

https://jellyfin.org/docs/general/admini...on-proxmox

[Ergo]

Giving yourself permissions to the GPU with "chmod -R 777 /dev/dri/*" is only temporary.  When you reboot it will reset.  Follow our directions at the link below to permanently give jellyfin permissions to access the GPU.

https://jellyfin.org/docs/general/admini...on-proxmox

I guess you are referring to the "4.Add jellyfin user to the video, render and/or input groups depending on who owns the device inside the container." part.
But isn't that referring to the commands I already launched, after the chmod line, inside the the jellyfin CT while setting up everything? specifically "usermod -aG render jellyfin"; "usermod -aG video jellyfin" and "usermod -aG input jellyfin". Or is there something I am totally clueless about? Is the user "jellyfin" (I login in the CT shell with "root" but i guess the user is jellyfin, at least when i connect via webUI? Is there something else I should do on the Host? (for me the indication of point 4 isn't dumbed down enough but "jellyfin" user doesn't exist on the Host so I guess it's not it).

   

I guess, with the settings I linked, I'm also running a privileged container (unprivilged container=no). I'm honestly stuck

[Ergo]

Giving yourself permissions to the GPU with "chmod -R 777 /dev/dri/*" is only temporary.  When you reboot it will reset.  Follow our directions at the link below to permanently give jellyfin permissions to access the GPU.

https://jellyfin.org/docs/general/admini...on-proxmox

I guess you are referring to the "4.Add jellyfin user to the video, render and/or input groups depending on who owns the device inside the container." part.
But isn't that referring to the commands I already launched, after the chmod line, inside the the jellyfin CT while setting up everything? specifically "usermod -aG render jellyfin"; "usermod -aG video jellyfin" and "usermod -aG input jellyfin". Or is there something I am totally clueless about? Is the user "jellyfin" (I login in the CT shell with "root" but i guess the user is jellyfin, at least when i connect via webUI? Is there something else I should do on the Host? (for me the indication of point 4 isn't dumbed down enough but "jellyfin" user doesn't exist on the Host so I guess it's not it).



I guess, with the settings I linked, I'm also running a privileged container (unprivilged container=no). I'm honestly stuck

I can  confirm that: power just shut down for a brief moment, server reboot, HW acceleration broke, typed "chmod -R 777 /ect/dri/*" and worked again. I have no idea, nor found any instruction on how to solve this