[syslinux] more on PXELinux confiuration file woes

Fredrik Nordgren fno at fno.mine.nu
Tue Jun 17 04:53:56 PDT 2003


I have a similar issue. Using 2.05-pre1, default and hex based IP address
configuration files works just fine. When using a MAC address as the
configuration file name, pxelinux stops just "Ready."

Here are screen dumps from two of my client computers:

---------------------------------------------------
Compaq Armada M700

Intel UNDI, PXE-2.0 (build 071)
Copyright (C) 1997,1998,1999  Intel Corporation

DHCP MAC ADDR: 00 D0 59 05 83 AE
CLIENT IP: 10.52.0.145  MASK: 255.255.255.0  DHCP IP: 10.99.1.10
GATEWAY IP: 10.52.0.253

PXELINUX 2.05 2.05-pre1  Copyright (C) 1994-2003 H. Peter Anvin
Found PXENV+ structure
PXE API version is 0201
UNDI data segment at:   00098E90
UNDI data segment size: 4D30
UNDI code segment at:   0009DBC0
UNDI code segment size: 1E70
PXE entry point fount (we hope) at 9DBC:0106
My IP address seems to be 0A340091 10.52.0.145
ip=10.52.0.145:10.99.1.10:10.52.0.253:255.255.255.0
TFTP prefix:
Trying to load: pxelinux.cfg/01-00-d0-59-05-83-ae
Loading memdisk...
Loading 2disk.img.........................
Ready.
---------------------------------------------------

Compaq Evo D510

Intel Boot Agent Version 4.1.08
Copyright (C) 1997-2002 Intel Corporation

DHCP MAC ADDR: 00 08 02 51 55 EC
CLIENT IP: 10.52.0.201  MASK: 255.255.255.0  DHCP IP: 10.99.1.10
GATEWAY IP: 10.52.0.253

PXELINUX 2.05 2.05-pre1  Copyright (C) 1994-2003 H. Peter Anvin
Found PXENV+ structure
PXE API version is 0201
UNDI data segment at:   00094540
UNDI data segment size: 94B0
UNDI code segment at:   0009D9F0
UNDI code segment size: 20B0
PXE entry point fount (we hope) at 9D9F:0106
My IP address seems to be 0A3400C9 10.52.0.201
ip=10.52.0.201:10.99.1.10:10.52.0.253:255.255.255.0
TFTP prefix:
Trying to load: pxelinux.cfg/01-00-08-02-51-55-ec
Loading memdisk...
Loading disk.img.........................
Ready.
---------------------------------------------------

Hope this is enough info for you to sort it out...


Best regards,

Fredrik Nordgren


----- Original Message ----- 
From: "James Jeffers" <jamesjef at us.ibm.com>
To: <SYSLINUX at zytor.com>
Sent: Thursday, June 12, 2003 3:08 PM
Subject: [syslinux] more on PXELinux confiuration file woes


>
>
>
>
> Relevant /var/log/messages:
> Jun 12 12:49:00 taco in.tftpd[29001]: RRQ from 172.20.5.255 filename
> pxelinux.0
> Jun 12 12:49:05 taco in.tftpd[29002]: RRQ from 172.20.5.255 filename
> pxelinux.0
> Jun 12 12:49:05 taco in.tftpd[29003]: RRQ from 172.20.5.255 filename
> pxelinux.cfg/1:0:2:55:7b:6:2a
> Jun 12 12:49:08 taco in.tftpd[29004]: RRQ from 172.20.5.255 filename
> linux.2.4.18-3.vmlinuz
> Jun 12 12:49:08 taco in.tftpd[29005]: RRQ from 172.20.5.255 filename
> linux.2.4.18-3.initrd.img
>
> Boot screen:
> PXELINUX 2.04 2003-04-16 Copyright (C) H. Peter Anvin
> UNDI data segment at:         0008F940
> UNDI data segment size: B450
> UNDI data segment at:         0008AD90
> UNDI data segment size: 30E0
> PXE entry point found at (we hope) at: 9AD9:0160
> My IP address seems to be AC1405FF 172.20.5.255
> ip=172.20.5.255:172.20.0.1:172.20.0.1:255.255.0.0
> TFTP prefix:
> Trying to load: pxelinux.cfg/1:0:2:55:7b:6:2a
> boot:
> Loading linux.2.4.18-3.vmlinuz....................................
> Loading linux.2.4.18-3.initrd.img...............................<lots more
> of these>........
> Ready.
>
> And it stops right there. The machine isn't locked: I can toggle the caps
> lock leds on the keyboard and using a CTRL-ALT-DEL to reset the machine
(an
> IBM x345 - intel based server).
>
> If I rename the file 1:0:2:55:7b:6:2a to default, the boot proceeds
without
> any problems. If I rename my original default file to AC1405FF, the boot
> proceeds. If I rename the original default to 1:0:2:55:7b:2a, same as the
> above problem. Very perplexing.
>
> I checked the packet captures. PXE requests TFTP for 9495 blocks of 1468
> bytes (447 on the last one), and each one is received and ack'd.
> Nothing fishy there, at least to my eyes.
>
>
> James Jeffers
> Software Engineer
> e1350 Linux Cluster Development
> (919) 254-6250
> T/L 444-6250
> <jamesjef at us.ibm.com>
>
>
>
>                       "H. Peter Anvin"
>                       <hpa at zytor.com>          To:       James
Jeffers/Raleigh/Contr/IBM at IBMUS
>                                                cc:
SYSLINUX at zytor.com
>                       06/11/2003 03:59         Subject:  Re: [syslinux]
more on PXELinux confiuration file woes
>                       PM
>
>
>
>
>
>
> James Jeffers wrote:
> >
> > I performed an experiment in which I had dhcpd specify a named file
> ("foo")
> > instead of
> > one based on a client's MAC address. Lo and behold, the same problem
> > occured. The PXE
> > stack requested and was served the right file, the kernel loaded as did
> the
> > initrd. But again, the
> > boot sequence stopped at "Ready."
> >
> > Keep in mind that the contents of the file are the same as was in the
> > "default" file, which when PXE clients
> > requested and used, everything went very smoothly.
> >
>
> This is extremely odd... could you please send a *complete* list of
> messages printed during boot?
>
>              -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.
>
>





More information about the Syslinux mailing list