[syslinux] pxelinux bootup problems on EPIA-M

David Meltzer asdffdsa at bellatlantic.net
Mon Jun 16 14:59:40 PDT 2003


im a newbie,
but should the broadcast-address be the same as the router and domain-name-servers addresses

thanks,
dave


-----Original Message-----
From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com]On
Behalf Of Andrea Rosso
Sent: Monday, June 16, 2003 2:09 AM
To: Hugo Mills
Cc: syslinux at zytor.com
Subject: RE: [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--

_______________________________________________
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