No subject

">> Because of the way we modified multiboot1 in Legacy GRUB for
>> network booting, it is not sufficient to use other multiboot1-
>> compliant loaders, unfortunately.
>
> Is there any documentation on the modifications made available?

Unfortunately, there is no documentation, but you can peruse the Legacy GRUB
source that is bundled with Solaris. The specific workaround I'm referring to
involves the use of the drives_addr field in the multiboot_info structure. On
netboot, the entire DHCP ACK packet is referred-to there.
See line ~1422 of usr/src/uts/i86pc/os/fakebop.c to see how that is
interpreted."

Passing the DHCP packet sounds like something gPXE is capable of
doing.  At this point one could either investigate the details and
write a gPXE patch or file a feature request at
http://support.etherboot.org/ so this issue isn't forgotten.

I am not able to look into Solaris boot at the moment but perhaps
someone is interested in getting this working with gPXE?

Stefan