Re: [Etherboot-users] Trouble Booting Kernel Image with Etherboot 4.6.7

[John L. <le...@oa...>]

Timothy Legge wrote:

>> This is my first attempt at booting over a network. I am
>> trying to load an image across the network and I am receiving
>> the following message (using Etherboot v4.6.7):
>>
>> "error: not a tagged file
>> unable to load file"
>>
>> over and over and over and over and over and over and over .
>> . . and over again.
>>
>> I've run "mkelf-linux --rootdir=/tftpboot vmlinuz initrd.img
>>
>>> linux.nb"
>>
>> on my image and am still receiving the message. I created an
>> Etherboot
>> v5.4.1 boot disk and am able to load the image via PXE, so
>> I'm sure the vmlinuz and initrd.img files are correct.
>> Updating the onboard ROM isn't an option at this point; I'm
>> stuck with v4.6.7.
>
> No you are not. Simply use 4.6.7 to download a 5.4.1 version of
> etherboot first. If you have a 5.4.1 version of the rom file (zrom)
> then I believe it is simply mknbi-rom whateverrom.zrom >
> whateverrom.zrom.nbi.
>
> Then update your dhcpd.conf file to send whateverrom.zrom.nbi if the
> vendor string is etherboot 4 and the kernel if it is etherboot 5.x
>
> Tim

Thank you Tim.  Your solution did indeed work.

Additional info:
Etherboot v4.6.7 does not report a vendor-class-identifier so I was able 
to do the following:

if substring (option vendor-class-identifier, 0, 9) = "Etherboot" {
    filename "my_image";
} else {
    filename "eb-5.4.1.nb";
}

to first load the new Etherboot version than the image I wanted.

John