• 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 Intel ARC Transcoding failure

    Pages (2): 1 2 Next »

     
    • 0 Vote(s) - 0 Average

    Intel ARC Transcoding failure

    FFmpeg error when transcoding using either QSV or VAAPI
    viggy96
    Offline

    Junior Member

    Posts: 9
    Threads: 2
    Joined: 2024 Sep
    Reputation: 0
    #1
    2025-01-21, 06:21 AM
    I've been trying to get hardware transcoding to work on my server using an Intel ARC A380 card. 
    I'm using Ubuntu 24.04, kernel 6.8.0-51.
    Official Jellyfin Docker container.
    When I run commands to test if transcoding will work, they seem to suggest it will.
    Also, intel_gpu_top shows activity like its trying to transcode.
    Here's the full FFmpeg logs.
    VAAPI: https://pastebin.com/63L77PRa
    QSV: https://pastebin.com/P1wvTVS8

    dco exec jellyfin /usr/lib/jellyfin-ffmpeg/ffmpeg -v verbose -init_hw_device qsv=hw -init_hw_device qsv@hw
    ffmpeg version 7.0.2-Jellyfin Copyright © 2000-2024 the FFmpeg developers
      built with gcc 12 (Debian 12.2.0-14)
      configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --extra-version=Jellyfin --disable-doc --disable-ffplay --disable-ptx-compression --disable-static --disable-libxcb --disable-sdl2 --disable-xlib --enable-lto=auto --enable-gpl --enable-version3 --enable-shared --enable-gmp --enable-gnutls --enable-chromaprint --enable-opencl --enable-libdrm --enable-libxml2 --enable-libass --enable-libfreetype --enable-libfribidi --enable-libfontconfig --enable-libharfbuzz --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libopenmpt --enable-libdav1d --enable-libsvtav1 --enable-libwebp --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-libzimg --enable-libfdk-aac --arch=amd64 --enable-libshaderc --enable-libplacebo --enable-vulkan --enable-vaapi --enable-amf --enable-libvpl --enable-ffnvcodec --enable-cuda --enable-cuda-llvm --enable-cuvid --enable-nvdec --enable-nvenc
      libavutil      59.  8.100 / 59.  8.100
      libavcodec    61.  3.100 / 61.  3.100
      libavformat    61.  1.100 / 61.  1.100
      libavdevice    61.  1.100 / 61.  1.100
      libavfilter    10.  1.100 / 10.  1.100
      libswscale      8.  1.100 /  8.  1.100
      libswresample  5.  1.100 /  5.  1.100
      libpostproc    58.  1.100 / 58.  1.100
    [AVHWDeviceContext @ 0x5ddac6052a80] Trying to use DRM render node for device 0, with matching vendor id (0x8086).
    [AVHWDeviceContext @ 0x5ddac6052a80] libva: VA-API version 1.22.0
    [AVHWDeviceContext @ 0x5ddac6052a80] libva: User requested driver 'iHD'
    [AVHWDeviceContext @ 0x5ddac6052a80] libva: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
    [AVHWDeviceContext @ 0x5ddac6052a80] libva: Found init function __vaDriverInit_1_22
    [AVHWDeviceContext @ 0x5ddac6052a80] libva: va_openDriver() returns 0
    [AVHWDeviceContext @ 0x5ddac6052a80] Initialised VAAPI connection: version 1.22
    [AVHWDeviceContext @ 0x5ddac6052a80] VAAPI driver: Intel iHD driver for Intel® Gen Graphics - 24.4.2 (b6b411f).
    [AVHWDeviceContext @ 0x5ddac6052a80] Driver not found in known nonstandard list, using standard behaviour.
    [AVHWDeviceContext @ 0x5ddac6052640] Use Intel® oneVPL to create MFX session, API version is 2.13, the required implementation version is 1.3
    libva info: VA-API version 1.22.0
    libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
    libva info: Found init function __vaDriverInit_1_22
    libva info: va_openDriver() returns 0
    libva info: VA-API version 1.22.0
    libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
    libva info: Found init function __vaDriverInit_1_22
    libva info: va_openDriver() returns 0
    [AVHWDeviceContext @ 0x5ddac6052640] Initialize MFX session: implementation version is 2.13
    Universal media converter
    usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

    Use -h to get full help or, even better, run 'man ffmpeg'

    dco exec jellyfin /usr/lib/jellyfin-ffmpeg/ffmpeg -v verbose -init_hw_device vaapi=vaConfused-facedev/dri/renderD128 -init_hw_device opencl@va
    ffmpeg version 7.0.2-Jellyfin Copyright © 2000-2024 the FFmpeg developers
      built with gcc 12 (Debian 12.2.0-14)
      configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --extra-version=Jellyfin --disable-doc --disable-ffplay --disable-ptx-compression --disable-static --disable-libxcb --disable-sdl2 --disable-xlib --enable-lto=auto --enable-gpl --enable-version3 --enable-shared --enable-gmp --enable-gnutls --enable-chromaprint --enable-opencl --enable-libdrm --enable-libxml2 --enable-libass --enable-libfreetype --enable-libfribidi --enable-libfontconfig --enable-libharfbuzz --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libopenmpt --enable-libdav1d --enable-libsvtav1 --enable-libwebp --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-libzimg --enable-libfdk-aac --arch=amd64 --enable-libshaderc --enable-libplacebo --enable-vulkan --enable-vaapi --enable-amf --enable-libvpl --enable-ffnvcodec --enable-cuda --enable-cuda-llvm --enable-cuvid --enable-nvdec --enable-nvenc
      libavutil      59.  8.100 / 59.  8.100
      libavcodec    61.  3.100 / 61.  3.100
      libavformat    61.  1.100 / 61.  1.100
      libavdevice    61.  1.100 / 61.  1.100
      libavfilter    10.  1.100 / 10.  1.100
      libswscale      8.  1.100 /  8.  1.100
      libswresample  5.  1.100 /  5.  1.100
      libpostproc    58.  1.100 / 58.  1.100
    [AVHWDeviceContext @ 0x56c17dd22640] libva: VA-API version 1.22.0
    [AVHWDeviceContext @ 0x56c17dd22640] libva: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
    [AVHWDeviceContext @ 0x56c17dd22640] libva: Found init function __vaDriverInit_1_22
    [AVHWDeviceContext @ 0x56c17dd22640] libva: va_openDriver() returns 0
    [AVHWDeviceContext @ 0x56c17dd22640] Initialised VAAPI connection: version 1.22
    [AVHWDeviceContext @ 0x56c17dd22640] VAAPI driver: Intel iHD driver for Intel® Gen Graphics - 24.4.2 (b6b411f).
    [AVHWDeviceContext @ 0x56c17dd22640] Driver not found in known nonstandard list, using standard behaviour.
    [AVHWDeviceContext @ 0x56c17dd5e3c0] 0.0: Intel® OpenCL Graphics / Intel® Arc™ A380 Graphics
    [AVHWDeviceContext @ 0x56c17dd5e3c0] Intel QSV to OpenCL mapping function found (clCreateFromVA_APIMediaSurfaceINTEL).
    [AVHWDeviceContext @ 0x56c17dd5e3c0] Intel QSV in OpenCL acquire function found (clEnqueueAcquireVA_APIMediaSurfacesINTEL).
    [AVHWDeviceContext @ 0x56c17dd5e3c0] Intel QSV in OpenCL release function found (clEnqueueReleaseVA_APIMediaSurfacesINTEL).
    Universal media converter
    usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

    Use -h to get full help or, even better, run 'man ffmpeg'
    gnattu
    Offline

    Team Member

    Posts: 342
    Threads: 0
    Joined: 2024 Feb
    Reputation: 17
    #2
    2025-01-21, 09:33 AM
    It appears that the file you intend to play contains unusual data that the hardware decoder encounters an issue with.
    nyanmisaka
    Offline

    Team Member

    Posts: 259
    Threads: 0
    Joined: 2023 Jun
    Reputation: 10
    #3
    2025-01-21, 02:12 PM (This post was last modified: 2025-01-21, 02:15 PM by nyanmisaka. Edited 1 time in total.)
    GPU's GuC/HuC firmware loading has failed.

    Check https://jellyfin.org/docs/general/admini...pu-support

    https://jellyfin.org/docs/general/admini...e-on-linux
    viggy96
    Offline

    Junior Member

    Posts: 9
    Threads: 2
    Joined: 2024 Sep
    Reputation: 0
    #4
    2025-01-22, 09:41 PM (This post was last modified: 2025-01-22, 09:44 PM by viggy96.)
    (2025-01-21, 02:12 PM)nyanmisaka Wrote: GPU's GuC/HuC firmware loading has failed.

    Check https://jellyfin.org/docs/general/admini...pu-support

    https://jellyfin.org/docs/general/admini...e-on-linux

    I've already checked GuC and HuC. When I run the commands to check the status, they appear to be running correctly.
    sudo cat /sys/kernel/debug/dri/1/gt0/uc/guc_info

    GuC firmware: i915/dg2_guc_70.bin
    status: RUNNING
    version: found 70.20.0
    uCode: 409856 bytes
    RSA: 384 bytes
    GuC status 0x8002f034:
    Bootrom status = 0x1a
    uKernel status = 0xf0
    MIA Core status = 0x2
    Scratch registers:
    0: 0x0
    1: 0xb03d7
    2: 0x42c800
    3: 0x4
    4: 0x40
    5: 0x3a0
    6: 0x56a50005
    7: 0x0
    8: 0x0
    9: 0x0
    10: 0x0
    11: 0x0
    12: 0x0
    13: 0x0
    14: 0x0
    15: 0x0

    GuC logging stats:
    Relay full count: 0
    DEBUG: flush count          0, overflow count          0
    CRASH: flush count          0, overflow count          0
    CAPTURE: flush count        74, overflow count          0
    CT enabled
    H2G Space: 2852
    Head: 306
    Tail: 306
    G2H Space: 12284
    Head: 320
    Tail: 320
    GuC Submission API Version: 1.9.0
    GuC Number Outstanding Submission G2H: 0
    GuC tasklet count: 0
    Requests in GuC submit tasklet:

    Global scheduling policies:
      DPC promote time  = 500000
      Max num work items = 15
      Flags              = 0

    sudo cat /sys/kernel/debug/dri/1/gt0/uc/huc_info

    HuC firmware: i915/dg2_huc_gsc.bin
    status: RUNNING
    version: found 7.10.3
    uCode: 0 bytes
    RSA: 0 bytes
    HuC status: 0x00164001

    I do see these errors repeating in dmesg | grep "i915":

    [369568.292626] Fence expiration time out i915-0000:83:00.0:vf#0:0[172986]:4!
    [369575.839717] i915 0000:83:00.0: [drm] GPU HANG: ecode 12:10:e75ffefe, in vf#0:0 [172986]
    [369575.839745] i915 0000:83:00.0: [drm] vf#0:0[172986] context reset due to GPU hang
    [369581.302844] i915 0000:83:00.0: [drm] GPU HANG: ecode 12:4:a77ffefe, in av:h264:df0 [173341]
    [369581.302872] i915 0000:83:00.0: [drm] av:h264:df0[173341] context reset due to GPU hang
    [369587.254425] i915 0000:83:00.0: [drm] GPU HANG: ecode 12:4:a77ffefe, in av:h264:df0 [173341]
    [369587.254453] i915 0000:83:00.0: [drm] av:h264:df0[173341] context reset due to GPU hang
    [369593.270410] i915 0000:83:00.0: [drm] GPU HANG: ecode 12:4:a77ffefe, in av:h264:df0 [173341]
    [369593.270439] i915 0000:83:00.0: [drm] av:h264:df0[173341] context reset due to GPU hang
    [369612.534503] i915 0000:83:00.0: [drm] GPU HANG: ecode 12:4:a77ffefe, in av:h264:df0 [173697]
    [369612.534532] i915 0000:83:00.0: [drm] av:h264:df0[173697] context reset due to GPU hang
    [369618.551027] i915 0000:83:00.0: [drm] GPU HANG: ecode 12:4:a77ffefe, in av:h264:df0 [173697]
    [369618.551056] i915 0000:83:00.0: [drm] av:h264:df0[173697] context reset due to GPU hang
    [369624.502370] i915 0000:83:00.0: [drm] GPU HANG: ecode 12:4:a77ffefe, in av:h264:df0 [173697]
    [369624.502399] i915 0000:83:00.0: [drm] av:h264:df0[173697] context reset due to GPU hang

    (2025-01-21, 09:33 AM)gnattu Wrote: It appears that the file you intend to play contains unusual data that the hardware decoder encounters an issue with.

    This happens with many files though, not just the one I've shown as an example.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #5
    2025-01-22, 10:38 PM
    Is this the first time you've used your Arc A380? I'm wondering if the card's firmware is very old.

    I wrote a guide for updating your Arc GPU's firmware in Linux.

    https://forum.jellyfin.org/t-flash-intel...e-in-linux

    The alternative is to throw this GPU in a Windows system. Intels driver installer also includes a firmware installer.
    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]
    viggy96
    Offline

    Junior Member

    Posts: 9
    Threads: 2
    Joined: 2024 Sep
    Reputation: 0
    #6
    2025-01-23, 07:57 AM (This post was last modified: 2025-01-23, 07:58 AM by viggy96.)
    (2025-01-22, 10:38 PM)TheDreadPirate Wrote: Is this the first time you've used your Arc A380?  I'm wondering if the card's firmware is very old.

    I wrote a guide for updating your Arc GPU's firmware in Linux.

    https://forum.jellyfin.org/t-flash-intel...e-in-linux

    The alternative is to throw this GPU in a Windows system.  Intels driver installer also includes a firmware installer.

    I've never used this card in anything except my server, and I've been trying for a while to get it to work for transcoding. And unfortunately I don't have any Windows system to put it in. I'll give your instructions a try, thanks.
    nyanmisaka
    Offline

    Team Member

    Posts: 259
    Threads: 0
    Joined: 2023 Jun
    Reputation: 10
    #7
    2025-01-23, 08:14 AM (This post was last modified: 2025-01-23, 08:16 AM by nyanmisaka. Edited 1 time in total.)
    What CPU and motherboard are you using? Do they support Resizable-BAR?

    Intel actually only supports ARC GPUs on a limited set of platforms.

    https://www.intel.com/content/www/us/en/...phics.html
    viggy96
    Offline

    Junior Member

    Posts: 9
    Threads: 2
    Joined: 2024 Sep
    Reputation: 0
    #8
    2025-01-23, 08:56 AM (This post was last modified: 2025-01-23, 08:57 AM by viggy96.)
    Hmm, didn't seem to do anything. Still get the same errors.

    (2025-01-23, 08:14 AM)nyanmisaka Wrote: What CPU and motherboard are you using? Do they support Resizable-BAR?

    Intel actually only supports ARC GPUs on a limited set of platforms.

    https://www.intel.com/content/www/us/en/...phics.html

    I'm using a ASRock Rack ROMED8-2T motherboard, with an EPYC 7702 processor. And resizable BAR is enabled in the BIOS.
    nyanmisaka
    Offline

    Team Member

    Posts: 259
    Threads: 0
    Joined: 2023 Jun
    Reputation: 10
    #9
    2025-01-23, 09:07 AM (This post was last modified: 2025-01-23, 09:09 AM by nyanmisaka.)
    They are new enough. I think the error is due to VBIOS or driver.

    If the output of sudo dmesg | grep i915 shows any other errors besides the above errors?
    viggy96
    Offline

    Junior Member

    Posts: 9
    Threads: 2
    Joined: 2024 Sep
    Reputation: 0
    #10
    2025-01-23, 09:20 AM (This post was last modified: 2025-01-23, 09:22 AM by viggy96. Edited 1 time in total.)
    No other errors in dmesg other than the ones I already shared above, a bunch of messages about GPU hang.
    I'm using the upstream driver in the kernel at the moment.
    Pages (2): 1 2 Next »

    « 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