@Tom-Elliott
Thanks for the info Tom.

Yes the firmware is up to date.
Bios N75 Ver 01.13 11/01/2016

Although older, I can confirm the Dell Poweredge R410 runs CentOS 7 just fine. It runs VMs like a champ using the Linux kernel’s built-in virtualization capabilities.

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?

@SDToone Clear screen shots of the errors would help to set the context of the error you see.

@Tom-Elliott Great stuff! Yeah from what I see in those MS surface posts it was only the CDC -ether driver causing the issue. Keeping my fingers crossed…

@falko I’ve generally had no problems with Lenovo & FOG overall. Can’t speak to this particular model. Figure out what chipset the NIC uses if you can, and research linux support for that chipset.

@jjacobs said in Dell 7040 NVMe SSD Boot Issue:

@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)

@chief Ok if you put a dumb switch in between the target computer and building switch and it resolved the problem. Then its probably one of the advanced protocols causing the issue.

This is typically spanning tree being enabled and not using one of the fast stp protocols.

Or you have green ethernet (802.3az) enabled on the building switch. We’ve seen this to be an issue with some realtek nics.

@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).

Links to people who had issues with surface pro and fog
https://wiki.fogproject.org/wiki/index.php?title=Surface_Pro

@Tom-Elliott j’ai fait la mise à jour de FOG 1.3.0RC et cela fonctionne correctement avec cette machine c’est top
Merci de ton aide

@Tom-Elliott I made the update of FOG 1.3.0RC and it works correctly with this machine it is top
Thanks for your help

@Andrew134 I’m glad yo have it worked out.

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.

Hi,

we have a lot of HP’s Probook 650 G2 and i never had a problem with them, i’ve imaged the last one on thursday.
Is this your first fog installation?

Regards X23

@Blsmith said in Need USB to Ethernet Adapter that works with Ipxe:

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.

The Shuttle-Bios doesn’t have these features.
The Dell-Bios is running in Legacy-Mode.

@george1421
Yes i have just tried that and the result is the same.

@george1421 I downloaded a copy from the kernel directory on a different PC and copied it over. They were just called bzImage and bzImage32. I will get the version in the morning and report back.

I did run the test before I left and it did fail network. I also wasn’t able to see the mac address or IP through the menu.

EDIT:

Also, running Ubuntu 14-04 LTS
I get bzImage: x86 boot sector

And I got the bzImage from here https://fogproject.org/kernels/

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[2612]: error creating spell? fd: Function not implemented
done

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)
Arg Passed:

I think I am making some progress here.

@george1421 Like I mentioned above, the Lenovo ThinkPad 13 works perfectly with the same BIOS setup. No need for the USB solution that the Yoga 260 requires for UEFI/Legacy dual booting. I fully believe the problem is entirely with the firmware on the Yoga.

Both work better now than they did 4 months ago with the BIOS version available then.

@Wayne-Workman Sorry, I will do that in the future. I was able to capture my image after fixing the GPT remnants.

Thank you for all your help!