On 10/2/23 03:00, Stuart Henderson wrote:
It doesn't directly help you, but the boot loader doesn't have any
NIC-specific code, it calls into EFI to make network connections.
That certainly does help clarify things.
the 1-line info for
the latest firmware for VP4650 says "CSM UEFI Network fix" so if you
don't have that already, I'd try updating first.
Thanks, that did the trick. After flashing the VP4650 with the newer
firmware from Protectli, it was then able to load and boot the OpenBSD
installer kernel over tftp. Unfortunately, that newer firmware with the
UEFI network fix is actually proprietary AMI (American Megatrends)
firmware. (Protectli supports both AMI and coreboot, but sadly they
doesn't yet offer any newer version of coreboot than the one this VP4650
shipped with.)
For reference, the coreboot firmware the with the UEFI
networking/PXE-boot problem shows up in OpenBSD's dmesg output as:
bios0: vendor 3mdeb version "Dasharo (coreboot+UEFI) v1.0.19" date
12/08/2022
And the proprietary AMI firmware which made PXE-boot work is labeled on
Protectli's download page as "VP4650-230615" / "CML6A 2.40":
https://kb.protectli.com/kb/bios-versions-for-the-vault/
and it shows up on dmesg as:
bios0: vendor American Megatrends Inc. version "5.17" date 06/09/2023
Good to know that it's not actually an OpenBSD bug, but coreboot. I'll
file a ticket with Protectli about it.
Thanks again for your help with this!
