Re: [Etherboot-developers] e1000 and etherboot menu

[Hans-Peter J. <hp...@ur...>]

Hi Anselm,

thanks for your quick answer.

On Tuesday 17 June 2003 18:56, Anselm Martin Hoffmeister wrote:
> Hello Hans-Peter,
>
> > [...]
> > only supported by the current development version, which
> > unfortunately has the menuing stuff removed.
> >
> > If I cannot flash etherboot on the NIC, I normally use a pxe target
> > to load etherboot (dhcp filename), which in turn presents the menu
> > and loads the default kernel.
> >
> > What is the prefered way to mimic this behaviour in the development
> > series?
>
> You can use some newer mknbi to create an external menu program which
> does exactly what you want. [man mknbi-menu] It seems to be with
> mknbi-1.2.6 and newer (though I did not use it myself). RTfineM...

Well, the manual is a bit sparse on that topic :-(.

Loading the e1000 driver from floppy and using menu.elf as the boot 
target restarts the system after printing
[E1000]Ethernet addr: xx:xx:xx:xx:xx:xx
(the last line printed is unpossible to read without a serial console)

Using menu.nbi gives the error message: not a valid image
Unable to load file and loops in the boot destination selection...

Never the less, even if I get the menu going, I have no idea, how to 
daisy chain it from the e1000.pxe image. Is it possible to combine 
those two images into one?

An additional side note: running e1000 from floppy stops in about 3 of 5 
times after loading the kernel image:

..........................done
[Freeze]

The kernel image was created with a command similar to:
mknbi-linux $kernelimg --format=elf --first32pm= --rootdir=$rootdir 
--ip=rom --append="$append > $netbootimg

> > Booting-from-floppy-is-really-uncool'ly y'rs
>
> Yup!
>
> > Pete
>
> Best regards,
>  Anselm Martin Hoffmeister
>  Stockholm Projekt Computer-Service
>  <an...@ho...>

Thanks again,
Pete