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.
Cheers
Andrew
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, May 19, 2005 at 02:19:41AM +0100, 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.Is pxelinux.0 actually transfered? (verify with `tcpdump port tftp` )> > I have /tftpboot/pxelinux.cfg/default as my config file.[ contents ]> 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.What is special about that CPU? ( tell more about the client )> Cheers > AndrewCheers Geert Stappers -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFCjtdbOSINbgwa/7sRAs7RAKCqJ3TJUzvm29LAKE5DE6AvtQGWxgCgtpxr /hBH9/SibE6c6nCBEnCYTEI=Y+Bw -----END PGP SIGNATURE-----
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, Quinn 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. > >Cheers >Andrew > > >_______________________________________________ >SYSLINUX mailing list >Submissions to SYSLINUX at zytor.com >Unsubscribe or set options at: >http://www.zytor.com/mailman/listinfo/syslinux >Please do not send private replies to mailing list traffic. > > > >
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