New Machine Problems
-
As they say, you can either pay me now or pay me later (when it comes to upgrades)…
To answer your question you can grab the latest kernels using these links. These are for FOG 1.3.0-rc1 but they will work for 1.2.0 without issue.
https://fogproject.org/kernels/bzImage
https://fogproject.org/kernels/bzImage32You want to place these files in /var/www/html/fog/service/ipxe directory. Just rename the original files and place these in their place.
-
@george1421 put these files in place and now reimaging in fog is not working. I had this issue with the Kernel I made as well. All I get when doing reimaging on a different machine is a strobing underscore. Did run compatibly check on both of the laptops and got the network failed again.
-
@Andrew134 Make sure they are owned by
fog:apache, orfog:www-data, orfog:http. Each of those are for different OSs. -
@Wayne-Workman How would I do that?
-
@Andrew134 Generally, use chown.
For example, Ubuntu:
chown -R fog:www-data /var/www/html/fog/service/ipxe -
@Wayne-Workman Sadly it is still doing the blinking. This is what I got from doing an ls -l
-
I just checked the Lenovo Thinkpad T460s and it has an intel nic which should be supported by the FOS engine (linux kernel supplied by bzImage).
Are these systems in legacy (bios) mode or uefi?
What ever the mode the iPXE menu is booting so the right iPXE kernel is being sent to the target computer, its just failing on the hand off from iPXE to bzImage starting. (just trying to state what we know so far).
-
My guess is the 1.2.0 init has no network link up.
I noticed a similar issue with FOG 1.2.
Kernels higher than the 4.1 series do not auto obtain network information within the kernel context. The development versions of fog had no issues with this because the init’s have a means to get the dhcp from the server like most other OS’s do, but 1.2 (and earlier) did not have this functionality. I don’t remember when I made the init’s capable of handling their own dhcp gathering, but I’m fairly sure a kernel newer than 4.1, but less than 4.4 should work both the drivers AND still allow your device to get dhcp.
Or simpler yet, Please install the RC-1, and all should work right out of the box.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@Tom-Elliott said in New Machine Problems:
…but I’m fairly sure a kernel newer than 4.1, but less than 4.4 should work both the drivers AND still allow your device to get dhcp.
This statement explains why others have seen success upgrading to 4.1.2 and not with 4.6.x. This was not understandable at the time, but is crystal clear now.
So just to state it another way if you are running 1.2.0 stable, you can only upgrade to kernels less than release 4.4.
-
Sorry I didn’t notice it sooner
-
@george1421 said in New Machine Problems:
I just checked the Lenovo Thinkpad T460s and it has an intel nic which should be supported by the FOS engine (linux kernel supplied by bzImage).
Are these systems in legacy (bios) mode or uefi?
I switched off uefi on the HP and it is now reimaging like a champ
However the Lenovo is still giving me issues, I turned it to Legacy and it still says network failed. If I change it to uefi it says starting PXE over IPv4, looks like it finds the fog server but then pops up PXE over IPv6 and hangs for a while before returning to the boot menu.
-
@Andrew134 for uefi mode 1.3.0 works a bit better since it has the updated iPXE drivers too. Also with uefi mode you need to ensure that secure boot is disabled in the firmware.
On the lenovo, if you can switch to legacy mode please do that, then pxe boot into the fog menu. Your dhcp server will need to be sure you are sending undionly.kpxe to these systems. Once you get into the FOG iPXE menu select the compatibility test menu and ensure that both the hard drive and network adapters are supported.
-
Alright so I have to throw in the towel. Still can’t get the Lenovo to re-image no matter what settings I change and we just got our new machines in and they won’t work either. They are HP Elitedesk 800 G2 and searched for the model in Fogproject forms and all I have found is trunk being the end all answer.
My question now is can I do an in place upgrade to Trunk or do I need to build a new server? Does the data port over okay from 1.2.0 to Trunk?
-
@Andrew134 upgrading is supported. http://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk
-
@Andrew134 said in New Machine Problems:
They are HP Elitedesk 800 G2 and searched for the model in Fogproject forms and all I have found is trunk being the end all answer.
You have to remember that FOG 1.2.0 is almost 3 years old (SVN 2094). With 1.3.0-rc1 somewhere north of 8600 there has been a ton of changes to FOG too. Hardware has changed so much since then its hard for the system to support it. Consider Windows 7 (which is still being actively installed today). You can’t install it on the new systems that have NVMe disks without first apply 2 hot fixes it (before OOBE boots the first time). Windows 7 does not support NVMe disks or new hardware without the proper drivers. There are other examples of network cards behaving differently because some enhanced functions have been off-loaded right into the network card. There are many more examples of why its past time to retire 1.2.0, that is why the devs are working hard to get 1.3.0 released as stable very soon.
So hang in there and follow the instructions to upgrade to trunk
-
Well I got her updated and it works… for the most part. Now my images do not work once they have been deployed. This was the image I was trying to use is there anything that jumps out at you just from this page?
-
Just to be clear the image is not working on both the machines I mentioned before (Lenovo and Elitedesk) both now can register and get images though.
-
@Andrew134 OK so can we say there is something different in how fog 1.3.0-rc1 handles the previously captured image?
What version of FOG were these captured under? My bet there is something we need to adjust like partclone or the config files. That part is a bit beyond what I know, but once we get things outlined we can get the devs involved. Don’t worry this issue can be fixed.
-
@george1421 said in New Machine Problems:
What version of FOG were these captured under? My bet there is something we need to adjust like partclone or the config files. That part is a bit beyond what I know, but once we get things outlined we can get the devs involved. Don’t worry this issue can be fixed.
They were captured in 1.2.0 and I have faith it can be.
-
@Andrew134 @Developers a little input on adjusting the image here?
