Hi Michael, Here are the BIOS messages for the D-Link DFE-530TX card which is working fine in the same system:
iPXE (http://ipxe.org) 05:00.0 6800 PCI3.00 PnP PMM+00106D80+00000000 CE80 Press Ctrl-B to configure iPXE (PCI 05:00.0)... iPXE 1.0.0+ (b6ffe) -- Open Source Network Boot Firmware -- http://ipxe.org Features: DNS HTTP TFTP ELF MBOOT PXE bzImage Menu PXEXT net0: 00:05:5d:dd:c6:84 using dlink-530tx on 0000:05:00.0 (open) [Link:up, TX:0 TXE:0 RX:0 RXE:0] Configuring (net0 00:05:5d:dd:c6:84)......... ok net0: 10.0.0.136/255.255.255.0 gw 10.0.0.254 Next server: 10.0.0.254 etc.... Quinn On Thu, Mar 14, 2019 at 12:28 AM Michael Brown <mc...@ipxe.org> wrote: > On 13/03/2019 17:26, Quinn Plattel wrote: > > Thanks for the quick response. Here is the banner message: > > > > iPXE (http://ipxe.org) 04:04.0 6800 PCI3.00 PnP PMM+00106D80+00000000 > CE00 > > Press Ctrl-B to configure iPXE (PCI 04:04.0)... > > Thanks; that explains the root cause of the problem. > > The BIOS is allocating a PMM block at 0x106d80 to hold a copy of the raw > ROM image, but failing the second PMM allocation for the temporary > decompression area. > > The default temporary decompression area used by iPXE if PMM allocation > fails is at 0x100000 (i.e. the start of high memory). The decompressed > ROM image is therefore overwriting the copy of the raw ROM image, which > leads to the CRC32 checksum failure. > > What banner line did you get on this system with the (working) DFE-530TX? > > Thanks, > > Michael > -- Best regards/Ystävällisin terveisin/Med venlig hilsen, Quinn Plattel
_______________________________________________ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel