[ipxe-devel] better chainload native ipxe-driver (i.e. intel) instead of undionly?

Oliver Rath oliver at greenunit.de
Mon Oct 15 12:55:59 UTC 2018

Hi Matt,

thank you for the hint! What is the content of ${product}? Unfortunatly
there is no documentation for this setting on ipxe.org.



On 15.10.2018 14:51, Matthew Helton wrote:
> Oliver,
> I do it all of the time. However depending on the system Architecture,
> BIOS and Driver support, it can and does introduce some problems with
> certain hardware. I use the iPXE variables for ${product} to blacklist
> problematic hardware.
> Best,
> Matt
> On Mon, Oct 15, 2018 at 7:38 AM Oliver Rath <oliver at greenunit.de
> <mailto:oliver at greenunit.de>> wrote:
>     Hi list,
>     does it make sense to chainload an ipxe-binary with native card
>     support
>     instead of undionly? Ich could imagine, this generate more speed i.e.
>     for downloading big files after ipxe-chainloading. In my case I have
>     always the same intel gigabit card with 82574L chip.
>     Tfh!
>     Oliver
>     _______________________________________________
>     ipxe-devel mailing list
>     ipxe-devel at lists.ipxe.org <mailto:ipxe-devel at lists.ipxe.org>
>     https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
> -- 
> There is never time enough to do it right, but there always seems to
> be enough time to do it again.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20181015/6dd50c15/attachment.htm>

More information about the ipxe-devel mailing list