On Sat 28 Feb 2026 at 21:40:45 +0100, Rhialto wrote:
> So I plugged my monitor into the motherboard DVI port to use the onboard
> Intel graphics. This involved checking a mysterious BIOS setting (in a
> strange place like Advanced/System Agent (SA) Configuration/Graphics
> Configuration) but that's fine.
>
> Both the "intel" and the "modesetting" driver seemed to work in a quick
> test.
After only about 22 days, the intel hw with modesetting driver also
managed to corrupt fatally (differently than with the radeon hardware),
and needed to be restarted. I was opening 3 or 4 windows with
print/foliate; it seemed likely that that was triggering it somehow but
or course it isn't certain.
From time to time the kernel logs
[ 1909454.2309810] {drm:netbsd:intel_pipe_update_start+0x2ff} *ERROR*
Potential atomic update failure on pipe A: -35
but that doesn't seem to correlate to actual corruption.
I am now on intel hw + intel driver. x11/redshift still doesn't work and
the firefox menu issue is also still there. I also see it with
graphics/xv (with both drivers).
<rant>
I really wonder what happened to X since NetBSD 9. It was running fine
for months on end, and now with 10 it gets fatally corrupted at the drop
of a hat. One would almost suspect a conspiracy to break X from the (go
a)wayland camp...
</rant>
-Olaf.
--
___ Olaf 'Rhialto' Seibert <rhialto/at/falu.nl>
\X/ There is no AI. There is just someone else's work. --I. Rose
Attachment:
signature.asc
Description: PGP signature