After Deploying Image, reboot loop; Dell e6520; Fog 0.32
-
That did it, would you mind if i tidied up the page on the wiki to make it a bit more clear?
-
Go for it! I think I spent all of two minutes typing that up off the top of my head, so any clarifications or better wording would be greatly appreciated.
-
Updated:
[url]http://www.fogproject.org/wiki/index.php?title=Boot_looping_and_Chainloading[/url]Thanks BryceZ
-
Thanks for updating the wiki.
Things seem to be moving in a better direction with these new forums 
On a side note most Dell E series have this chain loading issue.
-
Used BryceZ’s instructions to help resolve my problem with bootlooping as well (we typically only have the Dell Latitude E series in our organization).
Just wanted to say thanks for the wiki, it was very helpful.Is there any talk of including chainloading in newer versions of FOG?
-
Chainloading is a workaround for a bug most often seen with Dell BIOS, and does add additional levels of complexity that do not need to exist for everyone. So the developers are hesitant to build chainloading in. And as long as it’s simple to implement after the fact they’d prefer to keep it that way.
-
Interesting. Makes sense, though. Thanks for the response! I’ll keep that in mind whenever I’m working with Dell machines.
-
This is the first issue I ran in to after 3 years of using FOG on a 500+ client network.
[url]http://www.fogproject.org/wiki/index.php?title=Boot_looping_and_Chainloading[/url]
Easy to follow instructions and works a treat! Thanks for all the help everyone
-
We have a whole slew of Optiplex 790 Dells, and after applying this fix, the graphical menu displays, counts down from 3, then the countdown starts over again. I am using the exact syslinux version as the guide shows. I have setup a new fog server and tried the setup instructions and it behaves the same way. So either I am doing something identically wrong after following the guide, or perhaps this fix does not work on the Optiplex 790s? Any help?
-
For anyone with my problem described - it was due to me spelling kernel improperly… I had kernal chain.c32 instead of kernel chain.c32… live and learn.