mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
HWA not working with Intel B580 #7263
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @remygrandin on GitHub (Aug 18, 2025).
Description of the bug
On a new installation, using 10.11 RC5, when activating HWA with VAAPI the streaming fail.
FFMPEG report an error 135
Reproduction steps
What is the current bug behavior?
Streaming fail with HWA
What is the expected correct behavior?
Sreaming work with HWA
Jellyfin Server version
10.10.0+
Specify commit id
No response
Specify unstable release number
No response
Specify version number
10.11.0 RC5
Specify the build version
10.11.0-rc5
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
Tried updating the intel driver (intel-opencl-icd), it seem the debian of the current docker image is not recent enough, requireing newer glibc for exemple
The docker version seem to be using intel-opencl-icd/now 25.13.33276.16 but I find reference to much more recent version, like 25.31.34666.3 in some other forum
@PhilAllmighty commented on GitHub (Aug 19, 2025):
Any reason for VAAPI instead of QSV?
@remygrandin commented on GitHub (Aug 19, 2025):
As far as I understood the jellyfin docs, QSV is more for iGPU, and VAAPI for discreet ones, no?
I'll try with QSV to be sure.
@remygrandin commented on GitHub (Aug 19, 2025):
I confirm, same error code/behavior with QSV
@PhilAllmighty commented on GitHub (Aug 19, 2025):
oh well was worth a try I guess :-) ... still think you would get better performance with QSV over VAAPI at the end of the day... but don't know why it's not working with error code -135. I for myself have it working on 10.10.7... linux kernel 6.12.24. Same gpu
I'll let someone else with a better idea respond to this issue! Hope you get this working soon.
@nyanmisaka commented on GitHub (Aug 19, 2025):
Is Resizable BAR enabled in the BIOS? This is a mandatory requirement for Battlemage; otherwise the driver will crash.
@remygrandin commented on GitHub (Aug 19, 2025):
@nyanmisaka I think I enabled it, I'll double check
@PhilAllmighty are you on docker or on host?
@nyanmisaka commented on GitHub (Aug 19, 2025):
If your FFmpeg log only contains the provided part, then the driver has caused FFmpeg to crash.
You can also check if ReBAR is enabled by using
sudo dmesg | grep xe.@PhilAllmighty commented on GitHub (Aug 19, 2025):
Docker
@felix920506 commented on GitHub (Aug 19, 2025):
QSV should always be used unless you are running some ancient 5th gen or older iGPU.
@remygrandin commented on GitHub (Aug 20, 2025):
Ok so I definitly have enabled the ReBAR in the UEFI but all check on the linux side say me it's not ... I'll open a case with the GPU card vendor, we'll see ....
But according to the jellyfin documentation, it should only impact the max perf, but still work without it, no ?
@nyanmisaka commented on GitHub (Aug 20, 2025):
It is indeed noted in the documentation but not in the correct section, I have updated it.
https://github.com/jellyfin/jellyfin.org/pull/1527/files
@felix920506 commented on GitHub (Aug 20, 2025):
We had outdated info on our docs. Rebar is not required for Arc A series but is required for Arc B series cards.
@remygrandin commented on GitHub (Aug 25, 2025):
Ok, as a note for the next person who might face a similar issue :
The steps I took included :
Use clinfoto check for rebar enablementNow It finally work, and I only have to fine tune it as I get choppy video on big files, probably have to play with some of the values in it or find a less HDR/big file.
Thanks everyone anyway, i'll close the issue