FOG Project

    • Register
    • Login
    • Search
    • Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    what tftp image is right to use?

    General Problems
    2
    8
    177
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      fabritrento last edited by fabritrento

      What tftp image is right to use?

      I started configuring undionly.kpxe image on the dhcp server.

      all works, but i think that is the legacy bios image. what to use with uefi images?

      in a network with a mix of legacy and uefi bios howto configure both?

      images available is:

      10secdelay boot.txt i386-efi intel.kkpxe intel.pxe ipxe.iso ipxe.kpxe ipxe.lkrn ipxe.usb ncm–ecm–axge.efi realtek.kkpxe realtek.pxe snponly.efi undionly.kpxe
      arm64-efi default.ipxe intel.efi intel.kpxe ipxe.efi ipxe.kkpxe ipxe.krn ipxe.pxe memdisk realtek.efi realtek.kpxe snp.efi undionly.kkpxe undionly.pxe

      george1421 1 Reply Last reply Reply Quote 0
      • george1421
        george1421 Moderator @fabritrento last edited by

        @fabritrento said in what tftp image is right to use?:

        PXEClient:Arch:00007

        FWIW there are 3 or 4 uefi arch classes. I would at least create arch 7 and arch 9 classes, the others are for 32 bit processors.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        1 Reply Last reply Reply Quote 0
        • F
          fabritrento @george1421 last edited by

          @george1421 in this way don’t work i created 2 vendor classes, one PXEClient:Arch:00007 for uefi and onother PXEClient:Arch:00000 for legacy and in this way all works

          george1421 1 Reply Last reply Reply Quote 0
          • george1421
            george1421 Moderator @fabritrento last edited by

            @fabritrento For the legacy policy you just define the default dhcp options 66 and 67 for bios. So how it works is if there is not a uefi policy match it sends the bios boot file name. If there is a policy match then it sends the uefi boot file name.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            F 1 Reply Last reply Reply Quote 0
            • F
              fabritrento @george1421 last edited by

              @george1421 i defined uefi policy… but the wiki don’t tell me howto define legacy policy… what are the string that i must insert for legacy boot?

              george1421 1 Reply Last reply Reply Quote 0
              • F
                fabritrento @fabritrento last edited by

                @fabritrento the cause was a bad setting in the bios now ipxe.efi works thankyou very much

                1 Reply Last reply Reply Quote 0
                • F
                  fabritrento @george1421 last edited by

                  @george1421 i have a i5 hp pc that has efi bios.

                  the only image that i can run correctly is undionly.kpxe (bios). If I try to use one of *.efi images the bios hangs, none of available works.
                  There are a reason?
                  I want to use efi version and not the bios version because all pc on my network are efi

                  F 1 Reply Last reply Reply Quote 0
                  • george1421
                    george1421 Moderator @fabritrento last edited by

                    @fabritrento for uefi boot you need ipxe.efi or snp.efi to boot.

                    If you have a windows 2012 or later dhcp server you can use these instructions to make a dynamic pxe boot. https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy
                    If you have some other dhcp server like from firewall or router we can use another method to give dynamic (bios or uefi) boot files.

                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                    F 2 Replies Last reply Reply Quote 0
                    • 1 / 1
                    • First post
                      Last post

                    179
                    Online

                    10.2k
                    Users

                    16.3k
                    Topics

                    149.9k
                    Posts

                    Copyright © 2012-2020 FOG Project