UEFI won boot tools via fog menu.

[george1421]

@dureal99d If I understand it correctly your {next-server} value should come from your dhcp server (understand I’m guessing here a bit since I have not worked with uefi and dnsmasq as of now). But in my docs I also ahve this line:

dhcp-range=<fog_server_ip>,proxy

That defines the range.

Actually I still have my FOG-Pi server that I can boot back up. That has dnsmasq running on it. Let me see if I can get a working config.

[george1421]

@dureal99d From your image below its working. Well an iPXE kernel is getting loaded. So that should removed dnsmasq from the issues. Is your fog server at 192.168.1.1?

[dureal99d]

@george1421 NO, its at 192.168.1.109

[george1421]

@dureal99d Interesting because in the picture its thinks your fog server is 192.168.1.1 because that is where its trying to load the default.ipxe file from. I can’t remember off the top of my head where that setting comes from, its either from FOG or the next-server value from dhcp.

[dureal99d]

@george1421 at current my config looks like this

dhcp-match=set:efi-x86_64,option:client-arch,7
dhcp-boot=tag:efi-x86_64,ipxe.efi
dhcp-boot=undionly.kpxe,,192.168.1.109```

in the dnsmasq setting of ddwrt.

[george1421]

@dureal99d I started another thread where I’ve been documenting my travels with dnsmasq and uefi here: https://forums.fogproject.org/topic/8677/dnsmasq-bios-and-uefi

My config is pretty close. I can pxe boot a uefi system. Right now its hanging on the iPXE kernel initializing devices… But I did have to compile the latest dnsmasq program because the one for my distribution did not work even with the updated config file.

Looking at your config file I would have to say you need to update this line:
dhcp-boot=tag:efi-x86_64,ipxe.efi

to this:
dhcp-boot=tag:efi-x86_64,ipxe.efi,,192.168.1.109

Just like you did for the bios undionly line.

[Wayne Workman]

FYI to everyone, the sourcecode for dnsmasq can always be found on Simon Kelley’s website, here:
http://www.thekelleys.org.uk/dnsmasq/

And general info can be found here:
http://www.thekelleys.org.uk/dnsmasq/doc.html

There’s a mailing list as well, where you can ask a question, and he will respond - all emails are archived on his site forever - he needs to make a book out of them IMHO. I’ve been on his mailing list for about a year, he is very active and I normally get an email once a day with all the questions and replies from the previous day.

[Wayne Workman]

@george1421 Perhaps we should give instructions in the BIOS/UEFI coexistence article for getting the right dnsmasq source and compiling it, and configuring?

I know this won’t be a permanent problem as eventually all distros will have the working version, but that could be years.

[george1421]

@Wayne-Workman With the libraries mentioned I can get really close to the distro had, except for one module that didn’t seem to impact ipxe booting. But your idea of updating the wiki pages for dnsmasq is not a bad idea. I sure would like to get a solid boot before updating anything, but the key was to use dnsmasq 2.76 and the updated config to get it to boot anyway.

[dureal99d]

@george1421 said in UEFI won boot tools via fog menu.:

@dureal99d I started another thread where I’ve been documenting my travels with dnsmasq and uefi here: https://forums.fogproject.org/topic/8677/dnsmasq-bios-and-uefi

My config is pretty close. I can pxe boot a uefi system. Right now its hanging on the iPXE kernel initializing devices… But I did have to compile the latest dnsmasq program because the one for my distribution did not work even with the updated config file.

Looking at your config file I would have to say you need to update this line:
dhcp-boot=tag:efi-x86_64,ipxe.efi

to this:
dhcp-boot=tag:efi-x86_64,ipxe.efi,,192.168.1.109

Just like you did for the bios undionly line.

I will try that config and report back.

[Sebastian Roth]

@dureal99d I might be able to help you with understanding how the TFTP URL (in your case tftp://192.168.1.1/default.ipxe) is build. You need to check out the embedded script that comes compiled into the binaries we provide - find the code here: https://github.com/FOGProject/fogproject/blob/dev-branch/src/ipxe/src-efi/ipxescript

[dureal99d]

@Sebastian-Roth ok cool!!!

[Sebastian Roth]

@dureal99d That said I am wondering if you have another DHCP server in your network that is answering requests as well. Possibly a router or something that is interfering with what dnsmasq is sending?!?

[dureal99d]

@Sebastian-Roth said in UEFI won boot tools via fog menu.:

@dureal99d I might be able to help you with understanding how the TFTP URL (in your case tftp://192.168.1.1/default.ipxe) is build. You need to check out the embedded script that comes compiled into the binaries we provide - find the code here: https://github.com/FOGProject/fogproject/blob/dev-branch/src/ipxe/src-efi/ipxescript

i tried the sugggested dhcp-boot=tag:efi-x86_64,ipxe.efi,,192.168.1.109 and it worked but the other stuff like the memtest and all will not work just the basic functions and uefi laptops i have find a boot file but crash or pause at initializing ipxe devices

[dureal99d]

@Sebastian-Roth said in UEFI won boot tools via fog menu.:

@dureal99d That said I am wondering if you have another DHCP server in your network that is answering requests as well. Possibly a router or something that is interfering with what dnsmasq is sending?!?

I am using ddwrt and it is my dhcp server using its built in dnsmasq to attach clients to fog which works well in bios boot mode. no other dhcp exist.

[Sebastian Roth]

@dureal99d Have you tried dhcp-boot=tag:efi-x86_64,ipxe.efi,192.168.1.109,192.168.1.109 yet?? This only sets another option in the DHCP answer properly. Usually this does not make a difference but you never know how clients behave…

[dureal99d]

@Sebastian-Roth said in UEFI won boot tools via fog menu.:

dhcp-boot=tag:efi-x86_64,ipxe.efi,192.168.1.109,192.168.1.109

no but i will try it

[dureal99d]

@Sebastian-Roth its so weird, this is my config as of right now dhcp-boot=undionly.kpxe,,192.168.1.109 dhcp-match=set:efi-x86_64,option:client-arch,7 dhcp-boot=tag:efi-x86_64,ipxe.efi,192.168.1.109,192.168.1.109

downloads ipxe.efi

yet if i take this line away dhcp-match=set:efi-x86_64,option:client-arch,7 away it will dowload the undioly.pxe file

[dureal99d]

@Sebastian-Roth I did create one of those uefi usb boot scenarios as was postd here on the forum but without the usb device selected at boot, no uefi based client will boot to fog unless i boot in legacy

[dureal99d]

@Sebastian-Roth @george1421 @Wayne-Workman @Senior-Developers id be willing to setup and configure another server “more than likely virtual” if I can still use ddwrt to provide dhcp to machines on my network and allow fog uefi and bios boot to co-exist. assuming it will make this process easier.