I'm trying to confirm that I have the Intel HD 4600 working on my server. It's headless and getting a display connected to it is trouble because it's VGA only and I don't even had a VGA cable, never mind a monitor. I've followed the instructions located here to install the drivers for VAAPI which is what I need. I didn't use the HuC/GuC flags because according to the Arch wiki I don't need them for Haswell.
I then use vainfo to test out VAAPI but since I don't have a display I create a virtual display using Xvfb :99 -screen 0 1024x768x16 follow by export DISPLAY=:99 (courtesy of ChatGPT) but I don't know if that's the correct thing to do. I set the LIBVA_DRIVER_NAME to be i965 and run vainfo, the output I get is:
libva info: VA-API version 1.17.0
libva info: User environment variable requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [9]
param: 4, val: 0
that file is there and accesible, my user has permissions to access /dev/dri/renderD128. I'm not sure what else to do now.
I then use vainfo to test out VAAPI but since I don't have a display I create a virtual display using Xvfb :99 -screen 0 1024x768x16 follow by export DISPLAY=:99 (courtesy of ChatGPT) but I don't know if that's the correct thing to do. I set the LIBVA_DRIVER_NAME to be i965 and run vainfo, the output I get is:
libva info: VA-API version 1.17.0
libva info: User environment variable requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [9]
param: 4, val: 0
that file is there and accesible, my user has permissions to access /dev/dri/renderD128. I'm not sure what else to do now.
Statistics: Posted by Twinniw — 2025-01-04 09:40 — Replies 0 — Views 30