Date: Sun, 18 Dec 2022 16:27:31 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 267915] x11-wm/mutter: after graphics/mesa-* 21.3.8 -> 22.2.3 update OpenGL compositing fails on Intel Iris Pro Message-ID: <bug-267915-6497-3xYEnxMNjA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267915-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-267915-6497@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267915 Ting-Wei Lan <lantw44@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lantw44@gmail.com --- Comment #12 from Ting-Wei Lan <lantw44@gmail.com> --- I saw similar problems on FreeBSD 13.1-RELEASE-p5. The hardware is Intel i5-650. For the DRM part, it is the VT switch problem. If I don't switch VT after X= org is started, everything seems to be fine. However, if I switch to a differen= t VT and switch back, apps using OpenGL show these messages and use llvmpipe. libGL error: failed to authenticate magic 1 libGL error: failed to load driver: i965 This issue has been reported: https://github.com/freebsd/drm-kmod/issues/17= 5. Downgrading to drm-54-kmod can fix the problem. For the Mesa part, it is the modesetting driver problem. Mesa 21.3.8 works = fine with the modesetting driver, but Mesa 22.3.0 can't run GNOME Shell with the modesetting driver. I can move the mouse and click things, but GNOME Shell won't update the screen unless I switch to a different VT and switch back. Using xf86-video-intel instead of the modesetting driver can fix the GNOME Shell problem, but it seems to cause some apps to fail to update the screen. For example, PCManX sometimes fail to completely update the screen when scrolling with keyboard. I have to move the mouse or switch to a different window in order to see the updated screen. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267915-6497-3xYEnxMNjA>