iPXE discussion forum

Full Version: ipxe does not boot on a Realtek PCIe GBE
You're currently viewing a stripped down version of our content. View the full version with proper formatting.

I use iPXE hosted on a linux server with tftp and it works fine on many pc to use a iSCSI server to boot Windows 7 or 8.1 from SAN.

But on a old ASUS P7P55D with a Realtek PCIe GBE, iPXE stops at "initialisation...". It stops and nothing append even after 10 minutes.

What can I do to fix this?

From motherboard documentation, this LAN adapter is:
Realtek 8112L Gigabit LAN controller featuring AI NET2

Then does not seams supported in this list http://ipxe.org/appnote/hardware_drivers Sad even if it's from 2009.

Solved by using ipxe.pxe, but windows does not like the driver and does not install on SAN.
I'm guessing the PCI ID of this device is 10ec:8168 ? (which have a native driver in ipxe) where you using undionly.kpxe when it didn't work?
Id of the device is PCI\VEN_8086&DEV_3B50&SUBSYS_83831043&REV_05\3&11583659&0&E7

undionly.kpxe hangs at "initialization of the device..." message or kind of message, ipxe.pxe works.

After I patched all 3 .wim (PE, boot and install), Windows 10 did begin to install on SAN but after reboot it does an "inaccessible boot device" error I could not solve so I gave up with this spywareOS and did same with Windows 7 which did install properly on SAN.
By the way, any of Win7, 8 or 10 all require .wim patching to add latest version of LAN drivers to be able to install them on a SAN device on various PC I did try with different NIC or they all end up with a "signature of xxx.sys does not match..." error or "inaccessible boot device" after the first reboot but this is nothing related with iPXE.
(2016-02-17 18:57)Steph01 Wrote: [ -> ]PCI\VEN_8086&DEV_3B50

Hmm, 8086 is Intel what you refer to is actually a 8086:3b50 PCI Express Root Port and not a NIC

There is other posts talking about Windows iSCSI, Windows 10 does not work to install without a lot of "hacking".
Oh!! my mistake.
The Nic is PCI\VEN_10EC&DEV_8168&SUBSYS_83A31043&REV_03\4&61613AC&0&00E7 as you posted.
I did not copy the proper device, my bad.
You can try building the iPXE binary with debug for undi code enabled:
make bin/undionly.kpxe DEBUG=undi EMBED=...
Reference URL's