Issue with BCM 57712 - Printable Version +- iPXE discussion forum (https://forum.ipxe.org) +-- Forum: iPXE user forums (/forumdisplay.php?fid=1) +--- Forum: General (/forumdisplay.php?fid=2) +--- Thread: Issue with BCM 57712 (/showthread.php?tid=7400) |
Issue with BCM 57712 - nhathaitrieu6 - 2014-07-12 08:46 PCI-e 10GbE SFP+ Dual Port Adapter: undionly.kpxe-> ipxe.pxe -> When initializing, getting an error: iPXE initialising devices... Try to free Memory without Signature I think this was covered on the mailing the list back in August fairly thoroughly; are we still waiting for a new BNX2 driver? I was thinking about building a Whitelist/Blacklist to undionly.kpxe to bypass known broken/ missing NIC drivers preventing loading ipxe.pxe and hitting the next step in the chain, but was unsure about what options there were in iPXE to determine a NIC hardware type in the undionly.kpxe environment - the ${product} variable would probably be close enough with Enterprise-class hardware and LoMs. I might have a script to share before to long... RE: Issue with BCM 57712 - robinsmidsrod - 2015-03-09 12:17 Yes, the bnx2 driver is still not merged to mainline, because of lack of time to review/test the code. Using a ${product} or some of the other information from either SMBIOS or PCI configuration space to create a whitelist/blacklist seems appropriate. |