I am running mpv with Hyprland on this hardware, I have intel-media-driver, libva2 and libva-utils installed but for some reason it won’t run with hardware decoding as it should.
[ 0.106][v][vd] Codec list:
[ 0.106][v][vd] h264 - H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
[ 0.106][v][vd] h264_v4l2m2m (h264) - V4L2 mem2mem H.264 decoder wrapper
[ 0.106][v][vd] h264_qsv (h264) - H264 video (Intel Quick Sync Video acceleration)
[ 0.106][v][vd] libopenh264 (h264) - OpenH264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
[ 0.106][v][vd] h264_cuvid (h264) - Nvidia CUVID H264 decoder
[ 0.106][v][vd] Opening decoder h264
[ 0.106][v][vd] Looking at hwdec h264-vaapi...
[ 0.106][v][vo/gpu] Loading hwdec drivers for format: 'vaapi'
[ 0.106][v][vo/gpu] Loading hwdec driver 'vaapi'
[ 0.107][v][vo/gpu/vaapi] VAAPI hwdec only works with OpenGL or Vulkan backends.
[ 0.107][v][vo/gpu] Loading failed.
[ 0.107][v][vd] Could not create device.
[ 0.107][v][vd] Using software decoding.
[ 0.107][v][vd] Detected 4 logical cores.
(notice the software decoding part)
Can someone please help me figure out what the cause behind hardware decoding not working could be?
The system is Tumbleweed Slowroll.
In my understanding, this should work with hardware decoding.
How would I check if libvulkan_intel is installed (I doubt it is, I didn’t specifically install it so unless it came with another package then I don’t think it is).
I don’t think huc/guc is enabled, again I didn’t specifically enable it
But looking at the answer you provided to another user here, I don’t think it is enabled. It doesn’t show up.
@sft To see what’s installed use zypper se -i intel it may be there but install the other tools mentioned by inxi eg zypper se --provides eglinfo and if not installed, install the package.
So you have a Gen-9 device so GUC2, so could either add to grub with i915.enable_guc=2 it will taint the kernel, but worth a try after checking above first.
You can check for eample with;
journalctl -b --no-hostname | grep -E "guc|huc"
Jan 30 08:28:04 kernel: i915 0000:05:00.0: [drm] GT0: GuC firmware i915/dg2_guc_70.bin version 70.36.0
Jan 30 08:28:04 kernel: i915 0000:05:00.0: [drm] GT0: HuC firmware i915/dg2_huc_gsc.bin version 7.10.16
journalctl -b --no-hostname | grep -E "guc|huc"
Jan 30 15:34:58 kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/tgl_guc_70.bin version 70.36.0
Jan 30 15:34:58 kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
I did run the dracut regenerate command after adding “i915.enable_guc=2 grub” to GRUB_CMDLINE_LINUX_DEFAULT in the grub config, but the hardware decoding still isn’t working.
I did also install the libvulkan_intel package btw.
Well I hadn’t used the yast bootloader thing before but it is added as a kernel option and I’m assuming the reason you said to go through yast bootloader is because it does the update-initramfs thing?
It’s still not working however. Are there any other things worth trying? I might try reinstalling, as it could just be the system is just too littered with legacy crap at this point and it’s causing all sorts of conflicts.
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+-----------------------+-------------------------------------------------------------------------+--------
i+ | intel-gpu-tools | Collection of tools for development and testing of the Intel DRM driver | package
i+ | intel-media-driver | Intel Media Driver for VAAPI | package
i+ | intel-vaapi-driver | Intel Driver for Video Acceleration (VA) API for Linux | package
i | kernel-firmware-intel | Kernel firmware files for Intel-platform device drivers | package
i | libdrm_intel1 | Userspace interface for Kernel DRM services for Intel chips | package
i+ | libvulkan_intel | Mesa vulkan driver for Intel GPU | package
'kernel-firmware-intel' is already installed.
There is an update candidate for 'kernel-firmware-intel', but it comes from a repository with a lower priority. Use 'zypper install kernel-firmware-intel-20250122-1.1.noarch' to install this candidate.
I’m wondering if something got “missed” in the hardware setup because I’m running a bare-bones no-DE install, I guess it’s possible something happens in the setup of the DE that enables graphics but maybe isn’t being kicked off in a terminal-only or tiling WM install.