Realtek 8111\8168 & undionly.kpxe -> hangs on Initialising Devices...
-
[quote=“andjjru, post: 28728, member: 575”]I’m in the unfortunate situation of having a lot of important computers out there that require sanboot to continue to boot to hard drive, as well as a lot of important Dell laptops with IRRT enabled that need the opposite.
Rock, hard place, etc.[/quote]
If I had a solid knowledge of exactly which systems like (and/or) dislike a specific type, I could programmatically make this a non-issue. In your particular case, is there a specific model that requires certain types?
Maybe we can get a listing of Systems and their preferred method of exiting to the hard drive?
-
[quote=“Tom Elliott, post: 28793, member: 7271”]If I had a solid knowledge of exactly which systems like (and/or) dislike a specific type, I could programmatically make this a non-issue. In your particular case, is there a specific model that requires certain types?
Maybe we can get a listing of Systems and their preferred method of exiting to the hard drive?[/quote]
I know for sure that the Dell Optiplex 390 prefers sanboot, and a bunch of Dell Latitudes (E5540, E5520, E6510, probably more) that have IRRT turned on by default prefer exit-style. Those Latitude models are fine with sanboot if their SATA type had been switched to AHCI or ATA prior to imaging, but not all of our techs had been doing that.
-
last night, tom added a new feature to the development release of fog. if you install the svn version of fog, you will find a new option of “grub” for exit type. that will load the grub4dos boot-loader, which is known to exit cleanly on a wide variety of systems, and boot to hard disk.
-
Thanks guys! I’ll check into that on Monday.
-
I had to track down a laptop with the IRRT option to test. Unfortunately, the Latitude E6500 I grabbed won’t continue on to boot the hard drive with any of the three exit styles, in ATA, IRRT or AHCI.
-
[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