Mailing List Archive: Intel Boot Agent 4.0.19

Intel Boot Agent 4.0.19

May 2, 2002, 1:13 PM

Post #1 of 6 (2957 views)

This is a multi-part message in MIME format.

------=_NextPart_000_0000_01C1F1FC.A3D80360
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

First, THANKS! The SYSLINUX/PXELINUX s/w and docs are great. I have been
able to set up a working server for PXE boot in very little time, using our
existing Win2k DHCP server and a Red Hat 7.2 Linux server for tftp, etc...
It took very little time (compared to an earlier effort 4 months ago.....)
and the pxelinux/menu/memdisk environment is great for us.

The environment seems to support PXE clients up to and including Intel Boot
Agent 4.0.17. But most of the new systems we are getting use IBA 4.0.19 .
On any of the older clients, i can see the atftpd action in
/var/log/messages - pxelinux.0 goes out, it asks for
pxelinux.cfg/xxxxxxxx....pxelinux.cfg/x, then pxelinux.cfg/default. Then I
can see the display file specified there go out. Finally I see memdisk and
an image . Perfect. But with the 4.0.19 client, I see pxelinux.0 go out.
Then atftpd says it serving - nothing. Which of course, fails - it
retries 4 times, and gives up. The server is still OK, older clients can
continue to connect. But the 4.0.19 client just sits there..... (It has,
at that point displayed the IP parameters it got from DHCP, it displays
TFTP, which then gets erased, and then nothing further happens.)

My guess is that nothing is wrong with pxelinux, but rather that intel now
requires more info from DHCP or something. Nice of them to break a working
solution.... But I am hoping that you have at least come across this issue
and have found a solution. Intel is usually pretty good at documenting
revisions, but I haven't found that for IBA. Maybe you have and know the
answer.

Thanks in advance for any help you can provide!

Keith Josephson

--------------------
Keith Josephson
ION Computer Systems® Inc.
30 Oser Avenue
Hauppauge, NY 11788

(631) 630-0600 Ext.222

kjosephson@ioncomputer.com
<http://server.ioncomputer.com/> http://server.ioncomputer.com/
-------------------- <?xml:namespace prefix = o ns =
"urn:schemas-microsoft-com:office:office" />

------=_NextPart_000_0000_01C1F1FC.A3D80360
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DWindows-1252">

<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D353280121-02052002><FONT size=3D2>First, =
THANKS!  The=20
SYSLINUX/PXELINUX s/w and docs are great.  I have been able to set =
up a=20
working server for PXE boot in very little time, using our existing =
Win2k DHCP=20
server and a Red Hat 7.2 Linux server for tftp, etc...  It took =
very little=20
time (compared to an earlier effort 4 months ago.....) and the=20
pxelinux/menu/memdisk environment is great for us.</FONT></SPAN></DIV>
<DIV><SPAN class=3D353280121-02052002><FONT =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D353280121-02052002><FONT size=3D2>The environment =
seems to=20
support PXE clients up to and including Intel Boot Agent 4.0.17.  =
But most=20
of the new systems we are getting use IBA 4.0.19 .  On any of the =
older=20
clients, i can see the atftpd action in /var/log/messages - pxelinux.0 =
goes out,=20
it asks for pxelinux.cfg/xxxxxxxx....pxelinux.cfg/x, then=20
pxelinux.cfg/default.  Then I can see the display file specified =
there go=20
out.  Finally I see memdisk and an image .  Perfect.  But =
with=20
the 4.0.19 client, I see pxelinux.0 go out.  Then atftpd says it=20
serving   - nothing.  Which of course, fails - it retries =
4=20
times, and gives up.  The server is still OK, older clients can =
continue to=20
connect.  But the 4.0.19 client just sits there.....  (It has, =
at that=20
point displayed the IP parameters it got from DHCP, it displays TFTP, =
which then=20
gets erased, and then nothing further happens.)</FONT></SPAN></DIV>
<DIV><SPAN class=3D353280121-02052002><FONT =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D353280121-02052002><FONT size=3D2>My guess is that =
nothing is=20
wrong with pxelinux, but rather that intel now requires more info from =
DHCP or=20
something.  Nice of them to break a working solution....  But =
I am=20
hoping that you have at least come across this issue and have found a=20
solution.  Intel is usually pretty good at documenting revisions, =
but I=20
haven't found that for IBA.  Maybe you have and know the=20
answer.</FONT></SPAN></DIV>
<DIV><SPAN class=3D353280121-02052002><FONT =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D353280121-02052002><FONT size=3D2>Thanks in advance =
for any help=20
you can provide!</FONT></SPAN></DIV>
<DIV><SPAN class=3D353280121-02052002><FONT =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D353280121-02052002><FONT size=3D2>Keith=20
Josephson</FONT></SPAN></DIV>
<DIV><SPAN class=3D353280121-02052002></SPAN><SPAN =
class=3D353280121-02052002><FONT=20
size=3D2></FONT></SPAN> </DIV>
<DIV class=3DSection1>
<P><SPAN=20
style=3D"COLOR: navy; FONT-FAMILY: 'Courier =
New'">═════════&#95=
52;══════════=
<BR> </SPAN><STRONG><SPAN=20
style=3D"FONT-SIZE: 13.5pt; COLOR: navy; FONT-FAMILY: 'Courier =
New'">Keith=20
Josephson</SPAN></STRONG><SPAN=20
style=3D"COLOR: navy; FONT-FAMILY: 'Courier New'"><SPAN=20
style=3D"mso-spacerun: =
yes">           &n=
bsp;   =20
</SPAN><BR> ION Computer Systems<SUP>=AE</SUP> Inc.<SPAN=20
style=3D"mso-spacerun: yes">     </SPAN><BR> 30 =
Oser=20
Avenue<SPAN=20
style=3D"mso-spacerun: =
yes">           &n=
bsp;    =20
</SPAN><BR> Hauppauge, NY 11788<SPAN=20
style=3D"mso-spacerun: =
yes">           =20
</SPAN><BR><SPAN=20
style=3D"mso-spacerun: =
yes">           &n=
bsp;           &nb=
sp;       =20
</SPAN><BR> (631) 630-0600 Ext.222<SPAN=20
style=3D"mso-spacerun: =
yes">        =20
</SPAN><BR><SPAN=20
style=3D"mso-spacerun: =
yes">           &n=
bsp;           &nb=
sp;       =20
</SPAN><BR> <U><A=20
href=3D"mailto:kjosephson@ioncomputer.com">kjosephson@ioncomputer.com</A>=
</U><SPAN=20
style=3D"mso-spacerun: yes">     =
</SPAN><BR> <U><A=20
href=3D"http://server.ioncomputer.com/" target=3D_blank><SPAN=20
style=3D"COLOR: navy">http://server.ioncomputer.com/</SPAN></A></U>=20
<BR>═════════&#9552=
;══════════</=
SPAN><SPAN=20
style=3D"COLOR: navy; FONT-FAMILY: 'Lucida =
Console'"> <?xml:namespace prefix=20
=3D o ns =3D "urn:schemas-microsoft-com:office:office"=20
/><o:p></o:p></SPAN></P></DIV>
<DIV> </DIV></BODY></HTML>

------=_NextPart_000_0000_01C1F1FC.A3D80360--

Intel Boot Agent 4.0.19 [ In reply to ]

hpa at zytor

May 6, 2002, 1:53 PM

Post #2 of 6 (2882 views)

Permalink

Keith Josephson wrote:
> First, THANKS! The SYSLINUX/PXELINUX s/w and docs are great. I have
> been able to set up a working server for PXE boot in very little time,
> using our existing Win2k DHCP server and a Red Hat 7.2 Linux server for
> tftp, etc... It took very little time (compared to an earlier effort 4
> months ago.....) and the pxelinux/menu/memdisk environment is great for us.
>
> The environment seems to support PXE clients up to and including Intel
> Boot Agent 4.0.17. But most of the new systems we are getting use IBA
> 4.0.19 . On any of the older clients, i can see the atftpd action in
> /var/log/messages - pxelinux.0 goes out, it asks for
> pxelinux.cfg/xxxxxxxx....pxelinux.cfg/x, then pxelinux.cfg/default.
> Then I can see the display file specified there go out. Finally I see
> memdisk and an image . Perfect. But with the 4.0.19 client, I see
> pxelinux.0 go out. Then atftpd says it serving - nothing. Which of
> course, fails - it retries 4 times, and gives up. The server is still
> OK, older clients can continue to connect. But the 4.0.19 client just
> sits there..... (It has, at that point displayed the IP parameters it
> got from DHCP, it displays TFTP, which then gets erased, and then
> nothing further happens.)
>
> My guess is that nothing is wrong with pxelinux, but rather that intel
> now requires more info from DHCP or something. Nice of them to break a
> working solution.... But I am hoping that you have at least come across
> this issue and have found a solution. Intel is usually pretty good at
> documenting revisions, but I haven't found that for IBA. Maybe you have
> and know the answer.
>

First of all, have you complained to Intel? Seriously, if people don't
complain, vendors will continue their "if it works on M$, ship it" type
behaviour which seems to have become the standard in the firmware
industry over the last few years.

Second, please don't post HTML to this list.

-hpa

Intel Boot Agent 4.0.19 [ In reply to ]

hpa at zytor

May 7, 2002, 11:45 AM

Post #3 of 6 (2901 views)

Permalink

H. Peter Anvin wrote:
> Keith Josephson wrote:
>
>>First, THANKS! The SYSLINUX/PXELINUX s/w and docs are great. I have
>>been able to set up a working server for PXE boot in very little time,
>>using our existing Win2k DHCP server and a Red Hat 7.2 Linux server for
>>tftp, etc... It took very little time (compared to an earlier effort 4
>>months ago.....) and the pxelinux/menu/memdisk environment is great for us.
>>
>>The environment seems to support PXE clients up to and including Intel
>>Boot Agent 4.0.17. But most of the new systems we are getting use IBA
>>4.0.19 . On any of the older clients, i can see the atftpd action in
>>/var/log/messages - pxelinux.0 goes out, it asks for
>>pxelinux.cfg/xxxxxxxx....pxelinux.cfg/x, then pxelinux.cfg/default.
>>Then I can see the display file specified there go out. Finally I see
>>memdisk and an image . Perfect. But with the 4.0.19 client, I see
>>pxelinux.0 go out. Then atftpd says it serving - nothing. Which of
>>course, fails - it retries 4 times, and gives up. The server is still
>>OK, older clients can continue to connect. But the 4.0.19 client just
>>sits there..... (It has, at that point displayed the IP parameters it
>>got from DHCP, it displays TFTP, which then gets erased, and then
>>nothing further happens.)
>>

Could you please describe how the DHCP server is set up?

-hpa

Intel Boot Agent 4.0.19 [ In reply to ]

jsiemes at web

May 8, 2002, 2:01 AM

Post #4 of 6 (2887 views)

Permalink

Hi,

>The environment seems to support PXE clients up to and including Intel >Boot Agent 4.0.17. But most
> of the new systems we are getting use IBA 4.0.19 . On any >of the older clients, i can see the atftpd
> action in /var/log/messages - pxelinux.0 goes out, it asks >for pxelinux.cfg/xxxxxxxx....pxelinux.cfg/x,
> then pxelinux.cfg/default. Then I can see the display file >specified there go out. Finally I see
> memdisk and an image . Perfect. But with the 4.0.19 >lient, I see pxelinux.0 go out.

I have a system (IBM Thinkpad T30) with IBA 4.0.21 - works.
Could you try this version?

Regards,

Josef

________________________________________________________________
Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr!
Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13

Intel Boot Agent 4.0.19 [ In reply to ]

hpa at zytor

May 8, 2002, 8:16 AM

Post #5 of 6 (2882 views)

Permalink

wulu wrote:
> Hi,
>
> I had the same problem with an HP VL420 Desktop (onboard Pro100
> with IBA 4.0.19).
> Yesterday they released a new bios which pushes the IBA to version
> 4.1.01 - now everything works fine again :)
>

Okay, I'll add IBA 4.0.19 to the web page as a possibly broken version,
with the note that 4.0.17, 4.0.19, and 4.1.01 seem to work fine.

-hpa

Intel Boot Agent 4.0.19 [ In reply to ]

wulu at wulu

May 8, 2002, 11:56 AM

Post #6 of 6 (2902 views)

Permalink

Hi,

I had the same problem with an HP VL420 Desktop (onboard Pro100
with IBA 4.0.19).
Yesterday they released a new bios which pushes the IBA to version
4.1.01 - now everything works fine again :)

Ralf

On Wed, 8 May 2002 12:01:36 +0200, jsiemes@web.de said:
>Hi,
>
>>The environment seems to support PXE clients up to and including Intel >Boot Agent 4.0.17. But most
>> of the new systems we are getting use IBA 4.0.19 . On any >of the older clients, i can see the atftpd
>> action in /var/log/messages - pxelinux.0 goes out, it asks >for pxelinux.cfg/xxxxxxxx....pxelinux.cfg/x,
>> then pxelinux.cfg/default. Then I can see the display file >specified there go out. Finally I see
>> memdisk and an image . Perfect. But with the 4.0.19 >lient, I see pxelinux.0 go out.
>
>I have a system (IBM Thinkpad T30) with IBA 4.0.21 - works.
>Could you try this version?
>
>Regards,
>
>Josef
>
>________________________________________________________________
>Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr!
>Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13
>
>
>_______________________________________________
>SYSLINUX mailing list
>Submissions to SYSLINUX@zytor.com
>Unsubscribe or set options at:
>http://www.zytor.com/mailman/listinfo/syslinux
>
>