Incompatible BIOS version
-
@daniell you could register the hosts and issue the imaging task from the web gui instead of from the pxe menu
-
What version of FOG are you using (more to the point, what FOS kernel version is booting on the target computer)?
-
If I had to guess, this kernel update may have disallowed ‘legacy’ USB mode? Of course it’s possible something else broke it too? I don’t know, there’s just too many variables. Typically when I see the issues simple due to memory oberusage during boot up and the kernel, after 2-5 minutes starts throwing rcu errors. Maybe this is what’s happening? As George asked, what version of fog and kernel version are you running?
-
I am running version 1.3.5-RC-10, and Kernel Version 4.9.11. Also my FOG server is running CentOS7.
-
@Tom-Elliott So Tom, do you have a cache of older kernels maybe in the 4.9.0 or maybe even in the 4.8.X range.
The other thing may be just the opposite, the firmware update has changed what the FOS kernel is looking at.
-
@george1421 kernel updater
-
@Tom-Elliott The kernel updater will allow you to go backwards too?
-
@george1421 yessir
-
@Tom-Elliott
I am trying to revert to the last kernel version 4.9.4, but am running into an issue. I am following the guide here:
https://wiki.fogproject.org/wiki/index.php?title=Kernel_UpdateAfter selecting v4.9.4, I leave the Kernel name as the default, and click “Next”. I am then immediately kicked back to the FOG Dashboard. Would you be able to provide me with a direct link to previous kernel version, so I can manually update the kernel?
Thanks -
@daniell I’m not going to tell you where this came from…
https://fogproject.org/kernelsThe magic is contained within.
-
Thanks for all the help, but unfortunately I’m still having the same problem. I tried rolling back to version 4.9.4 and 4.9.0. Do you have any other recommendations on how to resolve this issue? If not I may just downgrade the BIOS on new PC’s I need to image.
Thanks -
@daniell Try downgrading one system first, this will ensure it is indeed a problem with the firmware or not.
Unfortunately there’s not much we can do to fix it. Did you try seeing if the “legacy usb mode” was enabled/disabled?