UEFI won boot tools via fog menu.
-
@dureal99d To add on further, backwards compatible does not mean, LEGACY, is “forwards compatible”
-
FOG supports both BIOS and UEFI, and the FOG Client installs on all major versions of Windows, OSX, and Linux. What your trying to do isn’t directly supported, but of course you can make it work. Follow Quazz’s suggestion, check secure boot, check the material you’re wanting to boot actually works in the mode you want it to work in. Also read through this, and if you get your particular project working for yourself, you should contribute what you did here in the forums - we are a community of volunteers and you can help too, by contributing what you did - step by step.
Now, what are you trying to boot, exactly?
-
@Wayne-Workman said in UEFI won boot tools via fog menu.:
what are you trying to boot, exactly?
@Wayne-Workman I am trying to boot Linux Ubuntu, mint, fedora, centos and windows tools as I am able to in bios boot mode.
-
@Wayne-Workman @Tom-Elliott it wont even run memtools in uefi mode
-
@Wayne-Workman then link you provided works well in bios boot mode but non of it works in uefi mode. it gives an nfs error but nfs is working fine. oh and cent os and fedora boots just fine though. nothing else
-
@dureal99d What is running DHCP in the environment? Have you seen this article? https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
-
@Wayne-Workman said in UEFI won boot tools via fog menu.:
is running DHCP in the environment? Have you seen this
@Wayne-Workman I am running ddwrt on a router and using it as my dhcp. I seen that article but remain confused as it points out the dns masq part which applies to me, but u really don’t understand this part. # x.x.x.x = TFTP. what does the x.x.x.x represent?
-
@dureal99d I’m not sure how dd-wrt handles vendor classes, but I’m pretty certain it can.
What’s likely happening with your problem is dd-wrt is only setup to serve a bios boot file, which is why most of your uefi ISOs don’t work.
Perhaps one of the @Developers or @Moderators or @Testers have dd-wrt at home and know how, but you need to set it up to hand out
ipxe.efifor uefi identifying machines andundionly.kkpxefor BIOS identifying machines (generally).If you read through the article I posted you might better understand what you need to do with your dd-wrt router.
Here’s something I found by searching Google for ‘dd-wrt dhcp vendor class’. The thread is probably so old that it doesn’t even apply to the latest version but it might point you in the right direction:
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=643566Another idea is to turn off dhcp on the router temporarily and then edit the fog servers
/opt/fog/.fogsettingsfile and change do dhcp and bldhcp to yes or 1, and rerun the installer and just see if your ISOs work then. Because FOGs dhcp setup already well supports many architecture types, some of that work I contributed to, it’s solid. To undo this, same steps but turn those two settings off, then manually stop and disable dhcp. For Ubuntu it should beservice dhcpd stop;service dhcpd disableHere is more info on .fogsettings if you get lost or curious:
https://wiki.fogproject.org/wiki/index.php?title=.fogsettings -
@Wayne-Workman said in UEFI won boot tools via fog menu.:
same steps but turn those two settings off
@Wayne-Workman will look into this and report back. promptly!!!
-
@Wayne-Workman yeah after reviewing it all I have been looking for how to add onto “dhcp-boot=undionly.kpxe,fog ip address” and add on the efi boot options. I am stomped on how to do this on dnsmsq of ddwrt.
-
From what I’ve read on the Wiki they need to be added to the additional dnsmasq options manually.
https://wiki.fogproject.org/wiki/index.php/FOG_with_DD-WRT_firmware
-
@Quazz said in UEFI won boot tools via fog menu.:
From what I’ve read on the Wiki they need to be added to the additional dnsmasq options manually.
https://wiki.fogproject.org/wiki/index.php/FOG_with_DD-WRT_firmware
@Quazz I know they need to be added on manually and i have no issue with that.
but what to add in addition to “dhcp-boot=undionly.kpxe,192.xxx.x.xxx” is what stomps me.Ive tried several configs all of which seems to make nothing work.
-
@dureal99d The dnsmasq on ddwrt may not support the options you need, not sure. I know they use a custom lightweight version of it.
-
@Quazz said in UEFI won boot tools via fog menu.:
sq on ddwrt may not support the options you need, not sure. I know they use a custom lightweight
@Quazz I am willing to try that option but i dont understand the x.x.x.x part outside of the obvious ip parts in the begin.
dhcp-match=set:bios,60,PXEClient:Arch:00000 dhcp-boot=tag:bios,undionly.kpxe,x.x.x.x,x.x.x.x <<clearly IP # ?.?.?.? = TFTP/FOG server IP -
@dureal99d I found this https://davidmnoriega.wordpress.com/2015/07/27/linksys-e4200-and-dd-wrt/
Which seems to indicate you need to replace tag with #
So eg
dhcp-match=set:bios,60,PXEClient:Arch:00000 dhcp-boot=#:bios,undionly.kpxe,x.x.x.x,x.x.x.xMight not be all you need, though.
-
@dureal99d The x.x.x.x simply refers to where your TFTP resides. The IP address of your FOG server most likely, unless you set it up elsewhere.
-
@Quazz said in UEFI won boot tools via fog menu.:
@dureal99d The x.x.x.x simply refers to where your TFTP resides. The IP address of your FOG server most likely, unless you set it up elsewhere.
@Quazz so does that mean i should put my tftp ip and where it says fog serve ip put the fog ip?
-
@dureal99d Yes
-
@Quazz tried this
dhcp-match=set:bios,60,PXEClient:Arch:00000 dhcp-boot=#:bios,undionly.kpxe,192.168.1.109 # 192.168.1.109 = TFTP/192.168.1.109did’nt work, im pretty ure its somthing im doing wrong
-
The tftp at that point is coming from your fog server .
For me, I use dd-wrt at home as well, and while I don’t have any UEFI machines to test I’m fairly sure you still need to tag the boot file line so it knows which match to use when.
It may be a light version of Dnsmasq, but it is still Dnsmasq.
