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

    Boot menu configuration

    Scheduled Pinned Locked Moved
    Linux Problems
    3
    18
    4.2k
    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.
    • B
      BedCruncher
      last edited by BedCruncher

      This post is deleted!
      1 Reply Last reply Reply Quote 0
      • B
        BedCruncher
        last edited by

        Ran across another issue with a different piece of software that I was trying to add to the boot menu. It’s the HDT Tool project. What I currently have done is attempted to use an old config and files from a previous PXE server while modifying the relevant boot menu options.

        I’ve also downloaded a bootable iso from the HDT site directly and mounted it in the same way as was done with the DBAN instructions. My current HDT boot configuration looks like.
        0_1469718773425_upload-89fe83dc-9df4-4f58-9aca-652a52560214 with the url located at that address showing
        0_1469718747308_upload-19c1aab6-dd48-46df-b832-599354fd1f0c

        Can anyone offer advice/help on this?

        1 Reply Last reply Reply Quote 0
        • B
          BedCruncher
          last edited by

          Don’t know why it isn’t putting the images in the reply correctly. to clarify the above.

          Boot Menu Entry

          Menu Item: 
          HDT
          
          Description: 
          Hardware Detection Tool
          
          Parameters: 
          kernel ${boot_url}/hdt/isolinux/hdt.c32
          boot
          

          URL Directory Listing

          backgnd.png
          boot.cat
          chain.c32
          display.png
          hdt.c32
          isolinux.bin
          isolinux.cfg
          memtest.bin
          menu.c32
          modules.ali
          pci.ids
          red.png
          
          Q Tom ElliottT 2 Replies Last reply Reply Quote 0
          • Q
            Quazz Moderator @BedCruncher
            last edited by

            @BedCruncher c32 is pxelinux files as far as I know.

            You’ll probably need to chain it or something.

            B 1 Reply Last reply Reply Quote 0
            • B
              BedCruncher @Quazz
              last edited by

              @Quazz
              Do you have a link showing how to do that with the new FOG 1.3 boot menus?

              Q 1 Reply Last reply Reply Quote 0
              • Q
                Quazz Moderator @BedCruncher
                last edited by

                @BedCruncher Try changing kernel to chain

                Could be enough, not sure.

                B 1 Reply Last reply Reply Quote 0
                • B
                  BedCruncher @Quazz
                  last edited by BedCruncher

                  @Quazz
                  Just changed. Will have to wait a bit before I can test that. I’m also upgrading that laptop to W10 to beat the deadline. Will post back once I can try again.

                  EDIT:
                  After modifying the menu entry as you wanted me to do, I simply get a black screen with blinking cursor.

                  1 Reply Last reply Reply Quote 0
                  • Tom ElliottT
                    Tom Elliott @BedCruncher
                    last edited by

                    @BedCruncher said in Boot menu configuration:

                    URL Directory Listing
                    backgnd.png
                    boot.cat
                    chain.c32
                    display.png
                    hdt.c32
                    isolinux.bin
                    isolinux.cfg
                    memtest.bin
                    menu.c32
                    modules.ali
                    pci.ids
                    red.png

                    What’s the variable for ${boot_url} set to?

                    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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                    B 1 Reply Last reply Reply Quote 0
                    • B
                      BedCruncher @Tom Elliott
                      last edited by

                      @Tom-Elliott
                      set fog-ip 192.168.240.10
                      set fog-webroot fog
                      set boot-url http://${fog-ip}/${fog-webroot}

                      Q 1 Reply Last reply Reply Quote 0
                      • Q
                        Quazz Moderator @BedCruncher
                        last edited by

                        @BedCruncher Try chaining the menu file. Or maybe isolinux.bin

                        B 1 Reply Last reply Reply Quote 0
                        • B
                          BedCruncher @Quazz
                          last edited by

                          @Quazz
                          Tried both, menu.c32 gives same blinking cursor. isolinux.bin provides the following.
                          0_1469801003596_upload-718e181a-5129-4d44-a653-add20c4c0847

                          Q 1 Reply Last reply Reply Quote 0
                          • Q
                            Quazz Moderator @BedCruncher
                            last edited by

                            @BedCruncher Alright, so essentially, isolinux.bin is the correct one to use, but you need to edit isolinux.cfg so that it can boot over the network and doesn’t get stuck looking for the CD.

                            Unfortunately, I’m not entirely sure how to do that properly, if it’s even possible at all.

                            Also, I notice you shared hdt/isolinux folder contents, but what’s in hdt itself?

                            B 2 Replies Last reply Reply Quote 0
                            • B
                              BedCruncher @Quazz
                              last edited by

                              @Quazz
                              the folder hdt is simply the mount point for the iso. It houses only the subfolder isolinux which contains the folder contents listed above. I will delve into the isolinux.cfg file to see where I can tweak it.Will report back with anything I can find.

                              1 Reply Last reply Reply Quote 0
                              • B
                                BedCruncher @Quazz
                                last edited by

                                @Quazz
                                OK!!! Houston we have liftoff…

                                I was able to get this working by completely ignoring mounting the iso at all and instead doing what I had found in another forum with directly using memdisk and the raw iso. My working config for this is as follows

                                0_1469802843514_upload-365ae328-e013-4ad9-b6cc-2f6183ce8087

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

                                165

                                Online

                                12.0k

                                Users

                                17.3k

                                Topics

                                155.2k

                                Posts
                                Copyright © 2012-2024 FOG Project