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

    add Ventoy to boot menu

    Scheduled Pinned Locked Moved
    Feature Request
    5
    23
    7.7k
    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 @youzersef
      last edited by

      @youzersef Understand I’m just making some guesses here because I don’t know ventoy. But if you look at the ventoy document link I provided. There is a section that talks about a drop down list on the configuration page where you need to change the dhcp server mode to ExternalNet.

      The second thing is it looks like they are running a customized version of iPXE (same thing fog uses as boot loader) but its qualifying the name and it doesn’t like ipxe.efi as the file name because its not its own app. I think this is why the error is being thrown.

      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!

      Y 1 Reply Last reply Reply Quote 0
      • Y
        youzersef @george1421
        last edited by youzersef

        @george1421 i changed to ExternalNet. but nothing has been changed. I found something in the community of ventoy which could help me.

        maybe you can tell me what the post means. because am not good enough in pxe.

        https://forums.ventoy.net/showthread.php?tid=2743

        someone posted:

        
        I managed to chainload from my main iPXE to iVentoy, basically you need to do following things:
        1. In your main iPXE boot.ipxe file, set user-class to a specific value, such as MyCustomClass
        2. In your dhcp server, match this user-class and send next-server as your iVentoy IP
        3. In your main iPXE boot.ipxe, run 'dhcp' command, after 'set user-class MyCustomClass' command, then 'chain tftp://${next-server}/iventoy_loader_16000'
        Done 
        
        1 Reply Last reply Reply Quote 0
        • B
          baovipboy156
          last edited by

          fog > ipxe menu > add option:

          set net0/next-server 192.168.1.254
          chain --replace --autofree ipxe.x64.snponly.efi.0
          

          on ubuntu fog server: edit file /etc/dhcp/dhcpd.conf

          class "UEFI-64-1" {
              match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
              if exists user-class and option user-class = "iVentoy"{
              filename "iventoy_loader_16000_uefi";
              next-server 192.168.152.254;
          } else {
              filename "ipxe.efi";
          }
          }
          

          i manged to chain ventoy but the graphic is bugged

          Y M 2 Replies Last reply Reply Quote 2
          • Y
            youzersef @baovipboy156
            last edited by

            @baovipboy156

            i tried on test server it is pfsense as DHCP-Server it works… Thank you.

            i will try it on my main Server next week 🙂 … it is windows server.

            @george1421 if you want i can post the configuration that i used to configure iventoy as next server after fog server… live photos:

            b9614ee7-11e4-4d6c-afb6-d9eb0a4b5100-grafik.png

            after i chose iVentoy…

            6671773f-2caa-44e6-a6a6-2d5b00b7a035-grafik.png

            thank you guys you made my day… 🙂

            george1421G B 2 Replies Last reply Reply Quote 1
            • george1421G
              george1421 Moderator @youzersef
              last edited by

              @youzersef said in add Ventoy to boot menu:

              if you want i can post the configuration that i used to configure iventoy as next server after fog server

              If this info would help the next guy, I would say yes. That way we can all learn from someone that has already walked the bloody path to victory. That’s what makes opensource and a community lead project work.

              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 1
              • B
                baovipboy156 @youzersef
                last edited by

                @youzersef
                Did you got the booting ISO working normally?, seem the graphic is bugged with some modern mainboard

                Y 1 Reply Last reply Reply Quote 0
                • Y
                  youzersef @baovipboy156
                  last edited by

                  @baovipboy156 i tested on vm and i did not get problems. I will test it on dell Laptops next week.

                  B 1 Reply Last reply Reply Quote 0
                  • B
                    baovipboy156 @youzersef
                    last edited by

                    @youzersef
                    I found it, root cause: screen resolution 39d260a7-cf2c-4fc3-b0eb-6d59310dae7c-image.png
                    some monitor can’t display 1024x768…wtf, then i set it to 1280x720 it work perfectly!

                    1 Reply Last reply Reply Quote 1
                    • Y
                      youzersef
                      last edited by youzersef

                      @george1421

                      do you have any idea how can i add the same rule on DHCP windows server?

                      class "UEFI-64-1" {
                          match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
                          if exists user-class and option user-class = "iVentoy"{
                          filename "iventoy_loader_16000_uefi";
                          next-server 10.132.7.113;
                      } else {
                          filename "ipxe.efi";
                      }
                      }
                      
                      george1421G 1 Reply Last reply Reply Quote 0
                      • george1421G
                        george1421 Moderator @youzersef
                        last edited by

                        @youzersef I don’t have an immediate answer for you, but I can point you in a direction. The FOG Project has a wiki page on how to setup policies in windows dhcp server. The first section of your code is outlined in the policy. https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence

                        You might be able to do the user class part too, but I don’t know. Windows dhcp server policies are very similar to what you can do in linux.

                        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
                        • M
                          microsam @baovipboy156
                          last edited by

                          @baovipboy156
                          thanks for your input, but cannot get it working with it…
                          would you please post more details and steps by steps to get it work, please…

                          iventoy1.20
                          fog 1.5.10.1615

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

                          189

                          Online

                          12.2k

                          Users

                          17.3k

                          Topics

                          155.5k

                          Posts
                          Copyright © 2012-2024 FOG Project