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

    Issues booting UEFI devices a

    Scheduled Pinned Locked Moved Solved
    Tutorials
    4
    32
    9.6k
    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.
    • george1421G
      george1421 Moderator @cnkpadobi
      last edited by

      @cnkpadobi said in Issues booting UEFI devices a:

      @george1421 so if I run the sudo netstat -an|grep 4011 it should give me something correct versus taking me back to the prompt?

      If it takes you back to the command prompt, then that tells us the dnsmasq is NOT running on your fog server.

      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
      • C
        cnkpadobi @george1421
        last edited by

        @george1421

        YES, all 3 config files are in that directory

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

          @cnkpadobi lets remove all but the correct one (like the one I posted). We can only have one configuration file in there with the options I provided. AND if that is the case /etc/dnsmasq.conf should remain unchanged from the original install.

          I would suggest that we keep the standard file of /etc/dnsmasq.d/ltsp.conf and then remove the rest.

          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!

          C 1 Reply Last reply Reply Quote 0
          • C
            cnkpadobi @george1421
            last edited by

            @george1421 should those configure files be rename or removed?

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

              @cnkpadobi removed. If its there it will be read. If you are concerned about the content then move them to /root (root’s home) or some other location, but not in the /ete/dnsmasq.d path.

              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
              • C
                cnkpadobi
                last edited by

                ok sorry,

                So I am still gett this error
                dnsmasq: bad option at line 2 of /etc/dnsmasq.d/q

                the only thing inthe ltsp.conf on line two is port=0

                there are no other config files in the directory

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

                  @cnkpadobi

                  In your ltsp.conf file add in the following lines below this one

                  # PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
                  pxe-prompt="Booting FOG Client", 1
                  
                  

                  and before the

                  dhcp-range=<fog_server_ip>,proxy
                  

                  Insert these:

                  # PXEClient:Arch:00000
                  pxe-service=X86PC, "Boot BIOS PXE", undionly.kpxe
                  
                  # PXEClient:Arch:00007
                  pxe-service=BC_EFI, "Boot UEFI PXE-BC", ipxe.efi
                  
                  # PXEClient:Arch:00009
                  pxe-service=X86-64_EFI, "Boot UEFI PXE-64", ipxe.efi
                  

                  These lines are only needed when your main dhcp server is giving conflicting next server information. Lets see if that fixes your uefi booting.

                  There is one additional condition that dnsmasq can (mask), this is where you force the next server as part of the pxe service command, where you append the IP address of your fog server to the pxe-service line. You will need to do this for each pxe-service command in your ltsp.conf file you inserted above.

                  pxe-service=BC_EFI, "Boot UEFI PXE-BC",ipxe.efi,<fog_server_ip>
                  

                  (this post is in response to several IM chat sessions to get the OP going. legacy mode is working, its just giving the uefi systems an error during iPXE kernel booting)

                  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!

                  C 1 Reply Last reply Reply Quote 0
                  • C
                    cnkpadobi @george1421
                    last edited by

                    @george1421 Thanks for this… just a quick clarification is there a space after the comma before the ip address

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

                      @cnkpadobi Only for humans to understand, computers don’t care. Space or no space it works the same.

                      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
                      • C
                        cnkpadobi
                        last edited by

                        this worked great issue resolved.

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

                        156

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project