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

    Fog iPXE Menu no input

    Scheduled Pinned Locked Moved Unsolved
    FOG Problems
    8
    19
    844
    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.
    • Tom ElliottT
      Tom Elliott @jfernandz
      last edited by Tom Elliott

      @jfernandz next-server comes from the dhcp server option 66 (I think that’s what it is in Windows DHCP at least?)

      That said, often when next-server is empty it’s usually because there’s multiple dhcp servers trying to tell the same single client their next-server and it doesn’t know which one to use, so it just goes blank. That’s not to say it couldn’t be a firmware issue, but just expressing my past experiences.

      As for the Keyboard:

      @AxeMeAQuestion22 @jfernandz

      The “legacy” setting shouldn’t be a Firmware related/removed thing. It’d be under (generally) the USB options of the BIOS settings. Not “Legacy BIOS modes” or anything. Specifically it’d usually be surrounding the USB specifically.

      Now, I don’t have this particular gear, so I could be wrong, just again speaking from prior experiences of many different systems (in general.)

      Edit:

      Looking for what I see, if you’re using 3rd party keyboards (non standard that came with the system, or basic basic keyboards, it seems lenovo just might drop them beyond initial key entries (f1 for bios setup mode or whatever.)

      https://forums.lenovo.com/t5/ThinkCentre-A-E-M-S-Series/M90q-gen-5-usb-keyboard-not-working-in-bios/m-p/5358388

      This isn’t quite the same machine, but just kind of describing what I was thinking about with the USB Keyboard/Legacy Support.

      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

      jfernandzJ 1 Reply Last reply Reply Quote 0
      • J
        jegan1337 @jfernandz
        last edited by

        @jfernandz For what it’s worth, I have a bunch of m920q and brand new m75q Lenovo desktops that are all suddenly experiencing the same issue. Previously any keyboard (including 3rd party and bluetooth) could interact with the Fog iPXE menu with no problem. There hasn’t been any BIOS updates for the m920q models in quite some time and we’ve standardized our BIOS settings. It just seemingly stopped working after updating fog.

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

          @jegan1337 That’s possible, that maybe something is missing (or was removed from IPXE)

          If someone’s able to do a git bisect, figure out when it worked, figure out when it stopped.

          Likely you would first do:

          1.5.10

          now

          then use bisect to let it jujmp around and until you see when it narrows down exactly when it broke?

          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
          • jfernandzJ
            jfernandz @Tom Elliott
            last edited by

            @Tom-Elliott said in Fog iPXE Menu no input:

            @jfernandz next-server comes from the dhcp server option 66 (I think that’s what it is in Windows DHCP at least?)

            That said, often when next-server is empty it’s usually because there’s multiple dhcp servers trying to tell the same single client their next-server and it doesn’t know which one to use, so it just goes blank. That’s not to say it couldn’t be a firmware issue, but just expressing my past experiences.

            Hmm … my problem isn’t an empty value for next-server, rather … it comes with an IP, but its the DNS server IP address! 😲 …

            Regarding the keyboard issue … we are working with Dell Precission 3930 Rack machines, but we also have in the same cluster a couple of Dell Precission 7960 Rack machines where I didn’t tested, I can say a couple of days ago, we upgraded the BIOS of the 3930 which are the ones I can detect this issue, that’s why I was guessing this could be a problem between iPXE and upgraded firmware 🤔

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

              @jfernandz It’s probably a combination of both. At least, best what i can tell about the 3930’s at least?

              Either way, similar to the post about bisect, below, might help us out as well.

              I mean firmware nearly always plays a part in things, but that’s not to say that something with the iPXE code is not at fault, either.

              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

              jfernandzJ 1 Reply Last reply Reply Quote 0
              • jfernandzJ
                jfernandz @Tom Elliott
                last edited by

                @Tom-Elliott said in Fog iPXE Menu no input:

                Either way, similar to the post about bisect, below, might help us out as well.

                I’d need more details, some article or document on how to perform this bisect, but I’m interested in contributing, sure 😉

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

                  @jfernandz https://stackoverflow.com/questions/4713088/how-do-i-use-git-bisect

                  This is just very basic overview and probably unhelpful.

                  If you’re familiar with git, you can switch to different points in time (via the dev-branch) to figure out when we last knew things were good. So first, I’d suggest trying to find exactly when that would’ve been.

                  I’d likely start, using dev-branch as the primary “tester case”

                  git checkout -b dev-branch
                  

                  If you haven’t already done so of course.

                  Then I’d put the branch at the same level as when we pushed out 1.5.10:

                  git checkout 081d1f4
                  

                  Run your install and see if things worked, if they do:

                  git checkout dev-branch
                  git bisect start
                  git bisect bad
                  git bisect good 081d1f4
                  

                  Of course the 081d1f4 is the hash of the commit where things were good: this might or might not be the 1.5.10 release, so your mileage may very and may need some more adjustment.

                  You can find these hashes on https://github.com/FOGProject/fogproject/commits/dev-branch/?after=f7fd3a7a3f188b4540f089a7f38c4d368b53376c+174 using the different pages at the bottom to find a point in time, and they show the hashes on the right and side of each commit.

                  It will iterate through things and you just mark after each install/test what worked (as good or bad) by testing:

                  If it still fails, you’d run git bisect bad, if it succeeds, you would run git bisect good each iteration.

                  It’s tedious I know. but it will help us find the exact point things broke and hopefully from what (maybe it’s something we did, maybe something within ipxe, but gives us a starting point to test things out.)

                  Thanks

                  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
                  • J
                    jikemin
                    last edited by

                    Has there been a solution to this problem? I have tried many versions of FOG, but I can’t input anything on the keyboard when entering the iPEX menu.

                    H 1 Reply Last reply Reply Quote 0
                    • H
                      hyperbrute @jikemin
                      last edited by

                      @jikemin same here.
                      Exactly same problems:
                      No keyboard input in ipxe menu.
                      (and no autoexec.ipxe too but i created the file as @AxeMeAQuestion22 did)
                      With computers:

                      • Dell OptiPlex 3040 Bios 1.20.1 (last update)
                      • Lenovo Thinkcentre M910T Bios 1.5A (last update)

                      iPXE version (1.21.1+)
                      Fog Version 1.5.10.1660
                      Kernel Version 1.5.10.1660

                      Thanks

                      1 Reply Last reply Reply Quote 0
                      • P
                        pposca
                        last edited by

                        Any update on this? I am having the same issue with the keyboard when booting from UEFI. It seems, however, work properly in Legacy mode (BIOS).

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

                        215

                        Online

                        12.1k

                        Users

                        17.3k

                        Topics

                        155.3k

                        Posts
                        Copyright © 2012-2024 FOG Project