Date: Wed, 10 Jan 2024 16:06:54 -0800 From: Mark Millard <marklmi@yahoo.com> To: void <void@f-m.fm> Cc: freebsd-arm@freebsd.org Subject: Re: current for arm64 tries tftp first for some reason Message-ID: <F8E08C95-344D-4BAF-B763-E7EBE2DDBDD1@yahoo.com> In-Reply-To: <5800841F-E8D7-4C82-8B93-FA61E5E37D69@yahoo.com> References: <ZZqgyHIJhgNoHtES@int21h> <C694B0F9-89C0-42F2-A00F-F77787775655@yahoo.com> <ZZ6CkoBI0q2s1XGj@int21h> <856D59CC-E55C-4667-97EE-458104C8DFEE@yahoo.com> <ZZ8h_INfm_p6VCXV@int21h> <5800841F-E8D7-4C82-8B93-FA61E5E37D69@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 10, 2024, at 15:49, Mark Millard <marklmi@yahoo.com> wrote: > On Jan 10, 2024, at 15:02, void <void@f-m.fm> wrote: >=20 >> On Wed, Jan 10, 2024 at 05:07:14AM -0800, Mark Millard wrote: >>>=20 >>> The file is not a text file and I've no clue if any >>> EFI variables happen to be related. >>=20 >> My rpi4b context doesn't create /boot/efi/ubootefi.var >> if the tftp part is allowed to complete. >=20 > This might be because I have a GPT partitioning. I tend > to do things like use a Rock64 snapshot dd'd ot media > and copy over the msdosfs materials from a rpi-arm64 > snapshot. Similarly, what I partition and set up for > myself is normally GPT based. >=20 > The file was not present until after the first boot, > which I did not interrupt. Evidence is the lack of a > reasonable timestamp. >=20 > I've just stopped it to get to a U-Boot> prompt and > used the eficonfig command. It displays a menu > that includes "Change Boot Order", for example. >=20 > But, so far, I've not found a way to change from > "Add Boot Option". Well, using the following command at the command prompt: U-Boot> bootefi bootmgr avoided the tftp sequence. FYI: I've still not managed to select "Change Boot Order" in the eficonfig menu. >> The OS was installed with dd to spinning rust and the ufs2 filesystem = as one partition auto-expanded to fill the disk. >=20 > I actually set up my USB3 media to boot most of the > aarch64 systems that I have access to. I move the > media around between the systems. No spinning rust. >=20 > This means that when I updated pre-existing media > with the newer U-Boot is when I got the new behavior > on teh first boot with the newer U-Boot. >=20 >> Maybe this installation method doesn't create it. >>=20 >> Previously I've booted to mmcsd, plugged in the usb3 disk, >> created a 256MB msdos partition, copied all of the msdos part of the >> mmcsd into that partition, ran bsdinstall with the plugged in disk >> as the target. =3D=3D=3D Mark Millard marklmi at yahoo.com =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F8E08C95-344D-4BAF-B763-E7EBE2DDBDD1>