Date: Tue, 27 Dec 2022 15:08:07 +0100 From: Johannes-Maria Kaltenbach <johannes-maria@t-online.de> To: questions@freebsd.org, Graham Perrin <grahamperrin@freebsd.org> Subject: Re: Unable to boot from internal hard disks on new PC Message-ID: <20221227140807.GE11926@localhost.org> In-Reply-To: <cba40072-9fe3-b75c-669b-3d7282944d44@freebsd.org> References: <20221227110800.GA11926@localhost.org> <45e305f7a1193cd6eac03dd0a1499e638c26ceda.camel@riseup.net> <20221227124617.GB11926@localhost.org> <cba40072-9fe3-b75c-669b-3d7282944d44@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 27, 2022 at 01:47:49PM +0000, Graham Perrin wrote: > On 27/12/2022 12:46, Johannes-Maria Kaltenbach wrote: > > > > =E2=80=A6 > > > > Output from efibootmgr: > > +Boot000B* UEFI: USB 2.0 PENDRIVE 1.0, Partition 1 > > Boot0008* UEFI OS > > Boot0002* UEFI: HTTP IPv4 Realtek PCIe GBE Family Controller > > Boot0003* UEFI: PXE IPv4 Realtek PCIe GBE Family Controller > > Boot0004* UEFI: HTTP IPv6 Realtek PCIe GBE Family Controller > > Boot000A* UEFI: PXE IPv6 Realtek PCIe GBE Family Controller > > > > (-b 000b is the installation stick and 0008 the other stick I tested; b= oth no problem) > > > > =E2=80=A6 > > > If the intention is to use the EFI system partition at ada0p2, and if > the operating system at ada0p4 is still bootable, and if you'll not boot that's what I wanted, but I never could boot from ada0 (or another ada#, only from da0 and da1). ada0p4 still contains the system installed from Boot000B, i. e. =66rom the USB with FreeBSD-13.1-RELEASE-amd64-memstick.img . I can still boot from Boot000B. > from the network: you can safely delete unwanted entries. yes, I do not boot from the network; so does that mean that I could delete Boot0002, Boot0003, Boot0004 and Boot000A? > If Boot0008 is mysterious, you could try activating it (and then Boot0008 is not mysterious; it's another USB containing a copy of the system of my old PC and I can boot this also. So I can boot from USB (da[01]), but not from the internal disks (ada[0-3]). > restarting the computer) to tell whether it's usable in relation to your > installation of FreeBSD. > > Things here are very sparse, enough for FreeBSD to boot: > > root@mowa219-gjp4-8570p-freebsd:~ # efibootmgr > Boot to FW : false > BootCurrent: 0000 > Timeout =C2=A0=C2=A0=C2=A0: 5 seconds > root@mowa219-gjp4-8570p-freebsd:~ # I tried to add ada0 using efibootmgr -a -c -l /mnt/efi/boot/BOOTx64.efi -L FreeBSD-13 that created an entry Boot0000* FreeBSD-13 but I didn't see a corresponding entry in bios after reboot and the system booted again from 000b. Best regards, Johannes-Maria
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20221227140807.GE11926>