Date: Fri, 19 Jul 2024 14:38:57 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Gareth de Vaux <stable@lordcow.org> Cc: freebsd-stable@freebsd.org, Ronald Klop <ronald-lists@klop.ws> Subject: Re: nextboot warns it won't reset Message-ID: <CAN6yY1sj_15odsHMap2VUeW_13O1Tx5neMbzts5Djmw6uvCMhw@mail.gmail.com> In-Reply-To: <Zpq4tKT2h9zOrAwJ@lordcow.org> References: <Zpl_ApIOpRkUNpnq@lordcow.org> <01D917DB-7E47-46D7-AD22-AD09C4F89A96@FreeBSD.org> <ZppBZzE1S6opfNAo@lordcow.org> <390734156.4694.1721387508471@localhost> <Zpq4tKT2h9zOrAwJ@lordcow.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000cd1623061da08664 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jul 19, 2024 at 12:05=E2=80=AFPM 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. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000cd1623061da08664 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon= t-family:tahoma,sans-serif;font-size:small">On Fri, Jul 19, 2024 at 12:05= =E2=80=AFPM Gareth de Vaux <<a href=3D"mailto:stable@lordcow.org">stable= @lordcow.org</a>> wrote:</div></div><div class=3D"gmail_quote"><blockquo= te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px = solid rgb(204,204,204);padding-left:1ex">On Fri 2024-07-19 (13:11), Ronald = Klop wrote:<br> > I think you don't need nextboot for what you want to do as long as= you have console access to the machine.<br> > <br> > If you have console access you can interrupt the boot loader and choos= e another kernel to boot.<br> <br> Thanks, that's what I meant by taking my chances manually. I've run= into trouble there, though will<br> create a new thread.<br></blockquote><div><br></div><div style=3D"font-fami= ly:tahoma,sans-serif;font-size:small" class=3D"gmail_default">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. Aga= in, it is almost certain that you can boot to a non-graphic system console.= </div><div style=3D"font-family:tahoma,sans-serif;font-size:small" class=3D= "gmail_default"><br></div><div style=3D"font-family:tahoma,sans-serif;font-= size:small" class=3D"gmail_default">When this happened to me two days ago, = I ended up with a running, but somewhat broken system after copying /boot/m= odules/* 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 wo= uld not work and I had to reset my sources to the running kernel and rebuil= d the system to get access to critical files.<br></div></div><br clear=3D"a= ll"><br><span class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"lt= r" class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><d= iv dir=3D"ltr"><div><div dir=3D"ltr">Kevin Oberman, Part time kid herder an= d retired Network Engineer<br>E-mail: <a href=3D"mailto:rkoberman@gmail.com= " target=3D"_blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerprint: = D03FB98AFA78E3B78C1694B318AB39EF1B055683</div></div></div></div></div></div= ></div></div></div> --000000000000cd1623061da08664--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1sj_15odsHMap2VUeW_13O1Tx5neMbzts5Djmw6uvCMhw>