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

    PXE boot hanging at bzImage and Init.xz during capture task

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    5
    612
    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.
    • Y
      Yeet
      last edited by Yeet

      I am attempting to capture an image, but for some reason during the PXE boot process it’s getting stuck at “bzImage… 34%”. I’ve tried rebooting multiple times & even recreating the capture task to no avail. It will either get stuck at bzImage or Init, and it always says a different percentage.

      That’s when I have a capture task active. When I don’t have a capture task active, I’m able to boot into the FOG menu just fine. Any ideas what could be going on here? I captured an image a few days ago with no issue, and I’m updated to the latest kernel.

      The PC I’m try to capture from is a HP 450 G9 ProBook, and I’m using the snp.efi bootfile.

      1 Reply Last reply Reply Quote 0
      • Y
        Yeet @Sebastian Roth
        last edited by

        @sebastian-roth I appreciate the response. Unfortunately none of those options resolved the issue.

        I spent some time reading through those articles you linked, and I saw a lot of suggestions for disabling DMA protection. I tried it out, and that fixed it for me!

        1 Reply Last reply Reply Quote 1
        • S
          Sebastian Roth Moderator
          last edited by

          @yeet said in PXE boot hanging at bzImage and Init.xz during capture task:

          The PC I’m try to capture from is a HP 450 G9 ProBook, and I’m using the snp.efi bootfile.

          Well this is the important information here. Some devices just don’t play nicely and this one seems to be a devil (1, 2, 3).

          First I suggest you update the BIOS/UEFI firmware to the very latest.

          If that doesn’ help you can try using different iPXE binaries (e.g. ipxe.efi) or update the iPXE binaries to the latest version: https://docs.fogproject.org/en/latest/reference/compile_ipxe_binaries.html

          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

          Y 2 Replies Last reply Reply Quote 0
          • Y
            Yeet @Sebastian Roth
            last edited by

            @sebastian-roth I appreciate the response. Unfortunately none of those options worked. It’s weird, I was able to do a full host registration last week, but now it won’t even do that. I can get to the FOG menus just fine, but any time I run a task such it’ll get stuck trying to load either bzImage or init.xz.

            It really is looking like it’s an issue with these g8+ HP ProBooks. Hopefully there’s a fix found eventually

            R 1 Reply Last reply Reply Quote 0
            • R
              rodluz Developer @Yeet
              last edited by rodluz

              @yeet I can’t really speak for that model of the ProBook, only have a 650 G8 at hand and it works, but I had an issue like that on 5 EliteBook 850 G6 from a batch of 50.

              I also tried all the same things that @Sebastian-Roth suggested with no luck. What I ended up doing for those few was to connect them using a USB-C to Ethernet adapter until right after the bzImage and init.xz then quickly switch the cable to the integrated Ethernet port when it’s connecting to the net0 interface.

              As Sebastian said, you may have some luck using ipxe.efi.

              1 Reply Last reply Reply Quote 0
              • Y
                Yeet @Sebastian Roth
                last edited by

                @sebastian-roth I appreciate the response. Unfortunately none of those options resolved the issue.

                I spent some time reading through those articles you linked, and I saw a lot of suggestions for disabling DMA protection. I tried it out, and that fixed it for me!

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

                235

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project