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

[Junkhacker]

i’m guessing it’s the https:// try http://

[Excel Group]

Nope did exactly the same, I can click on the link no issue and it comes up in firefox

[drjam]

[quote=“Excel Group, post: 35168, member: 18178”]Nope [/quote]

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

Seems a bit painful but it works at least lol.

[drjam]

whoa whoa whoa!!!
The latest issues was a gigabit cable not being compatible with our network…carry on citizens!
(but initial problem stands lol)

[Junkhacker]

[quote=“Excel Group, post: 35168, member: 18178”]Nope did exactly the same, I can click on the link no issue and it comes up in firefox[/quote]

then download it with firefox and upload it to the server. sorry if the instructions i gave were inaccurate, but i just copied/pasted them from another thread on the forum.

[eroneree]

@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!

[george1421]

@eroneree What version of fog are you running? I understand the mechanics behind why that worked, but 3 years later those (pita) Realtek nics should be working correctly.

[eroneree]

@george1421 Running Fog 1.4.4. They mostly work correctly but once in a while I get the “Initialising devices” hang.

[philippe.willems]

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.