[Bug 267915] x11-wm/mutter: after graphics/mesa-* 21.3.8 -> 22.2.3 update OpenGL compositing fails on Intel Iris Pro
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 15 Mar 2025 11:56:30 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267915
Harald Schmalzbauer <bugzilla.freebsd@omnilan.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugzilla.freebsd@omnilan.de
--- Comment #39 from Harald Schmalzbauer <bugzilla.freebsd@omnilan.de> ---
(In reply to Andre Albsmeier from comment #38)
> Unfortunately, the modesetting driver doesn't have this setting...
Just monkey see, monkey do report from my side,
with an excerpt of my etc/X11/xorg.conf.d/server.conf section I changed today:
# Setup for one X display, extended over 3 monitors
Section "Device"
Identifier "GT2-haswell"
Driver "modesetting"
Option "HotPlug" "0"
# Option DRI 3 enables the "iris" driver instead of "zink" fallback
Option "DRI" "3" # ('zink' is GL over Vulkan and shows
errors
# authenticate magic 1
# failed to load driver: iris
# with xdriinfo(1)/[glxinfo -B]).
Option "monitor-DP-1" "Dell-30inch-center"
Option "monitor-DP-2" "Eizo-24inch-left"
Option "monitor-HDMI-1" "Eizo-21portrait-right"
BusID "PCI:0:2:0"
EndSection
This is on stable/14 (1402504):
dmesg excerpt:
drmn0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0
VT: Replacing driver "efifb" with new "drmfb".
Relevant packages:
drm-61-kmod-6.1.128.1402000_2 DRM drivers modules
libdrm-2.4.123,1 Direct Rendering Manager library and headers
gpu-firmware-intel-kmod-kabylake-20230625.1402000 Firmware modules for kabylake
Intel GPUs
At least today, modesetting(4) seems to have the DRI Option.
Performance wise there's not too much difference, glxgears(1) shows now ~6300
FPS instead of ~5400 FPS with 'zink'.
Real benefit: These errors, which were continuously recorded in
~/.xsession-errors, vanished:
authenticate magic 1
failed to load driver: iris
Now invoking xdriinfo(1) shows (without errors):
xdriinfo
Screen 0: iris
Previously, "Screen 0:" read 'zink' and the "authenticate magic 1"/"failed to
load driver: iris" errors occurred.
I only understand a fraction of the whole mesa/dri mesh...
Just wanted to report that I have _no issues_ with adding
'Option "DRI" "3"'
to my modesetting(4) based config on my workstation
(CPU: Intel(R) Xeon(R) CPU E3-1275 v6 @ 3.80GHz)
--
You are receiving this mail because:
You are on the CC list for the bug.