On Sun, 9 Jul 2023 at 11:14, Mike Pumford <mpumf...@mudcovered.org.uk> wrote: > > On 08/07/2023 23:06, David Brownlee wrote: > > > Would it be worth trying to collect some data on users running NetBSD > > on intel display hardware, to see if there are any cases where > > intel_drv works and modesetting_drv does not? > > > > As a datapoint, on a Thinkpad T480 runs OK with the default intel_dev. > > Renaming away /usr/X11R7/lib/modules/drivers/intel_drv.so and > > restarting X runs fine with modesetting_drv, and "grep Mesa > > /var/log/Xorg.0.log" gives > > > > > (II) modeset(0): glamor X acceleration enabled on Mesa DRI Intel(R) > > UHD Graphics 620 (Kabylake GT2) > > > Both are equally bad for me. The console works perfectly but I get stuck > in the blank screen heartbeat death with both (see kern/57268): > > [ 44.509] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD > Graphics 4600 > [ 44.509] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, > sse4.2, avx, avx2; using a maximum of 4 threads > > So fiddling with the default X driver for intel hardware is only part of > the solution. We need to address the core issues in the i915kmsdrm that > impact both.
Absolutely, though that is an orthogonal issue - providing modesetting_drv is no worse on any hardware than intel_dev then it makes sense to have it used by default, and i915kmsdrm needs to work on more hardware (it's good there is a PR) David
