# cat /sys/kernel/debug/dri/0/gt/uc/huc_info # cat /sys/kernel/debug/dri/0/gt/uc/guc_info i915 0000:00:02.0: Incompatible option enable_guc=2 - HuC is not supported! # dmesg i915 0000:00:02.0: Incompatible option enable_guc=2 - GuC is not supported! If they are not supported by your graphics adapter you will see: On next boot you can verify both GuC and HuC are enabled by using dmesg: etc/modprobe.d/nf options i915 enable_guc=2 Otherwise, if you have addded the i915 module (see Kernel mode setting#Early KMS start) to initramfs, then you must instead set these options through a file in /etc/modprobe.d/, e.g.: If your system is configured for late KMS start (default), you can manually enable these features by setting i915.enable_guc as described in Kernel parameters. Moreover, enabling GuC/HuC firmware loading can cause issues on some systems disable it if you experience freezing (for example, after resuming from hibernation).įirstly, ensure that linux-firmware is installed. Warning: Manually enabling GuC / HuC firmware loading taints the kernel even when the feature is not supported. If GuC submission or HuC firmware loading is not enabled by default for your GPU, you can manually enable it. GuC functionality is controlled by the i915.enable_guc kernel parameter. The GuC and HuC firmware files are both provided by linux-firmware. CBR rate control on SKL low-power encoding mode) require loading the HuC firmware as well. With regards to HuC support, some video features (e.g. To use this functionality, the GuC firmware must be loaded. Introduced with Alder Lake-P (Mobile), within Gen12.
Refer to Kernel mode setting#Early KMS start for instructions on how to enable KMS as soon as possible at the boot process.
Kernel mode setting (KMS) is supported by Intel chipsets that use the i915 DRM driver and is mandatory and enabled by default. Also, check that you have not disabled Intel by using any modprobe blacklisting within /etc/modprobe.d/ or /usr/lib/modprobe.d/.Make sure you do not have nomodeset as a kernel parameter, since Intel requires kernel mode-setting.
The Intel kernel module should load fine automatically on system boot. However, the modesetting driver can cause problems such as screen tearing and mouse jittering on XFCE, artifacts when switching virtual desktops in Chromium, and vsync jitter/video stutter in mpv. See, , Xorg#Installation, and modesetting(4). Note: Some ( Debian & Ubuntu, Fedora, KDE) recommend not installing the xf86-video-intel driver, and instead falling back on the modesetting driver for Gen4 and newer GPUs (GMA 3000 from 2006 and newer).
For Vulkan support ( Ivy Bridge and newer), install the vulkan-intel package.Beside this functionality, this package is generally not recommended, see note below. For the DDX driver which provides 2D acceleration in Xorg, install the xf86-video-intel package.For 32-bit application support, also install the lib32-mesa package from the multilib repository.Install the mesa package, which provides the DRI driver for 3D acceleration. 6.16 Crash/freeze on low power Intel CPUs.6.15 No sound through HDMI on a Haswell CPU.6.14 KMS Issue: console is limited to small area.6.10 Kernel crashing w/kernels 4.0+ on Broadwell/Core-M chips.6.9 Corruption or unresponsiveness in Chromium and Firefox.