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

    Asus B660 M-C

    Scheduled Pinned Locked Moved
    Hardware Compatibility
    3
    7
    592
    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.
    • S
      sonic136
      last edited by

      Hi fog community

      We are unable to PXE boot to fog on an Asus B660 m-c motherboard.

      We are running 2pxe files - namely, the snponly and undionly - these files are linked to flags on the network - the flag system works perfectly.

      The machine BIOS has been updated and is set to network boot.

      It seems like the drivers for the B660 are not included in the efi file set.

      Is there any way to get the boot files loaded and to get the machine to PXE boot?

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

        @sonic136 said in Asus B660 M-C:

        It seems like the drivers for the B660 are not included in the efi file set.

        Just to be clear the B660 is configured for UEFI mode (you made referenced to BIOS in the previous sentence)?

        The snp.efi and snponly.efi only has one driver in it, the snp driver. The snp driver interfaces with the driver built into the nic adapter. So unless the mobo is from an early uefi generation, snp should just work. The alternate is the ipxe.efi boot loader. That boot loader is similar to linux in that it has all of the known network drivers built into the boot kernel. If the snp drivers don’t work, then see if the ipxe.efi boot loader works.

        The last bit, that I don’t think will help if you are using the undionly and snponly drivers is to recompile ipxe to the latest version to get the latest hardware support: https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe

        Also as long as you are updating stuff with FOG, make sure you are running the latest FOS Linux kernel 5.15.x series. That will get you support for the latest hardware beyond PXE boot environment.

        One final word about snp and snponly boot loaders. The snponly will only communicate over the network card to where the device was pxe booted from, where snp will communicate over any network adapter. This is only important if you have more than 1 network adapter in your computer.

        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!

        S 1 Reply Last reply Reply Quote 0
        • S
          sonic136 @george1421
          last edited by

          @george1421

          yes, the BIOS is set to use UEFI mode only, and the NIC is set to first boot in the priority. We have complied the lastest build and still not able to successfully PXE

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

            @sonic136 said in Asus B660 M-C:

            still not able to successfully PXE

            Probably best you take a picture of where exactly it hangs/fails and post that here.

            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
            • george1421G
              george1421 Moderator @sonic136
              last edited by

              @sonic136 OK so exactly where does it fail to boot? Could you provide a clear picture of where is stops in the process?

              Also try to use ipxe.efi instead of snponly.efi to see if that gives you a better/different result.

              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!

              S 1 Reply Last reply Reply Quote 0
              • S
                sonic136 @george1421
                last edited by

                @george1421 We have assigned a new flag and applied the ipxe.efi file to the flag. Seems like it has worked.

                Thank you @george1421

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

                  @sonic136 All I can say is that we’ve seen early versions of uefi bios have poor snp uefi drivers. But if this mobo was created in the last 5-6 years it shouldn’t have an issue with snp because uefi firmware has matured quite a bit. Strange, but we’ve seen it happen on certain models.

                  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

                  204

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project