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

Extra menus / Advanced menu no longer working in 1.3.5

Scheduled Pinned Locked Moved Solved
Bug Reports
3
8
2.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.
  • A
    AndrewC
    last edited by Feb 16, 2017, 4:29 PM

    Server
    • FOG Version: 1.3.5-RC-7
    • OS: Ubuntu 16.04
    Description

    I posted previously about custom menus not working under UEFI, but working okay with BIOS booting. I have since come to realize that all custom menus are no longer working no matter what image I am booting (tested with a VM as well as 3 different physical systems). I understand that since I’m using the latest RC that there are bound to be bugs, but I have not seen anyone else report this problem as of yet.

    As a test I enabled the built-in Advanced menu item, and made it accessible to all. I then wrote a very simple 2-line menu to see if it would work to no avail. I got the same result:

    Usage:
    
      choose [-m|–menu <menu>] [-d|–default <default>] [-t|–timeout <timeout>] [-k|–keep] <setting>
    
    See http://ipxe.org/cmd/choose for further information
    Could not boot: Result too large (http://ipxe.org/46162085)
    Could not boot: Result too large (http://ipxe.org/46162085)
    Chainloading failed, hit ‘s’ for the iPXE shell; reboot in 10 seconds
    

    It seems the “choose” command in the menus is somehow not the correct perimeters, but I was not able to get the menu to display no matter how I set it. This worked perfectly fine until about the 1.3.5 RCs. I’m not sure if this is an overall bug, or some kind of mis-configuration of my system. Any ideas?

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by Feb 16, 2017, 4:34 PM

      Can you give us your advanced menu to actually look at?

      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

      1 Reply Last reply Reply Quote 0
      • A
        AndrewC
        last edited by Feb 16, 2017, 5:11 PM

        Here is an example of the test menu I threw together in Advanced just to see if I could get it to work:

        menu Just a Test Menu
        item DebianTest Run the Debian 8.7.1 (64-bit) net/installer
        item ReturnTest Return to previous
        choose target && goto ${target}
        :DebianTest
        kernel http://${fog-ip}/debian87x/linux
        initrd http://${fog-ip}/debian87x/initrd.gz
        imgargs linux vga=788
        boot || goto MENU
        :ReturnTest
        chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || prompt
        goto MENU
        

        Regardless of what is included in the menu or how much… it always fails with the usage statement for the “choose” command. I have tried every possible way to phrase that command, but get the same result. “choose target && goto ${target}” in the test menu was taken right from the iPXE.org website.

        1 Reply Last reply Reply Quote 0
        • T
          Tom Elliott
          last edited by Feb 16, 2017, 5:23 PM

          Please update to RC 8. I just pushed it up and it corrects this, which is why I moved this into the “bugs” and solved it.

          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

          A 1 Reply Last reply Feb 16, 2017, 5:51 PM Reply Quote 0
          • J
            Junkhacker Developer
            last edited by Junkhacker Feb 16, 2017, 11:32 AM Feb 16, 2017, 5:28 PM

            edit: never mind

            signature:
            Junkhacker
            We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

            1 Reply Last reply Reply Quote 0
            • A
              AndrewC @Tom Elliott
              last edited by AndrewC Feb 16, 2017, 11:54 AM Feb 16, 2017, 5:51 PM

              @Tom-Elliott said in Extra menus / Advanced menu no longer working in 1.3.5:

              Please update to RC 8. I just pushed it up and it corrects this, which is why I moved this into the “bugs” and solved it.

              You da man! RC-8 definitely fixed the custom menus. They now load perfectly fine in BIOS or EFI. Everything boots successfully from the menus with one exception… apparently Memtest is now broken. Running Memtest stops loading, and it hangs at “Loading boot sector… booting…”

              Edit: Nevermind… the Memtest issue was related to a buggy test machine. It works on all others. Disregard

              T 1 Reply Last reply Feb 16, 2017, 5:54 PM Reply Quote 0
              • T
                Tom Elliott @AndrewC
                last edited by Feb 16, 2017, 5:54 PM

                @AndrewC I’m not seeing the problem, but I would imagine you are seeing this in particular with EFI style systems?

                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

                A 1 Reply Last reply Feb 16, 2017, 5:59 PM Reply Quote 0
                • A
                  AndrewC @Tom Elliott
                  last edited by Feb 16, 2017, 5:59 PM

                  @Tom-Elliott said:

                  @AndrewC I’m not seeing the problem, but I would imagine you are seeing this in particular with EFI style systems?

                  Yes. It was an issue with the particular test machine. Did not have a problem with any others BIOS or EFI. Worry not.

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

                  139

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project