On Fri, Aug 16, 2024, 5:22 PM Kevin Oberman <rkober...@gmail.com> wrote:
> On Tue, Aug 13, 2024 at 3:45 PM Warner Losh <i...@bsdimp.com> wrote: > >> >> >> On Tue, Aug 13, 2024, 4:02 PM Alexander Ziaee <concussi...@runbox.com> >> wrote: >> >>> On 2024-08-13 17:51 -04:00 EDT, "Shawn Webb" <shawn.w...@hardenedbsd.org> >>> wrote: >>> > On Tue, Aug 13, 2024 at 09:45:54PM UTC, Alexander Ziaee wrote: >>> >>> >> Compiling freebsd-current/generic at head commit 6481b4 on >>> freebsd-current/generic from July 11th after a `make cleanworld` panics on >>> bare metal boot on a thinkpad x230. >>> >>> > I had the same issue. I rebuilt/reinstalled the >>> graphics/gpu-firmware-kmod and >>> > graphics/drm-515-kmod ports. After a reboot, all was well. >>> >>> Cool, thanks Shawn! >>> >>> Should we put an entry in UPDATING when current will panic without the >>> latest drm-kmod, or some other type of instruction somewhere? >>> >> >> Every time you update the kernel, you must rebuild drm-kmod. If you don't >> all bets are off. >> >> I have a different panic with the kernel from 20 minutes ago. Joy. >> >> Warner >> >> Best, >>> Alex >>> >> > I have long had PORTS_MODULES+= graphics/drm-61-kmod in /etc/src.conf. > Thei does result in the module being rebuilt every time I build a kernel, > but it assures that it will work on the boot of the new kernel. > It's the only way to be safe. Warner > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkober...@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 >
