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

    ASIX AX88772A initialization failed

    Scheduled Pinned Locked Moved
    Hardware Compatibility
    4
    7
    3.4k
    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
      Jeff Turley
      last edited by

      I am attempting to boot fog on a Lenovo Thinkpad with a Sabrent USB NIC. ASIX AX88772A is the description on the PXE boot screen. I have USB 3.0 disabled in the BIOS. PXE boot works and ipxe attempts to initialize the driver. After about 15 seconds it failed to initialize AX88772B. I have tried 10 or 11 different kernels same think with all of them.

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

        Kernel’s aren’t the problem. You could try other “undionly” files within the tftp folder.

        There’s
        undionly.pxe
        undionly.kpxe (This is the default)
        undionly.kkpxe
        ipxe.pxe
        ipxe.kpxe
        ipxe.kkpxe

        Try one of the ipxe.* files as your undionly and maybe they’ll be success?

        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
          Jeff Turley
          last edited by

          [quote=“Tom Elliott, post: 30441, member: 7271”]Kernel’s aren’t the problem. You could try other “undionly” files within the tftp folder.

          There’s
          undionly.pxe
          undionly.kpxe (This is the default)
          undionly.kkpxe
          ipxe.pxe
          ipxe.kpxe
          ipxe.kkpxe

          Try one of the ipxe.* files as your undionly and maybe they’ll be success?[/quote]

          1 Reply Last reply Reply Quote 0
          • J
            Jeff Turley
            last edited by

            undionly.kkpxe worked it was the last one i tried, I was getting nervous. What is the diffrence between these files. Thanks

            1 Reply Last reply Reply Quote 0
            • JunkhackerJ
              Junkhacker Developer
              last edited by

              the differences between those files and what the naming conventions mean are complicated and poorly documented, unfortunately.
              [url]http://etherboot.org/wiki/gpxe_imagetypes[/url]
              undionly.x files are universal configurations
              ipxe.x files contain a lot of hardware specific drivers that may or may not work better then a universal build, depending on your hardware.

              signature:
              Junkhacker
              We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

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

                I don’t know of a good method to distinguish besides the undi/ipxe files nor the pxe, kpxe, and kkpxe files extentions. I wrote about them somewhere but can’t remember where.

                What I do know,
                ipxe has drivers, undionly uses the “undi” stack made by the manufacturer.

                pxe unloads undi and pxe stack.
                kpxe unloads just the pxe stack
                kkpxe keeps both undi and pxe stacks in place.

                kkpxe works best for buggy hardware. Only recommended if you’re having weird issues with the undionly.kpxe
                kpxe is the normal file we want in use as it seems to be the best between pxe/chaining I can find without flashing roms.
                pxe is ultimately the goal, but there’s not enough information to allow this to actually work flawlessly everytime.

                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
                • W
                  Wolfbane8653 Developer
                  last edited by

                  Used some info that has been thrown around about these files and checked on a few other sites and threw this together. This should cover most questions on PXE and iPXE along with the different file types.
                  [U][url]http://fogproject.org/wiki/index.php/IPXE[/url][/U]

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

                  146

                  Online

                  12.1k

                  Users

                  17.3k

                  Topics

                  155.3k

                  Posts
                  Copyright © 2012-2024 FOG Project