Date: Wed, 20 Jan 2021 22:57:59 -0500 From: Robert Huff <roberthuff@rcn.com> To: Chris Hill <chris@monochrome.org> Cc: questions@freebsd.org Subject: Re: drm-kmod kills FreeBSD Message-ID: <24584.64455.966459.479993@jerusalem.litteratus.org> In-Reply-To: <alpine.BSF.2.20.2101202008490.73682@tripel.monochrome.org> References: <alpine.BSF.2.20.2101201919360.73682@tripel.monochrome.org> <CAM8r67D-TZ0ZrLO7=JWTQ5Ak2jcq%2B3P3pAXuu1HCnMrxQjG5Ow@mail.gmail.com> <alpine.BSF.2.20.2101202008490.73682@tripel.monochrome.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Hill <chris@monochrome.org> writes:
> > You need to build and reinstall drm-kmod-g20190710 and
> > drm-fbsd12.0-kmod-4.16.g20201016 manually from ports, so module
> > gets 12.2 stuff in it, pkg installs binary that is built on 12.1
> > and will not work on 12.2 properly. This is a known issue and
> > fix :-)
>
> Really! That's extremely helpful to know. Do I actually need both
> of those? I'm not sure what the difference is.
Short version:
To do what they do, drm-kmods and gpu-firmware-kmod burrow _deep_
into the kernel; everything needs to be _perfectly_ in sync or
... <hairball!> On my systems I upgrade as a triplet:
{kernel+world,drm,gpu-firmware}.
Respectfully,
Robert Huff
--
Hello ... my name is SARS-CoV-2.
You are not wearing a mask?
Prepare to die!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24584.64455.966459.479993>