Fog Server throws error when trying to image new HP G4 Desktops

[IndustrialTech87]

Hello,
I have searched for solutions to this problem online and have found one or two articles that mention that the kernel may need to be updated on the fog server, however, they were not having the exact same error message as we get. I did find one online forum post and in the middle some guy posted a screenshot and he had the exact same error message as I am getting but no one ever answered him.

We have been able to use FOG for a long time but we just got some new HP ProDesk 600 G4 SFF computers. I am able to network boot and select Full Host Inventory and Registry but when it comes up, it has an error message and then says it fails to pull an IP via DHCP. I will post a picture of the screen below. The desktops we have been using are the same but G3’s. I know that pulling an IP isn’t really the problem.

Any suggestions are appreciated.

I apologize for the quality of the screenshot but it shows the full error message. Here is the link to the screenshot.

And I just wanted to state that we can still image the other computers using FOG. It is these batch of new computers that will not work.

[george1421]

@IndustrialTech87 OK for 1.4.4 that’s a bit old. I checked the linux kernel site and the first kernel release that supported that network adapter is 4.12.

hardware ref: vendor: 8086 (“Intel Corporation”), device: 15bb (“Ethernet Connection (7) I219-LM”)

So Download the FOS kernels from this web site https://fogproject.org/kernels/ Download 4.12.3, don’t go any newer. Its questionable if 4.12.3 will work with FOG 1.4.4. Just be aware of this. Don’t go any newer than what is absolutely necessary with 1.4.4. You will need to download both bzImage and bzImage32 and place them in /var/www/html/fog/service/ipxe directory. Make sure you rename the existing bzImage and bzImage32 so you can go back if you need. The downloaded kernels will need to be named bzImage and bzImage32 exactly (case is important).

[george1421]

@IndustrialTech87 There are two paths here that I can see. One is for collecting data and the other is to see if an older kernel will work. Both paths are important.

Path 1

1. Manually register this troubled target computer with FOG.
2. Schedule a capture or deploy it doesn’t matter, but before you hit the schedule button, check the debug check box. Then schedule the task.
3. PXE boot the target computer. After a few enter key presses on the target computer you will be dropped to a linux (FOS) command prompt.
4. I need you to collect and post the screen shots of these two commands:
   ip addr show
lspci -nn|grep -i net
5. If the mac address is displayed for eth0 in the ip addr show command then issue this command udhcpc -i eth0 --now then run the ip addr show command again. If it displays an IP address then try to ping your fog server.

Path 2

1. If you are running fog 1.5.4 or 1.5.5 and you are on FOS kernel 4.19.x downgrade your FOS kernel to 4.18.x. If 4.18.x doesn’t work try 4.15.x.

Both paths are important to understand what is going wrong with your system.

[IndustrialTech87]

@george1421
Thanks for your help.
Path 1 - No MAC is shown. Screenshot here has output from both commands. Sorry again for quality.

Path 2 - We are on an older version of FOG, version 1.4.4

[george1421]

@IndustrialTech87 OK for 1.4.4 that’s a bit old. I checked the linux kernel site and the first kernel release that supported that network adapter is 4.12.

hardware ref: vendor: 8086 (“Intel Corporation”), device: 15bb (“Ethernet Connection (7) I219-LM”)

So Download the FOS kernels from this web site https://fogproject.org/kernels/ Download 4.12.3, don’t go any newer. Its questionable if 4.12.3 will work with FOG 1.4.4. Just be aware of this. Don’t go any newer than what is absolutely necessary with 1.4.4. You will need to download both bzImage and bzImage32 and place them in /var/www/html/fog/service/ipxe directory. Make sure you rename the existing bzImage and bzImage32 so you can go back if you need. The downloaded kernels will need to be named bzImage and bzImage32 exactly (case is important).

[IndustrialTech87]

@george1421

Thanks. Our Network Manager actually updated the Kernel just before you replied. I will send him your reply in case he needs to do any of those steps. Will post if it starts working or not.

[IndustrialTech87]

Upgrading the Kernel fixed this issue. I am not sure what version he upgraded to but I can now image these new computers. Thank you for your help @george1421