[syslinux] PXE boot problem

[Ellery D'Souza]

Mike,

Try adding the "next-server 192.168.1.1" config to your dhcp.conf file. 

The boot server is not set, that is why you see 0.0.0.0 in the ip= line

Mike Kinton wrote:
> The symptoms are as follows:-
> 1) dhcp allocates the correct ip address 192.168.1.254
> 2) PXE 3.31 loads
> 3) gives correct ip address followed by
>    ip=192.168.1.254:0.0.0.0:192.168.1.1:255.255.255.0
> 4) tries to load - MAC address to default and then gives the message
>    "Unable to locate configuration file"
>
> The server is running Suse 10.2 on a Via epia motherboard.
> Suse says that the ethernet chip is "Rhine" ... 
>
> The dhcp.conf file is:
> ===================================================================
> allow booting;
> allow bootp;
> option domain-name "waymaker";
> option domain-name-servers 62.241.162.200;
> option routers 192.168.1.1;
> ddns-update-style interim;
> ignore client-updates;
> default-lease-time 14400;
> subnet 192.168.1.0 netmask 255.255.255.0 {
>   option subnet-mask 255.255.255.0;
>   range 192.168.1.100 192.168.1.254;
>   default-lease-time 21600;
>   max-lease-time 43200;
> }
> host kt {
>     filename "pxelinux.0";
>     hardware ethernet 00:80:91:32:22:3a;
>     fixed-address 192.168.1.254;
> }
> =================================================================  
> tftp config file is
> -----------------------------------------------------------------
> # default: off
> # description: tftp service is provided primarily for booting or when a \
> # 	router need an upgrade. Most sites run this only on machines acting
> as
> # 	"boot servers".
> service tftp
> {
> 	socket_type     = dgram
> 	protocol        = udp
> 	wait            = yes
> 	user            = root
> 	server          = /usr/sbin/in.tftpd
> 	server_args     =  -s /tftpboot -vv
> 	disable         = no
> }
> -----------------------------------------------------------------
> Default file in pxelinux.cfg
> -----------------------------
> prompt 1
> default linux
> timeout 30
> label linux
> 	kernel vmlinuz
> 	append initrd=initrd.img ramdisk_size=9216 noapic acpi=off
> ================================================================
> Listing of the pxe.cfg directory is 
> -----------------------------------
> total 4
> -rw-r--r-- 1 root root   0 2007-04-01 18:59 01-00-80-91-32-22-3a
> -rwxr-xr-x 1 root root   0 2007-03-24 10:46 C
> -rwxr-xr-x 1 root root   0 2007-03-22 21:35 C0
> -rwxr-xr-x 1 root root   0 2007-03-22 21:36 C0A
> -rwxr-xr-x 1 root root   0 2007-03-22 21:36 C0A8
> -rwxr-xr-x 1 root root   0 2007-03-22 21:36 C0A80
> -rwxr-xr-x 1 root root   0 2007-03-22 21:36 C0A801
> -rwxr-xr-x 1 root root   0 2007-03-24 10:48 C0A801F
> -rwxr-xr-x 1 root root   0 2007-03-22 21:36 C0A801FE
> -rwxr-xr-x 1 root root 124 2007-03-28 20:14 default
> ===============================================================
>
> I hope that this is sufficient information.  I have checked permissions and
> turned off the firewall.
>
> The machine that I am trying to load with Fedora core 4 is a Toshiba ST-60
> till.
>
>  
>
>
>
> -----Original Message-----
> From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] On
> Behalf Of H. Peter Anvin
> Sent: 30 March 2007 21:44
> To: Josef Siemes
> Cc: Malkowski, Dennis (GE Healthcare, non-ge); syslinux at zytor.com
> Subject: Re: [syslinux] PXE boot problem
>
> Josef Siemes wrote:
>   
>> can't see any problem. Give more details: Did it work before? Syslinux
>>     
> version? Hardware? DHCP config? Screen Output? etc.pp.
>   
>
> Indeed, without the above information it's pretty impossible to figure out.
>
> 	-hpa
>
> _______________________________________________
> 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.
>
> _______________________________________________
> 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.
>
>
>
>