| 29 Apr 2023 |
 diode_ee | Nice! | 16:22:35 |
| diode_ee | Did you end up enabling quicksync on your instance? If so, what was required to be added in order to get it to work with JF? | 16:29:40 |
 jwillikers | In reply to @diode_ee:matrix.org
Did you end up enabling quicksync on your instance? If so, what was required to be added in order to get it to work with JF? My ROCKPro64 doesn't have QuickSync, but I did configure Jellyfin for using the hardware accelerated graphics. You need to make sure the user running containers is in the render group, or whatever group has ownership of /dev/dri. For good measure, you might want to add the user to the video group, too. Once you have that configured, you need to run the container with the flags to add the user inside the container to those groups, i.e. --group-add (getent group render | cut -d: -f3) and --group-add (getent group video | cut -d: -f3). That should take care of access, which just leaves passing through the actual hardware devices. Pass through all of the devices under /dev/dri with a --device flag. On my setup, this I have to pass through use these flags: --device /dev/dri/card0:/dev/dri/card0, --device /dev/dri/card1:/dev/dri/card1, and --device /dev/dri/renderD128:/dev/dri/renderD128. | 22:35:47 |
| jwillikers | In reply to @diode_ee:matrix.org
Did you end up enabling quicksync on your instance? If so, what was required to be added in order to get it to work with JF? * My ROCKPro64 doesn't have QuickSync, but I did configure Jellyfin for using the hardware accelerated graphics. You need to make sure the user running containers is in the render group, or whatever group has ownership of /dev/dri. For good measure, you might want to add the user to the video group, too. Once you have that configured, you need to run the container with the flags to add the user inside the container to those groups, i.e. --group-add (getent group render | cut -d: -f3) and --group-add (getent group video | cut -d: -f3). That should take care of access, which just leaves passing through the actual hardware devices. Pass through all of the devices under /dev/dri with a --device flag. On my setup, I have to use these flags: --device /dev/dri/card0:/dev/dri/card0, --device /dev/dri/card1:/dev/dri/card1, and --device /dev/dri/renderD128:/dev/dri/renderD128. | 22:37:04 |
| jwillikers | * My ROCKPro64 doesn't have QuickSync, but I did configure Jellyfin to use the hardware accelerated graphics. You need to make sure the user running containers is in the render group, or whatever group has ownership of /dev/dri. For good measure, you might want to add the user to the video group, too. Once you have that configured, you need to run the container with the flags to add the user inside the container to those groups, i.e. --group-add (getent group render | cut -d: -f3) and --group-add (getent group video | cut -d: -f3). That should take care of access, which just leaves passing through the actual hardware devices. Pass through all of the devices under /dev/dri with a --device flag. On my setup, I have to use these flags: --device /dev/dri/card0:/dev/dri/card0, --device /dev/dri/card1:/dev/dri/card1, and --device /dev/dri/renderD128:/dev/dri/renderD128. | 22:37:33 |
| 30 Apr 2023 |
|  @glownigger:matrix.ralnet.org joined the room. | 01:39:59 |
 Strit | I wasn't aware that the jellyfin container's ffmpeg had support for v4l2-requests, which is what the GPU in Rockchip boards use for acceleration. | 06:11:11 |
| diode_ee | In reply to @jwillikers:matrix.org
My ROCKPro64 doesn't have QuickSync, but I did configure Jellyfin to use the hardware accelerated graphics. You need to make sure the user running containers is in the render group, or whatever group has ownership of /dev/dri. For good measure, you might want to add the user to the video group, too. Once you have that configured, you need to run the container with the flags to add the user inside the container to those groups, i.e. --group-add (getent group render | cut -d: -f3) and --group-add (getent group video | cut -d: -f3). That should take care of access, which just leaves passing through the actual hardware devices. Pass through all of the devices under /dev/dri with a --device flag. On my setup, I have to use these flags: --device /dev/dri/card0:/dev/dri/card0, --device /dev/dri/card1:/dev/dri/card1, and --device /dev/dri/renderD128:/dev/dri/renderD128. This is what I had in my docker-compose file on my debian box which is still up and running. I'm passing the /dev/dri through to the container and quicksync is working. Maybe that's not my issue here? I'll try adding the user to the video group to see if that helps. | 13:54:27 |
| diode_ee | jellyfin:
image: lscr.io/linuxserver/jellyfin:latest
container_name: jellyfin
environment:
- PUID=1000
- PGID=1000
- UMASK=002
- TZ=America/Los_Angeles
- DOCKER_MODS=linuxserver/mods:jellyfin-opencl-intel
- JELLYFIN_PublishedServerUrl=192.168.0.5 #optional
volumes:
- /home/diode/docker_apps/jellyfin/:/config
- /mnt/data/:/data/
- /mnt/data:/data/
ports:
- 8096:8096
- 8920:8920 #optional
- 7359:7359/udp #optional
- 1900:1900/udp #optional
restart: unless-stopped
devices:
- /dev/dri:/dev/dri
| 13:54:28 |
| jwillikers | While I did manage to configure it I never did properly test it. The ffmpeg comes from Debian stable and I don't see any flag to specifically enable the feature. Has v4l2-requests landed in upstream ffmpeg? | 14:14:12 |
| jwillikers | In reply to @diode_ee:matrix.org
jellyfin:
image: lscr.io/linuxserver/jellyfin:latest
container_name: jellyfin
environment:
- PUID=1000
- PGID=1000
- UMASK=002
- TZ=America/Los_Angeles
- DOCKER_MODS=linuxserver/mods:jellyfin-opencl-intel
- JELLYFIN_PublishedServerUrl=192.168.0.5 #optional
volumes:
- /home/diode/docker_apps/jellyfin/:/config
- /mnt/data/:/data/
- /mnt/data:/data/
ports:
- 8096:8096
- 8920:8920 #optional
- 7359:7359/udp #optional
- 1900:1900/udp #optional
restart: unless-stopped
devices:
- /dev/dri:/dev/dri
On NixOS, run ls -l /dev/dri to show the permissions there. You can use group_add in your Docker Compose: https://docs.docker.com/compose/compose-file/compose-file-v2/#group_add and you can add devices using the devices key: https://docs.docker.com/compose/compose-file/compose-file-v2/#devices | 14:17:58 |
| diode_ee | I have a Rock 5 that I'm still trying to get up and running. It will eventually make its way over to my trailer and we'll use it as a streaming device while camping. I'm still having a difficult time getting that one to boot from the m.2 without freezing up constantly. | 15:19:26 |
| diode_ee | looks like it's still "render" group for the QuickSync. | 15:22:29 |
| diode_ee | rw-rw-rw- 1 root render 226, 128 Apr 28 06:12 renderD128
| 15:22:30 |
| Strit | No it has not | 15:58:08 |
|  qmaiaiaiahak joined the room. | 16:02:32 |
| 1 May 2023 |
|  @kusuriya:corrupted.io joined the room. | 22:35:21 |
|  opensourceaccountant changed their display name from opensourceaccountant to openSourceAccountant. | 23:17:33 |
| 2 May 2023 |
|  mrios joined the room. | 01:27:07 |
| @glownigger:matrix.ralnet.org left the room. | 08:52:00 |
| 3 May 2023 |
|  stefan joined the room. | 22:56:50 |
| 4 May 2023 |
|  coffeeandcynicism joined the room. | 00:31:57 |
| 5 May 2023 |
|  @qck4fun:matrix.bohemiahoney.cz joined the room. | 19:29:39 |
| @qck4fun:matrix.bohemiahoney.cz left the room. | 19:30:22 |
| 6 May 2023 |
|  Brett joined the room. | 23:36:27 |
| 8 May 2023 |
|  fungear5010 joined the room. | 01:09:28 |
|  Danny Seymour joined the room. | 04:43:18 |
| Danny Seymour changed their display name from firstofth300 to Danny Seymour. | 04:45:22 |
| Danny Seymour set a profile picture. | 04:45:38 |
|  nafnlaus changed their profile picture. | 21:13:33 |
