Date: Tue, 25 Jun 2019 21:04:04 +0200 From: Jan Beich <jbeich@FreeBSD.org> To: Rebecca Cran <bcran@freebsd.org> Cc: freebsd-current@freebsd.org, D Scott Phillips <scottph@FreeBSD.org> Subject: Re: CTF: UEFI HTTP boot support Message-ID: <7e99-pjvf-wny@FreeBSD.org> References: <5cbfe8da-25d3-123f-52a1-08cde4e83f67@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Rebecca Cran <bcran@freebsd.org> writes:
> I've been working with D Scott Phillips to test the UEFI HTTP loader
> code he's written, and we're now ready for wider testing.
[...]
I can't boot after r349349. loader.efi appears to fail to load. As my
boot pool is striped maybe HTTP code interferes with ZFS code assembling
bits from multiple disks. Any ideas how to debug?
Note, UEFI Network Stack is disabled and UEFI Hard Disk is #1 boot option.
>> FreeBSD EFI boot block
Loader path: /boot/loader.efi
Initializing modules: ZFS UFS
Load Path: \EFI\BOOT\BOOTX64.EFI
LoadDevice: PciRoot(0x0)/Pci(0x1B,0x0)/Pci(0x0,0x0)/Unit(0x1)/HD(2,GPT,...)
BootCurrent: 0004
BootOrder: 0004 0005 0006 0007
Probing 20 block devices......+.....*....+..... done
ZFS found the following pools: foo bar
UFS found no partitions
command args: -DS115200
Consoles: EFI console
Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk1p3:
\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7e99-pjvf-wny>