@Seb-B Thanks for clarifying. As well great that you tried the suggested debugging steps in the iPXE forums. There is a new suggestion on using an embedded iPXE script. Hopefully we’ll see more useful information this way. :-)
We are over some tests at last. As you suggested I did the following:
used a total dumb “link” between the pc and the network (hub): no change, still no boot properly
I used undionly.kkpxe and ipxe.pxe one by one. unfortunatelly no change.
Still no change, that means this hardware has somehow problems. Any other suggestion maybe? The problem is that we will surely get such hw, so it would be good to have a workaround somehow. Ah, one more thing. ipxe.pxe file gave a little difference. It said during boot that it boots from SAN device. Does it changes a thing?
@george1421, no we are using the legacy mode, i didn’t knew that the uefi mode worked in Fog :)
OK thanks for clearing that up.
Yes, uefi (working well) and nvme disks were added in an early 1.2.0 trunk release of FOG. With FOG 1.3.x both are fully supported and work very well. UEFI (EFI) is here to stay so its either support or die. Many new systems are coming uefi only (i.e. MS Surface Pro)
@fritoss007 Then you might be better doing the fixparts methodology. Now I’ve added postinitscripts to the working branch data so things should be able to be automated much more nicely for those 18 or so systems you’re seeing with this issue. (You can add checks to get things working how you need it).
FWIW: By default the P5510s are in uefi mode and has secure boot enabled. You can leave the P5510s in uefi mode if you disable secure boot (required for everything uefi that will be imaged by FOG) and send the uefi iPXE menu kernel to the uefi system “ipxe.efi” this is mandatory for all uefi systems not just the 5510.
Thanks everyone for their help. I have purchased the official USB-to-Ethernet adapters from Microsoft and Lenovo and are going to try them out since they state that they support LAN or pxe boot. Once they come in I will let you know if they work with the guides you have posted. Thanks again for your assistance.
This is what we are finding is the best solution (purchase the recommended ones from the hardware mfg). WIth UEFI the firmware has to support the ethernet driver (usb or otherwise) for pxe booting to work with uefi systems. Without the supported network adapter the firmware will simply not see the network adapter.
EDIT 2: Not sure why the edit from my main post vanished. Let me put that here again.
I took a video of the newest message. From reading the blurry video, this is what I can read before the fog text logo comes up.
mmc0: Unknown controller version (3). You may experience problems.
usb 1-5: device descriptor read\64, error -71
EXT4-fs (read): couldn’t mount as ext3 due to feature incompatibles
Starting logging: OK
Populating /dev using udev: udev: error creating spell? fd: Function not implemented
EDIT 3: Took bzImage files and init files from a test fog machine I was messing with. 1.3.0 FOG on there. Copied the to the FOG 1.2.0 server.
The compatibility test comes back with disk and network passing.
Trying to register a host and I get:
Unable to register host: Invalid MAC Address (/bin/fog.man.reg)