UEFI won boot tools via fog menu.

[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.

[george1421]

@dureal99d I’ve kind of lost where this thread is going.

Lets recap. You are using dnsmasq on dd-wrt to supply the missing bits needed to pxe boot a target computer in uefi mode. (I haven’t looked) but doesn’t dd-wrt use isc dhcp server? If so then dnsmasq is not required, since isc dhcp is all you need. There is a FOG wiki page on how to set it up. https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

Can you pxe boot a target computer into the fog ipxe menu and capture or deploy an image. If this doesn’t work then we need to understand what is going sideways. Beyond that if you are trying to pxe boot random applications not delivered with FOG then those need to be addressed. But we need to make a clear distinction is this a FOG issue or third party application issue.

[dureal99d]

@george1421 I don’t know if ddwrt uses isc, I do know it uses dnsmasq. and it will onlt boot into uefi mode if I use the usb I made based on an tutorial I found on this forum.

and yes the main issue I’m having is none of the third party tools work in uefi mode. I am not sure if this is an issue with uefi or the software. but I assumed at least memtest would work and it fails as well.

I have however successfully captured a image.

[Quazz]

@george1421 DDWRT uses a lightweight version of DNSMASQ.

[Wayne Workman]

@george1421 According to this: https://www.dd-wrt.com/wiki/index.php/DNSMasq_as_DHCP_server

dd-wrt uses dnsmasq or uses uDHCPd but not both at the same time. It’s one or the other.

[Sebastian Roth]

Well then it probably uses an older version of dnsmasq which does not handle PXE booting of UEFI devices properly?!?!

[dureal99d]

@Sebastian-Roth @Wayne-Workman I think that its clear that I need to invoke a new setup to properly handle co-existing environment, going forward what is the recommended way to remedy this situation. should I use fogs built in dhcp server or setup a new one and if so what server type Linux, windows?

[Wayne Workman]

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

should I use fogs built in dhcp server

Yes. The installer will set it up for you perfectly. Earlier in this thread, I described how to change your current server to do this.

[dureal99d]

@Wayne-Workman is this a situation were I will have to disable dhcp on my router, or will they both work in tandem with each other.

[Wayne Workman]

@dureal99d They will not work in tandem without expert configuration, and we don’t have time for that. That’s something you can mess around with after things are working.

[dureal99d]

@Wayne-Workman @Senior-Developers @Moderators @Developers
I know this thread has sparked somewhat of a up and down exhaustive debacle on if and how to make the efi load with the dns masq of ddwrt.

This configuration right here is partially working and has allowed me to boot successfully a sony Lenovo laptop in uefi mode.

although non of the Linux isos boot and no third party tools work at least its a step in the right direction, I think?

If you look at the loading sequence it states something strange that I’m sure you pros can identify. Link up on net0..............Connection timed out??
At any rate I am now wondering if I must create one of these entries for each type of .efi file ie. snp.efi etc.

dhcp-match=set:efibc,option:client-arch,7
dhcp-boot=tag:efibc,ipxe.efi,,192.168.1.109
dhcp-match=set:i386-efi/ipxe.efi,option:client-arch,6
dhcp-boot=tag:i386-efi/ipxe.efi,,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
dhcp-match=set:efi-x86_64,option:client-arch,8
dhcp-boot=tag:efi-x86_64,ipxe.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,9
dhcp-boot=tag:efi-x86_64,ipxe.efi,,192.168.1.109
dhcp-boot=undionly.kpxe,,192.168.1.109