Date: Wed, 10 Jan 2024 23:02:20 +0000 From: void <void@f-m.fm> To: freebsd-arm@freebsd.org Subject: Re: current for arm64 tries tftp first for some reason Message-ID: <ZZ8h_INfm_p6VCXV@int21h> In-Reply-To: <856D59CC-E55C-4667-97EE-458104C8DFEE@yahoo.com> References: <ZZqgyHIJhgNoHtES@int21h> <C694B0F9-89C0-42F2-A00F-F77787775655@yahoo.com> <ZZ6CkoBI0q2s1XGj@int21h> <856D59CC-E55C-4667-97EE-458104C8DFEE@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 10, 2024 at 05:07:14AM -0800, Mark Millard wrote: > >The file is not a text file and I've no clue if any >EFI variables happen to be related. My rpi4b context doesn't create /boot/efi/ubootefi.var if the tftp part is allowed to complete. The OS was installed with dd to spinning rust and the ufs2 filesystem as one partition auto-expanded to fill the disk. Maybe this installation method doesn't create it. 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. --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZZ8h_INfm_p6VCXV>