Re: nextboot warns it won't reset

On Fri, Jul 19, 2024 at 12:05 PM Gareth de Vaux <stable@lordcow.org> wrote:

> On Fri 2024-07-19 (13:11), Ronald Klop wrote:
> > I think you don't need nextboot for what you want to do as long as you
> have console access to the machine.
> >
> > If you have console access you can interrupt the boot loader and choose
> another kernel to boot.
>
> Thanks, that's what I meant by taking my chances manually. I've run into
> trouble there, though will
> create a new thread.
>

While booting a non-standard kernel (e.g. kernel.old) will use the
/boot/kernel.old for the kernel and many modules, kernel modules from ports
(e.g. /boot/modules/i915kmod.ko) don't have an "old" version. As a result,
things like graphics and such often won't work with kernel.old. They need
to be built with the kernel sources matching the kernel booted. If you have
a backup from before the update, simply copy /boot/modules/* from backup.
Again, it is almost certain that you can boot to a non-graphic system
console.

When this happened to me two days ago, I ended up with a running, but
somewhat broken system after copying /boot/modules/* from a backup made
before building the new system. This did leave userlan out of sync with the
kernel and, due to unfortunate timing, geli would not work and I had to
reset my sources to the running kernel and rebuild the system to get access
to critical files.


-- 
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683