Realtek 8111\8168 & undionly.kpxe -> hangs on Initialising Devices...

I haven’t seen any other forum posts on this exact issue but I don’t like what I read when I Google it. Has anyone used a different file/method to get this NIC successfully working in 1.0.0? It’s hard to believe that there isn’t a solution for this…the Realtek GbE family has a pretty pervasive presence to my knowledge.

I have the same issue on the Realtek 8168. But this is all under hyper-v. On my old pc, with intel NIC, everything worked fine, but now on my new PC with the Realtek 8168 I am running FOG as a virtual machine and a PXE client on. All on hyper-v. It looks like hyper-v inherits the properties of the host system, even with private networks. When using EFI it all works, just not on a legacy NIC.

@junkhacker This was exactly my issue. All I had to do was boot the offending laptops into Windows, shut down, and reboot. The “Initialising devices” hang was gone. My thanks, more than 3 years after the original post!

Damn. I have just tried a different motherboard using realtec NIC hardware…FFS it wont even SEE the fog server now.
Is there a way to simply:
[LIST=1]
[]download the hardware vendor driver (what driver would that be??)
[]inject that driver into Fog somewhere (where?)
[/LIST]

if not, i need to do my work-around that works for the new Fog:

put the new hard drive into an OLD pc.
fog that hdd.
put that HDD into the new pc i WANT to work.
run

Then move the undionly.kpxe file to undionly.kpxe_MAIN
[code]mv /tftpboot/undionly.kpxe /tftpboot/undionly.kpxe_MAIN[/code]

Then just create symbolic links to undionly.kpxe from the file you want to try out. For example:
[code]ln -s /tftpboot/undionly.kkpxe /tftpboot/undionly.kpxe[/code]

You don’t have to keep rebooting services to test it. When you’re ready to try another file you simply:
[code]rm /tftpboot/undionly.kpxe; ln -s /tftpboot/<NEWFILETOTEST> /tftpboot/undionly.kpxe[/code][/quote]
When I try this im getting error 404 not found on the wget stage

Wish I could say the same.
Im using an AsRock MB with NIC Chipset: Qualcomm® Atheros® AR8171
It does not progress past the issues others mentioned already: ipxe initialising devices…

I can soft reset it.
iPXE works on other pcs.

The weird thing is, i was able to INITIALLY fog this pc. and now it wont log on to fog.
gawdammit some days i want to firebomb technology and software with as dirty-a-nuke as 3rd-world money can buy.

Am using 1.1.2 Fog as well. i did download the files mentioned here as well, and FTP uploaded them to my fog server’s tftpboot dir. I even restarted tft service on the fog server. and rebooted. and cried…i nearly hit my screen but that costs moeny to replace, so more work. sigh. what a run a round. And yes, i have googled till i have bue brass monkeyballs.

We’ve updated the BIOS for our problematic device (Lenovo Thincenter E72 3493-KAG) and now the PXE boot goes a little further

With :
[LIST]
[]ipxe.kpxe : it goes further, gets a Configuring line, display a timeout i got on camera then loads windows
[]undionly.kpxe : it goes further, gets a Configuring line but then quickly the screen goes black and it load Windows
[]undionly.kkpxe : same
[]undionly.kpxe.INTEL : same
[*]undionly.pxe : bootloop
[/LIST]
[media=youtube]e2ohnkfJhGU[/media]