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

HP-17by3452 - Realtek NIC doesn't receive IP from DHCP server with ipxe.efi

Scheduled Pinned Locked Moved
Hardware Compatibility
4
11
1.8k
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.
  • F
    FabianN.
    last edited by Oct 16, 2020, 12:03 PM

    Hello fog people!
    We received some new HP-17by3452 laptops with 10th Generation Intel CPUs. Unfortunatly the onboard Realtek NIC doesn’t receive an IP address from our DHCP server when booting ipxe.efi.

    Link-up on net0 is OK, but when it starts to configure net0 it aborts with error message “No configuration methods suceeded”.

    The BIOS is the latest version from HP website, F.9 from August 2020.

    Fog Kernel also up to date:
    bzImage Version: 4.19.143
    bzImage32 Version: 4.19.143

    Other devices from Dell with Intel and Realtek NICs work just fine with ipxe.efi.

    Any suggestions or ideas?

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by george1421 Oct 16, 2020, 10:22 AM Oct 16, 2020, 4:22 PM

      I assume you are using FOG 1.5.9? If so, see if snponly.efi or snp.efi works with these network adapters. The snponly.efi is roughly equivalent to the undionly.kpxe where it uses part of the built in universal driver found in the nic’s firmware (in the case of efi its called snp and bios its undi).

      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!

      F 1 Reply Last reply Jan 24, 2024, 9:01 PM Reply Quote 0
      • F
        FabianN.
        last edited by Oct 21, 2020, 8:56 AM

        Hello george142, thank you for your reply!
        The snponly.efi did not work for me, I will try the snp.efi and report here.

        G 1 Reply Last reply Oct 21, 2020, 9:14 AM Reply Quote 0
        • G
          george1421 Moderator @FabianN.
          last edited by Oct 21, 2020, 9:14 AM

          @FabianN Just to make sure we are thinking the same, you can not get to the fog iPXE menu at all right?

          Another remote possibility is that you have standard spanning tree configured on the network port where you are trying to image this computer. For pxe booting FOG you should have enabled one of the fast spanning tree protocols (rstp, mstp, port-fast, etc) . Or some kind of green ethernet setting turned on. If its either of these cases you can test by putting an inexpensive (read cheap, like those home 5 port network switches) network switch between the building switch and pxe booting computer. This will mask the spanning tree issue.

          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!

          F 1 Reply Last reply Dec 1, 2020, 7:26 AM Reply Quote 0
          • F
            FabianN.
            last edited by Nov 30, 2020, 12:46 PM

            Hello, sorry for the late reply. None of the *.efi boot images succeeded configuring the integrated Realtek NIC in the HP Notebook with 10th Generation Intel CPU. I ended up cloning the devices locally with an external USB 3.0 harddisk.

            1 Reply Last reply Reply Quote 0
            • F
              FabianN. @george1421
              last edited by Dec 1, 2020, 7:26 AM

              @george1421

              Hi George, just to clarify, it went fine to the FOG menu, but after selecting the proper image, right before partclone should start, link-up on net0 is OK, but it aborts with the error message “No configuration methods suceeded”.

              1 Reply Last reply Reply Quote 0
              • S
                Sebastian Roth Moderator
                last edited by Dec 1, 2020, 12:27 PM

                @fabiann said in HP-17by3452 - Realtek NIC doesn't receive IP from DHCP server with ipxe.efi:

                No configuration methods suceeded

                This is a error message generated by iPXE - something you should not see if you got past the FOG menu part already! Please take a video of the boot process, upload to a file share and post a link here. Try to rest the camera/smartphone on a pile of books for a steady picture.

                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

                F 1 Reply Last reply Dec 7, 2020, 12:07 PM Reply Quote 0
                • F
                  FabianN. @Sebastian Roth
                  last edited by Dec 7, 2020, 12:07 PM

                  Hello, unfortunatly I can’t provide you a video because the devices are already in production use.
                  All I have is a screenshot of the error messege in the boot process.

                  @sebastian-roth image.jpg

                  1 Reply Last reply Reply Quote 0
                  • S
                    Sebastian Roth Moderator
                    last edited by Dec 7, 2020, 3:46 PM

                    @FabianN I am still confused on why you’d see the FOG menu but run into that obvious iPXE (before the menu!)?!

                    I suspect there is an issue in the iPXE drivers with that network card. Very hard to debug.

                    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
                    • F
                      flat4vw @george1421
                      last edited by Jan 24, 2024, 9:01 PM

                      @george1421
                      I know this is an old post, where do you changed the to boot using that pxe name and if I have the realtek.pxe file where does that get placed what’s the path

                      Thank you

                      G 1 Reply Last reply Jan 24, 2024, 9:34 PM Reply Quote 0
                      • G
                        george1421 Moderator @flat4vw
                        last edited by Jan 24, 2024, 9:34 PM

                        @flat4vw I guess a couple of things.

                        Instead of realtek.pxe you probably want to use realtek.kpxe.

                        The *?pxe files are for bios based computers. They will not boot on a uefi system.

                        The file is physically located in the FOG server in the /tftpboot directory.

                        How do you make the computer load the file? Update dhcp option 67 on your dhcp server. Either by the windows dhcp manager or if linux in /etc directory.

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

                        165

                        Online

                        12.1k

                        Users

                        17.3k

                        Topics

                        155.3k

                        Posts
                        Copyright © 2012-2024 FOG Project