Ars Technica article

[Kevin Oberman]

On Mon, Apr 13, 2020 at 5:16 PM Theron <theron.tarigo at gmail.com> wrote:

> On 2020-04-13 06:34, Niclas Zeising wrote:
> > When FreeBSD 12.1 was first released, there were issues with the
> > binary package of drm-fbsd12.0-kmod, since all packages still were
> > built on 12.0, and a kmod built on 12.0 didn't work on 12.1.  Since
> > then, the package build cluster has changed to build all packages for
> > 12 on 12.1, so if you're running 12.1 the binary package should work.
> > If you are running 12-stable you need to compile the driver though.
> > Regards
> Won't this become an issue again when 12.2 is released, seeing as
> today's 12-stable can't use the 12.1 package?  I'm not aware of any
> progress on this matter or any technical discussions since these:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241101
> https://github.com/FreeBSDDesktop/kms-drm/issues/183
> https://reviews.freebsd.org/D23881
>
> At very least, drm-kmod should be set NO_PACKAGE=yes before 12.2 is
> released, since the 12.1 package becomes garbage anyway on new
> installations or upgrades.
>
> Theron


It is, of course, drm-fbsd12.0-kmod is actually the port. This problem has
hit both drm-fbsd12.0-kmod and virtualbox-ose-kmod in the past and has
caused real pain that would have avoided by simply building a trusted port
for these kmod ports whenever a RELEASE is made. Of course, people running
head or STABLE should be aware that they should build these ports from
source and not install a package.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman at gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683