mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-07-16 05:43:54 +03:00
[Issue]: iHD_drv_video.so init failed on Synology NAS #5420
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 @peerless2012 on GitHub (Feb 1, 2024).
Originally assigned to: @nyanmisaka on GitHub.
Please describe your bug
I use jellyfin on Synology NAS SA6400, when use package from the Package Center, the QSV and VAAPI transcode broken. when use the lastest mirror in docker, the transcode works fun with QSV.
Jellyfin Version
10.8.z
if other:
No response
Environment
Jellyfin logs
FFmpeg logs
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@nyanmisaka commented on GitHub (Feb 1, 2024):
@peerless2012
I suspect the Intel iHD driver from Synology Package Center is outdated for Intel N100.
Those package are not packaged and maintained by us.
@peerless2012 commented on GitHub (Feb 1, 2024):
The sa6400 is use Linux 5.10.55, and with the intel-gpu-i915-backports.
In docker, the transcode is worked, and it means the gpu driver is ok, there may be something else goes wrong.
@nyanmisaka commented on GitHub (Feb 1, 2024):
@peerless2012
I mean the user-space driver iHD, not the kernel-space driver i915. FFmpeg interacts with iHD not i915.
iHD is intel-media-driver, which is still in version 22.5. But the latest one is 24.1.2.
Please file an issue here to inform the SynoCommunity. https://github.com/SynoCommunity/spksrc/issues
@peerless2012 commented on GitHub (Feb 1, 2024):
I test emby test on my device use package, The transcode works 。It seems maybe you are right,The Synology package is not distributed by you ?
@nyanmisaka commented on GitHub (Feb 1, 2024):
Nope. I dont have Synology devices to test with.
@peerless2012 commented on GitHub (Feb 1, 2024):
OK, I Will follow up this issue, and close it when it is fix。
Anyway, thanks a lot for your work, to give us a free way for watch.
@felix920506 commented on GitHub (Mar 3, 2024):
Closing this as there is really nothing we can do about it.