SOLVED: New A380, trouble with HW acceleration

SOLVED: New A380, trouble with HW acceleration - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: New A380, trouble with HW acceleration (/t-solved-new-a380-trouble-with-hw-acceleration)

Pages: 1 2

New A380, trouble with HW acceleration - JustAnotherDude - 2025-02-11

I recently got a Sparkle A380 to add to my linux server. Up until now I have been running everything on a Ryzen 7600 with the integrated graphics.

I think I have all of the necessary Intel GPU packages installed. I enabled Intel QSV and checked all of the boxes under 'Enable Hardware Decoding For:' header, checked boxes for 'Enable Hardware Encoding' and allow encoding in both HEVC and AV1.

Trying to play any video fails with the following log:

Code:
Stream mapping:

  Stream #0:0 -> #0:0 (hevc (hevc_qsv) -> av1 (av1_qsv))

  Stream #0:1 -> #0:1 (aac (native) -> aac (libfdk_aac))

Press [q] to stop, [?] for help

[libfdk_aac @ 0x556e65015d40] Note, the VBR setting is unsupported and only works with some parameter combinations

[av1_qsv @ 0x556e64eee800] Error initializing the encoder: unknown error (-1)

[vost#0:0/av1_qsv @ 0x556e64f72780] Error while opening encoder - maybe incorrect parameters such as bit_rate, rate, width or height.

[vf#0:0 @ 0x556e64eec840] Error sending frames to consumers: Unknown error occurred

[vf#0:0 @ 0x556e64eec840] Task finished with error code: -1313558101 (Unknown error occurred)

[vf#0:0 @ 0x556e64eec840] Terminating thread with return code -1313558101 (Unknown error occurred)

[vost#0:0/av1_qsv @ 0x556e64f72780] Could not open encoder before EOF

[vost#0:0/av1_qsv @ 0x556e64f72780] Task finished with error code: -22 (Invalid argument)

[vost#0:0/av1_qsv @ 0x556e64f72780] Terminating thread with return code -22 (Invalid argument)

[out#0/hls @ 0x556e64fed840] Nothing was written into output file, because at least one of its streams received no packets.

frame=    0 fps=0.0 q=0.0 Lsize=      0KiB time=N/A bitrate=N/A speed=N/A    

Conversion failed!

Disabling all HW acceleration allows video playback as normal.

Does anybody have any tips for configuring Jellyfin to use the Intel A380?

RE: New A380, trouble with HW acceleration - TheDreadPirate - 2025-02-11

What distro is running on? Did you install the HuC/GuC firmware?

What is the output of this command?

Code:
sudo dmesg | grep i915

If your server has been up for a while, that command may not output anything. Run this command instead to search older dmesg logs.

Code:
sudo grep i915 /var/log/dmesg.log.1

sudo zgrep i915 /var/log/dmesg.*.gz

RE: New A380, trouble with HW acceleration - JustAnotherDude - 2025-02-12

I am using OpenMandriva, this is a fresh install done after putting the A380 in my PC, so I assume the i915 installed automatically.

Code:
[JustAnotherDude@localhost ~]$ sudo dmesg | grep i915

[    3.855290] i915 0000:03:00.0: [drm] Found DG2/G11 (device ID 56a5) display version 13.00 stepping C0

[    3.856175] i915 0000:03:00.0: [drm] VT-d active for gfx access

[    3.856201] i915 0000:03:00.0: vgaarb: deactivate vga console

[    3.870164] i915 0000:03:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none

[    3.874748] i915 0000:03:00.0: [drm] Finished loading DMC firmware i915/dg2_dmc_ver2_08.bin (v2.8)

[    3.922393] i915 0000:03:00.0: [drm] GT0: GuC firmware i915/dg2_guc_70.bin version 70.29.2

[    3.922396] i915 0000:03:00.0: [drm] GT0: HuC firmware i915/dg2_huc_gsc.bin version 7.10.16

[    3.931859] i915 0000:03:00.0: [drm] GT0: GUC: submission enabled

[    3.931860] i915 0000:03:00.0: [drm] GT0: GUC: SLPC enabled

[    3.932064] i915 0000:03:00.0: [drm] GT0: GUC: RC enabled

[    3.952763] i915 0000:03:00.0: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.

[    3.971786] [drm] Initialized i915 1.6.0 for 0000:03:00.0 on minor 0

[    4.082359] fbcon: i915drmfb (fb0) is primary device

[    4.082395] i915 0000:03:00.0: [drm] fb0: i915drmfb frame buffer device

[    5.598562] snd_hda_intel 0000:04:00.0: bound 0000:03:00.0 (ops i915_audio_component_bind_ops [i915])

[    5.979337] i915 0000:03:00.0: [drm] GT0: HuC: authenticated for all workloads

[    5.979340] mei_pxp i915.mei-gsc.768-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:03:00.0 (ops i915_pxp_tee_component_ops [i915])

[JustAnotherDude@localhost ~]$

RE: New A380, trouble with HW acceleration - TheDreadPirate - 2025-02-12

How is Jellyfin installed? Docker? A generic Linux install? RPM via RPM Fusion?

RE: New A380, trouble with HW acceleration - JustAnotherDude - 2025-02-12

Installed by following the generic install instructions on the documentation page, using the newest tar.xz files.

RE: New A380, trouble with HW acceleration - TheDreadPirate - 2025-02-12

Did you also install jellyfin ffmpeg? Or are you using a generic version of ffmpeg?

RE: New A380, trouble with HW acceleration - JustAnotherDude - 2025-02-12

Jellyfin-ffmpeg 7.whatever from the downloads page.

RE: New A380, trouble with HW acceleration - TheDreadPirate - 2025-02-12

Can you share the full ffmpeg log?

RE: New A380, trouble with HW acceleration - JustAnotherDude - 2025-02-13

https://pastebin.com/fXNMYmmx

RE: New A380, trouble with HW acceleration - JustAnotherDude - 2025-02-13

Disabling the HEVC and AV1 options under the 'Encoding Format Options' allows for video playback. I still have 'Enable hardware encoding' option selected. Does this allow for hardware acceleration in H264 only? Or am I just falling back to CPU/software only?