@george1421 said in Mixed driver environment:

Talk about worked like a champ!
Wasn’t sure if recompiling would cause more headaches, or not.

We have been trying to find a way to get UEFI to play nice, we didn’t find your post from Nov 2…

@george1421, THANK YOU!!!
!SOLVED!

@george1421 said in Mixed driver environment:

Talk about worked like a champ!
Wasn’t sure if recompiling would cause more headaches, or not.

We have been trying to find a way to get UEFI to play nice, we didn’t find your post from Nov 2…

@george1421, THANK YOU!!!
!SOLVED!

@george1421
When one is flabbergasted, one’s brain doesn’t work quite right.

1. Correct. This network is only for imaging. FOG server is connected to a Cisco switch.
2. The FOG server is the DHCP server. Rather I opted for FOG to handle the DHCP roll, during the setup process.
3. All machines we have, are now exclusively UEFI. The option for Legacy BIOS is either missing or hidden

Mixed driver environment

Noob here. Both to Linux and FOG!

We have a FOG server running on Ubuntu Server 20.04.3 LTS on an Air Gaped network. It has a GUI and all required software/tools needed to get everything working. (No fluff software.)

We were able to get NBP and SPNonly.pxe to finally work with our desktops (Lenovo Think Centre –> Intel OB LAN NIC) to work. Although it is a little finicky:
When we go to PXE boot, it goes straight to FOG. However when we select ‘Deploy Image’ it fails, upon an immediate reboot and we go back to FOG it deploys the image without issue. WOW is it fast!

Thanks to the IOT/chip shortage, we are force to go with a different vendor HP for our laptops (HP G250 G8 -> Reltek PCIe GbE NIC).
The laptops refuse to connect to the FOG server.

The screen reads as follows:

Start PXE over !Pv4
Start IP address is 10.101.10.24

Server IP Address is 10.101.10.62
NBP Filename is ipxe.efi
NBP filesize is 1044256 bytes
Downloading NBP file…

NBP file downloaded successfully.
iPXE initializing devices…ok

iPXE 1.20.1+ (g4bd0) – Open Source Network Boot Firmware – http://ipxe.org
Features: DNS FTP HTTP HTTPS iSCSI NFS TFTP SRP VLAN AoE EFI Menu
Waiting for link-up on net0… ok
Configuring (net0 <MAC_HERE>)… No configuration methods succeeded (http://ipxe.org/040ee186)
Configuring (net0 <MAC_HERE>)… No configuration methods succeeded (http://ipxe.org/040ee186)

---

I know this is a DHCP error (according to the iPXE link).
I also know that this is also a Red Harring, due to the above scenario of the desktop computers connecting to FOG and deploying an image.

There is this thread to compile a new latest version of ipxe.efi and snponly.efi (https://forums.fogproject.org/topic/15198/fujitsu-a3510-pxe-uefi-boot/4), however I’m weary of doing this.

If it ain’t broke, don’t fix it!

• I have it working for our desktops.

Short of dual booting, two different installs of FOG (one for desktop/one for laptop), would there be a possible way to create a script that would switch back and forth between iPXE unidonly and NBP+SPN?

• If I said it incorrectly, I’m still new to this don’t kill me.