I need help setting up efi pxe boot, bios boot already works

[robmorin]

Hello all... I have non uefi or bios boot via pxe working just fine, however i am confused on how to get uefi working as our new Dell laptops are uefi only.

Has anyone done this before?

ANy help appreciated.

[robmorin]

So I am getting somewhere now, I setup dnsmasq to also have efi booting like so:

dhcp-match=x86PC, option:client-arch, 0 #BIOS x86
dhcp-match=BC_EFI, option:client-arch, 7 #EFI x86-64

# Set boot file name only when tag is "bios" or "uefi"
dhcp-boot=tag:x86PC,/tftpboot/bios/pxelinux.0,zion,192.168.2.253 # for Legacy BIOS detected by dhcp-match above
dhcp-boot=tag:BC_EFI,/tftpboot/uefi/syslinux.efi,zion,192.168.2.253 # for UEFI arch detected by dhcp-match above

my dir on the tftp server is like:

/tftpboot/bios/
ifl.ini
azerty.ktl
fgGIod.ktl
vmlinuz
pxelinux.0
pxelinux.cfg/default
qwerty.ktl
qwertz.ktl
menu.txt
dvorak.ktl
initrmfs.gz

/tftpboot/uefi/
vmlinuz - Copied from the above dir?
initrmfs.gz - Copied from above dir?
pxelinux.cfg/default
ldlinux.e64
syslinux.efi



pxelinux.cfg/default looks like this a copy from above dir:
timeout 50
kbdmap qwerty.ktl
prompt 1
display menu.txt
default 2
label 1
kernel vmlinuz
append vga=794 switchx=yes iflkmap=us ktl=qwerty initrd=initrmfs.gz iflbflag=0
label 2
kernel vmlinuz
append vga=791 switchx=yes iflkmap=us ktl=qwerty initrd=initrmfs.gz iflbflag=0
label 3
kernel vmlinuz
append vga=788 switchx=yes iflkmap=us ktl=qwerty initrd=initrmfs.gz iflbflag=0
label 4
kernel vmlinuz
append vga=785 switchx=yes iflkmap=us ktl=qwerty initrd=initrmfs.gz iflbflag=0
label 4gh
kernel vmlinuz
append vga=791 switchx=yes mem=2G iflkmap=us ktl=qwerty initrd=initrmfs.gz iflbflag=0


When the laptop boots it gets a DHCP address and finds the uefi and runs vmlinuz, but then freezes at loading initrmfs.gz
Any ideas?
Thanks..

[TeraByte Support]

Hello,

Use the x64 kernel version.

That will probably start being the default on the next update as well.

On 9/17/2019 7:51 AM, robmorin wrote:
> So I am getting somewhere now, I setup dnsmasq to also have efi booting like so:
>
> dhcp-match=x86PC, option:client-arch, 0 #BIOS x86
> dhcp-match=BC_EFI, option:client-arch, 7 #EFI x86-64
>
> # Set boot file name only when tag is "bios" or "uefi"
> dhcp-boot=tag:x86PC,/tftpboot/bios/pxelinux.0,zion,192.168.2.253 # for Legacy BIOS detected by dhcp-match above
> dhcp-boot=tag:BC_EFI,/tftpboot/uefi/syslinux.efi,zion,192.168.2.253 # for UEFI arch detected by dhcp-match above
>
> my dir on the tftp server is like:
>
> /tftpboot/bios/
> ifl.ini
> azerty.ktl
> fgGIod.ktl
> vmlinuz
> pxelinux.0
> pxelinux.cfg/default
> qwerty.ktl
> qwertz.ktl
> menu.txt
> dvorak.ktl
> initrmfs.gz
>
> /tftpboot/uefi/
> vmlinuz - Copied from the above dir?
> initrmfs.gz - Copied from above dir?
> pxelinux.cfg/default
> ldlinux.e64
> syslinux.efi
>
>
>
> pxelinux.cfg/default looks like this a copy from above dir:
> timeout 50
> kbdmap qwerty.ktl
> prompt 1
> display menu.txt
> default 2
> label 1
> kernel vmlinuz
> append vga=794 switchx=yes iflkmap=us ktl=qwerty initrd=initrmfs.gz iflbflag=0
> label 2
> kernel vmlinuz
> append vga=791 switchx=yes iflkmap=us ktl=qwerty initrd=initrmfs.gz iflbflag=0
> label 3
> kernel vmlinuz
> append vga=788 switchx=yes iflkmap=us ktl=qwerty initrd=initrmfs.gz iflbflag=0
> label 4
> kernel vmlinuz
> append vga=785 switchx=yes iflkmap=us ktl=qwerty initrd=initrmfs.gz iflbflag=0
> label 4gh
> kernel vmlinuz
> append vga=791 switchx=yes mem=2G iflkmap=us ktl=qwerty initrd=initrmfs.gz iflbflag=0
>
>
> When the laptop boots it gets a DHCP address and finds the uefi and runs vmlinuz, but then freezes at loading initrmfs.gz
> Any ideas?
> Thanks..
>
>

[robmorin]

Use the 64 bit version of what IFL, how do i know if its the 64 bit version its, not like it says ifl64 or anything?

[timg11]

I'm just looking into setting up a TFTP server for PXE boot to IFL.
I read the KB https://www.terabyteunlimited.com/kb/article.php?id=597, and the process is clearly meant to run from Linux.

I normally create IFL media using Makedisk, which is Windows.

From the KB, running the ./makePXE is the first step.

But what is the environment that script is run from?

Is it run from an arbitrary system booted into IFL from temporary media (bootable USB or CDROM)?
Or does IFL need to be installed into a desktop Ubuntu or similar environment before running the script?

[TeraByte Support(PP)]

robmorin wrote:
> Use the 64 bit version of what IFL, how do i know if its the 64 bit version
> its, not like it says ifl64 or anything?

The 64-bit version of IFL is available to download from your account. It's the "English (x64) Download" version in the IFL section.

[TeraByte Support(PP)]

timg11 wrote:
> I'm just looking into setting up a TFTP server for PXE boot to IFL.
> I read the KB https://www.terabyteunlimited.com/kb/article.php?id=597, and
> the process is clearly meant to run from Linux.
>
> I normally create IFL media using Makedisk, which is Windows.
>
> From the KB, running the ./makePXE is the first step.
>
> But what is the environment that script is run from?
>
> Is it run from an arbitrary system booted into IFL from temporary media
> (bootable USB or CDROM)?
> Or does IFL need to be installed into a desktop Ubuntu or similar
> environment before running the script?

I think it would normally be run from a Linux installation (could be installed in a VM, for example, if a real install isn't wanted or available). Using an installed Linux is nicer for tweaking things since you don't need to recreate the custom builds every time.

If you run it when booted to IFL you'll need to run the iflbuild script (right-click desktop and select "Create IFL Boot Media") and use the "Zip File Mode" option. This means that you'll first need to copy in the IFL zip download you want to use (ifl_en_gui.zip, for example) so it's available. Once the files have been extracted you can exit the script, open a terminal, and go into the iflbuild folder. From there, run the makePXE script to generate the files (will be placed into the "pxe" folder).