iPXE discussion forum

Full Version: IPXE Error (Unsupported NIC/Intel)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
(2014-11-07 02:09)heckj Wrote: [ -> ]I just build a debug version off master that includes that patch and used it on a Intel S2600GZ server that's booting off an i350 nic, and it didn't seem to report the correct Mac.

The nic is reporting (via ethtool -i) that it's running firmware version 1.48.

The nic reported when it started PXE booting: 01:1E:67:87:CE:66
Then when it's doing the debug output (make DEBUG=pci,device,intel,undionly,undinet):

INTEL 0xc2a24 MAC+PHY reset (ctrl 001c0261)
INTEL 0xc2a24 has autoloaded MAC address 01:1e:67:87:ce:69
INTEL 0xc2a24 link status is 8028078c

From the (slightly blurry) video, it looks as though all ports of the i350 are enumerated, including the one with the 01:1e:67:87:ce:66 MAC address.

Quote:IPXE goes on to iterate through debug output related to PCI, finally hanging or (I'm guessing) crashing and resetting the machine.

The crash seems to happen when iPXE tries to load an UNDI ROM for some other NIC in the system. Could you try using bin/intel.pxe instead of bin/ipxe.pxe?

(2014-10-31 18:30)Fr3DBr Wrote: [ -> ]For win2k8 I get a red screen, with an offset/assembly error. And for win2k12 the screen just remain black and nothing happens anymore. (With Linux/CentOS, it works fine).

2K8 Error:
[Image: ib1kBfGUnf0e1y.png]

For the benefit of anyone reading this thread in future: this issue is now fixed (as of wimboot v2.4.0).

Problem 100% Fixed. Thanks for everything !!!
It is worth to remember, that we also had to start using the "kpxe" image of ipxe, instead of "kkpxe", it because for a few server revisions it works better and without issues.
Pages: 1 2
Reference URL's