Forum / NoMachine for Linux / Hardware encoder not working on Linux
- This topic has 30 replies, 2 voices, and was last updated 7 months ago by taiziccf.
-
AuthorPosts
-
April 15, 2024 at 16:08 #47769taiziccfParticipant
using from opt i get this
libva info: VA-API version 1.19.0
libva info: User environment variable requested driver ‘iHD’
libva info: Trying to open /opt/intel/mediasdk/lib64/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_18
libva info: va_openDriver() returns 0
2799 3133 2024-04-14 21:37:55 922.019 QuickSync/QuickSync: WARNING! Failed to set display handle. Error is -17: Device operation failure.
Info: Using H.264 software encoder.
using from /usr i get this
libva info: VA-API version 1.19.0
libva info: User environment variable requested driver ‘iHD’
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: va_openDriver() returns -1
4092 4751 2024-04-15 23:07:32 975.026 QsLibraries/QsLibraries: WARNING! Failed to initialize display for device /dev/dri/renderD128 with error -1.
libva info: VA-API version 1.19.0
libva info: User environment variable requested driver ‘iHD’
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: va_openDriver() returns -1
4092 4751 2024-04-15 23:07:32 977.102 QsLibraries/QsLibraries: WARNING! Failed to initialize display for device /dev/dri/card0 with error -1.
Info: Using H.264 software encoder.
April 15, 2024 at 16:12 #47770taiziccfParticipantAnyway both file is identical but I don’t understand why the error message is different, i guess we are close to the answer?
chchia@ubuntu:/opt/intel/mediasdk/lib64$ sha256sum iHD_drv_video.so
52d7749266442efef206d457016fa880fd903eb7bd1e9e4da3db2319efc4be3d iHD_drv_video.so
chchia@ubuntu:/opt/intel/mediasdk/lib64$ sha256sum /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
52d7749266442efef206d457016fa880fd903eb7bd1e9e4da3db2319efc4be3d /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
April 15, 2024 at 18:00 #47775BritgirlKeymasterWe’re doing some tests in our lab and we’ll let you know.
April 16, 2024 at 08:16 #47782taiziccfParticipantThanks, looking forward for some solution.
April 16, 2024 at 10:31 #47784BritgirlKeymasterCan you give us the output of lspci?
April 16, 2024 at 11:47 #47786taiziccfParticipantlcpci
00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:1c.1 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:1c.2 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:1c.3 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
00:1f.0 ISA bridge: Intel Corporation 82801IB (ICH9) LPC Interface Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: Intel Corporation Alder Lake-S GT1 [UHD Graphics 730] (rev 0c)
02:00.0 Audio device: Intel Corporation Alder Lake-S HD Audio Controller (rev 11)
05:01.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge
05:02.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge
05:03.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge
05:04.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge
06:0a.0 SCSI storage controller: Red Hat, Inc. Virtio block device
06:12.0 Ethernet controller: Red Hat, Inc. Virtio network device
07:1b.0 USB controller: Red Hat, Inc. QEMU XHCI Host Controller (rev 01)
April 16, 2024 at 11:48 #47787taiziccfParticipantlspci -nnk related to VGA only
01:00.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-S GT1 [UHD Graphics 730] [8086:4692] (rev 0c)
Subsystem: Micro-Star International Co., Ltd. [MSI] Alder Lake-S GT1 [UHD Graphics 730] [1462:7d42]
Kernel driver in use: i915
Kernel modules: i915, xe
April 16, 2024 at 11:59 #47788taiziccfParticipantlspci -nnkv
01:00.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-S GT1 [UHD Graphics 730] [8086:4692] (rev 0c) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Alder Lake-S GT1 [UHD Graphics 730] [1462:7d42]
Physical Slot: 0
Flags: bus master, fast devsel, latency 0, IRQ 58
Memory at 80000000 (64-bit, non-prefetchable) [size=16M]
Memory at 7000000000 (64-bit, prefetchable) [size=256M]
I/O ports at 7000 [size=64]
Expansion ROM at <ignored> [disabled]
Capabilities: [40] Vendor Specific Information: Len=0c <?>
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [100] Null
Capabilities: [200] Address Translation Service (ATS)
Capabilities: [300] Page Request Interface (PRI)
Kernel driver in use: i915
Kernel modules: i915, xe
April 17, 2024 at 13:03 #47811taiziccfParticipantHi, just to follow up is there any progress? thanks.
April 17, 2024 at 15:35 #47813BritgirlKeymasterWe’re analyzing the information you provided to us, so thank you, and now it’s a question of replicating the environment and reproducing the exact same errors. We’ll update the topic as soon as we can.
April 22, 2024 at 09:20 #47891taiziccfParticipanthi, just to check if there any potential update for this? thanks.
April 22, 2024 at 15:03 #47901BritgirlKeymasterWe’re still trying to reproduce it.
Can you give us the output of
export LIBVA_DRIVER_NAME=iHD ; for DEVICE in /dev/dri/* ; do echo -e "Device: $DEVICE" && vainfo --display drm --device $DEVICE ; done
in the meantime?April 22, 2024 at 16:39 #47902taiziccfParticipanthere the output, thanks.
export LIBVA_DRIVER_NAME=iHD ; for DEVICE in /dev/dri/* ; do echo -e “Device: $DEVICE” && vainfo –display drm –device $DEVICE ; done
Device: /dev/dri/by-path
Failed to open the given device!
Device: /dev/dri/card0
libva info: VA-API version 1.19.0
libva info: User environment variable requested driver ‘iHD’
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_18
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.19 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics – 23.2.3 ()
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileNone : VAEntrypointStats
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointFEI
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointFEI
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointFEI
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointFEI
VAProfileHEVCMain : VAEntrypointEncSliceLP
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointEncSliceLP
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile0 : VAEntrypointEncSliceLP
VAProfileVP9Profile1 : VAEntrypointVLD
VAProfileVP9Profile1 : VAEntrypointEncSliceLP
VAProfileVP9Profile2 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointEncSliceLP
VAProfileVP9Profile3 : VAEntrypointVLD
VAProfileVP9Profile3 : VAEntrypointEncSliceLP
VAProfileHEVCMain12 : VAEntrypointVLD
VAProfileHEVCMain12 : VAEntrypointEncSlice
VAProfileHEVCMain422_10 : VAEntrypointVLD
VAProfileHEVCMain422_10 : VAEntrypointEncSlice
VAProfileHEVCMain422_12 : VAEntrypointVLD
VAProfileHEVCMain422_12 : VAEntrypointEncSlice
VAProfileHEVCMain444 : VAEntrypointVLD
VAProfileHEVCMain444 : VAEntrypointEncSliceLP
VAProfileHEVCMain444_10 : VAEntrypointVLD
VAProfileHEVCMain444_10 : VAEntrypointEncSliceLP
VAProfileHEVCMain444_12 : VAEntrypointVLD
VAProfileHEVCSccMain : VAEntrypointVLD
VAProfileHEVCSccMain : VAEntrypointEncSliceLP
VAProfileHEVCSccMain10 : VAEntrypointVLD
VAProfileHEVCSccMain10 : VAEntrypointEncSliceLP
VAProfileHEVCSccMain444 : VAEntrypointVLD
VAProfileHEVCSccMain444 : VAEntrypointEncSliceLP
VAProfileAV1Profile0 : VAEntrypointVLD
VAProfileHEVCSccMain444_10 : VAEntrypointVLD
VAProfileHEVCSccMain444_10 : VAEntrypointEncSliceLP
Device: /dev/dri/renderD128
libva info: VA-API version 1.19.0
libva info: User environment variable requested driver ‘iHD’
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_18
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.19 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics – 23.2.3 ()
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileNone : VAEntrypointStats
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointFEI
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointFEI
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointFEI
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointFEI
VAProfileHEVCMain : VAEntrypointEncSliceLP
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointEncSliceLP
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile0 : VAEntrypointEncSliceLP
VAProfileVP9Profile1 : VAEntrypointVLD
VAProfileVP9Profile1 : VAEntrypointEncSliceLP
VAProfileVP9Profile2 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointEncSliceLP
VAProfileVP9Profile3 : VAEntrypointVLD
VAProfileVP9Profile3 : VAEntrypointEncSliceLP
VAProfileHEVCMain12 : VAEntrypointVLD
VAProfileHEVCMain12 : VAEntrypointEncSlice
VAProfileHEVCMain422_10 : VAEntrypointVLD
VAProfileHEVCMain422_10 : VAEntrypointEncSlice
VAProfileHEVCMain422_12 : VAEntrypointVLD
VAProfileHEVCMain422_12 : VAEntrypointEncSlice
VAProfileHEVCMain444 : VAEntrypointVLD
VAProfileHEVCMain444 : VAEntrypointEncSliceLP
VAProfileHEVCMain444_10 : VAEntrypointVLD
VAProfileHEVCMain444_10 : VAEntrypointEncSliceLP
VAProfileHEVCMain444_12 : VAEntrypointVLD
VAProfileHEVCSccMain : VAEntrypointVLD
VAProfileHEVCSccMain : VAEntrypointEncSliceLP
VAProfileHEVCSccMain10 : VAEntrypointVLD
VAProfileHEVCSccMain10 : VAEntrypointEncSliceLP
VAProfileHEVCSccMain444 : VAEntrypointVLD
VAProfileHEVCSccMain444 : VAEntrypointEncSliceLP
VAProfileAV1Profile0 : VAEntrypointVLD
VAProfileHEVCSccMain444_10 : VAEntrypointVLD
VAProfileHEVCSccMain444_10 : VAEntrypointEncSliceLP
April 22, 2024 at 16:42 #47903taiziccfParticipantthis is ls -la in /dev/dri/by-path in case you need it.
root@ubuntu:/dev/dri/by-path# ls -la
total 0
drwxr-xr-x 2 root root 80 Apr 21 01:54 .
drwxr-xr-x 3 root root 100 Apr 21 01:54 ..
lrwxrwxrwx 1 root root 8 Apr 21 01:54 pci-0000:01:00.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Apr 21 01:54 pci-0000:01:00.0-render -> ../renderD128
root@ubuntu:/dev/dri/by-path#
April 26, 2024 at 16:21 #47971BritgirlKeymasterThanks for your patience. We were able to reproduce your issue, but it’s not clear to us why MFX just throws out an error on alder lake CPU/GPU in a NoMachine session. We were hoping that it would be something we could fix or provide a workaround for, but it’s not looking that way. Given that MediaSDK has become legacy, the best way forward is to wait for NoMachine 8.12 which will ship support for VPL (Intel’s replacement of MediaSDK). This is coming in the next week or so.
-
AuthorPosts
This topic was marked as solved, you can't post.