[HW Accel Support]: Intel Arrow Lake

[lutfijw]

Describe the problem you are having

Hi All,
I have difficulty in enabling the iGPU Hardware Acceleration for Intel Arrow Lake iGPU. My system is using Intel Core Ultra 235 with iGPU enabled and I am planning to run Frigate in Proxmox LXC.

I can see the /dev/dri/card1 and /dev/dri/renderD128 in Proxmox host, however when I try to run vainfo in proxmox host, it is always showing error:
error: can't connect to X server! libva info: VA-API version 1.17.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_17 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_8 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit

my GPU is detected and driver is loaded but somehow vainfo is unable to load the driver

`root@pve:~# lspci -vv -nn -s 00:02������������������������������������00:02.0 VGA compatible controller [0300]: Intel Corporation Arrow Lake-S [Intel Graphics] [8086:7d67] (rev 06) (prog-if 00 [VGA controller])
DeviceName: Onboard - Video
Subsystem: Micro-Star International Co., Ltd. [MSI] Arrow Lake-S [Intel Graphics] [1462:7e33]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin ? routed to IRQ 181
IOMMU group: 0
Region 0: Memory at b017000000 (64-bit, prefetchable) [size=16M]
Region 2: Memory at a000000000 (64-bit, prefetchable) [size=256M]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities: [40] Vendor Specific Information: Len=0c <?>
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag+ RBE+ FLReset+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
DevCap2: Completion Timeout: Range B, TimeoutDis+ NROPrPrP- LTR+
10BitTagComp+ 10BitTagReq+ OBFF Not Supported, ExtFmt+ EETLPPrefix-
EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
FRS-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 10BitTagReq- OBFF Disabled,
AtomicOpsCtl: ReqEn-
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit+
Address: 00000000fee00018 Data: 0000
Masking: 00000000 Pending: 00000000
Capabilities: [d0] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Null
Capabilities: [110 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [420 v1] Physical Resizable BAR
BAR 2: current size: 256MB, supported: 256MB
Capabilities: [320 v1] Single Root I/O Virtualization (SR-IOV)
IOVCap: Migration- 10BitTagReq+ Interrupt Message Number: 000
IOVCtl: Enable- Migration- Interrupt- MSE- ARIHierarchy- 10BitTagReq-
IOVSta: Migration-
Initial VFs: 7, Total VFs: 7, Number of VFs: 0, Function Dependency Link: 00
VF offset: 1, stride: 1, Device ID: 7d67
Supported Page Size: 00000553, System Page Size: 00000001
Region 0: Memory at 000000b010000000 (64-bit, prefetchable)
VF Migration: offset: 00000000, BIR: 0
Capabilities: [400 v1] Latency Tolerance Reporting
Max snoop latency: 0ns
Max no snoop latency: 0ns
Kernel driver in use: i915
Kernel modules: i915, xe

root@pve:~# lspci | grep VGA������������������������������������������00:02.0 VGA compatible controller: Intel Corporation Arrow Lake-S [Intel Graphics] (rev 06)
80:14.5 Non-VGA unclassified device: Intel Corporation Device 7f2f (rev 10) `

I have not installed Frigate yet since vainfo in proxmox host still not running

Version

N.A

Frigate config file

N.A

docker-compose file or Docker CLI command

N/A

Relevant Frigate log output

N/A

Relevant go2rtc log output

N/A

FFprobe output from your camera

N/A

Install method

Proxmox via Docker

Object Detector

OpenVino

Network connection

Wired

Camera make and model

N/A

Screenshots of the Frigate UI's System metrics pages

N/A

Any other information that may be helpful

No response

[banthungprong]

I simply quote hawkeye from 3 hours ago:

Frigate runs best in Docker on bare metal. A good number of our support issues are users struggling with Proxmox in one way or another. You might consider removing the Proxmox virtualization layer and seeing if your issues persist.

[lutfijw]

is this mean my Hardware Acceleration is working? I cant run VAINFO in the host as it always shown error but intel_gpu_top showing that there is activities in my GPU and seem frigate is using GPU since my CPU load is very little, less than 2%.

Veri Confusing…

[hawkeye217]

Yes, it is working.

[lutfijw]

Any idea why vainfo is failing in the host? Look so strange for me. Is it because the hardware is too recent and linux driver is not fully compatible?

I had also manage to try using NPU, but the inference time is too slow. GPU is much better for Frigate.

[hawkeye217]

Any idea why vainfo is failing in the host?

Not sure. Perhaps it's proxmox related in some way?

[Solear]

iGPU is working on bare metal debian/docker with a 265k.

I've had no luck with proxmox.