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

FOG + Pfsense DHCP

Scheduled Pinned Locked Moved
FOG Problems
6
24
16.9k
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
    Albertus @george1421
    last edited by Feb 26, 2016, 3:43 PM

    @george1421

    Good Day

    I am running FOG 1.2.0.
    This is what i get booting in efi mode, not bios mode.
    in pc bios i selected UEFI not Legacy.

    Hope this helps to help me.

    Thank You

    Albertus Geyser

    01000001 01101100 01100010 01100101 01110010 01110100 01110101 01110011
    That's me in a nutshell!!

    T A 2 Replies Last reply Feb 26, 2016, 3:46 PM Reply Quote 0
    • T
      Tom Elliott @Albertus
      last edited by Feb 26, 2016, 3:46 PM

      @Albertus if you’re running 1.2.0 then what ipxe files are you using?

      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 26, 2016, 3:49 PM Reply Quote 0
      • A
        Albertus @Tom Elliott
        last edited by Feb 26, 2016, 3:49 PM

        @Tom-Elliott

        Good Day

        I am running ipxe.efi . . .

        Thank You

        Albertus Geyser

        01000001 01101100 01100010 01100101 01110010 01110100 01110101 01110011
        That's me in a nutshell!!

        T 1 Reply Last reply Feb 26, 2016, 3:50 PM Reply Quote 0
        • T
          Tom Elliott @Albertus
          last edited by Feb 26, 2016, 3:50 PM

          @Albertus what I’m getting at is the version of the ipxe file is not that of the version released in 1.2.0, at least if I recall 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

          1 Reply Last reply Reply Quote 0
          • A
            Albertus @Albertus
            last edited by Feb 26, 2016, 4:03 PM

            Good Day

            Added are images of what i get when booting legacy mode on this client:

            0_1456502514575_ipxe2.jpg

            0_1456502552196_ipxe3.jpg

            After second image then pc reboots and loops.

            Thank You

            Albertus Geyser

            01000001 01101100 01100010 01100101 01110010 01110100 01110101 01110011
            That's me in a nutshell!!

            T 1 Reply Last reply Feb 26, 2016, 4:05 PM Reply Quote 0
            • T
              Tom Elliott @Albertus
              last edited by Feb 26, 2016, 4:05 PM

              @Albertus again those are not 1.2.0 ipxe files. Somebody switched out the files. How do I know?

              The version of ipxe is found with the d739 part. 1.2.0 ipxe started with a letter a if I recall correctly.

              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 26, 2016, 4:07 PM Reply Quote 0
              • A
                Albertus @Tom Elliott
                last edited by Feb 26, 2016, 4:07 PM

                @Tom-Elliott should i replace some files? is that what you mean?
                If so where can i find files to replace?

                01000001 01101100 01100010 01100101 01110010 01110100 01110101 01110011
                That's me in a nutshell!!

                1 Reply Last reply Reply Quote 0
                • G
                  george1421 Moderator @Guest
                  last edited by Feb 26, 2016, 4:19 PM

                  @Albertus Lets take a step back and think for a minute. I think we have a language translation issue. This is no problem, we will just take the information collection slower.

                  Lets start with the basics. When you access the FOG management GUI, there is a picture of a cloud on the upper left side of the screen. On that cloud there are little numbers on the right side of the cloud. Can you tell us what numbers are there?

                  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!

                  A 1 Reply Last reply Feb 27, 2016, 6:02 AM Reply Quote 0
                  • S
                    Sebastian Roth Moderator
                    last edited by Sebastian Roth Feb 26, 2016, 4:59 PM Feb 26, 2016, 4:28 PM

                    You are perfectly right Tom. This can’t be an official FOG 1.2.0 binary - not just because of the version but there actually was no ipxe.efi in FOG 1.2.0 and neither was there a i386-efi/ipxe.efi file in /tftpboot directory.

                    So I guess he downloaded a new set of iPXE binaries somewhere around last summer. At least the version number d739 is pointing to an iPXE commit around June 2015. But anyhow.

                    @Albertus Downloading a set of iPXE binaries is fine if they work for you. So don’t worry, you did nothing wrong. You can try downloading a new set of iPXE binaries to see of they work better (this is on debian - you might need to adjust some of the service commands if you are on CentOS):

                    sudo service tftpd-hpa stop
                    sudo mv /tftpboot /tftpboot.backup
                    sudo mkdir /tftpboot
                    sudo svn export http://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/ /tftpboot
                    sudo chown -R fog /tftpboot
                    sudo service tftpd-hpa start
                    

                    The last picture (BIOS mode) you posted is cut off at the bottom exactly where I guess there might be valuable information.
                    But the UEFI mode picture is better! “Exec format error” could be because the kernel you are using is too old. EFI_STUB was added in kernel version 3.16.x and FOG 1.2.0 default kernel is 3.15.6!!
                    Please run file /var/www/fog/service/ipxe/bzImage on your FOG server to see which kernel version you have. You can update the kernel in the web interface (FOG configuration).

                    Edit: Just stumbled upon the commit that had iPXE version d739 (git / svn FWIW)

                    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 1
                    • A
                      Albertus @george1421
                      last edited by Feb 27, 2016, 6:02 AM

                      @george1421 the numbers in cloud is 3613.

                      01000001 01101100 01100010 01100101 01110010 01110100 01110101 01110011
                      That's me in a nutshell!!

                      W G 2 Replies Last reply Feb 27, 2016, 6:18 AM Reply Quote 0
                      • W
                        Wayne Workman @Albertus
                        last edited by Feb 27, 2016, 6:18 AM

                        @Albertus said:

                        @george1421 the numbers in cloud is 3613.

                        You should update to the latest in this case, since you are already on Trunk. There’s been a lot of changes since 3613.

                        You can do that by following one of the methods here:
                        https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

                        I would recommend either the svn or the git method. Either is fine.

                        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!
                        Daily Clean Installation Results:
                        https://fogtesting.fogproject.us/
                        FOG Reporting:
                        https://fog-external-reporting-results.fogproject.us/

                        1 Reply Last reply Reply Quote 0
                        • G
                          george1421 Moderator @Albertus
                          last edited by george1421 Feb 27, 2016, 9:54 AM Feb 27, 2016, 2:33 PM

                          @Albertus said:

                          @george1421 the numbers in cloud is 3613.

                          I agree Wayne 3613 is pretty old in the trunk. The latest trunk version (as I write this) is 6483. The Devs have made great progress in the last month to support the newest hardware and hard drive configurations. Its well worth the effort to upgrade. When you get to the latest trunk release and still have issues, then we can get the Devs attention to your specific problem.

                          From your original post, I’m pretty sure your issue is not pfsense or pxe 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!

                          1 Reply Last reply Reply Quote 1
                          • A
                            Albertus
                            last edited by Feb 29, 2016, 9:10 AM

                            Good Day

                            I reinstalled FOG 1.2.0.

                            When booting with ipxe.efi it now gives me the following:

                            0_1456736985201_ipxe4.jpg

                            What could still be the problem?

                            Thank You

                            Albertus Geyser

                            01000001 01101100 01100010 01100101 01110010 01110100 01110101 01110011
                            That's me in a nutshell!!

                            1 Reply Last reply Reply Quote 0
                            • G
                              george1421 Moderator
                              last edited by george1421 Feb 29, 2016, 5:09 AM Feb 29, 2016, 11:06 AM

                              Please understand the recommendation was for you to upgrade to the latest trunk version (i.e. a pre release of version 1.3.0) not to reinstall 1.2.0. Version 1.2.0 does not work well with EFI systems. The upgrade process is outlined in the link provided by Wayne Workman: https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

                              Your error screen shows that the ipxe.efi does not exist on your FOG server. Which is understandable since this file did not exist in FOG 1.2.0. The file snponly.efi is the recommended file for 1.2.0.

                              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!

                              A 1 Reply Last reply Mar 2, 2016, 6:38 AM Reply Quote 2
                              • A
                                Albertus @george1421
                                last edited by Mar 2, 2016, 6:38 AM

                                @george1421 When will 1.3.0 be realesed as production (Stable) version?

                                01000001 01101100 01100010 01100101 01110010 01110100 01110101 01110011
                                That's me in a nutshell!!

                                G 1 Reply Last reply Mar 2, 2016, 11:24 AM Reply Quote 0
                                • G
                                  george1421 Moderator @Albertus
                                  last edited by Mar 2, 2016, 11:24 AM

                                  @Albertus At this time there is no defined release date for 1.3.0 stable. The developers are working hard to get the trunk version to the stable level.

                                  The situation is the more people we can get into the trunk version to find the bugs, the quicker the bugs can be identified and resolved. If people not upgrade waiting for the stable release the longer it will take to find the bugs. So the best situation is to get as many people as possible into the trunk stream to identify issues faster. This will make the 1.3.0 release come faster too.

                                  Understand when I say bugs, the trunk is not unstable today. There are many updates to fog per week as the code is fine tuned for best performance. So you will need to update your fog code frequently to take advantage of the performance improvements.

                                  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
                                  • 1
                                  • 2
                                  • 1 / 2
                                  1 / 2
                                  • First post
                                    18/24
                                    Last post

                                  194

                                  Online

                                  12.1k

                                  Users

                                  17.3k

                                  Topics

                                  155.3k

                                  Posts
                                  Copyright © 2012-2024 FOG Project