On Sat, Apr 2, 2022 at 2:01 PM Christian Weisgerber
wrote:
> Warner Losh:
>
> > This suggests that we've broken the KBI we were trying to keep stable
> > between 13.0
> > and 13.1
>
> When I updated my stable/13 machine from source, from
> March 16 to March 30, DRM was broken (did nothing).
>
Warner Losh:
> This suggests that we've broken the KBI we were trying to keep stable
> between 13.0
> and 13.1
When I updated my stable/13 machine from source, from
March 16 to March 30, DRM was broken (did nothing).
Rebuilding graphics/drm-fbsd13-kmod fixed it.
So there was an ABI break in
On Sat, Apr 2, 2022 at 5:31 AM Dave Cottlehuber wrote:
> On Sat, 2 Apr 2022, at 09:18, Neal Nelson wrote:
> > I have been using the BETAs quite happily on my Intel 11th gen NUC
> > (Tiger Lake), but RC1 has a show stopper for me in that DRM no longer
> > works. I have posted the bug here:
> > htt
On Sat, 2 Apr 2022, at 09:18, Neal Nelson wrote:
> I have been using the BETAs quite happily on my Intel 11th gen NUC
> (Tiger Lake), but RC1 has a show stopper for me in that DRM no longer
> works. I have posted the bug here:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262982
>
> Unfort
I have been using the BETAs quite happily on my Intel 11th gen NUC
(Tiger Lake), but RC1 has a show stopper for me in that DRM no longer
works. I have posted the bug here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262982
Unfortunately I mislabelled the bug as USB when I first filed it,
Hi!
> The first RC build of the 13.1-RELEASE release cycle is now available.
If I update my 13.1-BETA2 system to 13.1-RC1, this happens:
poudriere jail -u -j 131 -t 13.1-RC1
freebsd-update.fixed: Cannot upgrade from 13.1-RC1 to itself
But
poudriere jail -l
still says:
131 13.1-BETA2
