Jonathon Anderson

I updated the release notes with the full changelog since v4.3.0, and also added explicit notes about the command-line changes to nodes and profiles.

Thanks: will do. Can we compile with DEBUG=Intel,intelx,netdevice all together? Or is netdevice just meant to be a stand-in for the specific device anyway?

Understood; that `I` was just because I was typing my last message on my phone. :/ We'll get that debug information generated and to you. Thanks!

We have gathered the requested debug information. This is using iPXE builds with `DEBUG=intel,intelx,netdevice`. The interface we're trying to bring up has mac address 00:8C:FA:F2:12:3E, which is showing up as...

> In the BIOS case, you are using undionly.kpxe which (by design) will only ever see a single network interface since it includes no native iPXE drivers and can only...

> I suppose I had assumed that we had to use undionly.kpxe when running in BIOS mode. It appears we are / Warewulf is trying to follow the advice here:...

> Ah, I see the source of the confusion Thank you so much for the explanation! > Could you please try building make DEBUG=intel,intelx bin/intelx.pxe and testing that in BIOS...

Here is a (failed) boot attempt in legacy/bios mode using the requested bin/intelx.pxe with DEBUG=intel,intelx (and an embedded script that drops to an iPXE shell after an autoboot attempt). ...

> Something that will probably also just work is for you to use snponly.efi and avoid the native driver. But that would not help fixing any issues, just work around...

Thanks for the pointer to snponly.efi. I've cut a build of that, and we'll see if that works in our environment. I'm also checking on whether this is a 1GB...