+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Hardware Transcoding (/t-hardware-transcoding--6971)
Pages:
1
2
RE: Hardware Transcoding - taliaferro - 2024-07-16
(2024-07-16, 07:52 PM)TheDreadPirate Wrote: Did you pass the GPU into the VM? Is there anything when you run "ls -l /dev/dri" in the VM?
Again, check if you have the linux-headers package installed.
Thank you -- I do have the GPU passed through, it's there in /dev/dri and shows up in the output of lspci.
The instructions don't say to install
linux-headers, but I've just installed them. What will I use them for?
RE: Hardware Transcoding - TheDreadPirate - 2024-07-16
The linux-headers are not required for a lot of tasks, but they are important for transcoding. The Intel Quick Sync drivers (and Nvidia NVENC and AMD AMF) run in user space and need to interface with the kernel driver. The linux headers create that interface between user space and kernel space.
Most systems come with the linux-headers package when you install a kernel, but when you start using custom kernels if the meta package doesn't include the linux-headers then they don't get installed.
RE: Hardware Transcoding - taliaferro - 2024-07-17
Thank you for that explanation, that does help.
I've installed the headers for my kernel, but am still seeing the same error (
Failed to set value 'opencl@va' for option 'init_hw_device': No such device).What else should I try?
RE: Hardware Transcoding - TheDreadPirate - 2024-07-17
Restart the VM if you haven't done so. Make sure that IOMMU/VT-D is enabled in your BIOS. Double check the GPU passthrough is a true passthrough.
RE: Hardware Transcoding - draxer - 2024-07-17
I seem to have the same issue hardware transcoding stopped working and ffmpeg logs tell me
libva info: VA-API version 1.21.0
libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_21
libva info: va_openDriver() returns 0
libva info: VA-API version 1.21.0
libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_21
libva info: va_openDriver() returns 0
[AVHWDeviceContext @ 0x59efeceea440] Failed to get number of OpenCL platforms: -1001.
Device creation failed: -19.
Failed to set value 'opencl=ocl@va' for option 'init_hw_device': No such device
Error parsing global options: No such device
I am running jellyfin through a docker container on Ubuntu noble 24.04 x86_64 with kernel 6.8.0-38-generic.
Hardware is:
CPU: AMD Ryzen 5 3600X (12) @ 4,41 GHz
GPU: Intel Arc A380 @ 2,45 GHz
RE: Hardware Transcoding - TheDreadPirate - 2024-07-17
(2024-07-17, 05:07 PM)draxer Wrote: I seem to have the same issue hardware transcoding stopped working and ffmpeg logs tell me
libva info: VA-API version 1.21.0
libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_21
libva info: va_openDriver() returns 0
libva info: VA-API version 1.21.0
libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_21
libva info: va_openDriver() returns 0
[AVHWDeviceContext @ 0x59efeceea440] Failed to get number of OpenCL platforms: -1001.
Device creation failed: -19.
Failed to set value 'opencl=ocl@va' for option 'init_hw_device': No such device
Error parsing global options: No such device
I am running jellyfin through a docker container on Ubuntu noble 24.04 x86_64 with kernel 6.8.0-38-generic.
Hardware is:
CPU: AMD Ryzen 5 3600X (12) @ 4,41 GHz
GPU: Intel Arc A380 @ 2,45 GHz
@draxer - roll back the kernel to 6.8.0-36. 6.8.0-38 inherited an upstream kernel bug that breaks transcoding. One of the jellyfin devs and I submitted a report to the Ubuntu kernel team to backport a pair of patches.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072755
Nyanmisaka and I validated the backport worked on a test kernel. So it should appear in a later Ubuntu kernel release. For now stay on 6.8.0-36. Reboot your system, press Esc after the BIOS screen if your system doesn't show the boot loader by default, select Advanced and the -36 kernel should be an option.
RE: Hardware Transcoding - draxer - 2024-07-17
(2024-07-17, 05:25 PM)TheDreadPirate Wrote:(2024-07-17, 05:07 PM)draxer Wrote: I seem to have the same issue hardware transcoding stopped working and ffmpeg logs tell me
libva info: VA-API version 1.21.0
libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_21
libva info: va_openDriver() returns 0
libva info: VA-API version 1.21.0
libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_21
libva info: va_openDriver() returns 0
[AVHWDeviceContext @ 0x59efeceea440] Failed to get number of OpenCL platforms: -1001.
Device creation failed: -19.
Failed to set value 'opencl=ocl@va' for option 'init_hw_device': No such device
Error parsing global options: No such device
I am running jellyfin through a docker container on Ubuntu noble 24.04 x86_64 with kernel 6.8.0-38-generic.
Hardware is:
CPU: AMD Ryzen 5 3600X (12) @ 4,41 GHz
GPU: Intel Arc A380 @ 2,45 GHz
@draxer - roll back the kernel to 6.8.0-36. 6.8.0-38 inherited an upstream kernel bug that breaks transcoding. One of the jellyfin devs and I submitted a report to the Ubuntu kernel team to backport a pair of patches.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072755
Nyanmisaka and I validated the backport worked on a test kernel. So it should appear in a later Ubuntu kernel release. For now stay on 6.8.0-36. Reboot your system, press Esc after the BIOS screen if your system doesn't show the boot loader by default, select Advanced and the -36 kernel should be an option.
thanks for the help!
RE: Hardware Transcoding - taliaferro - 2024-07-18
Thanks for the guidance -- I've rebooted the VM and made doubly sure that IOMMU is enabled on my machine (the devices all show up in
/sys/kernel/iommu_groups on the host) but the problem persists.In addition, even with hardware transcoding turned on, playback works just fine with non-HDR content, so I think the GPU is properly being made available to the VM. (I'm glad, at least, that it's only HDR content causing problems!)
Are there more detailed troubleshooting steps I can try to make sure OpenCL is working correctly?
update: now this is interesting; once I set
amd_iommu=on in my kernel command line, the playback behavior didn't change -- but now that same OpenCL test from the documentation passes successfully...so maybe that *was* part of it?Now it seems the player just sits there indefinitely without crashing as well, which is interesting.
RE: Hardware Transcoding - TheDreadPirate - 2024-07-18
Does it generate an ffmpeg log? If so, can you share it. Also, strange that you had to make a kernel option change to get something to work.