• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting Hardware Acceleration not working on fresh Debian 12

     
    • 0 Vote(s) - 0 Average

    Hardware Acceleration not working on fresh Debian 12

    Hardware Acceleration not working on fresh Debian 12
    sananani
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2024 Feb
    Reputation: 0
    Country:Germany
    #1
    2024-02-13, 11:51 PM
    Hey Guys,
    after googling around i landed here in hope, someone can help me. I just bought a fresh EX101 at Hetzner (german server provider) (INTEL i9 13900), installed fresh debian 12 (6.1.0-13-amd64), installed fresh jellyfin like you described in the quick start section. After that, i went to the hardware-acceleration guide here -> https://jellyfin.org/docs/general/admini...ion/intel/

    Did any step like described and everything worked so far but at step 7, when i enter:

    Code:
    sudo /usr/lib/jellyfin-ffmpeg/vainfo --display drm --device /dev/dri/renderD128

    it doesn't work. This is the log/output ->

    Code:
    root@Debian-bookworm-latest-amd64-base /media # sudo /usr/lib/jellyfin-ffmpeg/vainfo --display drm --device /dev/dri/renderD128
    Trying display: drm
    libva info: VA-API version 1.20.0
    libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
    libva info: Found init function __vaDriverInit_1_20
    libva error: /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so init failed
    libva info: va_openDriver() returns 1
    libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/i965_drv_video.so
    libva info: Found init function __vaDriverInit_1_20
    libva error: /usr/lib/jellyfin-ffmpeg/lib/dri/i965_drv_video.so init failed
    libva info: va_openDriver() returns -1
    vaInitialize failed with error code -1 (unknown libva error),exit

    intel-opencl-icd is at version 22.43.24595.41-1

    Hetzner has also a guide to enable iGPU, but that one is from 2019 and i already enabled it/it was already enabled. 

    Code:
    root@Debian-bookworm-latest-amd64-base /media # ls -lisa /dev/dri/
    total 0
    690 0 drwxr-xr-x  3 root root        100 Feb 13 23:22 .
      1 0 drwxr-xr-x 18 root root      3680 Feb 13 23:50 ..
    697 0 drwxr-xr-x  2 root root        80 Feb 13 23:22 by-path
    692 0 crw-rw----  1 root video  226,  0 Feb 13 23:22 card0
    691 0 crw-rw----  1 root render 226, 128 Feb 13 23:22 renderD128

    So as i couldn't find any working solution for my problem here, on reddit or on stackoverflow, i hope someone can guide me the way to get hardware acceleration running. Of course i added the user to the group render and did any step as described inside your manual.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2024-02-14, 12:01 AM
    What is the output of

    Code:
    sudo apt list --installed | grep headers

    If it is blank, run

    Code:
    sudo apt install linux-headers-amd64
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    sananani
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2024 Feb
    Reputation: 0
    Country:Germany
    #3
    2024-02-14, 08:31 AM
    (2024-02-14, 12:01 AM)TheDreadPirate Wrote: What is the output of
    Code:
    sudo apt list --installed | grep headers

    Hey DreadPirate, thanks for your reply! I already have all headers installed ->

    Code:
    linux-headers-6.1.0-18-amd64/stable,stable,now 6.1.76-1 amd64 [installed,automatic]
    linux-headers-6.1.0-18-common/stable,stable,now 6.1.76-1 all [installed,automatic]
    linux-headers-amd64/stable,stable,now 6.1.76-1 amd64 [installed]
    nyanmisaka
    Offline

    Team Member

    Posts: 258
    Threads: 0
    Joined: 2023 Jun
    Reputation: 10
    #4
    2024-02-14, 11:01 AM
    The user-side VA-API driver cannot communicate with the kernel driver. This usually means that the i915 driver on the kernel side is outdated or the GPU firmware is not loading properly. Please share the output of sudo dmesg | grep i915.
    tmsrxzar
    Offline

    Senior Member

    Posts: 755
    Threads: 6
    Joined: 2023 Nov
    Reputation: 20
    #5
    2024-02-14, 05:13 PM
    since this is a VPS that you are paying for then part of what you are paying for is their support

    kernel things in a VPS are usually based on the host system and proxied into the VPS so if you're not able to load drivers and do other kernel related things it may be something they need to setup on their side

    recommend seeking support from your VPS provider
    sananani
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2024 Feb
    Reputation: 0
    Country:Germany
    #6
    2024-02-14, 09:13 PM
    (2024-02-14, 11:01 AM)nyanmisaka Wrote: Please share the output of sudo dmesg | grep i915.

    Thanks four your reply nyanmisaka - please see attached the output, seems like there is sth wrong.

    Code:
    root@Debian-bookworm-latest-amd64-base ~ # sudo dmesg | grep i915
    [    3.128805] i915 0000:00:02.0: [drm] VT-d active for gfx access
    [    3.128823] i915 0000:00:02.0: vgaarb: deactivate vga console
    [    3.128853] i915 0000:00:02.0: [drm] Using Transparent Hugepages
    [    3.129429] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
    [    3.129542] i915 0000:00:02.0: firmware: failed to load i915/adls_dmc_ver2_01.bin (-2)
    [    3.129546] i915 0000:00:02.0: firmware: failed to load i915/adls_dmc_ver2_01.bin (-2)
    [    3.129547] i915 0000:00:02.0: Direct firmware load for i915/adls_dmc_ver2_01.bin failed with error -2
    [    3.129549] i915 0000:00:02.0: [drm] Failed to load DMC firmware i915/adls_dmc_ver2_01.bin. Disabling runtime power management.
    [    3.129550] i915 0000:00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
    [    3.129863] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_70.bin (-2)
    [    3.129866] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_70.bin (-2)
    [    3.129869] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_70.1.1.bin (-2)
    [    3.129871] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_70.1.1.bin (-2)
    [    3.129874] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_69.0.3.bin (-2)
    [    3.129876] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_69.0.3.bin (-2)
    [    3.129878] i915 0000:00:02.0: GuC firmware i915/tgl_guc_70.bin: fetch failed with error -2
    [    3.129879] i915 0000:00:02.0: Please file a bug on drm/i915; see https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for details.
    [    3.129880] i915 0000:00:02.0: [drm] GuC firmware(s) can be downloaded from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
    [    3.207195] i915 0000:00:02.0: [drm] GuC firmware i915/tgl_guc_70.bin version 0.0.0
    [    3.207268] i915 0000:00:02.0: GuC initialization failed -2
    [    3.207269] i915 0000:00:02.0: Enabling uc failed (-5)
    [    3.207270] i915 0000:00:02.0: Failed to initialize GPU, declaring it wedged!
    [    3.207630] i915 0000:00:02.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by intel_gt_init+0xb3/0x2f0 [i915]
    [    3.398865] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
    [    3.399760] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
    [    3.399918] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
    [    3.399985] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes


    (2024-02-14, 05:13 PM)tmsrxzar Wrote: since this is a VPS that you are paying for then part of what you are paying for is their support
    Of course i will do that when its clear that it's a problem they can help with.
    sananani
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2024 Feb
    Reputation: 0
    Country:Germany
    #7
    2024-02-14, 09:35 PM
    I just found out: Hetzner has disabled some modules via a
    Code:
    blacklist-hetzner.conf
    ... 


    1.  
    Code:
    nano /etc/modprobe.d/blacklist-hetzner.conf

    Code:
    ### Hetzner Online GmbH - installimage
    ### unwanted kernel modules
    blacklist pcspkr
    blacklist snd_pcsp
    ### buggy kernel modules
    blacklist mei
    blacklist mei-me
    blacklist sm750fb

    just comment out
    Code:
    blacklist mei
    and
    Code:
    blacklist mei-me
    with
    Code:
    #
    , reboot, done - it works. 

    Sorry guys, that i didn't looked that up before. But thanks for help!
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode