Moderators

@alienco Reimaging is completely unnecessary. The problem is with the bios/firmware settings not the target OS.

The snarky answer is don’t let the FOG server go down or become unavailable.

A bit more realistic answer is change the boot order so that it boots from the hard drive by default in bios. Then when you want to image the computer, have the imaging tech sit in front of the target computer and press F12 or F10 while booting to get into the uefi/bios boot manager and pick pxe boot from there. That is how we do it on my campus. I require the fog tech to sit in front of the computer they are imaging. This avoids accidentally reimaging the CFO computer during quarter end close (it only happened once). So normally under this methodology the computer always boots to the hard drive and the exception is to pxe boot during imaging only.

@djgalloway Thank you. Actually this thread helps advance the project too. The devs won’t add this driver to the main kernel but if they need to create a one off kernel the instructions are here.

@djgalloway said in No network interfaces found | Dell PowerEdge R650 | Intel E810-XXV:

Is there any additional information I could provide that might be helpful?

No that should do it if it sees the nic and it gets an IP address. Just remember to remove your debug deploy task and you should be done. It sees the disks so it should image now

Is there any harm in replacing my existing bzImage files with this patched kernel?

No harm in replacing your current default image. I would go in and change the global kernel parameter in the fog configuration -> fog settings -> expand add method. You just have to remember you are running under a one off kernel when/if you do a kernel update since the default kernel is something other than bzImage. But this kernel is the same that as what is released by the developers with the addition of the qed and ice spf+ drivers.

@sebastian-roth said in No network interfaces found | Dell PowerEdge R650 | Intel E810-XXV:

I don’t think I have seen this ever before and I am not sure the buildroot init is able to properly handle this.

Same here on the naming convention. I’m building it outside of build root, but in a kernel dev environment so I have a bit more flexibility to create mischief.

@djgalloway OK updated version: https://drive.google.com/file/d/18jEOG-qqTpJOS6NzfBRzDXBu1E7O9ZHt/view?usp=sharing

Save as bzImage5.15.44-ice2

I did exactly what Sebastian mentioned. I copied the .pkg file to ice.pkg and did a complete rebuild on the kernel thats why it took a bit longer to complete.

@george1421 Looks like the DDP binary blob needs to be named as ice.pkg without the version number (code ref). I don’t think I have seen this ever before and I am not sure the buildroot init is able to properly handle this.

Could you try manually renaming the file after cloning the firmware repo and adjust the filename within the kernel config?

@Endriu-Wilian Three different URLs are used to query that information. Find the URLs in the code (line 2700…2702): https://github.com/FOGProject/fogproject/blob/dev-branch/packages/web/lib/fog/fogpage.class.php#L2695

Earlier versions (before 1.5.9) used fogproject.org only - just in case you use an older one.

@george1421 Here is the link to the one-off kernel :https://drive.google.com/file/d/18pWcju562KfM-iFbkD86ylWM5R2YxgK5/view?usp=sharing

This one is called bzImage5.15.44-ice Looking at the custom kernel I had the ice driver installed but was missing the firmware bit. So this kernel has CONFIG_ICE enabled as well as preloading the firmware intel/ice/ddp/ice-1.3.26.0.pkg into the kernel.

For installing it use the same instructions as the qed-2 kernel below, use the -ice name instead.

A short cut here is in the host definition you just created, there is a kernel field. Update that field to bzImage5.15.44-ice, then save the host profile. Reboot the target computer (assuming its still in debug mode). Have a quick eye, as you should see it now transfer bzImage5.15.44-ice to the target computer as it pxe boots. At the FOS Linux command prompt key in ip a s to see if it gives you an IP address now. If no report back and we will continue debugging.

@abulhol Thanks for looking into the error and fixing the issue via the github PR. Merge is done.

@multipass ok would you follow this tutorial to capture a pcap of the pxe booting process. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

Upload that pcap to a file share site and DM me the link using FOG chat. I’ll take a look at it for the next steps. The capture filter will only collect the dhcp process and no other traffic on your network.