Michael Brown

> > I do not see this happening anywhere. > > I'm probably just misreading the output, then, as I trust your interpretation over mine. But here's what I was...

@anderbubble Thank you for the debug images! > So, if I understand properly, this indicates that the problem isn't an issue with legacy/bios vs uefi, but an issue with undi...

> ``` > $ make bin/snponly.efi EMBED=$(readlink -f shell.ipxe) > make: *** No rule to make target 'bin/snponly.efi'. Stop. > ``` > > How do I build this? `make bin-x86_64-efi/snponly.efi`

@gp397 Yes, the E810 will be using the `ice` driver. There is no common driver code shared between that and the `intelx` driver. (The 10G `intelx` driver reuses shared code...

> I'm also checking on whether this is a 1GB network connection, which seems not unlikely to me. (I've experienced a similar problem with link in a Dell iDRAC situation...

> @mcb30 I'm not 100% certain yet, but I think we've confirmed that this 10Gb port is plugged into a 1Gb switchport (possibly through [something like this](https://www.fs.com/products/20057.html)? I know I've...

> The `snponly.efi` build is working in this environment now, and the end-user has further confirmed that this is connected to a 1GbE network. I'm hopeful that when @mcb30 is...

iPXE currently has minimal support for non-ASCII characters. Use UTF8 directly within iPXE scripts (e.g. `echo Héllo wôrld`: no need for `${char_e_acute}` etc.) If the output console supports UTF8 then...

> Will the commit message get a `Reported-by dyeske` or something simular? (See also #723) Check the author of the commit.

> I see the recent commits for ARM64 support, does anyone have any instructions on how I can build this on my own? Just type `make` and you'll get both...