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

    Unable to register/capture/deploy "Failed to get an IP via DHCP! Tried on Interfaces:"

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    12
    779
    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.
    • J
      Jpolk91
      last edited by Jpolk91

      @george1421 Thank you for the swift reply!

      I jumped into windows and the hardware ID had several lines for the Ethernet adapter so here is the entire thing:
      PCI\VEN_8086&DEV_15BB&SUBSYS_83E2103C&REV_10
      PCI\VEN_8086&DEV_15BB&SUBSYS_83E2103C
      PCI\VEN_8086&DEV_15BB&CC_020000
      PCI\VEN_8086&DEV_15BB&CC_0200

      and here is the picture showing the output of those commands:
      64efad14-7aa1-4d8a-bc65-3fd7a5e1fa36-image.png

      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @Jpolk91
        last edited by

        @Jpolk91 excellent results. I did make a mistake and should have had you enter a command line switch on the lspci command. lspce -nn|grep etwor That command will give us the vend and device ID that should match what windows sees.

        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
        • S
          Sebastian Roth Moderator
          last edited by

          @Jpolk91 said in Unable to register/capture/deploy "Failed to get an IP via DHCP! Tried on Interfaces:":

          PCI\VEN_8086&DEV_15BB

          Well that’s interesting. This NIC is supported in the default Intel driver e1000e since kernel version 4.12.x - long time.

          @Jpolk91 When you boot into a debug task again, please run the following command, take a picture and post here: dmesg | grep -i -e eth -e e1000e

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

            Sorry for the delay! I had a lot to do after work yesterday and had to bail pretty fast.

            @george1421 your command is the very first two lines in the picture.

            @Sebastian-Roth here ya go.

            23d27c1a-567b-4ad3-82c2-ce6566df405f-image.png

            1 Reply Last reply Reply Quote 0
            • J
              Jpolk91
              last edited by

              Hey! @Sebastian-Roth I was thinking and was going to go back to the 4.12.x kernel you mentioned just to check so I went to the page and it caught my eye that the kernel version showing in the version info is showing 4.11 for some reason… I tried going to a few different kernels and it never changed. Does my version of FOG not support kernels over 4.11 for some reason?

              d075e675-1773-474b-aa58-8e03e696d1fc-image.png

              george1421G 1 Reply Last reply Reply Quote 0
              • george1421G
                george1421 Moderator @Jpolk91
                last edited by george1421

                @Jpolk91 Ah, that’s the problem. That should have been the first question I asked, what version of FOG are you using??? 1.4.2 is pretty old.

                You will need to manually update to 4.12.3 from here: https://fogproject.org/kernels/ Don’t get greedy, move up to a kernel that supports that network adapter but don’t move the latest because they won’t work with FOG 1.4.2 very well.

                You will need to download those files to /var/www/html/fog/service/ipxe. Rename the existing bzImage and bzImage32 to bzImage411 and bzImage32411. And finally rename the downloaded files to match bzImage (for the 64 bit) and bzImage32 for the 32 bit.

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

                  @george1421 Should I expect any problems just moving up to FOG 1.5.5 from 1.4? I don’t have any particular reason for staying on the old version other than “If it ain’t broke don’t fix it”

                  george1421G 1 Reply Last reply Reply Quote 0
                  • george1421G
                    george1421 Moderator @Jpolk91
                    last edited by

                    @Jpolk91 There has been some issues with the 1.5.x line but most have been ironed out with 1.5.5 (1.5.6 is not to far off either). The 1.5.x has a new web gui with a bit heaver load on the FOG server CPU, its not quite a snappy as 1.4.x versions, but its not bad with quite a few improvements in other areas making it a wash performance wise.

                    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
                    • S
                      Sebastian Roth Moderator
                      last edited by

                      @Jpolk91 said in Unable to register/capture/deploy "Failed to get an IP via DHCP! Tried on Interfaces:":

                      kernel version showing in the version info is showing 4.11 for some reason

                      Yes that is definitely the reason. See if you can use the 4.12.3 kernels as suggested. If you run into a kernel error then you might need to use the compat inits as well (32 bit and 64 bit).

                      Just for the record, the command used to get the network card information only shows the wireless adapter. Use lspci -nn | grep -i net to get both.

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

                        @george1421, @Sebastian-Roth

                        Thank you both VERY much! I just went and updated to 1.55 instead of doing the kernel update manually, figured it would probably be better in the long run. Now it appears to be working normally. Sorry I didn’t notice earlier the kernel wasn’t what I thought it was!

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

                        218

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project