iPXE works fine, I tested it last night on a CN65, it just requires some changes to both coreboot and edk2 as the current edk2 PXE implementation does not work with Realtek LAN NICs.
I’ll try to get it cleaned up and pushed later today or tomorrow
Thank you, sir. I am as impressed, if not more, with your work today as I was several years ago when I discovered it. I’d made very good use of these devices since. This is last one I have and I’m not ready to part with it, I’ve identified a new use case for it and the PXE bits help.
you can add:
CONFIG_EDK2_TAG_OR_REV="origin/ipxe_test"
CONFIG_EDK2_CUSTOM_BUILD_PARAMS="-D NETWORK_IPXE=TRUE"
to your board config (eg, configs/kbl/config.fizz.uefi) and then rebuild/flash and see if that works for you. I can’t seem to get a DHCP lease (no RX) but it was working at some point last night so IDK
Do I need to pull the latest source first?
you should be using the tip of the MrChromebox-2509 branch
1 Like
I just pushed an update to the MrChromebox-2509 branch which adds iPXE support and enables it by default for devices with a LAN interface. You can just rebuild FIZZ from source and it will have the iPXE option in the boot menu. You can also add a custom autorun/config script to iPXE which will be executed by default - just need to select that build option.
I found that Kaisa did not add this configuration.
I am working hard on Kaisa equipment.
But your direction is to integrate IPXE.
My direction is that edk2 has built-in PXE support.
The problem with all MAC addresses being 0 is the issue with R8168.c.
There are three related configurations:
RT8168_GET_MAC_FROM_VPD
RT8168_PUT_MAC_TO_ERI
REALTEK_8168_RESET
fixed
it doesn’t work, which is why I removed it in favor of iPXE, which does work
these coreboot configs have nothing to do with the issue. do not mess around with them.