thr3ads.net - Syslinux - [syslinux] pxelinux bootup problems on EPIA-M [Jun 2003]

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

Andrea Rosso

2003-Jun-15 06:35 UTC

[syslinux] pxelinux bootup problems on EPIA-M

Hi,

I was wondering if anyone had a good dhcpd.conf and /tftpboot
files for a EPIA-M motherboard with RedHat 9.0.... Or maybe
just a configuration that works with the EPIA-M (doesn't matter
which type of linux).

I'm trying to boot the system from the network and it seems to
be getting to downloading pxelinux.0 but then nothing happens
after that....

I'm using ISC dhcpd V3.0pl2, tftp-hpa 0.34 and pxelinux 2.04.

Here is a tcpdump of what's happening:

21:59:14.792397 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0x64c4edbb
secs:4
flags:0x8000 [|bootp]
21:59:14.793743 sole2.bootps > 255.255.255.255.bootpc:  xid:0x64c4edbb
secs:4 fl
ags:0x8000 Y:musica S:sole2 [|bootp] [tos 0x10]
21:59:16.795384 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0x64c4edbb
secs:4
flags:0x8000 [|bootp]
21:59:16.797349 sole2.bootps > 255.255.255.255.bootpc:  xid:0x64c4edbb
secs:4 fl
ags:0x8000 Y:musica S:sole2 [|bootp] [tos 0x10]
21:59:16.798268 musica.bootpc > 255.255.255.255.bootps:  xid:0x64c4edbb
secs:4 f
lags:0x8000 C:musica [|bootp]
21:59:16.800189 sole2.bootps > 255.255.255.255.bootpc:  xid:0x64c4edbb
secs:4 fl
ags:0x8000 C:musica Y:musica S:sole2 [|bootp] [tos 0x10]
21:59:17.837427 arp who-has sole2 tell musica
21:59:17.837475 arp reply sole2 is-at 0:3:ba:b:e6:b1
21:59:17.837537 musica.2070 > sole2.tftp:  27 RRQ "pxelinux.0"
21:59:17.845698 sole2.33030 > musica.2070: udp 14 (DF)
21:59:17.845772 musica.2070 > sole2.33030: udp 17
21:59:17.845873 musica.2071 > sole2.tftp:  32 RRQ "pxelinux.0"
21:59:17.856330 sole2.33031 > musica.2071: udp 15 (DF)
21:59:17.856404 musica.2071 > sole2.33031: udp 4
21:59:17.856976 sole2.33031 > musica.2071: udp 1460 (DF)
21:59:17.857225 musica.2071 > sole2.33031: udp 4
21:59:17.857474 sole2.33031 > musica.2071: udp 1460 (DF)
21:59:17.857706 musica.2071 > sole2.33031: udp 4
21:59:17.857912 sole2.33031 > musica.2071: udp 1460 (DF)
21:59:17.858145 musica.2071 > sole2.33031: udp 4
21:59:17.858338 sole2.33031 > musica.2071: udp 1460 (DF)
21:59:17.858571 musica.2071 > sole2.33031: udp 4
21:59:17.858757 sole2.33031 > musica.2071: udp 1460 (DF)
21:59:17.858988 musica.2071 > sole2.33031: udp 4
21:59:17.859172 sole2.33031 > musica.2071: udp 1460 (DF)
21:59:17.859404 musica.2071 > sole2.33031: udp 4
21:59:17.859588 sole2.33031 > musica.2071: udp 1460 (DF)
21:59:17.859822 musica.2071 > sole2.33031: udp 4
21:59:17.860077 sole2.33031 > musica.2071: udp 968 (DF)
21:59:17.860247 musica.2071 > sole2.33031: udp 4

So it seems like things are going ok until the pxelinux.0 is downloaded.
My dhcpd.conf is setup like this:

allow booting;
allow bootp;

# Standard configuration directives...

option domain-name "rossoweb.com";
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.2.1;
option domain-name-servers 192.168.2.1;
option routers 192.168.2.1;

ddns-update-style none;
subnet 192.168.2.0 netmask 255.255.255.0 {
 range 192.168.2.100 192.168.2.255;
}

# Group the PXE bootable hosts together
group {
        # PXE-specific configuration directives...
        next-server 192.168.2.1;
        option vendor-class-identifier "PXEClient";
        option vendor-encapsulated-options
09:0f:80:00:0c:4e:65:74:77:6f:72:6b:2
0:62:6f:6f:74:0a:07:00:50:72:6f:6d:70:74:06:01:02:08:03:80:00:00:47:04:80:00
:00:
00:ff;
        filename "pxelinux.0";

        # You need an entry like this for every host
        # unless you're using dynamic addresses
        host musica {
                        hardware ethernet 00:40:63:c4:ed:bb;
                        fixed-address 192.168.2.100;
                }
        }

I added the option vendor* lines to see if this might make a difference but
I didn't have any luck.

On the bootup screen I only see:

...<EPIA startup stuff>

CLIENT MAC ADDR: ........
CLIENT IP: 192.168.2.100 MASK: 255.255.255.0 DHCP IP:192.168.2.1
GATEWAY IP: 192.168.2.1

Auto-select:
	Network boot

BOOT SERVER IP: 192.168.2.1

And then it stops there...

Anyone have any ideas? I'm a newbie at this so it's probably some small
setting
which I'm not doing right. Let me know if you need more info.

Thanks,

Andrea

H. Peter Anvin

2003-Jun-15 18:20 UTC

head link

[syslinux] pxelinux bootup problems on EPIA-M

Andrea Rosso wrote:> 
> On the bootup screen I only see:
> 
> ...<EPIA startup stuff>
> 
Please don't delete
> CLIENT MAC ADDR: ........
> CLIENT IP: 192.168.2.100 MASK: 255.255.255.0 DHCP IP:192.168.2.1
> GATEWAY IP: 192.168.2.1
This looks like PXE 0.99-type messages.  Those PXE stacks are 
cantankerous at best.
> Auto-select:
> 	Network boot
> 
> BOOT SERVER IP: 192.168.2.1
> 
> And then it stops there...
> 
> Anyone have any ideas? I'm a newbie at this so it's probably some
small
> setting
> which I'm not doing right. Let me know if you need more info.
> 
> Thanks,
> 
> Andrea
> 
> 
> 
> 
> _______________________________________________
> 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.

Hugo Mills

2003-Jun-15 18:43 UTC

head link

[syslinux] pxelinux bootup problems on EPIA-M

On Sat, Jun 14, 2003 at 11:35:44PM -0700, Andrea Rosso
wrote:> I was wondering if anyone had a good dhcpd.conf and /tftpboot
> files for a EPIA-M motherboard with RedHat 9.0.... Or maybe
> just a configuration that works with the EPIA-M (doesn't matter
> which type of linux).
   Take a look at http://www.carfax.org.uk/docs/Netboot/ for my
(successful) experiences with an EPIA-M10000 board.

   Hugo.

-- 
=== Hugo Mills: hugo at ... carfax.org.uk | darksatanic.net | lug.org.uk ==  PGP
key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
        --- Great oxymorons of the world, no. 2: Common Sense ---

Andrea Rosso

2003-Jun-16 06:08 UTC

head link

[syslinux] pxelinux bootup problems on EPIA-M

Hugo,

I tried following your directions. Now my dhcpd.conf file looks like:


allow booting;
allow bootp;

# Standard configuration directives...

option domain-name "rossoweb.com";
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.2.1;
option domain-name-servers 192.168.2.1;
option routers 192.168.2.1;

ddns-update-style none;
subnet 192.168.2.0 netmask 255.255.255.0 {
 range 192.168.2.100 192.168.2.255;
}

option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;

# Group the PXE bootable hosts together
group {
        # PXE-specific configuration directives...
        option vendor-class-identifier "PXEClient";
        option vendor-encapsulated-options
09:0f:80:00:0c:4e:65:74:77:6f:72:6b:2
0:62:6f:6f:74:0a:07:00:50:72:6f:6d:70:74:06:01:02:08:03:80:00:00:47:04:80:00
:00:
00:ff;

        next-server 192.168.2.1;
        filename "pxelinux.0";
        option PXE.mtftp-ip 0.0.0.0;
        vendor-option-space PXE;

        # You need an entry like this for every host
        # unless you're using dynamic addresses
        host musica {
                        hardware ethernet 00:40:63:c4:ed:bb;
                        fixed-address 192.168.2.100;
                }
        }

Still no change in what happens... The tcpdump is the same. Seems like the
client does
not go on to ask for the config file. If it was trying to look for something
on another
port I should be able to see it in tcpdump I would think....

One thing I did notice is that if I remove the vendor-encapsulated-options
line the bootup
screen never displays these lines:

Auto-select:
	Network boot

BOOT SERVER IP: 192.168.2.1

things just stop right after the GATEWAY IP line. Does anyone know what this
line
contains?

Maybe I should try another version of PXELinux? BTW, I'm on a EPIA-ME6000
board
and not an M10000 but I assume they should be similar...

Thanks,

Andrea

-----Original Message-----
From: Hugo Ranger Mills [mailto:hrm at carfax.org.uk]On Behalf Of Hugo
Mills
Sent: Sunday, June 15, 2003 11:37 AM
To: Andrea Rosso
Cc: syslinux at zytor.com
Subject: Re: [syslinux] pxelinux bootup problems on EPIA-M



----=_NextPart_ST_11_37_06_Sunday_June_15_2003_15388
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sat, Jun 14, 2003 at 11:35:44PM -0700, Andrea Rosso
wrote:> I was wondering if anyone had a good dhcpd.conf and /tftpboot
> files for a EPIA-M motherboard with RedHat 9.0.... Or maybe
> just a configuration that works with the EPIA-M (doesn't matter
> which type of linux).
   Take a look at http://www.carfax.org.uk/docs/Netboot/ for my
(successful) experiences with an EPIA-M10000 board.

   Hugo.

--
=== Hugo Mills: hugo at ... carfax.org.uk | darksatanic.net | lug.org.uk ==  PGP
key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
        --- Great oxymorons of the world, no. 2: Common Sense ---

----=_NextPart_ST_11_37_06_Sunday_June_15_2003_15388
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD4DBQE+7LzZssJ7whwzWGARAqgwAJsGdq+ES9A0AFK4hGFWyYWS09QC8gCXbEqv
ZHqjfPwA7ad0+I2flVg+CQ==WTDd
-----END PGP SIGNATURE-----

----=_NextPart_ST_11_37_06_Sunday_June_15_2003_15388--

David Meltzer

2003-Jun-16 22:53 UTC

head link

[syslinux] pxelinux bootup problems on EPIA-M

look at this setting from that dhcpd.conf file

option domain-name-servers 192.168.2.1;

it should be 192.168.2.255 but it is 192.168.2.1

which is correct?


-----Original Message-----
From: H. Peter Anvin [mailto:hpa at zytor.com]
Sent: Monday, June 16, 2003 6:09 PM
To: asdffdsa at bellatlantic.net
Cc: syslinux at zytor.com
Subject: Re: [syslinux] pxelinux bootup problems on EPIA-M


David Meltzer wrote:> im a newbie,
> but should the broadcast-address be the same as the router and
domain-name-servers addresses
> 
Definitiely not.  broadcast-address = network-address | ~subnet_mask, in
this case 192.168.2.255.

	-hpa

H. Peter Anvin

2003-Jun-16 22:56 UTC

head link

[syslinux] pxelinux bootup problems on EPIA-M

David Meltzer wrote:> look at this setting from that dhcpd.conf file
> 
> option domain-name-servers 192.168.2.1;
> 
> it should be 192.168.2.255 but it is 192.168.2.1
> 
> which is correct?
> 
domain-name-servers should definitely not be the broadcast address...

	-hpa

Andrea Rosso

2003-Jun-21 06:38 UTC

head link

[syslinux] pxelinux bootup problems on EPIA-M

I tried downgrading to pxelinux 1.76 and it worked like a charm... downloads
the config, the Redhat image, loads it up, etc.

Any reason to try to get 2.x working? What are the differences? 

Thanks,

Andrea



-----Original Message-----
From: H. Peter Anvin [mailto:hpa at zytor.com]
Sent: Monday, June 16, 2003 10:05 AM
To: Andrea Rosso
Cc: syslinux at zytor.com
Subject: Re: [syslinux] pxelinux bootup problems on EPIA-M


Andrea Rosso wrote:> Oh, sorry... here is the missing top part:
> 
> Verifying DMI Pool Data ..............
> 
> Intel UNDI, PXE-2.0 (build 082)
> Copyright (C) 1997,1998,1999 Intel Corporation
> VIA VT6102 Rhine II Fast Ethernet Adapter		v2.13 (2202/08/09)
> 
> I assume by the PXE-2.0 message that this is a 2.0 version?
> 
Yes.  There has been a lot of people lately reporting they needed to
upgrade their EPIA motherboards, so you might look for a BIOS upgrade.

	-hpa

Apparently Analagous Threads

Search for more seemingly similar threads

Syslinux - Jun 2003 - pxelinux bootup problems on EPIA-M

[syslinux] pxelinux bootup problems on EPIA-M

[syslinux] pxelinux bootup problems on EPIA-M

[syslinux] pxelinux bootup problems on EPIA-M

[syslinux] pxelinux bootup problems on EPIA-M

[syslinux] pxelinux bootup problems on EPIA-M

[syslinux] pxelinux bootup problems on EPIA-M

[syslinux] pxelinux bootup problems on EPIA-M

Apparently Analagous Threads