From nobody Fri Jul 19 21:38:57 2024 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WQjjt73n4z5QQC7 for ; Fri, 19 Jul 2024 21:39:14 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WQjjt5JGQz4S2L for ; Fri, 19 Jul 2024 21:39:14 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb36.google.com with SMTP id 3f1490d57ef6-e05ed8a5526so2432105276.3 for ; Fri, 19 Jul 2024 14:39:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721425154; x=1722029954; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/2jLSZsXh97c6LIzEySBvDSQffBtQVfLLDFe9xGqWfw=; b=MaC+RVhbdUEoGUP/KyDF24afTcanWbafLI/TYCBxaw1sV6tfCAO8XnmuIHBKqWS2p5 UxPYcrZw5T8RNARlNYt+hHjvIjG0O2DgBtXt4ST5JU0FIqeNLD/Nzt/1WsLpwezcvPSv sbZYxIyVMz75a6jB3lOjEhKSQQEW38GOpDAYC4ehHIbr7cjuKj3Kyx/zAeo0YRDmylOU GmAIdHEKAnwosF9bokAbRTJ5ceo2tf0QtAXnFDm5TPc4RYgiW177HtnhTQHa8lwI5EWN Dqy0xDKhq4/2bFhdgpeeaDGiFvFZ7QgjKP3tHtHDcVUEZHMIq+PimrHjKdJhqONSOjDe xqmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721425154; x=1722029954; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/2jLSZsXh97c6LIzEySBvDSQffBtQVfLLDFe9xGqWfw=; b=rFz2VUxNXHEPAazeYGhh3FuhrAQLFNg2GDM0f+q0ZSwZds2bHSSsNyTHD0ReA6hoJU SBiz13wdVCRm0yJhUHvJZ05WKD5rtMJ/S8AVY9/74nMcKZdbiK7hFDQ2eaysf1lMTz2Z C7NjITXgyV4+oy4g587tTywTmlJE3+fr/xHcVObEDmpR67xz9rRVQql0e+Nxkhn6CZHH /GfKEDHnlLB2cb5Lz8CnGOsQ11gNWOQgm+++c2BiX5H+Av7k0H7H7DEHHnkp245SK3Yg +stxMeKg1Mdi0RwHmgqKDZnGhNN9zBVotr5rV5mXm+8qbnukVsksmlUM3R0yGCWYQ4ee 99Fw== X-Gm-Message-State: AOJu0YzQ1PrpPW0Jbzku69MD0KfGXBntHTCr2Sdp9Je55huBykRnIgS2 GeEh5mLIAAHarZsKgD6o2M8NUmomx5dhFVSvqkzqNEPYnWfuFKyY5/BO67a6trMeLoOntahB89T DVP7obRtqk6rz7ExJ1iWwJwj8FV8AoGUI X-Google-Smtp-Source: AGHT+IGDbvqYTVeffQIu2jLJPs1l1KDjvC9q9EmIEtQr8/7yW0I48d8UWIPSNQ65CyEB/SQFqKFta2jR8D5ofNvx0hM= X-Received: by 2002:a05:6902:2302:b0:e03:5db1:a760 with SMTP id 3f1490d57ef6-e05ed78f13dmr9488508276.36.1721425153820; Fri, 19 Jul 2024 14:39:13 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 References: <01D917DB-7E47-46D7-AD22-AD09C4F89A96@FreeBSD.org> <390734156.4694.1721387508471@localhost> In-Reply-To: From: Kevin Oberman Date: Fri, 19 Jul 2024 14:38:57 -0700 Message-ID: Subject: Re: nextboot warns it won't reset To: Gareth de Vaux Cc: freebsd-stable@freebsd.org, Ronald Klop Content-Type: multipart/alternative; boundary="000000000000cd1623061da08664" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4WQjjt5JGQz4S2L --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 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
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 choos= e 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. Aga= in, 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/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.


--
Kevin Oberman, Part time kid herder an= d retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: = D03FB98AFA78E3B78C1694B318AB39EF1B055683
--000000000000cd1623061da08664--