[syslinux] 3.86-pre1 gpxelinux.0 SIS900 long boot time / fails to boot / no entries in tftp server log

Andrew Stuart andrew at shopcusa.com
Tue Mar 16 16:12:00 PDT 2010


Okay guys, This is separate from my last few messages. Along with those 
attempts, I decided to migrate from pxelinux.0 to gpxelinux.0 in my 
existing setup. Admittedly I haven't tried previous gpxelinux.0's but I 
am willing to if someone thinks it would be useful. Everything works as 
expected with pxelinux.0 of the same version.

With gpxelinux.0:

TFTP Prefix:
Trying to load: pxelinux.cfg/fffff- ..
(two minutes delay)
Trying to load: pxelinux.cfg/01-00...
(I believe also two minutes delay)
Trying to load: pxelinux.cfg/C0...
(same..)
...
Trying to load: pxelinux.cfg/default
(wait....)
Unable to locate configuration file

Boot failed: press a key to retry, or wait for reset...
........._

Server Side:
Mar 16 15:33:14 scrappy in.tftpd[60494]: RRQ from 192.168.1.198 filename 
gpxelinux.0
Mar 16 15:33:14 scrappy in.tftpd[60494]: tftp: client does not accept 
options
Mar 16 15:33:14 scrappy in.tftpd[60495]: RRQ from 192.168.1.198 filename 
gpxelinux.0
--snip next client/test here--


With pxelinux.0, I don't even see it go by, it trys, and instantly my 
menu.c32 pops up.

Server side:
Mar 16 15:32:21 scrappy in.tftpd[60444]: RRQ from 192.168.1.198 filename 
pxelinux.0
Mar 16 15:32:21 scrappy in.tftpd[60444]: tftp: client does not accept 
options
Mar 16 15:32:21 scrappy in.tftpd[60445]: RRQ from 192.168.1.198 filename 
pxelinux.0
Mar 16 15:32:21 scrappy in.tftpd[60446]: RRQ from 192.168.1.198 filename 
pxelinux.cfg/ffffffff-ffff-ffff-ffff-ffffffffffff
--snip all normal responses here --
Mar 16 15:32:21 scrappy in.tftpd[60456]: RRQ from 192.168.1.198 filename 
pxelinux.cfg/default
Mar 16 15:32:21 scrappy in.tftpd[60457]: RRQ from 192.168.1.198 filename 
menu.c32

I thought I read a message about someone else having a similar complaint 
a while back, but I couldn't find it. Any ideas? (Yes, I know.. replace 
the nic, sadly that isn't an option, also setting custom rules in dhcp 
isn't ideal, as I get a variety of these at different times..)


-Andrew




More information about the Syslinux mailing list