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 last edited by Wayne Workman
@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 and
undionly.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:
Another 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 be
service dhcpd stop;service dhcpd disable
Here is more info on .fogsettings if you get lost or curious:
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?
Wayne Workman last edited by
@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 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
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 last edited by
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?
@dureal99d To add on further, backwards compatible does not mean, LEGACY, is “forwards compatible”
@dureal99d It will not automatically recognize the difference. UEFI will not auto boot to another type system. Essentially, as I understand it, all “UEFI is backwards compatible” means is UEFI Motherboards will allow Legacy style systems to work, but it doesn’t necessarily have to do this “on the fly”.
tools you’re trying to boot don’t support UEFI mode. Maybe you left Secure Boot on BIOS. Or maybe it’s something else entirely.
Check those two things for us first, if for nothing else but to rule them out
I have tried and I get the error “VFS: Unable to mount root?”
I am confused as to why I would experience this error on booting Linux isos when they say uefi is backwards compatible.
Should it not stand to reason that I should not have to change anything as relates to boot codes?
@dureal99d This will depend entirely on what you’re trying to boot and how your machines are setup and what not.
Maybe the tools you’re trying to boot don’t support UEFI mode. Maybe you left Secure Boot on BIOS. Or maybe it’s something else entirely.
Check those two things for us first, if for nothing else but to rule them out.
extra stuff such as you want to boot iso images, and foreign kernels via the FOG iPXE menus
Yes!!! Iso images and foreign kernels, why can I not boot them in uefi mode, or rather why am I getting this error?
Could you clarify what “extra stuff” you are talking about?
Is that extra stuff that comes with FOG, or extra stuff such as you want to boot iso images, and foreign kernels via the FOG iPXE menus?
Just to be clear, the FOG Client is service that gets loaded into a target OS to allow the FOG server to interact with the target OS. Les make sure we are talking about the same function.