Jellyfin hardware acceleration crashes after update

[ilovethensa]

Describe the bug

After i updated my server today hardware acceleration with quicksync no longer works

Steps To Reproduce

Steps to reproduce the behavior:

1. Use this config

  hardware.graphics = {
    # hardware.opengl in 24.05 and older
    enable = true;
    extraPackages = with pkgs; [
      intel-media-driver # For Broadwell (2014) or newer processors. LIBVA_DRIVER_NAME=iHD
      intel-vaapi-driver # For older processors. LIBVA_DRIVER_NAME=i965
      vaapiVdpau
      intel-compute-runtime # OpenCL filter support (hardware tonemapping and subtitle burn-in)
      vpl-gpu-rt # QSV on 11th gen or newer
      intel-media-sdk # QSV up to 11th gen
    ];
  };
  environment.sessionVariables = {LIBVA_DRIVER_NAME = "iHD";}; # Optionally, set the environment variable
  nixpkgs.config.packageOverrides = pkgs: {
    vaapiIntel = pkgs.vaapiIntel.override {enableHybridCodec = true;};
  };

3. enable hardware acceleration using QSV
4. Media doesnt play anymore

Expected behavior

It transcodes and streams the media using ffmpeg

Screenshots

Additional context

Here is the log of the transcode
https://pastebin.com/raw/p0AtE8M2

Metadata

 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.60, NixOS, 24.11 (Vicuna), 24.11.20241111.dc460ec`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.24.10`
 - nixpkgs: `/nix/store/4r8s42c9mwfvgdlxv0izb1cmlzrsb5nz-source`

Notify maintainers

@nyanloutre @minijackson @purcell @jojosch

---

Note for maintainers: Please tag this issue in your PR.

---

Add a 👍 reaction to issues you find important.

[purcell]

After i updated my server today

Updated from what to what? Did the jellyfin version change? I see mention of a similar issue here that seems related to opencl versions, so perhaps other library versions included in your update are responsible for this regression.

(Disclaimer: I'd find it hard to help much with the specific issue, not having a suitable Linux host available.)

[aloop]

I see mention of a similar issue here that seems related to opencl versions, so perhaps other library versions included in your update are responsible for this regression.

This is very possible I think. I'm pretty sure Jellyfin mainly uses OpenCL for certain subtitle operations and hardware accelerated HDR-to-SDR tone mapping. Tone mapping doesn't seem to be the culprit based on the logs given here, but DVDSUB format subtitles do appear to be present. If I recall correctly, DVDSBUB is an image-based format, and Jellyfin may try to use OpenCL to accelerate scaling/conversion/embedding.

Unfortunately it seems like Intel CPUs prior to Gen 12 have been moved to legacy support in intel-compute-runtime according to their repository, so it seems like the legacy branch may need to be packaged separately as intel-compute-runtime-legacy or something? For now I'm pulling in the version of the package from 24.05 and it's working for me on my i5-8500t system, this is obviously not a long-term solution though.

[ilovethensa]

I see mention of a similar issue here that seems related to opencl versions, so perhaps other library versions included in your update are responsible for this regression.

This is very possible I think. I'm pretty sure Jellyfin mainly uses OpenCL for certain subtitle operations and hardware accelerated HDR-to-SDR tone mapping. Tone mapping doesn't seem to be the culprit based on the logs given here, but DVDSUB format subtitles do appear to be present. If I recall correctly, DVDSBUB is an image-based format, and Jellyfin may try to use OpenCL to accelerate scaling/conversion/embedding.

Unfortunately it seems like Intel CPUs prior to Gen 12 have been moved to legacy support in intel-compute-runtime according to their repository, so it seems like the legacy branch may need to be packaged separately as intel-compute-runtime-legacy or something? For now I'm pulling in the version of the package from 24.05 and it's working for me on my i5-8500t system, this is obviously not a long-term solution though.

How did you manage to solve it? this is what i currently do, but it doesnt seem to work

  hardware.opengl = {
    # hardware.opengl in 24.05 and older
    enable = true;
    extraPackages = with inputs.nixpkgs-stable.legacyPackages.x86_64-linux; [
      intel-media-driver
      vaapiVdpau
      intel-media-sdk
      intel-compute-runtime
    ];
  };

nixpkgs-stable.url = "github:nixos/nixpkgs/nixos-24.05";

[aloop]

That's pretty close to what I'm currently doing, though I'm on nixos-unstable for everything other than intel-compute-runtime.

As a flake input I also have:

nixpkgs-stable.url = "github:nixos/nixpkgs/nixos-24.05";

Also in the flake, for my system with jellyfin I have the following module defining an overlay (so I access nixpkgs-stable via pkgs.stable)

{
  nixpkgs.overlays = [
    (final: prev: {
      stable = import nixpkgs-stable {
        system = prev.system;
        config.allowUnfree = true;
      };
    })
  ];
}

And then in that system's configuration:

hardware.graphics = {
  extraPackages = with pkgs; [
    intel-media-driver
    libva-vdpau-driver
    stable.intel-compute-runtime
    vpl-gpu-rt # QSV on 11th gen or newer
    intel-media-sdk # QSV up to 11th gen
  ];
};

[justinas]

Unfortunately it seems like Intel CPUs prior to Gen 12 have been moved to legacy support in intel-compute-runtime according to their repository, so it seems like the legacy branch may need to be packaged separately as intel-compute-runtime-legacy or something? For now I'm pulling in the version of the package from 24.05 and it's working for me on my i5-8500t system, this is obviously not a long-term solution though.

This seems like it could be the root cause. In that case it is a broader regression in regards to OpenCL on older Intel iGPUs.

On my end, I have a i3-10100 CPU which comes with Gen11 graphics, and the following:

{
  hardware.graphics = {
    enable = true;
    extraPackages = with pkgs; [
      vaapiIntel
      vaapiVdpau
      libvdpau-va-gl
      intel-media-driver
      intel-compute-runtime
    ];
  };
}

vainfo output is okay:

vainfo

# vainfo
Trying display: wayland
Trying display: x11
error: can't connect to X server!
Trying display: drm
libva info: VA-API version 1.22.0
libva info: Trying to open /run/opengl-driver/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 24.3.4 ()
vainfo: Supported profile and entrypoints
      VAProfileNone                   : VAEntrypointVideoProc
      VAProfileNone                   : VAEntrypointStats
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Simple            : VAEntrypointEncSlice
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointFEI
      VAProfileH264Main               : VAEntrypointEncSliceLP
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointFEI
      VAProfileH264High               : VAEntrypointEncSliceLP
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointEncPicture
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointFEI
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
      VAProfileVP8Version0_3          : VAEntrypointVLD
      VAProfileVP8Version0_3          : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointVLD
      VAProfileHEVCMain               : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointFEI
      VAProfileHEVCMain10             : VAEntrypointVLD
      VAProfileHEVCMain10             : VAEntrypointEncSlice
      VAProfileVP9Profile0            : VAEntrypointVLD
      VAProfileVP9Profile2            : VAEntrypointVLD

But OpenCL is missing, despite an ICD existing:

]# clinfo
Number of platforms                               0

ICD loader properties
  ICD loader Name                                 OpenCL ICD Loader
  ICD loader Vendor                               OCL Icd free software
  ICD loader Version                              2.3.2
  ICD loader Profile                              OpenCL 3.0

# ls -la /run/opengl-driver/etc/OpenCL/vendors/
total 12
dr-xr-xr-x 2 root root 4096 Jan  1  1970 .
dr-xr-xr-x 3 root root 4096 Jan  1  1970 ..
-r--r--r-- 2 root root  111 Jan  1  1970 intel-neo.icd

Everything was fine on 24.05 (Jellyfin via QSV with HDR tonemapping, subtitle burn-in).

I can confirm that by rolling back to 24.05's version of intel-compute-runtime OpenCL is fixed:

# clinfo | head -n 5
Number of platforms                               1
  Platform Name                                   Intel(R) OpenCL Graphics
  Platform Vendor                                 Intel(R) Corporation
  Platform Version                                OpenCL 3.0
  Platform Profile                                FULL_PROFILE

and Jellyfin transcodes work again (with either QSV or VAAPI option in Jellyfin).

[justinas]

Tagging @SuperSandro2000 as the maintainer of intel-compute-runtime.

Unfortunately it seems like Intel CPUs prior to Gen 12 have been moved to legacy support in intel-compute-runtime according to their repository, so it seems like the legacy branch may need to be packaged separately as intel-compute-runtime-legacy or something?

Any ideas on how we could remedy this? Having a "-legacy" package seems like a decent solution, but the unfortunate part is the 24.11 update already broke this, and introducing a "-legacy" package means it's a manual fix for anyone running older generations of Intel hardware. If we'd caught this before 24.11, it at least could've been noted in release notes 😕

I don't think we can combine both legacy and current packages into one derivation to support all hardware either?

[nyanmisaka]

My suggestion is to wait for the next release of intel compute-runtime and switch to depend on libigc2. Then add a -legacy package for legacy hardware and depend on legacy libigc1. This way there will be no dependency conflicts.

intel/compute-runtime#770
https://github.com/intel/intel-graphics-compiler/releases/tag/v2.1.12

BTW the OpenCL runtime is only used for tonemapping in Jellyfin, it has nothing to do with subtitles.

[Atemu]

the unfortunate part is the 24.11 update already broke this, and introducing a "-legacy" package means it's a manual fix for anyone running older generations of Intel hardware. If we'd caught this before 24.11, it at least could've been noted in release notes 😕

Eh, shit happens. We'll just simply backport the new legacy package. As long as we do that in the next few weeks, it's actually not a huge issue because 24.05 is still supported.

If this is only used for OpenCL, couldn't we just use Mesa's rusticl instead?

[nyanmisaka]

If this is only used for OpenCL, couldn't we just use Mesa's rusticl instead?

Compared to the compute-runtime developed by Intel, rusticl is more like an unpolished pet project. It lacks many extensions such as cl_intel_va_api_media_sharing which is required by Jellyfin and FFmpeg.

[aloop]

BTW the OpenCL runtime is only used for tonemapping in Jellyfin, it has nothing to do with subtitles.

Thanks for the clarification. I Could have sworn I had read that it was used to accelerate subtitle burn-in somewhere, but I must have it mixed up with some other software or something.

[justinas]

I looked into making a package of 24.35.30872.22 (the last release supporting legacy iGPUs), but for some reason I'm getting:

[AVHWDeviceContext @ 0x2ed45bc0] Failed to get number of OpenCL platforms: -1001.

from FFmpeg with it, despite clinfo reporting the device just fine. This is different from the version of i-c-r that we have in 24.05 - that works just fine.

It also seems theoretically possible to make a combined package of legacy + modern intel-compute-runtimes, since Intel smartly renamed everything _legacy on the legacy side, thus avoiding name clashes inside /run/opengl-driver. Here's what a "legacy" build of the 24.35.X branch looks like

$ tree result
result
├── bin
│   └── ocloc-24.35.0
├── etc
│   └── OpenCL
│       └── vendors
│           └── intel_legacy1.icd
├── include
│   └── level_zero
│       └── zet_intel_gpu_debug.h
└── lib
    ├── intel-opencl
    │   └── libigdrcl_legacy1.so
    └── libocloc_legacy1.so

I have only so much knowledge about all this, so I haven't figured out why my package no worky with jellyfin-ffmpeg. 😕 I might revisit it another day.

In any case, we should give this bug attention, since it affects more than just Jellyfin: OpenCL is broken on 24.11 for people using older, but not-that-old Intel iGPUs.