[syslinux] Can not boot using pxelinux

Geert Stappers stappers at stappers.nl
Sat May 21 03:16:32 PDT 2005


On Sat, May 21, 2005 at 09:35:12AM +0200, Quinn wrote:
> Andrew Soroka wrote:
> 
> >I have fedora3 runing tftp.
> >The server log shows that the client has requested the bootfile
> >
> >May 19 02:04:57 mouse dhcpd: BOOTREQUEST from 00:0d:60:00:8c:b9 via eth0
> >May 19 02:04:57 mouse dhcpd: BOOTREPLY for 192.168.2.200 to mercury (00:0d:60:00:8c:b9) via eth0
> >May 19 01:04:58 mouse in.tftpd[3422]: RRQ from 192.168.2.200 filename pxelinux.0
> >
> >On the client side I can see the following
> >Bootp
> >TFTP.......
> >
> >Then a blinking cursor.
> >
> >Is almost as if pxelinux.0 was not running or was not reading its config
> >file.
> >
> >I have /tftpboot/pxelinux.cfg/default as my config file.
> >
> >Its contents are 
> >
> >DEFAULT memdisk
> >LABEL memdisk
> >     Display HelloWorld.txt
> >     KERNEL vmlinuz
> >     APPEND initrd=initrd.img
> >
> >Note I have tried memdisk and a doss boot floppy image but to no avail.
> >
> >Any help would be appreciated.
> >
> >The client machine is a via C3, I wonder if I need to recompile the 
> >pxelinux
> >for this cpu.
> >
> Judging by the client side messages, pxelinux is not the issue at this 
> point.  Try and
> configure your dhcpd server to load a linux kernel directly instead of 
> pxelinux.0 and
> see if it hangs the same way.  If the test fails, check your network and 
> dhcp/tftp
> settings.
> 
> Another possibility is the client architecture - is it a i386 based 
> processor?  Pxelinux
> will not run on non-i386 processors like PowerPC, Arm, etc.  Via C3 
> should be i386,
> but doing the 1st check above with a linux kernel (compiled for i386) 
> should determine
> if C3 is i386 compatible.
> 
> Hope this helps,

And I hope that further follow-ups go below the text.


Cheers
Geert Stappers




More information about the Syslinux mailing list