Re: NIC identification with PXE?

I've used with success a driver made with this line:

make 
bin/undi--rtl8139--eepro100--3c90x--via-rhine--sis900--ns8390--prism2_plx.zpxe

it combines some native driver for the most common NICs and a UNDI 
driver, used when no native driver match the NIC...

Look at the readme inside
http://prdownloads.sourceforge.net/thinstation/BootPXE535.zip?download
to get some more detail... inside the .zip there is also a precompiled 
version

bye!

Paolo



John Connett ha scritto:
> Geert Stappers wrote:
> 
>> Looking forward to your report where you tell how you solved this
>>
>> (off-topic) problem.
>>
> My apologies for being off-topic and many thanks for the suggested
> solutions.
> 
> I will most probably use the undi.zpxe driver as suggested by Michael
> Brown <[email protected]>.  This appears to be the most general
> solution although it is dependant on the quality of the firmware in the
> PXE ROM.  His other suggestion for using Etherboot ROMs should also work
> but I would prefer a solution which works with unmodified firmware.
> 
> My second choice, as suggested by H. Peter Anvin <[email protected]>, would
> be to use an Etherboot binary which contains both drivers.
> 
> The approach suggested by Felix Möller <[email protected]> would work
> too as the NICs are from different manufacturers with different MAC
> address prefixes but would not discriminate between different models of
> NIC from the same manufacturer.
> 
> I may have misunderstood Geert Stappers <[email protected]>
> suggestion but there appears to be insufficient information in the
> incoming request to identify the NIC, vendor-class-identifier will only
> differentiate between PXEClient and Etherboot.  I had investigated this
> at some length before I posted my question.
> 
>>> -- 
>>> John
>>>
>>> PS. Once I have a solution to this problem I will be able to test
>>> Timothy Legge's Broadcom 5721 patch.  This is the onboard NIC for the
>>> Fujitsu-Siemens TX150 S3.
>>>
>>
>> Ah, a promise, that is good.
>>
> The undi.zpxe driver appears to work although the upload of the FreeBSD
> kernel file did not complete successfully.  I suspect this is a problem
> with the local tftp server implementation.  Ethereal shows that
> synchronisation between target and client was lost after about 1400
> blocks had been transfered.  Here is a hand copied version of the
> console output:
> 
> ------------------------------------------------------------------------
> BootManage UNDI, PXE-2.1 (build 084)
> BootManage PXE-2.1 PROM 1.1, BCM572X 1.10, SDK 3.0/004 (OEM73)
> Copyright (C) 1989,2004 bootix Technology GmbH, D-41466 Neuss.
> PXE Software Copyright (C) 1997, 1998, 1999, 2000 Intel Corporation.
> Licensed to FSC GmbH
> 
> CLIENT MAC ADDR: 00 30 05 83 54 C5  GUID: 
> 00000000-0000-0000-0000-0030058354C5
> CLIENT IP: 10.4.2.46  MASK: 255.255.255.0  DHCP ID: 10.4.2.152
> PXE->EB !PXE 9551:0040 9551:00D6 9551:4B4D 9086:4CB0 0000 0000 0000 0269 ok
> Etherboot 5.4.0 (GPL) http://etherboot.org
> Drivers: UNDI UNDI   Images: ELF FreeBSD Multiboot a.out PXE   Exports: PXE
> Protocols: DHCP TFTP
> Relocating _text from: [00086c10,0009a0e0) to [3fd6cb30,3f6f0000)
> Probing pci nic...
> [UNDI]Hunting for PnP BIOS...found $PNP at f000:6f80...ok
> Hunting for pixies...none found
> Hunting for ROMs...found 55AA at 000ca800...PCI:1044:a501...not me 
> (14e4:1659)
> ...found 55AA at 000c9800...PCI:14e4:1659...ok
> ROM contains BootManage PXE, Slot 0500 by bootix Technology GmbH
> Located UNDI ROM supporting revision 2.1.0
> Installing UNDI driver code to 94c0:0000, data at 8fc0:0000
> UNDI driver created a pixie at 94c0:0040...ok
> API 94c0:00d6 St 8ec0:0800 UD 8fc0:4cb0 UC 94c0:4b4d BD 0000:3bc0 BC 
> 0000:7c98
> Initializing UNDI driver.  Please wait...
> Initialized UNDI NIC with IO 0x0000, IRQ 11, MAC 00:30:05:03:54:C5
> NDIS type DIX+802.3 interface at 100 Mbps
> Searching for server (DHCP)...\
> Me: 10.4.2.46, DHCP: 10.4.2.152, TFTP: 10.4.2.152
> Loading 10.4.2.152:kernel (ELF/FreeBSD)...-
> ------------------------------------------------------------------------
> 
> I have also tried the tg3.zpxe driver with the patch (tg3.diff) which
> was attached to the message from Timothy Legge <[email protected]> dated
> 06/04/05.  This loops outputting the following messages on the console:
> ------------------------------------------------------------------------
> Probing isa nic...
> <sleep>
> Probing pci nic...
> [tg3-5721]PCI_CHIP_REV_ID: 0x4101
> phy probe failed, err -2
> Problem fetching invariants of chip, aborting.
> ------------------------------------------------------------------------
> 
> Thanks again for the useful suggestions.  I hope the output above will
> be of some use.  Please let me know if there are any additional tests
> you would like me to run on the tg3 driver / Broadcom 5721.
> 
> Regards
> -- 
> John
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> Etherboot-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/etherboot-developers
> 

-- 
Paolo Salvan
_______________________________
X v i s i o n
Via Vigonovese 123A
35127 - Padova - Italy
+39 049 8709427 tel
+39 049 8709426 fax
www.xvision.it


-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005