Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable Intel media driver building #89

Merged
merged 1 commit into from
Feb 20, 2022

Conversation

Shadowghost
Copy link
Contributor

Changes:

References: jellyfin-archive/jellyfin-build#12

@Shadowghost
Copy link
Contributor Author

Shadowghost commented Feb 2, 2022

The pipeline failures are due to packages temporarily being not available via the Ubuntu mirrors.

Copy link
Member

@nyanmisaka nyanmisaka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Tested with Xe Graphics:

[AVHWDeviceContext @ 0x56516d303240] Trying to use DRM render node for device 0, with matching kernel driver (i915).
[AVHWDeviceContext @ 0x56516d303240] libva: VA-API version 1.14.0
[AVHWDeviceContext @ 0x56516d303240] libva: User requested driver 'iHD'
[AVHWDeviceContext @ 0x56516d303240] libva: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
[AVHWDeviceContext @ 0x56516d303240] libva: Found init function __vaDriverInit_1_14
[AVHWDeviceContext @ 0x56516d303240] libva: va_openDriver() returns 0
[AVHWDeviceContext @ 0x56516d303240] Initialised VAAPI connection: version 1.14
[AVHWDeviceContext @ 0x56516d303240] VAAPI driver: Intel iHD driver for Intel(R) Gen Graphics - 22.1.1 (31c1b99).
[AVHWDeviceContext @ 0x56516d303240] Driver not found in known nonstandard list, using standard behaviour.
[AVHWDeviceContext @ 0x56516d302d80] Initialize MFX session: API version is 1.35, implementation version is 1.35
[AVHWDeviceContext @ 0x56516d31f200] 0.0: Intel(R) OpenCL HD Graphics / Intel(R) Iris(R) Xe Graphics [0x9a49]
[AVHWDeviceContext @ 0x56516d31f200] Intel QSV to OpenCL mapping function found (clCreateFromVA_APIMediaSurfaceINTEL).
[AVHWDeviceContext @ 0x56516d31f200] Intel QSV in OpenCL acquire function found (clEnqueueAcquireVA_APIMediaSurfacesINTEL).
[AVHWDeviceContext @ 0x56516d31f200] Intel QSV in OpenCL release function found (clEnqueueReleaseVA_APIMediaSurfacesINTEL).

@joshuaboniface joshuaboniface merged commit 3c5d0de into jellyfin:jellyfin Feb 20, 2022
@theAeon
Copy link

theAeon commented Feb 23, 2022

wait, so how does this interact with the system installed intel-media-va-driver-non-free?

@nyanmisaka
Copy link
Member

wait, so how does this interact with the system installed intel-media-va-driver-non-free?

The included driver is only used by jellyfin-ffmpeg and won't affect other apps.

@theAeon
Copy link

theAeon commented Feb 24, 2022

only for the dockerized version? Or for any install?

@nyanmisaka
Copy link
Member

For any install. Other app won't load driver from the private folder of jellyfin-ffmpeg. /usr/lib/jellyfin-ffmpeg/lib/dri

@reffu42
Copy link

reffu42 commented Feb 28, 2022

How does this work for non-docker installs? The only file change I see is for docker-build..sh

@Shadowghost
Copy link
Contributor Author

Just install the new 4.4.1-2 release and the current Intel compute runtime. jellyfin-ffmpeg will automatically load the included driver.

There are only changes to docker-build.sh since there everything relevant is specified :)

@Shadowghost Shadowghost deleted the intel-media-driver branch February 28, 2022 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants