thr3ads.net - Syslinux - [syslinux] PXE boot hangs after trying to load cfg/<max address> [Sep 2005]

If this information is useful, please help other people find it:
Share via:

Sander

2005-Sep-15 20:07 UTC

[syslinux] PXE boot hangs after trying to load cfg/<max address>

Hi,

i'm trying to get my VIA Epia with VIA Rhine ethernet device to boot
PXELinux. I have done this before, but now i can't get it to work.

The machine loads pxelinux.0, i see some messages. But it fails just
after trying reading the first config file (the one with the mac
address). It kinda says this (transcribed):

CLIENT IP: 192.168.1.23  MASK: 255.255.255.0  DHCP IP: 192.168.1.93
GATEWAY IP: 192.168.1.1

PXELINUX 2.11 (Debian, 2004-09-10)  Copyright (C) 1994-2004 H. Peter Anvin
UNDI data segment at:   00094F30
UNDI data segment size: 9750
UNDI code segment at:   0009E680
UNDI code segment size: 1706
PXE entry point found (we hope) at 9E68:00F6
My IP address seems to be C0A80117 192.168.1.23
ip=192.168.1.23:0.0.0.0:192.168.1.1:255.255.255.0
TFTP prefix:
Trying to load: pxelinux.cfg/01-00-40-63-ca-68-a5

192.168.1.23 is the preferred ip address for this machine. 192.168.1.93
is the dhcp/tftp server. 192.168.1.1 is the router/firewall.

I tried tftpd-hpa and atftpd. I used atftpd some time ago (with the exact
same pxelinux/debian-installer files), but now this fails.

On my dhcp/tftp server i have gcc4. A current Debian unstable with 2.6
kernel. I have tried hard rebooting, disabling WOL and i have no ACPI.

This is what the tftp daemon writes in my log

tftpd-hpa

Sep 15 19:38:59 tuner in.tftpd[3904]: RRQ from 192.168.1.23 filename pxelinux.0 
Sep 15 19:38:59 tuner in.tftpd[3904]: tftp: client does not accept options 
Sep 15 19:38:59 tuner in.tftpd[3905]: RRQ from 192.168.1.23 filename pxelinux.0 

or atftpd

Sep 15 21:41:03 tuner in.tftpd[3998]: connect from 192.168.1.23 (192.168.1.23)
Sep 15 21:41:03 tuner atftpd[3998]: Advanced Trivial FTP server started (0.7)
Sep 15 21:41:03 tuner atftpd[3998]: Serving pxelinux.0 to 192.168.1.23:2070
Sep 15 21:41:03 tuner atftpd[3998]: Serving pxelinux.0 to 192.168.1.23:2071

And this is what ethereal sees

2157.836001      0.0.0.0 -> 255.255.255.255 DHCP DHCP Discover - Transaction
ID 0x64ca68a5
2157.836579 192.168.1.93 -> 255.255.255.255 DHCP DHCP Offer    - Transaction
ID 0x64ca68a5
2159.837314      0.0.0.0 -> 255.255.255.255 DHCP DHCP Request  - Transaction
ID 0x64ca68a5
2159.837881 192.168.1.93 -> 255.255.255.255 DHCP DHCP ACK      - Transaction
ID 0x64ca68a5
2159.841851 ViaTechn_ca:68:a5 -> Broadcast    ARP Who has 192.168.1.93?  Tell
192.168.1.23
2159.841871 tuner.rotzorg.org -> ViaTechn_ca:68:a5 ARP 192.168.1.93 is at
00:10:4b:2a:ce:2f
2159.841974 192.168.1.23 -> 192.168.1.93 TFTP Read Request, File: pxelinux.0,
Transfer type: octet
2159.843251 192.168.1.93 -> 192.168.1.23 TFTP Option Acknowledgement
2159.843363 192.168.1.23 -> 192.168.1.93 TFTP Error Code, Code: Not defined,
Message: TFTP Aborted
2159.844558 192.168.1.23 -> 192.168.1.93 TFTP Read Request, File: pxelinux.0,
Transfer type: octet
2159.845581 192.168.1.93 -> 192.168.1.23 TFTP Option Acknowledgement
2159.845691 192.168.1.23 -> 192.168.1.93 TFTP Acknowledgement, Block: 0
2159.846121 192.168.1.93 -> 192.168.1.23 TFTP Data Packet, Block: 1
2159.846659 192.168.1.23 -> 192.168.1.93 TFTP Acknowledgement, Block: 1
2159.846796 192.168.1.93 -> 192.168.1.23 TFTP Data Packet, Block: 2

<sniip>

2159.851266 192.168.1.23 -> 192.168.1.93 TFTP Acknowledgement, Block: 8
2159.851394 192.168.1.93 -> 192.168.1.23 TFTP Data Packet, Block: 9 (last)
2159.851549 192.168.1.23 -> 192.168.1.93 TFTP Acknowledgement, Block: 9
2159.870665 192.168.1.23 -> 0.0.0.0      TFTP Read Request, File:
pxelinux.cfg/01-00-40-63-ca-68-a5, Transfer type: octet
2164.843251 tuner.rotzorg.org -> ViaTechn_ca:68:a5 ARP Who has 192.168.1.23? 
Tell 192.168.1.93
2164.843342 ViaTechn_ca:68:a5 -> tuner.rotzorg.org ARP 192.168.1.23 is at
00:40:63:ca:68:a5

and there it stops. I can't even get Num Lock to change anymore.

I see no Ack from the tftp server, which suggests
something is wrong there and not on the booting machine. This seems even
more plausible because of the fact that haven't touched the
debian-install tftp files but did upgrade my machine through Debian
Unstable. I can't figure it out though.

Thanks in advance
Sander De Graaf

Geert Stappers

2005-Sep-16 14:25 UTC

head link

[syslinux] PXE boot hangs after trying to load cfg/<max address>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Sep 15, 2005 at 10:07:44PM +0200, Sander wrote:> Hi,
> 
> i'm trying to get my VIA Epia with VIA Rhine ethernet device to boot
> PXELinux. I have done this before, but now i can't get it to work.
> 
> The machine loads pxelinux.0, i see some messages. But it fails just
> after trying reading the first config file (the one with the mac
> address). It kinda says this (transcribed):
> 
> CLIENT IP: 192.168.1.23  MASK: 255.255.255.0  DHCP IP: 192.168.1.93
> GATEWAY IP: 192.168.1.1
> 
> PXELINUX 2.11 (Debian, 2004-09-10)  Copyright (C) 1994-2004 H. Peter Anvin
> UNDI data segment at:   00094F30
> UNDI data segment size: 9750
> UNDI code segment at:   0009E680
> UNDI code segment size: 1706
> PXE entry point found (we hope) at 9E68:00F6
> My IP address seems to be C0A80117 192.168.1.23
> ip=192.168.1.23:0.0.0.0:192.168.1.1:255.255.255.0
                  ^^^^^^^> TFTP prefix:
> Trying to load: pxelinux.cfg/01-00-40-63-ca-68-a5
> 
> 192.168.1.23 is the preferred ip address for this machine. 192.168.1.93
> is the dhcp/tftp server. 192.168.1.1 is the router/firewall.
> 
> I tried tftpd-hpa and atftpd. I used atftpd some time ago (with the exact
> same pxelinux/debian-installer files), but now this fails.
> 
> On my dhcp/tftp server i have gcc4. A current Debian unstable with 2.6
> kernel. I have tried hard rebooting, disabling WOL and i have no ACPI.
> 
> This is what the tftp daemon writes in my log
> 
> tftpd-hpa
> 
> Sep 15 19:38:59 tuner in.tftpd[3904]: RRQ from 192.168.1.23 filename
pxelinux.0
> Sep 15 19:38:59 tuner in.tftpd[3904]: tftp: client does not accept options 
> Sep 15 19:38:59 tuner in.tftpd[3905]: RRQ from 192.168.1.23 filename
pxelinux.0
> 
> or atftpd
> 
> Sep 15 21:41:03 tuner in.tftpd[3998]: connect from 192.168.1.23
(192.168.1.23)
> Sep 15 21:41:03 tuner atftpd[3998]: Advanced Trivial FTP server started
(0.7)
> Sep 15 21:41:03 tuner atftpd[3998]: Serving pxelinux.0 to 192.168.1.23:2070
> Sep 15 21:41:03 tuner atftpd[3998]: Serving pxelinux.0 to 192.168.1.23:2071
> 
> And this is what ethereal sees
> 
> 2157.836001      0.0.0.0 -> 255.255.255.255 DHCP DHCP Discover -
Transaction ID 0x64ca68a5
> 2157.836579 192.168.1.93 -> 255.255.255.255 DHCP DHCP Offer    -
Transaction ID 0x64ca68a5
> 2159.837314      0.0.0.0 -> 255.255.255.255 DHCP DHCP Request  -
Transaction ID 0x64ca68a5
> 2159.837881 192.168.1.93 -> 255.255.255.255 DHCP DHCP ACK      -
Transaction ID 0x64ca68a5
During Dynamic Host Configuration is "0.0.0.0" the not yet configured
client.
> 2159.841851 ViaTechn_ca:68:a5 -> Broadcast    ARP Who has 192.168.1.93? 
Tell 192.168.1.23
> 2159.841871 tuner.rotzorg.org -> ViaTechn_ca:68:a5 ARP 192.168.1.93 is
at 00:10:4b:2a:ce:2f
> 2159.841974 192.168.1.23 -> 192.168.1.93 TFTP Read Request, File:
pxelinux.0, Transfer type: octet
> 2159.843251 192.168.1.93 -> 192.168.1.23 TFTP Option Acknowledgement
> 2159.843363 192.168.1.23 -> 192.168.1.93 TFTP Error Code, Code: Not
defined, Message: TFTP Aborted
> 2159.844558 192.168.1.23 -> 192.168.1.93 TFTP Read Request, File:
pxelinux.0, Transfer type: octet
> 2159.845581 192.168.1.93 -> 192.168.1.23 TFTP Option Acknowledgement
> 2159.845691 192.168.1.23 -> 192.168.1.93 TFTP Acknowledgement, Block: 0
Client .23 acknowledge  TFTP server .93
> 2159.846121 192.168.1.93 -> 192.168.1.23 TFTP Data Packet, Block: 1
> 2159.846659 192.168.1.23 -> 192.168.1.93 TFTP Acknowledgement, Block: 1
> 2159.846796 192.168.1.93 -> 192.168.1.23 TFTP Data Packet, Block: 2
> 
> <sniip>
> 
> 2159.851266 192.168.1.23 -> 192.168.1.93 TFTP Acknowledgement, Block: 8
> 2159.851394 192.168.1.93 -> 192.168.1.23 TFTP Data Packet, Block: 9
(last)
> 2159.851549 192.168.1.23 -> 192.168.1.93 TFTP Acknowledgement, Block: 9
> 2159.870665 192.168.1.23 -> 0.0.0.0      TFTP Read Request, File:
pxelinux.cfg/01-00-40-63-ca-68-a5, Transfer type: octet                              ^^^^^^^



Client .23 requests server .0 the MAC-address file.
> 2164.843251 tuner.rotzorg.org -> ViaTechn_ca:68:a5 ARP Who has
192.168.1.23?  Tell 192.168.1.93
> 2164.843342 ViaTechn_ca:68:a5 -> tuner.rotzorg.org ARP 192.168.1.23 is
at 00:40:63:ca:68:a5
> 
> and there it stops. I can't even get Num Lock to change anymore.
> 
> I see no Ack from the tftp server, which suggests
> something is wrong there and not on the booting machine. This seems even
> more plausible because of the fact that haven't touched the
> debian-install tftp files but did upgrade my machine through Debian
> Unstable. I can't figure it out though.
You have a incomplete configured DHCP server,
add the "next server" command in dhcpd.conf.

See also
 http://sourceforge.net/mailarchive/forum.php?thread_id=8206258&forum_id=6402
> Thanks in advance
For a better world it is a good thing to tell
if an answer was ( or wasn't )  helpfull.

> Sander De Graaf

St

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFDKtW8OSINbgwa/7sRAg98AJ44xs6h0NW43nrDXAVob31q0gB7VwCeLZ9B
edm+xQ9rXPg1yB8SYRaPYKo=6zP4
-----END PGP SIGNATURE-----

Reasonably Related Threads

Search for more seemingly similar threads

Syslinux - Sep 2005 - PXE boot hangs after trying to load cfg/<max address>

[syslinux] PXE boot hangs after trying to load cfg/<max address>

[syslinux] PXE boot hangs after trying to load cfg/<max address>

Reasonably Related Threads