2023-09-18, 10:33 PM
(This post was last modified: 2023-09-18, 10:40 PM by bitmap. Edited 2 times in total.)
Gotta make that declaration a code block or it just thinks you're very meh about your iGPU...
I also tend to add the associated card device (which is card0 if you're using the Intel device and do not have a dGPU on the device...doubtful in a NAS box).
Also I'd take a look at the user running Jellyfin and see what groups they're part of, as @nooobieee suggested. Then you can:
This is important because differernt distros use different groups for device perms. Ubuntu uses video and render. So it would look like this for me (requires sudo, but you'll never copy sudo from me):
You can figure out exactly which version of Linux you're running by using a few different commands, but try:
Or:
I also tend to add the associated card device (which is card0 if you're using the Intel device and do not have a dGPU on the device...doubtful in a NAS box).
Code:
devices:
- /dev/dri/renderD128:/dev/dri/renderD128
- /dev/dri/card0:/dev/dri/card0
Also I'd take a look at the user running Jellyfin and see what groups they're part of, as @nooobieee suggested. Then you can:
Code:
usermod -aG [group1],[group2] [user]
This is important because differernt distros use different groups for device perms. Ubuntu uses video and render. So it would look like this for me (requires sudo, but you'll never copy sudo from me):
Code:
usermod -aG video,render bitmap
You can figure out exactly which version of Linux you're running by using a few different commands, but try:
Code:
cat /etc/os-release
Or:
Code:
lsb_release -a
Jellyfin 10.10.5 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage