Realtek 8111\8168 & undionly.kpxe -> hangs on Initialising Devices...
-
[SIZE=3][quote=“Tom Elliott”]ipxe hangs on Initializing Devices…[/quote][/SIZE]
[SIZE=3]i know this forum is about Realtek 8111\8168 & undionly.kpxe but i couldnt find any other forum reporting this issue.[/SIZE]
[SIZE=3]i am also having this issues with " IPXE Initializing Devices… "[/SIZE]
[SIZE=3]But it seems to be related to Intel Boot Agent v1.4.10 after testing 20 or so different computers, of different manufactures & models, it seems that any version of the Intel Boot Agent above 1.4.xx hangs on the " IPXE Initializing Devices… " screen and will never make it to the ipxe menu.[/SIZE]
[SIZE=3]it also appears that the hardware completely locks up and manually pulling the power is the only way to restart the PC. [/SIZE]
[SIZE=3]How can i debug whats going on it seems that all HP Computer 2014 and above will be shipped with this version so i really need to find a fix or a work around for this or a way to roll back ipxe to pxe and still be on Fog 1.0.1 as the issue doesn’t appear when using the old version of fog 0.32 pxe config.[/SIZE]
-
Have you looked at this thread and/or tried any of these other files to see if they can help you?
[url]http://fogproject.org/forum/threads/040ee119-error-on-boot.10493/page-3#post-28887[/url]
-
The undionly.kkpxe from trunk seems to have resolved my IRRT issues, at least on the E6500. Moves on to the hard drive via sanboot no problem.
[url]http://sourceforge.net/p/freeghost/code/1769/tree//trunk/packages/tftp/undionly.kkpxe[/url]
-
Stuck in that case with Lenovo Edge72 SFF computers, Realtek 8111\8168 GBie Network Cards.
[LIST]
[]Debian 7.5
[]FOG 1.1.1
[]RSTP on switchs
[]Tried the Pause/Return trick
[*]Did try several undionly.kpxe files
[/LIST]
Any hints ? I tried google it several times without success.
Cheers![url=“/_imported_xf_attachments/1/1024_2014-06-19 18.39.30.jpg?:”]2014-06-19 18.39.30.jpg[/url]
-
what happens if you boot into windows and do a restart?
-
I know the dev team has made leaps and bounds in this area since I originally started the topic. Have you tried the ipxe.kpxe file I uploaded to this thread?
-
Same “iPXE initializing devices…_”
-
[quote=“tamatech, post: 30826, member: 24111”]I know the dev team has made leaps and bounds in this area since I originally started the topic. Have you tried the ipxe.kpxe file I uploaded to this thread?[/quote]
Yes same status with your ipxe.kpxe file…
-
Have you explored all of these - including the .INTEL one?
[url]http://sourceforge.net/p/freeghost/code/1769/tree//trunk/packages/tftp/[/url]
-
Did you try undionly.kkpxe as I recommended earlier in the thread?
-
[quote=“andjjru, post: 30830, member: 575”]Did you try undionly.kkpxe as I recommended earlier in the thread?[/quote]
yup
-
[quote=“tamatech, post: 30829, member: 24111”]Have you explored all of these - including the .INTEL one?
[url]http://sourceforge.net/p/freeghost/code/1769/tree//trunk/packages/tftp/[/url][/quote]
nope, i’ll try them right now
-
I tried your files, nothing better.
FOG still works fine with other computers. I have that issue with that model only =/
If anyone has the magic pack of *.kpxe files it would be great to deliver !
-
[quote=“K3nnyfr, post: 30834, member: 17017”]I tried your files, nothing better.
FOG still works fine with other computers. I have that issue with that model only =/
If anyone has the magic pack of *.kpxe files it would be great to deliver ![/quote]
Can you try one of the more recent kpxe/kkpxe files:
[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/[/url] -
[quote=“Tom Elliott, post: 30835, member: 7271”]Can you try one of the more recent kpxe/kkpxe files:
[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/[/url][/quote]Hi Tom, i’ll try it tomorrow morning (it’s 20h07, CEST here), i leaved work for now.
I will download all the files you provided and replace the existant and tell you if it works.
Just saw that on gPXE wiki :
[QUOTE]
[SIZE=4][B][FONT=Lucida Grande][SIZE=21px][COLOR=#000000][SIZE=3]How to Fix[/SIZE][/COLOR][/SIZE][/FONT][/B][/SIZE][SIZE=16px][FONT=Lucida Grande][COLOR=#000000][LIST]
[*][SIZE=3]Buy another NIC. Really. I tried two and both did never work reliably (link problems – either no link detected or DHCP answers missed – could be a firmware issue, but how do I fix the firmware when I need to boot with that NIC??).[/SIZE]
[/LIST][/COLOR][/FONT][/SIZE]
[/QUOTE]Made me laugh =P
-
that’s part of the reason i asked what happens if you boot into windows and restart. for some nics the windows drivers properly initialize and shut off the card, allowing the card to properly initialize on the next boot. but a non-windows reboot may not.
-
[quote=“Tom Elliott, post: 30835, member: 7271”]Can you try one of the more recent kpxe/kkpxe files:
[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/[/url][/quote]Hi there, I’ve replaced all the exisiting files with those on the SVN, we tried them one by one.
Sometimes the screen is cleaned and a “iPxe Initializing devices…” appears, sometimes the same screen as before.
Nothing better or worst.
-
When you say you’re trying these files, are you replacing the “broken” undionly.kpxe with the file, or just downloading them into the /tftpboot folder?
-
This is what we did (with my trainees)
[LIST]
[]service tftp-hpa stop && service isc-dhcp-server stop
[]mv tftpboot tftpboot.bak
[]mkdir tftpboot
[]wget all the files in that fresh folder
[*]edit /etc/dhcp/dhcpd.conf
[/LIST]
In that file we replaced succesively the filename property with the different .kpxe/.kkpxe file in tftpboot folder.
Then start up tftp-hpa and isc-dhcpd and boot up our problematic device.
Am I doin it right ? Are we totally wrong doing it ?
Should we procede otherwise ?Cheers and thanks for your support !
-
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
mkdir /tftpboot
cd /tftpboot
wget -r ftp https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/*
[/code]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]
