Re: xenodm presents dark screen since snapshot of May 14th

On Sunday, May 17th, 2026 at 19:30, Matthieu Herrb <[email protected]> wrote:

> On Sun, May 17, 2026 at 06:40:49PM +0200, Matthieu Herrb wrote:
> > On Sun, May 17, 2026 at 04:16:43PM +0000, Dannis 't Hart wrote:
> > > Hello,
> > > Just mentioning: since the May 14th snapshot, I get no further than a dark ("blank") screen after booting, at the point that xenodm is starting up.
> > > I put back the /usr/X11R6 directory tree from May 13th snapshot, everything works as usual.
> > > This is on my Lenovo Thinkpad T490s.
> > > Something buggy must have happened between May 13th and 14th snapshots.
> > > Kind regards,
> > > Dannis.
> >
> > Anything intersting to share from /var/log/Xorg.0.log or
> > /var/log/xenodm.log ?
> >
> > Without more information, it's hard to tell what can be wrong.
> >
> > https://www.openbsd.org/report.html
> >
> 
> I think I've guessed what the problem is, and have committed a fix.
> 
> If your macihne is using the intel X.Org driver, and you know how to
> rebuild things, update the driver/xf86-video-intel/src/sna/sna_accel.c
> to the latest version (1.12) and rebuild the driver. (make -f
> Makefile.bsd-wrapper build).
> 
> Otherwise, wait for the next snapshot.
> --
> Matthieu Herrb
> 

Okay, thank you, I'll do a CVS update on the xenocara tree and rebuild the driver.
I'll try and report back.

Other than that, I seem to be stuck in snapshots. 
On my laptop I'm on May 15th snapshot, but /usr/X11R6 is copied from May 13th. This works fine.
But several machines I have, including a VM at OpenBSD.Amsterdam, don't seem to be able to sysupgrade -s presently.
It ends with:
  cp: /mnt/var/log/ai.log/18444: No such file or directory
  chmod: /mnt/var/log/ai.log/18444: No such file or directory
  /upgrade: cannot create /mnt/etc/rc.firsttime: No such file or directory
I'm not sure if /etc/rc.firsttime is supposed to be in base79.tgz in snapshots, but in May 17th's it isn't.

Kind regards,
Dannis.