Date: Mon, 13 Apr 2020 18:01:11 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Theron <theron.tarigo@gmail.com> Cc: Niclas Zeising <zeising@freebsd.org>, Grzegorz Junka <list1@gjunka.com>, "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org> Subject: Re: Ars Technica article Message-ID: <CAN6yY1sXNy%2BJLpsqcqzJafUd-%2B_UfU1FJZQ88du_3D29wwrznQ@mail.gmail.com> In-Reply-To: <24943162-97e4-7221-45c8-aeda7907c168@gmail.com> References: <4e3bf6be-aecf-7c62-df98-1cc4b01b8db9@gmail.com> <qjPID4gTE2NvAVjSZKmSBSLDOK7gxaJbnPw46O71vKnmV0b7uoMZ7xTv3RI30bRpPqphZAXTHd3r3RYSQ8UGaRVO45afo-EcYB34INKVAM8=@protonmail.ch> <43f83193-e495-2bf2-f85d-91aa0b36c1a0@gmail.com> <slUQwwm1giIIEaqmUKBQ1G5UIlVSvzfWkk3vZm-dBYNRA-wng7tDluv_Es3eOiaNYDE9yNtKFfd-2iOEozSGK1JNIjFbqCXV1a1sgkQ1sHE=@protonmail.ch> <0e205fe8-fbc6-5d91-99b0-1bd4870b8a5d@gmail.com> <CAGwOe2ZHZFhVwSvjk7JDe0szY-1oZH_HvDhMqp-zXXV9%2BePtHg@mail.gmail.com> <d263368c-5dcc-61c2-9c77-3d59c5493182@gmail.com> <536A0D50-4119-4C28-9202-28622152B203@freebsd.org> <20200413052406.GA90880@FreeBSD.org> <CANCZdfqfkVGDGssHC%2Bts6df7QeiCsA68CQnjOAAXdH2JsDMTaQ@mail.gmail.com> <20200413075034.GA46382@FreeBSD.org> <2761dfd9-f031-9a47-024e-71ef29f9ac23@gjunka.com> <e0d5490b-4d6b-bf4a-1e53-15574a373842@freebsd.org> <24943162-97e4-7221-45c8-aeda7907c168@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 13, 2020 at 5:16 PM Theron <theron.tarigo@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@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1sXNy%2BJLpsqcqzJafUd-%2B_UfU1FJZQ88du_3D29wwrznQ>