Re: [FFmpeg-user] Initialising hardware device fails with error -17
Hi Haihao, this is an update finding myself in a happy mood openSuSE ships both _libmfx_, and _libmfx-gen_. It took me some time to realise that, but your last response lead me in the right direction. I compiled libmfx-gen, and voila I can qsv transcode as desired. Thank you for your continuous support, Martin. Am 24/04/2024 um 04:26 schrieb Xiang, Haihao: Hi Martin, /usr/lib64/libmfxhw64.so.1.35 is for legacy HWs, you should install the vpl runtime for your i9-13900. libmfx-gen.so is a link to the vpl runtime. For example, below is the runtime in my system: $ ls -l /usr/lib/x86_64-linux-gnu/libmfx-gen.so* lrwxrwxrwx 1 root root17 Apr 24 10:09 /usr/lib/x86_64-linux-gnu/libmfx-gen.so -> libmfx-gen.so.1.2 lrwxrwxrwx 1 root root20 Apr 24 10:09 /usr/lib/x86_64-linux-gnu/libmfx-gen.so.1.2 -> libmfx-gen.so.1.2.10 -rw-r--r-- 1 root root 114212224 Apr 24 10:09 /usr/lib/x86_64-linux-gnu/libmfx-gen.so.1.2.10 Please install the runtime component via apt/yum etc or install the library to /usr/lib64 when building the runtime from source code, then retest. BRs Haihao Hi Haihao, when running "vpl-inspect", I get this, and only this Implementation #0: mfxhw64 Library path: /usr/lib64/libmfxhw64.so.1.35 AccelerationMode: MFX_ACCEL_MODE_VIA_VAAPI ApiVersion: 1.35 Impl: MFX_IMPL_TYPE_HARDWARE VendorImplID: 0x ImplName: mfxhw64 License: Version: 1.2 Keywords: MSDK,x64 VendorID: 0x8086 mfxAccelerationModeDescription: Version: 1.0 Mode: MFX_ACCEL_MODE_VIA_VAAPI mfxPoolPolicyDescription: Version: 1.0 mfxDeviceDescription: MediaAdapterType: MFX_MEDIA_UNKNOWN DeviceID: a780/0 Version: 1.1 mfxDecoderDescription: Version: 0.0 mfxEncoderDescription: Version: 0.0 mfxVPPDescription: Version: 0.0 NumExtParam: 0 Warning - MFX_IMPLCAPS_SURFACE_TYPES not supported Total number of implementations found = 1 I do NOT have the library "libmfx-gen.so" in my system... Best wishes, Martin. On Tuesday, 23 April, 2024 17:57 CEST, "Xiang, Haihao" wrote: Hi Martin, I may reproduce your issue in my side if there is only msdk runtime (libmfxhw.so) in my system. Could you run vpl-inspect to check whether vpl gpu runtime (libmfx-gen.so) is available in your side ? $ vpl-inspect | grep libmfx-gen.so BRs Haihao ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". -- Martin Stenzel · er/ihm · he/him m.sten...@mail.xy-space.de An der Drehscheibe 9 D-50733 Köln · Cologne Deutschland · Germany This message was checked by ESET Endpoint Antivirus for Linux. Detection Engine Version: 29125 (20240425). smime.p7s Description: S/MIME Cryptographic Signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Initialising hardware device fails with error -17
Hi Martin, /usr/lib64/libmfxhw64.so.1.35 is for legacy HWs, you should install the vpl runtime for your i9-13900. libmfx-gen.so is a link to the vpl runtime. For example, below is the runtime in my system: $ ls -l /usr/lib/x86_64-linux-gnu/libmfx-gen.so* lrwxrwxrwx 1 root root17 Apr 24 10:09 /usr/lib/x86_64-linux-gnu/libmfx-gen.so -> libmfx-gen.so.1.2 lrwxrwxrwx 1 root root20 Apr 24 10:09 /usr/lib/x86_64-linux-gnu/libmfx-gen.so.1.2 -> libmfx-gen.so.1.2.10 -rw-r--r-- 1 root root 114212224 Apr 24 10:09 /usr/lib/x86_64-linux-gnu/libmfx-gen.so.1.2.10 Please install the runtime component via apt/yum etc or install the library to /usr/lib64 when building the runtime from source code, then retest. BRs Haihao > > Hi Haihao, > > when running > > "vpl-inspect", I get this, and only this > Implementation #0: mfxhw64 > Library path: /usr/lib64/libmfxhw64.so.1.35 > AccelerationMode: MFX_ACCEL_MODE_VIA_VAAPI > ApiVersion: 1.35 > Impl: MFX_IMPL_TYPE_HARDWARE > VendorImplID: 0x > ImplName: mfxhw64 > License: > Version: 1.2 > Keywords: MSDK,x64 > VendorID: 0x8086 > mfxAccelerationModeDescription: > Version: 1.0 > Mode: MFX_ACCEL_MODE_VIA_VAAPI > mfxPoolPolicyDescription: > Version: 1.0 > mfxDeviceDescription: > MediaAdapterType: MFX_MEDIA_UNKNOWN > DeviceID: a780/0 > Version: 1.1 > mfxDecoderDescription: > Version: 0.0 > mfxEncoderDescription: > Version: 0.0 > mfxVPPDescription: > Version: 0.0 > NumExtParam: 0 > Warning - MFX_IMPLCAPS_SURFACE_TYPES not supported > > Total number of implementations found = 1 > I do NOT have the library "libmfx-gen.so" in my system... > > Best wishes, Martin. > > > > On Tuesday, 23 April, 2024 17:57 CEST, "Xiang, Haihao" > wrote: > > Hi Martin, > > I may reproduce your issue in my side if there is only msdk runtime > (libmfxhw.so) in my system. Could you run vpl-inspect to check whether vpl gpu > runtime (libmfx-gen.so) is available in your side ? > > $ vpl-inspect | grep libmfx-gen.so > > BRs > Haihao > > > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Initialising hardware device fails with error -17
Hi Haihao, when running "vpl-inspect", I get this, and only this Implementation #0: mfxhw64 Library path: /usr/lib64/libmfxhw64.so.1.35 AccelerationMode: MFX_ACCEL_MODE_VIA_VAAPI ApiVersion: 1.35 Impl: MFX_IMPL_TYPE_HARDWARE VendorImplID: 0x ImplName: mfxhw64 License: Version: 1.2 Keywords: MSDK,x64 VendorID: 0x8086 mfxAccelerationModeDescription: Version: 1.0 Mode: MFX_ACCEL_MODE_VIA_VAAPI mfxPoolPolicyDescription: Version: 1.0 mfxDeviceDescription: MediaAdapterType: MFX_MEDIA_UNKNOWN DeviceID: a780/0 Version: 1.1 mfxDecoderDescription: Version: 0.0 mfxEncoderDescription: Version: 0.0 mfxVPPDescription: Version: 0.0 NumExtParam: 0 Warning - MFX_IMPLCAPS_SURFACE_TYPES not supported Total number of implementations found = 1 I do NOT have the library "libmfx-gen.so" in my system... Best wishes, Martin. On Tuesday, 23 April, 2024 17:57 CEST, "Xiang, Haihao" wrote: Hi Martin, I may reproduce your issue in my side if there is only msdk runtime (libmfxhw.so) in my system. Could you run vpl-inspect to check whether vpl gpu runtime (libmfx-gen.so) is available in your side ? $ vpl-inspect | grep libmfx-gen.so BRs Haihao -- Martin Stenzel · er/ihm · he/him m.sten...@mail.xy-space.de An der Drehscheibe 9 D-50733 Köln · Cologne Deutschland · Germany This message was checked by ESET Endpoint Antivirus for Linux. Detection Engine Version: 29111 (20240423). smime.p7s Description: S/MIME Cryptographic Signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Initialising hardware device fails with error -17
Hi Martin, I may reproduce your issue in my side if there is only msdk runtime (libmfxhw.so) in my system. Could you run vpl-inspect to check whether vpl gpu runtime (libmfx-gen.so) is available in your side ? $ vpl-inspect | grep libmfx-gen.so BRs Haihao > > Dear all, > > well, I tried different versions, compiled, tried everything. > Still the error is there, no progress, unfortunately. > If, at any time, I will be more lucky than right now, I will let you know. > > Martin. > > > > On Monday, 22 April, 2024 17:46 CEST, "Xiang, Haihao" > wrote: > > > > > Hi, > > > > yes, I did so, but it did not help, see here > > > > vainfo > > Trying display: wayland > > Trying display: x11 > > libva info: VA-API version 1.20.0 > > libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so > > libva info: Found init function __vaDriverInit_1_20 > > libva info: va_openDriver() returns 0 > > vainfo: VA-API version: 1.20 (libva 2.20.1) > > vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 24.1.3 > > () > > vainfo: Supported profile and entrypoints > > ... > > > > I again receive this error. > > > > [AVHWDeviceContext @ 0x55be64a65600] libva: VA-API version 1.20.0 > > [AVHWDeviceContext @ 0x55be64a65600] libva: User requested driver 'iHD' > > [AVHWDeviceContext @ 0x55be64a65600] libva: Trying to open > > /usr/lib64/dri/iHD_drv_video.so > > [AVHWDeviceContext @ 0x55be64a65600] libva: Found init function > > __vaDriverInit_1_20 > > [AVHWDeviceContext @ 0x55be64a65600] libva: va_openDriver() returns 0 > > [AVHWDeviceContext @ 0x55be64a65600] Initialised VAAPI connection: version > > 1.20 > > [AVHWDeviceContext @ 0x55be64a65600] VAAPI driver: Intel iHD driver for > > Intel(R) Gen Graphics - 24.1.3 (). > > [AVHWDeviceContext @ 0x55be64a65600] Driver not found in known nonstandard > > list, using standard behaviour. > > [AVHWDeviceContext @ 0x55be64a65140] Use Intel(R) oneVPL to create MFX > > session, API version is 2.10, the required implementation version is 1.3 > > [AVHWDeviceContext @ 0x55be64a65140] Initialize MFX session: implementation > > version is 1.35 > > Seems you didn't install the right vpl runtime. You may install libmfx-gen1.2 > through yum/apt etc or build it from source code > (https://github.com/intel/vpl-gpu-rt ) > > > Thanks > Haihao > > > [AVHWDeviceContext @ 0x55be64a65140] Error setting child device handle: -17 > > Device creation failed: -1313558101. > > Failed to set value 'qsv:hw,child_device=/dev/dri/renderD128' for option > > 'init_hw_device': Unknown error occurred > > Error parsing global options: Unknown error occurred > > > > > > Martin. > > > > > > > > > > > > On Monday, 22 April, 2024 14:51 CEST, "Xiang, Haihao" > > wrote: > > > > [...] > > [AVHWDeviceContext @ 0x560662049440] libva: VA-API version 1.20.0 > > [AVHWDeviceContext @ 0x560662049440] libva: User requested driver 'iHD' > > [AVHWDeviceContext @ 0x560662049440] libva: Trying to open > > /usr/lib64/dri/iHD_drv_video.so > > [AVHWDeviceContext @ 0x560662049440] libva: Found init function > > __vaDriverInit_1_15 > > [AVHWDeviceContext @ 0x560662049440] libva: va_openDriver() returns 0 > > [AVHWDeviceContext @ 0x560662049440] Initialised VAAPI connection: version > > 1.20 > > [AVHWDeviceContext @ 0x560662049440] VAAPI driver: Intel iHD driver for > > Intel(R) Gen Graphics - 24.1.3 (). > > > > VA-API version is 1.20 however your driver was built against 1.15, could you > > rebuild your driver against vaapi 1.20 ? > > > > BRs > > Haihao > > > > > > ___ > > ffmpeg-user mailing list > > ffmpeg-user@ffmpeg.org > > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > > > To unsubscribe, visit link above, or email > > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". > > > > ___ > > ffmpeg-user mailing list > > ffmpeg-user@ffmpeg.org > > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > > > To unsubscribe, visit link above, or email > > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". > > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". > > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Initialising hardware device fails with error -17
Dear all, well, I tried different versions, compiled, tried everything. Still the error is there, no progress, unfortunately. If, at any time, I will be more lucky than right now, I will let you know. Martin. On Monday, 22 April, 2024 17:46 CEST, "Xiang, Haihao" wrote: > > Hi, > > yes, I did so, but it did not help, see here > > vainfo > Trying display: wayland > Trying display: x11 > libva info: VA-API version 1.20.0 > libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so > libva info: Found init function __vaDriverInit_1_20 > libva info: va_openDriver() returns 0 > vainfo: VA-API version: 1.20 (libva 2.20.1) > vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 24.1.3 () > vainfo: Supported profile and entrypoints > ... > > I again receive this error. > > [AVHWDeviceContext @ 0x55be64a65600] libva: VA-API version 1.20.0 > [AVHWDeviceContext @ 0x55be64a65600] libva: User requested driver 'iHD' > [AVHWDeviceContext @ 0x55be64a65600] libva: Trying to open > /usr/lib64/dri/iHD_drv_video.so > [AVHWDeviceContext @ 0x55be64a65600] libva: Found init function > __vaDriverInit_1_20 > [AVHWDeviceContext @ 0x55be64a65600] libva: va_openDriver() returns 0 > [AVHWDeviceContext @ 0x55be64a65600] Initialised VAAPI connection: version > 1.20 > [AVHWDeviceContext @ 0x55be64a65600] VAAPI driver: Intel iHD driver for > Intel(R) Gen Graphics - 24.1.3 (). > [AVHWDeviceContext @ 0x55be64a65600] Driver not found in known nonstandard > list, using standard behaviour. > [AVHWDeviceContext @ 0x55be64a65140] Use Intel(R) oneVPL to create MFX > session, API version is 2.10, the required implementation version is 1.3 > [AVHWDeviceContext @ 0x55be64a65140] Initialize MFX session: implementation > version is 1.35 Seems you didn't install the right vpl runtime. You may install libmfx-gen1.2 through yum/apt etc or build it from source code (https://github.com/intel/vpl-gpu-rt ) Thanks Haihao > [AVHWDeviceContext @ 0x55be64a65140] Error setting child device handle: -17 > Device creation failed: -1313558101. > Failed to set value 'qsv:hw,child_device=/dev/dri/renderD128' for option > 'init_hw_device': Unknown error occurred > Error parsing global options: Unknown error occurred > > > Martin. > > > > > > On Monday, 22 April, 2024 14:51 CEST, "Xiang, Haihao" > wrote: > > [...] > [AVHWDeviceContext @ 0x560662049440] libva: VA-API version 1.20.0 > [AVHWDeviceContext @ 0x560662049440] libva: User requested driver 'iHD' > [AVHWDeviceContext @ 0x560662049440] libva: Trying to open > /usr/lib64/dri/iHD_drv_video.so > [AVHWDeviceContext @ 0x560662049440] libva: Found init function > __vaDriverInit_1_15 > [AVHWDeviceContext @ 0x560662049440] libva: va_openDriver() returns 0 > [AVHWDeviceContext @ 0x560662049440] Initialised VAAPI connection: version > 1.20 > [AVHWDeviceContext @ 0x560662049440] VAAPI driver: Intel iHD driver for > Intel(R) Gen Graphics - 24.1.3 (). > > VA-API version is 1.20 however your driver was built against 1.15, could you > rebuild your driver against vaapi 1.20 ? > > BRs > Haihao > > > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". > > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". -- Martin Stenzel · er/ihm · he/him m.sten...@mail.xy-space.de An der Drehscheibe 9 D-50733 Köln · Cologne Deutschland · Germany This message was checked by ESET Endpoint Antivirus for Linux. Detection Engine Version: 29111 (20240423). smime.p7s Description: S/MIME Cryptographic Signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Initialising hardware device fails with error -17
> > Hi, > > yes, I did so, but it did not help, see here > > vainfo > Trying display: wayland > Trying display: x11 > libva info: VA-API version 1.20.0 > libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so > libva info: Found init function __vaDriverInit_1_20 > libva info: va_openDriver() returns 0 > vainfo: VA-API version: 1.20 (libva 2.20.1) > vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 24.1.3 () > vainfo: Supported profile and entrypoints > ... > > I again receive this error. > > [AVHWDeviceContext @ 0x55be64a65600] libva: VA-API version 1.20.0 > [AVHWDeviceContext @ 0x55be64a65600] libva: User requested driver 'iHD' > [AVHWDeviceContext @ 0x55be64a65600] libva: Trying to open > /usr/lib64/dri/iHD_drv_video.so > [AVHWDeviceContext @ 0x55be64a65600] libva: Found init function > __vaDriverInit_1_20 > [AVHWDeviceContext @ 0x55be64a65600] libva: va_openDriver() returns 0 > [AVHWDeviceContext @ 0x55be64a65600] Initialised VAAPI connection: version > 1.20 > [AVHWDeviceContext @ 0x55be64a65600] VAAPI driver: Intel iHD driver for > Intel(R) Gen Graphics - 24.1.3 (). > [AVHWDeviceContext @ 0x55be64a65600] Driver not found in known nonstandard > list, using standard behaviour. > [AVHWDeviceContext @ 0x55be64a65140] Use Intel(R) oneVPL to create MFX > session, API version is 2.10, the required implementation version is 1.3 > [AVHWDeviceContext @ 0x55be64a65140] Initialize MFX session: implementation > version is 1.35 Seems you didn't install the right vpl runtime. You may install libmfx-gen1.2 through yum/apt etc or build it from source code (https://github.com/intel/vpl-gpu-rt ) Thanks Haihao > [AVHWDeviceContext @ 0x55be64a65140] Error setting child device handle: -17 > Device creation failed: -1313558101. > Failed to set value 'qsv:hw,child_device=/dev/dri/renderD128' for option > 'init_hw_device': Unknown error occurred > Error parsing global options: Unknown error occurred > > > Martin. > > > > > > On Monday, 22 April, 2024 14:51 CEST, "Xiang, Haihao" > wrote: > > [...] > [AVHWDeviceContext @ 0x560662049440] libva: VA-API version 1.20.0 > [AVHWDeviceContext @ 0x560662049440] libva: User requested driver 'iHD' > [AVHWDeviceContext @ 0x560662049440] libva: Trying to open > /usr/lib64/dri/iHD_drv_video.so > [AVHWDeviceContext @ 0x560662049440] libva: Found init function > __vaDriverInit_1_15 > [AVHWDeviceContext @ 0x560662049440] libva: va_openDriver() returns 0 > [AVHWDeviceContext @ 0x560662049440] Initialised VAAPI connection: version > 1.20 > [AVHWDeviceContext @ 0x560662049440] VAAPI driver: Intel iHD driver for > Intel(R) Gen Graphics - 24.1.3 (). > > VA-API version is 1.20 however your driver was built against 1.15, could you > rebuild your driver against vaapi 1.20 ? > > BRs > Haihao > > > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". > > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Initialising hardware device fails with error -17
On Mon, 22 Apr 2024, 18:25 Martin Stenzel via ffmpeg-user, < ffmpeg-user@ffmpeg.org> wrote: > > Hi, > > yes, I did so, but it did not help, see here > > vainfo > Trying display: wayland > Trying display: x11 > libva info: VA-API version 1.20.0 > libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so > libva info: Found init function __vaDriverInit_1_20 > libva info: va_openDriver() returns 0 > vainfo: VA-API version: 1.20 (libva 2.20.1) > vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - > 24.1.3 () > vainfo: Supported profile and entrypoints > ... > > I again receive this error. > > [AVHWDeviceContext @ 0x55be64a65600] libva: VA-API version 1.20.0 > [AVHWDeviceContext @ 0x55be64a65600] libva: User requested driver 'iHD' > [AVHWDeviceContext @ 0x55be64a65600] libva: Trying to open > /usr/lib64/dri/iHD_drv_video.so > [AVHWDeviceContext @ 0x55be64a65600] libva: Found init function > __vaDriverInit_1_20 > [AVHWDeviceContext @ 0x55be64a65600] libva: va_openDriver() returns 0 > [AVHWDeviceContext @ 0x55be64a65600] Initialised VAAPI connection: version > 1.20 > [AVHWDeviceContext @ 0x55be64a65600] VAAPI driver: Intel iHD driver for > Intel(R) Gen Graphics - 24.1.3 (). > [AVHWDeviceContext @ 0x55be64a65600] Driver not found in known nonstandard > list, using standard behaviour. > [AVHWDeviceContext @ 0x55be64a65140] Use Intel(R) oneVPL to create MFX > session, API version is 2.10, the required implementation version is 1.3 > [AVHWDeviceContext @ 0x55be64a65140] Initialize MFX session: > implementation version is 1.35 > [AVHWDeviceContext @ 0x55be64a65140] Error setting child device handle: -17 > Device creation failed: -1313558101. > Failed to set value 'qsv:hw,child_device=/dev/dri/renderD128' for option > 'init_hw_device': Unknown error occurred > Error parsing global options: Unknown error occurred > > > Martin. > > > > > > On Monday, 22 April, 2024 14:51 CEST, "Xiang, Haihao" < > haihao.xiang-at-intel@ffmpeg.org> wrote: > > [...] > [AVHWDeviceContext @ 0x560662049440] libva: VA-API version 1.20.0 > [AVHWDeviceContext @ 0x560662049440] libva: User requested driver 'iHD' > [AVHWDeviceContext @ 0x560662049440] libva: Trying to open > /usr/lib64/dri/iHD_drv_video.so > [AVHWDeviceContext @ 0x560662049440] libva: Found init function > __vaDriverInit_1_15 > [AVHWDeviceContext @ 0x560662049440] libva: va_openDriver() returns 0 > [AVHWDeviceContext @ 0x560662049440] Initialised VAAPI connection: version > 1.20 > [AVHWDeviceContext @ 0x560662049440] VAAPI driver: Intel iHD driver for > Intel(R) Gen Graphics - 24.1.3 (). > > VA-API version is 1.20 however your driver was built against 1.15, could > you rebuild your driver against vaapi 1.20 ? > > BRs > Haihao > > > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". > > -- > Martin Stenzel · er/ihm · he/him > m.sten...@mail.xy-space.de > > An der Drehscheibe 9 > D-50733 Köln · Cologne > Deutschland · Germany > Install the runtime components and retest: sudo zypper install -y \ intel-level-zero-gpu level-zero \ intel-media-driver libigfxcmrt7 libvpl2 libvpl-tools libmfxgen1 libmfx1 > ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Initialising hardware device fails with error -17
Hi, yes, I did so, but it did not help, see here vainfo Trying display: wayland Trying display: x11 libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.20 (libva 2.20.1) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 24.1.3 () vainfo: Supported profile and entrypoints ... I again receive this error. [AVHWDeviceContext @ 0x55be64a65600] libva: VA-API version 1.20.0 [AVHWDeviceContext @ 0x55be64a65600] libva: User requested driver 'iHD' [AVHWDeviceContext @ 0x55be64a65600] libva: Trying to open /usr/lib64/dri/iHD_drv_video.so [AVHWDeviceContext @ 0x55be64a65600] libva: Found init function __vaDriverInit_1_20 [AVHWDeviceContext @ 0x55be64a65600] libva: va_openDriver() returns 0 [AVHWDeviceContext @ 0x55be64a65600] Initialised VAAPI connection: version 1.20 [AVHWDeviceContext @ 0x55be64a65600] VAAPI driver: Intel iHD driver for Intel(R) Gen Graphics - 24.1.3 (). [AVHWDeviceContext @ 0x55be64a65600] Driver not found in known nonstandard list, using standard behaviour. [AVHWDeviceContext @ 0x55be64a65140] Use Intel(R) oneVPL to create MFX session, API version is 2.10, the required implementation version is 1.3 [AVHWDeviceContext @ 0x55be64a65140] Initialize MFX session: implementation version is 1.35 [AVHWDeviceContext @ 0x55be64a65140] Error setting child device handle: -17 Device creation failed: -1313558101. Failed to set value 'qsv:hw,child_device=/dev/dri/renderD128' for option 'init_hw_device': Unknown error occurred Error parsing global options: Unknown error occurred Martin. On Monday, 22 April, 2024 14:51 CEST, "Xiang, Haihao" wrote: [...] [AVHWDeviceContext @ 0x560662049440] libva: VA-API version 1.20.0 [AVHWDeviceContext @ 0x560662049440] libva: User requested driver 'iHD' [AVHWDeviceContext @ 0x560662049440] libva: Trying to open /usr/lib64/dri/iHD_drv_video.so [AVHWDeviceContext @ 0x560662049440] libva: Found init function __vaDriverInit_1_15 [AVHWDeviceContext @ 0x560662049440] libva: va_openDriver() returns 0 [AVHWDeviceContext @ 0x560662049440] Initialised VAAPI connection: version 1.20 [AVHWDeviceContext @ 0x560662049440] VAAPI driver: Intel iHD driver for Intel(R) Gen Graphics - 24.1.3 (). VA-API version is 1.20 however your driver was built against 1.15, could you rebuild your driver against vaapi 1.20 ? BRs Haihao ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". -- Martin Stenzel · er/ihm · he/him m.sten...@mail.xy-space.de An der Drehscheibe 9 D-50733 Köln · Cologne Deutschland · Germany This message was checked by ESET Endpoint Antivirus for Linux. Detection Engine Version: 29104 (20240422). smime.p7s Description: S/MIME Cryptographic Signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Initialising hardware device fails with error -17
[...] [AVHWDeviceContext @ 0x560662049440] libva: VA-API version 1.20.0 [AVHWDeviceContext @ 0x560662049440] libva: User requested driver 'iHD' [AVHWDeviceContext @ 0x560662049440] libva: Trying to open /usr/lib64/dri/iHD_drv_video.so [AVHWDeviceContext @ 0x560662049440] libva: Found init function __vaDriverInit_1_15 [AVHWDeviceContext @ 0x560662049440] libva: va_openDriver() returns 0 [AVHWDeviceContext @ 0x560662049440] Initialised VAAPI connection: version 1.20 [AVHWDeviceContext @ 0x560662049440] VAAPI driver: Intel iHD driver for Intel(R) Gen Graphics - 24.1.3 (). VA-API version is 1.20 however your driver was built against 1.15, could you rebuild your driver against vaapi 1.20 ? BRs Haihao ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Initialising hardware device fails with error -17
Yes, in the initial email I forgot to mention this important information. cat /proc/cpuinfo vendor_id : GenuineIntel cpu family : 6 model : 183 model name : 13th Gen Intel(R) Core(TM) i9-13900 stepping : 1 microcode : 0x113 cpu MHz : 2399.975 cache size : 36864 KB physical id : 0 siblings : 32 core id : 47 cpu cores : 24 apicid : 94 initial apicid : 94 fpu : yes fpu_exception : yes cpuid level : 32 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities vmx flags : vnmi preemption_timer posted_intr invvpid ept_x_only ept_ad ept_1gb flexpriority apicv tsc_offset vtpr mtf vapic ept vpid unrestricted_guest vapic_reg vid ple shadow_vmcs ept_mode_based_exec tsc_scaling usr_wait_pause bugs : spectre_v1 spectre_v2 spec_store_bypass swapgs eibrs_pbrsb bogomips : 3993.60 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management:There is no dedicated GPU in the system The device does exist ls -la /dev/dri/renderD128 crw-rw-rw- 1 root render 226, 128 Feb 23 17:06 /dev/dri/renderD128 ffmpeg -loglevel verbose -init_hw_device qsv ffmpeg version 6.1.1 Copyright (c) 2000-2023 the FFmpeg developers built with gcc 13 (SUSE Linux) configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --incdir=/usr/include/ffmpeg --extra-cflags='-O2 -g -m64 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables' --optflags='-O2 -g -m64 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables' --disable-htmlpages --enable-pic --disable-stripping --enable-shared --disable-static --enable-gpl --enable-version3 --disable-openssl --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libdc1394 --enable-libdrm --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libopenjpeg --enable-libopenmpt --enable-libx264 --enable-libopenh264-dlopen --enable-libopus --enable-libpulse --enable-librubberband --enable-libsoxr --enable-li bspeex --enable-libssh --enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libxml2 --enable-libzmq --enable-libzvbi --enable-lv2 --enable-libvpl --enable-vaapi --enable-version3 --enable-libfdk-aac-dlopen --enable-nonfree --enable-libx265 --enable-libxvid libavutil 58. 29.100 / 58. 29.100 libavcodec 60. 31.102 / 60. 31.102 libavformat 60. 16.100 / 60. 16.100 libavdevice 60. 3.100 / 60. 3.100 libavfilter 9. 12.100 / 9. 12.100 libswscale 7. 5.100 / 7. 5.100 libswresample 4. 12.100 / 4. 12.100 libpostproc 57. 3.100 / 57. 3.100 [AVHWDeviceContext @ 0x560662049440] Trying to use DRM render node for device 0, with matching kernel driver (i915). [AVHWDeviceContext @ 0x560662049440] libva: VA-API version 1.20.0 [AVHWDeviceContext @ 0x560662049440] libva: User requested driver 'iHD' [AVHWDeviceContext @ 0x560662049440] libva: Trying to open /usr/lib64/dri/iHD_drv_video.so [AVHWDeviceContext @ 0x560662049440] libva: Found init function __vaDriverInit_1_15 [AVHWDeviceContext @ 0x560662049440] libva: va_openDriver() returns 0 [AVHWDeviceContext @ 0x560662049440] Initialised VAAPI connection: version 1.20 [AVHWDeviceContext @ 0x560662049440] VAAPI driver: Intel iHD driver for Intel(R) Gen Graphics - 24.1.3 (). [AVHWDeviceContext @ 0x560662049440] Driver not found in known nonstandard list, using standard behaviour. [AVHWDeviceContext @ 0x560662048f80] Use Intel(R) oneVPL to create MFX session, API version is 2.10, the required implementation version is 1.3 [AVHWDeviceContext @ 0x560662048f80] Initialize MFX session: implementation version is 1.35 [AVHWDeviceContext @ 0x560662048f80]
Re: [FFmpeg-user] Initialising hardware device fails with error -17
On 21-04-2024 22:53, Martin Stenzel via ffmpeg-user wrote: Error setting child device handle: -17 device=/dev/dri/renderD128 Did you test that this device does actually exist on your system? Can you specify what GPU you have? Does the error also occur if you leave out the explicit child device specification? ffmpeg -loglevel verbose -init_hw_device qsv ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
