FOG BIOS And EFI Coexistence

[Wayne Workman]

[url]http://fogproject.org/wiki/index.php/Filename_Information[/url]

.efi files are for UEFI, everything else is for BIOS.

There are ipxe.efi, snp.efi, and snponly.efi that you can try.

[need2]

There’s also 32bit efi files in the i386-efi folder.

[Jeroen Brussich]

I am at home now and can only resume testing in 3 days.

I downloaded ipxe.efi twice and calculated the checksum for both files.
I compared the md5-hash with the file on in my tftpfolder and it was trice the same…
No errors there…

I tested the ipxe.efi ROM on 2 different machines (intel NUC DC3217IYE and a Lenovo [SIZE=13px][FONT=Ubuntu][COLOR=#555555]ThinkPad Edge E540).[/COLOR][/FONT][/SIZE]Both time, the boot was interrupted as described above.

I will test snp.efi and snponly.efi in 3 days but I still got the feeling I’m doing something wrong.
Or is it a coincidence both machines refused to boot from the ipxe?

Would it help to try a legacy boot from ipxe.kpxe to test the ROM in non-uefi mode?

[need2]

Yeah, that could rule out other issues.

[Wayne Workman]

[quote=“need2, post: 47117, member: 21891”]There’s also 32bit efi files in the i386-efi folder.[/quote]

I never even thought of that…

[Lee Rowlett]

we have it working here with Windows DHCP 2012 - as Junkhacker said really is simple process just create the vendor class then setup the DHCP policy and specify bootfile (option 67 and don’t need to specify option 66 in the policy as it will pick this up from already defined option in the scope)

[need2]

I finally have all of our licenses in order, so I should be able to push forward with creating the new DHCP as early as next week. Thank you everyone for your input.

[Wayne Workman]

@need2
Documentation / screen shots please.

[need2]

Oh but of course.

[Tom Elliott]

I really wish we could get this working with a proxyDHCP or native dhcp systems. Maybe a third party utility rather than all requiring linux-dhcp and/or Windows Server 2012 or higher for user class support.

[need2]

Yeah I really would love to find a way to package something into FOG as well. Unfortunately a lot of current UEFI systems I’ve been working with seem to really hate on the methods that are used to load the extra PXE data onto an existing DHCP Server’s response.

[Wayne Workman]

Just created this article:

https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence

[need2]

I should buy you a beer.

[Sebastian Roth]

@need2 said:

Yeah I really would love to find a way to package something into FOG as well. Unfortunately a lot of current UEFI systems I’ve been working with seem to really hate on the methods that are used to load the extra PXE data onto an existing DHCP Server’s response.

I just came across this post: http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2015q1/009216.html

I am trying to get in contact with him to see why WDS seams to work with proxyDHCP.

Any new findings on this? I just updated Wayne’s article to include isc-dhcp config for BIOS/UEFI but I guess this is not the preferred way to go, right!?

[Wayne Workman]

@Uncle-Frank You’re amazing! What you posted is very similar to what I came up with in a thread, but I haven’t gotten around to testing it.

If you get dnsmasq to work with co-existence then you’re like… everyone’s hero… for real. Because if we can get a rock-solid dnsmasq config for all types of booting - then for 95% of fog setups out there, we’ve eliminated the need to change DHCP. Fog can then come with dnsmasq setup by default and it JUST WORK without further setup.

In my opinion, Linux DHCP is far superior to Windows DHCP… but dnsmasq would be the ultimate solution if we could just get it to work.