[gPXE] Boot very slow or not boot

[Shao Miller]

Milton Labanda wrote:
> ...
> Then i am specifyng only the filename : filename "gpxe/menu.gpxe" at 
> the  *dhcpd.conf*
> The menu.gpxe say:
> #!gpxe
>
> chain menu.c32 menu.cfg
> So you say me need to tell gPXE to load two files by using the second 
> gPXE script I, but
>  i think my *menu.cfg* tell thouse  syslinux in this way:...

Yes, that looks good. :)  Your DHCP service tells the gPXE client to 
execute a gPXE script, and that gPXE script runs a menu system from the 
Syslinux suite.

> The *minirt24.gz*  (initrd) and *linux24* (kernel) i extrated from a 
> *dsl-4.4.10-initrd.iso*  image
> i believe its ready to boot. On purpose where i can get the images 
> like *ubuntu-initrd.img *or *debian-initrd.img*
> that appears in the appnotes?

I'm not familiar with where you can get these files...  Perhaps they are 
available in the "live CD" .ISO file for those Linux distributions, if 
they exist?

> lastly i test with commands
> gPXE> kernel gpxe/dsl/linux24
> its ok.
> gPXE> initrd gpxe/dsl/minirt24.gz
> its say 
> ....................................................................................
> ...............................................................................................
> ..............................................................................................
> and not pass

Is there an error code given after your 'initrd' command above or do you 
never get back to the "gPXE> " prompt?  If you are hanging, it would be 
good to know why.  A possible reason could be an out-of-memory 
condition, but I would expect gPXE to catch that and give an error 
code.  If you are using the Control-B prompt to get the gPXE CLI where 
you are entering these commands, are you pressing Control-B from the 
very first gPXE message you see on the computer?  If so, it might be 
"too early" and the E820 memory map might not be initialized by the 
BIOS.  This only applies if you are using a gPXE ROM image.  Are you?  
If so, wait until you see the second "press Control-B" message and try 
your above test again.

As far as your automated booting goes, you could try to narrow down 
which part of the process might be a possible point of failure.  You 
could eliminate your use of menu.c32 and use a gPXE script which 
directly contains the 'kernel' and 'initrd' commands you'd like to 
test.  If that works, it would suggest a complication with using the 
menu system.

Disclaimer: All claims and opinions are solely those of myself and do 
not and should not be perceived as representing the Etherboot nor the 
gPXE projects in any way.  Thank you for your understanding.

- Shao Miller
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://etherboot.org/pipermail/gpxe/attachments/20100207/c56af9db/attachment.html