<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>On 15-03-2019 14:50, Quinn Plattel wrote:<br>
</p>
<blockquote type="cite"
cite="mid:CALu+JK0YAmzTDPAy-G6-gYPi3c2FAQRpHD0VNdwnGUqdMZh_Lg@mail.gmail.com">On
Thu, Mar 14, 2019 at 12:28 AM Michael Brown <<a
href="mailto:mcb30@ipxe.org" moz-do-not-send="true">mcb30@ipxe.org</a>>
wrote:<br>
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">On 13/03/2019 17:26,
Quinn Plattel wrote:<br>
> Thanks for the quick response. Here is the banner
message:<br>
> <br>
> iPXE (<a href="http://ipxe.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">http://ipxe.org</a>)
04:04.0 6800 PCI3.00 PnP PMM+00106D80+00000000 CE00<br>
> Press Ctrl-B to configure iPXE (PCI 04:04.0)...<br>
<br>
Thanks; that explains the root cause of the problem.<br>
<br>
The BIOS is allocating a PMM block at 0x106d80 to hold a
copy of the raw <br>
ROM image, but failing the second PMM allocation for the
temporary <br>
decompression area.<br>
<br>
The default temporary decompression area used by iPXE if PMM
allocation <br>
fails is at 0x100000 (i.e. the start of high memory). The
decompressed <br>
ROM image is therefore overwriting the copy of the raw ROM
image, which <br>
leads to the CRC32 checksum failure.<br>
<br>
What banner line did you get on this system with the
(working) DFE-530TX?<br>
</blockquote>
</div>
<br>
<div>I did another type of test now:</div>
<div><br>
</div>
<div>I disabled AUTOBOOT_ROM_FILTER in config/general.h and
recompiled the 905b rom file.</div>
<div>I then flashed it to the 29C512 chip but this time I
installed this chip into the DFE-530TX D-Link card. I put
both cards into the same machine with the 3com card installed
without a bootrom chip. When I started the machine, the 3com
code in the d-link card executed successfully this time and
found the 3Com pci card and did a successful dhcp connection.
Interestingly both roms report 00000000 on the second address
of there banner pages.</div>
<br>
</div>
</blockquote>
<p>I wouldn't be surprised if we are dealing with flacky BIOS.</p>
<p>Testing the NIC in a totaly different computer could confirm that
gut feeling.</p>
<p><br>
</p>
<p>Cheers</p>
<p>Geert Stappers</p>
<p>DevOps Engineer at Hendrikx ITC<br>
</p>
</body>
</html>