Posts made by dureal99d

@george1421 if I am reading right this will work with your router as the dhcp

@george1421 I will get to it soon as I get home from work!!! as always I will report back!!!

@george1421 Cool ill be looking forward to that!!!

@george1421 do you have a how to compile your own dnsmasq?

Server

• FOG Version: RC11
• OS: Ubuntu 16.04

Client

• Service Version: 11.5
• OS: Windows 10 and Ubuntu 16.04

Description

I have been on a mission to dual boot Legacy and UEFI.

this configuration works but only boots clients that support ipxe.efi!! but boots far less:

dhcp-boot=undionly.kpxe,,192.168.1.109
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

I have finally succeeded in booting every unfit Machine using the 7156 strain. However there is an issue. I’m getting an dhcp error.

dhcp-boot=undionly.kpxe,,192.168.1.109
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-match=set:efibc,option:client-arch,7
dhcp-boot=tag:efibc,intel.efi,,192.168.1.109
dhcp-match=set:i386-efi/intel.efi,option:client-arch,6
dhcp-boot=tag:i386-efi/intel.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,7
dhcp-boot=tag:efi-x86_64,intel.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,8
dhcp-boot=tag:efi-x86_64,intel.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,9
dhcp-boot=tag:efi-x86_64,intel.efi,,192.168.1.109
dhcp-match=set:efibc,option:client-arch,7
dhcp-boot=tag:efibc,realtek.efi,,192.168.1.109
dhcp-match=set:i386-efi/realtek.efi,option:client-arch,6
dhcp-boot=tag:i386-efi/realtek.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,7
dhcp-boot=tag:efi-x86_64,realtek.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,8
dhcp-boot=tag:efi-x86_64,realtek.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,9
dhcp-boot=tag:efi-x86_64,realtek.efi,,192.168.1.109
dhcp-match=set:efibc,option:client-arch,7
dhcp-boot=tag:efibc,snp.efi,,192.168.1.109
dhcp-match=set:i386-efi/snp.efi,option:client-arch,6
dhcp-boot=tag:i386-efi/snp.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,7
dhcp-boot=tag:efi-x86_64,snp.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,8
dhcp-boot=tag:efi-x86_64,snp.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,9
dhcp-boot=tag:efi-x86_64,snp.efi,,192.168.1.109
dhcp-match=set:efibc,option:client-arch,7
dhcp-boot=tag:efibc,snponly.efi,,192.168.1.109
dhcp-match=set:i386-efi/snponly.efi,option:client-arch,6
dhcp-boot=tag:i386-efi/snponly.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,7
dhcp-boot=tag:efi-x86_64,snponly.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,8
dhcp-boot=tag:efi-x86_64,snponly.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,9
dhcp-boot=tag:efi-x86_64,snponly.efi,,192.168.1.109
dhcp-match=set:efibc,option:client-arch,7
dhcp-boot=tag:efibc,snponly7156.efi,,192.168.1.109
dhcp-match=set:i386-efi/snponly7156.efi,option:client-arch,6
dhcp-boot=tag:i386-efi/snponly7156.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,7
dhcp-boot=tag:efi-x86_64,snponly7156.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,8
dhcp-boot=tag:efi-x86_64,snponly7156.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,9
dhcp-boot=tag:efi-x86_64,snponly7156.efi,,192.168.1.109
dhcp-match=set:efibc,option:client-arch,7
dhcp-boot=tag:efibc,ipxe7156.efi,,192.168.1.109
dhcp-match=set:i386-efi/ipxe7156.efi,option:client-arch,6
dhcp-boot=tag:i386-efi/ipxe7156.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,7
dhcp-boot=tag:efi-x86_64,ipxe7156.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,8
dhcp-boot=tag:efi-x86_64,ipxe7156.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,9
dhcp-boot=tag:efi-x86_64,ipxe7156.efi,,192.168.1.109
dhcp-match=set:efibc,option:client-arch,7
dhcp-boot=tag:efibc,snp7156.efi,,192.168.1.109
dhcp-match=set:i386-efi/snp7156.efi,option:client-arch,6
dhcp-boot=tag:i386-efi/snp7156.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,7
dhcp-boot=tag:efi-x86_64,snp7156.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,8
dhcp-boot=tag:efi-x86_64,snp7156.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,9
dhcp-boot=tag:efi-x86_64,snp7156.efi,,192.168.1.109
dhcp-match=set:efibc,option:client-arch,7
dhcp-boot=tag:efibc,realtek7156.efi,,192.168.1.109
dhcp-match=set:i386-efi/realtek7156.efi,option:client-arch,6
dhcp-boot=tag:i386-efi/realtek7156.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,7
dhcp-boot=tag:efi-x86_64,realtek7156.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,8
dhcp-boot=tag:efi-x86_64,realtek7156.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,9
dhcp-boot=tag:efi-x86_64,realtek7156.efi,,192.168.1.109
dhcp-match=set:efibc,option:client-arch,7
dhcp-boot=tag:efibc,intel7156.efi,,192.168.1.109
dhcp-match=set:i386-efi/intel7156.efi,option:client-arch,6
dhcp-boot=tag:i386-efi/intel7156.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,7
dhcp-boot=tag:efi-x86_64,intel7156.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,8
dhcp-boot=tag:efi-x86_64,intel7156.efi,,192.168.1.109
dhcp-match=set:efi-x86_64,option:client-arch,9
dhcp-boot=tag:efi-x86_64,intel7156.efi,,192.168.1.109```

@Joe-Schmitt You are welcome! Fogs ability to deploy snapins is awesome and deserves acknowledgement.

I hope this tutorial on how to install Microsoft office is helpful to you.

The process is relatively simple with a little know how and planning.

follow the steps and you cant go wrong.

here

I goofed a bit on spelling and this is my first tutorial ever so be easy on me.

Good day!!!

@Tom-Elliott said in UEFI won boot tools via fog menu.:

hink

I see!! that’s great to know!!!

@Tom-Elliott Yes i have tested the booting of the Linux isos in both bios and uefi and they work the same.

@dureal99d I run ddwrt sp2 v24 and being as it has successfully dual booted bios and uefi is it safe to say that it has the correct version of dnsmasq to handle the job?

@dureal99d for the Linux distros the argument initrd=initrd.lz was missing. that’s crazy!!!

@Tom-Elliott said in UEFI won boot tools via fog menu.:

kernel http://${fog-ip}/bootimgs/16.04.1_64/casper/vmlinuz.efi
initrd http://${fog-ip}/bootimgs/16.04.1_64/casper/initrd.lz
imgargs vmlinuz.efi initrd=initrd.lz root=/dev/nfs boot=casper netboot=nfs nfsroot=${fog-ip}:/var/www/html/bootimgs/16.04.1_64/ locale=en_US.UTF-8 keyboard-configuration/layoutcode=la mirror/country=US
boot || goto failed
goto start

your edit to my config file works flawlessly!!!

THank you @Tom-Elliott @Quazz @Wayne-Workman @george1421 & @Moderators @Senior-Developers @Developers.

this has been one heck of a trip but it was worth it in the end.
t

@Tom-Elliott said in UEFI won boot tools via fog menu.:

@dureal99d ISO’s can be created to run in only “BIOS” mode. This means, while UEFI is backwards compatible from a support perspective, the ISO’s have no idea how to use UEFI. BIOS expects certain things to run. You must remember BIOS booting has been around, essentially, since the beginning of personal computers. UEFI is relatively new so simply saying “UEFI is supposed to be backwards compatible” doesn’t mean much. EFI has been around for quite some time, but only recently has it been in “major” use.

I understand.

@Tom-Elliott Ok I’m going to try that now

also i tried this config and its getting farther than before by loads

initrd http://${fog-ip}/bootimgs/16.04.1_64/casper/initrd.lz
chain http://${fog-ip}/bootimgs/16.04.1_64/casper/vmlinuz.efi initrd=initrd.lz root=http://${fog-ip}/bootimgs/16.04.1_64/casper/squashfs
ip=dhcp – || read void
boot || goto MENU```

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

know why it would work in BIOS mode

yes I am also at a loss, that is also what I find strange, I see no reason I can upload and download an image but not boot these isos in uefi mode. its crazy to me. but ive read uefi is pretty pick about stuff so who knows?

@Quazz Keep in mind in bios boot mode these options work just fine, the issue exist in uefi mode.

also, what is a trailing slash?

@Quazz

@Quazz

dureal99d@dureal99d-Precision-WorkStation-T5400:~$ sudo exportfs -a
exportfs: duplicated export entries:
exportfs: 	*:/opt/bootimgs
exportfs: 	*:/opt/bootimgs
dureal99d@dureal99d-Precision-WorkStation-T5400:~$ showmount -e 127.0.0.1
Export list for 127.0.0.1:
/opt/bootimgs *
/images2/dev  *
/images2      *
/images/dev   *
/images       *
dureal99d@dureal99d-Precision-WorkStation-T5400:~$ ```

Does this look right?

/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)
/images2 *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=2)
/images2/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=3)
/var/www/html/bootimgs *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=4)
/opt/bootimgs *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=5)

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

showmount -e 127.0.0.1

dureal99d@dureal99d-Precision-WorkStation-T5400:~$ sudo exportfs -a
exportfs: /etc/exports [5]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/var/www/html/bootimgs".
  Assuming default behaviour ('no_subtree_check').
  NOTE: this default has changed since nfs-utils version 1.0.x

exportfs: /etc/exports [6]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/opt/bootimgs".
  Assuming default behaviour ('no_subtree_check').
  NOTE: this default has changed since nfs-utils version 1.0.x

exportfs: duplicated export entries:
exportfs: 	*:/opt/bootimgs
exportfs: 	*:/opt/bootimgs
dureal99d@dureal99d-Precision-WorkStation-T5400:~$ showmount -e 127.0.0.1
Export list for 127.0.0.1:
/opt/bootimgs *
/images2/dev  *
/images2      *
/images/dev   *
/images       *

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

i see add

@Quazz I shall add fsid= to the export and shall report back