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.
philippe.willems last edited by
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.
eroneree last edited by
@george1421 Running Fog 1.4.4. They mostly work correctly but once in a while I get the “Initialising devices” hang.
@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 last edited by
@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!
[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.
whoa whoa whoa!!!
The latest issues was a gigabit cable not being compatible with our network…carry on citizens!
(but initial problem stands lol)
[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:
download the hardware vendor driver (what driver would that be??)
inject that driver into Fog somewhere (where?)
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.
Seems a bit painful but it works at least lol.
Nope did exactly the same, I can click on the link no issue and it comes up in firefox
i’m guessing it’s the https:// try http://
[quote=“Tom Elliott, post: 30923, member: 7271”]It sounds like you’re doing it “right” persay, but doing a lot of extra work.
Really, you can “cheatify it” as such.
No need to stop tftp-hpa or tftpd-hpa or isc-dhcp-server
Doing the first few steps just as you did:
[code]mv /tftpboot /tftpboot.bak
wget -r ftp https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/*
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
then try the version in the svn trunk, they’ve been updated since 1.2.0 came out
Wont have any luck with 1.2.0 either as I’ve just upgraded to the same and having same issue
you may have better luck if you upgrade to 1.2.0
the network boot files have been updated
[quote=“andjjru, post: 28706, member: 575”]After much trial and error, this one is working well for me.
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.
Glad others could sort this!
netbootdisk last edited by
Gigabyte [URL=‘http://www.gigabyte.com.au/products/product-page.aspx?pid=3475#ov’]GA-880GM-UD2H[/URL] motherboard with Realtek 8111 also suffers this problem.
Unfortunately the machine is in another city so I can’t test further yet.
I made a video tutorial for USB Boot Drive creation and BIOS Update then PXE Boot with FOG 1.1.1
Enjoy the show !
I’m so stupid.
I FORGOT TO RE-ADD THE DEFAULT.IPXE FILE SO IT CANNOT BOOT
It’s now loading properly
To conclude :
- FOG Fresh install of 1.1.1
- Use the latest trunk files that Tom gave/ Use my command script to retrieve them in /tftpboot
- chown them with the right user:group (fog:root)
- recreate the Default.ipxe file
- Flash your BIOS with latest update so it can properly boot up iPxe (for Lenovo 3493-KAG : [url]http://support.lenovo.com/en_GB/downloads/default.page?selector=expand[/url])
- File to use for Realtek 8111 network card is undionly.kpxe provided by Tom
Thanks Tom, Junkhacker, andjjru and tamatech for your support
We’ve updated the BIOS for our problematic device (Lenovo Thincenter E72 3493-KAG) and now the PXE boot goes a little further
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
[url="/_imported_xf_attachments/1/1027_2014-06-20 15.00.44.jpg?:"]2014-06-20 15.00.44.jpg[/url]
Your wget command didn’t work for me, I did
[CODE]wget -i listdownload.txt[/CODE]
with that list
I’m trying with symbolic links now.
Edit : got that screen with undionly.kpxe and undionly.kkpxe
[url="/_imported_xf_attachments/1/1026_2014-06-20 14.20.43.jpg?:"]2014-06-20 14.20.43.jpg[/url]