Date: Tue, 21 Feb 2023 21:28:33 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 266315] linuxkpi panic after recent updates (13.1-STABLE #0 stable/13-9cbba5950: Wed Sep 7 23:42:41 CEST 2022) Message-ID: <bug-266315-7141-F5z8UajPuV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-266315-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-266315-7141@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=3D266315 --- Comment #32 from Paul Dufresne <dufresnep@zoho.com> --- (In reply to jakub_lach from comment #31) >Note, that I had working/stable accelerated intel driver for years prior t= o rm-510-kmod. You seems to consider modesetting as no hardware acceleration. Most likely, modesetting would use Glamor as hardware acceleration. A kind of hardware acceleration that use the card 3D to achieve 2D acceleration. Old 2D acceleration, is I believed, a bit forgotten by developers... because they prefer Glamor. Also, and I am less sure... I think Glamor also used the drm stack... so testing with Intel would allows like help to determine if the problem is wi= thin the Xorg Intel driver or in the drm stack. But yeah... frankly I think most people should just use modesetting with Gl= amor acceleration and avoid the Xorg intel driver. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-266315-7141-F5z8UajPuV>