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

Can't boot on PXE with a specific computer

Scheduled Pinned Locked Moved
Hardware Compatibility
4
7
2.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.
  • K
    Kusa555
    last edited by Kusa555 Jun 12, 2023, 2:43 AM Jun 12, 2023, 8:12 AM

    Hello everyone ,

    I recently installed a FOG server and i was able to capture and deploy image for the majority of the computer we use at my company.
    However with a specific computer, i get a error message (see on the screen capture) and i would like some advices on what i can try to make it work.
    PXE.jpg
    A little bit of context :
    -I use the 1.5.10 version of FOG
    -The computer is a Hp pro 3130
    -I was able to boot on PXE on this network with other computers
    -the bootfile i tried is undionly.kpxe and undionly.kkpxe .
    -I tried to capture the dhcp request to see what pxe architecture the computer is using. on the “vendor class identifier” i get : PXEClient:Arch:00000 : UNDI:002001

    Thanks a lot for the help,
    Laurent

    F G 2 Replies Last reply Jun 12, 2023, 12:32 PM Reply Quote 0
    • F
      FoggyBottoms @Kusa555
      last edited by Jun 12, 2023, 12:32 PM

      @Kusa555

      Was having a similar issue on new uefi only Dell PC’s/laptops
      Switched from undionly.pxe to ipxe.efi as the boot file, and all my new systems are now PXE booting and imaging successfully (after secure boot disabled)

      1 Reply Last reply Reply Quote 1
      • G
        george1421 Moderator @Kusa555
        last edited by Jun 14, 2023, 8:47 PM

        @Kusa555 So this system just stays at the initializing devices and never leaves? This is rare for undi (bios) mode. The undionly.kpxe boot loader is correct since your computer is in bios mode.

        It looks like that hardware was released in 2010 so it should be well supported by FOG.

        Check to see if there is a bios (firmware) update for this computer. This issue is specifically between iPXE, bios, and the hardware. Technically FOG hasn’t started in the screen shot.

        The last thing I can think of is if this computer has any abnormal add in cards (like networking) where iPXE might have an issue configuring them.

        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!

        K 1 Reply Last reply Jun 26, 2023, 2:22 PM Reply Quote 1
        • K
          Kusa555
          last edited by Jun 26, 2023, 2:19 PM

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • K
            Kusa555 @george1421
            last edited by Jun 26, 2023, 2:22 PM

            @george1421 @FoggyBottoms

            Thank you both for your response.
            I tried a couple of different bootfiles and i found one that works.

            However i would like to understand the difference between bootfiles such as undionly.kpxe , ipxe.pxe , ipxe.efi
            I tried with these 3 files and it only boots with ipxe.pxe .

            Can someone explain to me the differences between these 3 and why does it works now ?

            Thanks a lot ,
            Laurent

            T G 2 Replies Last reply Jun 26, 2023, 2:36 PM Reply Quote 0
            • T
              Tom Elliott @Kusa555
              last edited by Tom Elliott Jun 26, 2023, 8:37 AM Jun 26, 2023, 2:36 PM

              @Kusa555 The ipxe files are multifold.

              The pxe/kpxe/kkpxe are for MBR (legacy) boot systems
              The efi labelled files are newer systems for booting (UEFI/EFI based)

              ipxe.<label> is using drivers built and maintained for the use in the ipxe code
              undionly.pxe/kpxe/kkpxe is attempting to use and surpass (hence kpxe/kkpxe) some mild bugs using the well known and programmed standard by all legacy NIC booting.

              snp/snponly.efi is attempting to do the same type of thing for UEFI based systems as k/kkpxe files for MBR/Legacy based systems.

              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 1
              • G
                george1421 Moderator @Kusa555
                last edited by george1421 Jun 26, 2023, 9:00 AM Jun 26, 2023, 2:58 PM

                @Kusa555 To add on to what Tom said just remember this,

                ipxe.{efi or kpxe} contains all of the common network drivers much like linux or windows OS’ contains all of the common network drivers already built in.

                The undionly.kpxe only contains 1 network driver for the undi network protocol that is built into each bios network adapter’s firmware.
                The snp.efi and snponly.efi only contain 1 network driver for the snp network protocol built into each uefi network adapter’s firmware.

                Boot loaders that end in .pxe, .kpxe, .kkpxe are bios boot loaders
                Boot loaders that end in .efi are uefi boot loaders

                So what should you use?

                For bios, undionly.kpxe
                For older uefi system (older than 4 years) use ipxe.efi.
                For current uefi systems you may have better utility from snp.efi

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

                155

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project