[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-poweredge
Subject:    RE: PXE w/ Broadcom NIC
From:       "Mann, Andrew" <amann () ea ! com>
Date:       2006-10-31 4:09:17
Message-ID: 154149F9739F2E4E8009B613329CF61C05603469 () EAHQ-CSMB9 ! rws ! ad ! ea ! com
[Download RAW message or body]

	I PXE booted a pair of 2950s which have Broadcom NICs a few
weeks ago without seeing this, and without any issues.  Does this only
apply to some of the Dell servers?

Andrew

-----Original Message-----
From: linux-poweredge-bounces@dell.com
[mailto:linux-poweredge-bounces@dell.com] On Behalf Of Richard Krill
Sent: Thursday, October 19, 2006 12:01 PM
To: linux-poweredge@dell.com
Subject: PXE w/ Broadcom NIC

There's a solution to the PXE-problem where a hexadecimal ff00 is added
to the filename.

Short description of the problem:

Want to boot via DHCP (PXE on the client) and TFTP.
Have bootfilename (for instance PXELINUX.0), and put this filename in
dhcp-options of the DHCP server.
The client, however, does not receive "pxelinux.0" but
"pxelinux.M-^?" (tcpdump tells us), and cannot find the file on the TFTP
server.

A pragmatic workaround for the problem would be (and works, I've
tested):
rename the file on the TFTP server as the same:
Command:

cp pxelinux.0 `echo -e "pxelinux.0\xff\x00"
This looks in a ls as pxelinux.0M-^?

The TFTP server can than find the file, and the client will boot.

RK

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
[prev in list] [next in list] [prev in thread] [next in thread]