Date: Thu, 21 Jan 2021 07:51:07 -0500 From: Robert Huff <roberthuff@rcn.com> To: Kevin Oberman <rkoberman@gmail.com> Cc: questions@freebsd.org Subject: Re: drm-kmod kills FreeBSD Message-ID: <24585.30907.103931.103592@jerusalem.litteratus.org> In-Reply-To: <CAN6yY1tqsSWbFggFpLfFtfaEoDUQqKdf6MLLuJi8ei=RV8YpBw@mail.gmail.com> 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> <24584.64455.966459.479993@jerusalem.litteratus.org> <CAN6yY1tqsSWbFggFpLfFtfaEoDUQqKdf6MLLuJi8ei=RV8YpBw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Kevin Oberman <rkoberman@gmail.com> writes, following up to me:
> > 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}.
>
> Easy way to make this "just work" is to add drm-fbsd12.0-kmod to
> PORTS_MODULES in /etc/src.conf. This probably should also be done
> for lsof and virtualbox-osf-kmod, as well, as both depend on
> unstable KBIs. I have:
Usually true.
However - check out the
"Current kernel build broken with linuxkpi"
thread on current@.
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?24585.30907.103931.103592>