brand new dell latitude 3500



  • seems that the newest kernel finds no hard drive - these things are brand new, they are fresh off the line from dell.

    anything I can do to see if its a hardware compatibility problem or something different?
    these don’t have ‘legacy’ boot mode anymore - its all uefi.


  • Moderator

    @bigjim Your dnsmasq config is outdated if you’re using the a newer version. (and UEFI + BIOS proxydhcp didn’t work at all on older versions)

    dhcp-boot=tag:UEFI32,i386-efi/ipxe.efi,10.5.0.240

    dhcp-boot=tag:UEFI,ipxe.efi,10.5.0.240

    dhcp-boot=tag:UEFI64,ipxe.efi,10.5.0.240

    The syntax tag: is no longer valid and needs to be replaced with net:

    https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq#Install_dnsmasq_on_CentOS_7 for reference

    It’s confusing because there’s info on both older versions of dnsmasq and the newer ones, but likely this is the cause.


  • Moderator

    @bigjim If we look at the boot table map these are the different classes of systems

               Type   Architecture Name
               ----   -----------------
                 0    Intel x86PC
                 1    NEC/PC98
                 2    EFI Itanium
                 3    DEC Alpha
                 4    Arc x86
                 5    Intel Lean Client
                 6    EFI IA32
                 7    EFI BC (EFI Byte Code)
                 8    EFI Xscale
                 9    EFI x86-64
    

    For this device Arch:0007 should have matched, which is EFI_BC so the flag UEFI should be set.

    So the boot file name should match dhcp-boot=tag:UEFI,ipxe.efi,,10.5.0.240

    The following section has noting to do with the tags above because this is the boot menu, but its needed to boot correctly with some firmware.

    pxe-prompt="Booting FOG Client", 1
    
    # The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
    # Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
    # This option is first and will be the default if there is no input from the user.
    pxe-service=X86PC, "Boot to FOG", undionly.kpxe
    pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
    pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi
    

    In this menu BC_EFI flag should match, because this is an internal variable. The pxe-prompt is set to 1 second because there is nothing for the user to select here because dnsmasq picks the correct flag.

    Now I might suggest that you remove the comment at the end of hte BC line pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi #ipxe7156.efi

    Now there is one more trick if you have really wacky uefi firmware. Where you append the IP address of your fog server to the end of the pxe-service line making.

    pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi, 10.5.0.240
    

    But I haven’t see this extra trick needed in quite a while.

    All this does is send the correct boot file name to the target computer using proxyDHCP protocol (over udp port 4011)



  • @george1421 Thanks for the response. Before I added PXEClient:Arch:00007:UNDI:003016 to the conf the laptop showed the
    Boot to FOG UEFI PXE-BC
    on the screen
    but iPXE would never start as if it was not finding the file.
    The screen goes away too fast to see if there are any other messages

    You are correct 7156 was removed, I pulled it from an old build to try different options.

    Thanks


  • Moderator

    @bigjim said in brand new dell latitude 3500:

    When i look in the dnsmasq log it shows the vendorclass as PXEClient:Arch:00007:UNDI:003016

    Lets first try to understand your problem so we can work on a solution.

    Just for clarity PXEClient:Arch:00007:UNDI:003016 The undi part is not unique to identify the hardware, that is only the undi version 3.16 which is not a unique identifier. I’m going to say the issue is that both tags UEFI and UEFIBC will match, then when you get down to the dhcp-boot section, the UEFI will match first and then not check the remainder (guess) so only ipxe.efi will be sent to the client. Also thing to note, unless you have an old version of FOG, ipxe71567.efi should no longer be supported. I’d have to check but that boot loader should have been removed from the build.

    What isn’t working at the moment here?



  • @p4cm4n I have the same problem you had. When i look in the dnsmasq log it shows the vendorclass as PXEClient:Arch:00007:UNDI:003016
    so i created dhcp-vendorclass=UEFIBC,PXEClient:Arch:00007:UNDI:003016
    iwith that in the ltsp.conf i get the Boot to FOG UEFI PXE-BC prompt but it never boots the efi
    here is my conf file.
    If anyone could help it would be appreciated.

    # Don't function as a DNS server:
    port=0
    
    # Log lots of extra information about DHCP transactions.
    log-dhcp
    
    log-queries
    
    # Set the root directory for files available via FTP.
    tftp-root=/tftpboot
    
    # The boot filename, Server name, Server Ip Address
    dhcp-boot=undionly.kpxe,,10.5.0.240
    
    # Disable re-use of the DHCP servername and filename fields as extra
    # option space. That's to avoid confusing some old or broken DHCP clients.
    dhcp-no-override
    
    # inspect the vendor class string and match the text to set the tag
    dhcp-vendorclass=BIOS,PXEClient:Arch:00000
    dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
    dhcp-vendorclass=UEFI,PXEClient:Arch:00007
    dhcp-vendorclass=UEFI64,PXEClient:Arch:00009
    dhcp-vendorclass=UEFIBC,PXEClient:Arch:00007:UNDI:003016
    
    
    
    # Set the boot file name based on the matching tag from the vendor class (above)
    dhcp-boot=tag:UEFI32,i386-efi/ipxe.efi,,10.5.0.240
    dhcp-boot=tag:UEFI,ipxe.efi,,10.5.0.240
    dhcp-boot=tag:UEFI64,ipxe.efi,,10.5.0.240
    dhcp-boot=tag:UEFIBC,ipxe7156.efi,,10.5.0.240
    
    
    # PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
    pxe-prompt="Booting FOG Client", 3
    
    # The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
    # Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
    # This option is first and will be the default if there is no input from the user.
    pxe-service=X86PC, "Boot to FOG", undionly.kpxe
    pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
    pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi #ipxe7156.efi
    
    dhcp-range=10.5.0.240,proxy,255.255.0.0```

  • Moderator

    @Joe-Gill said in brand new dell latitude 3500:

    Ding ding ding ding! I need to set my dhcp server settings for UEFI!!!

    You may want to consider:
    https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy



  • @p4cm4n

    Ding ding ding ding! I need to set my dhcp server settings for UEFI!!! Thanks!!!



  • @Joe-Gill i successfully ran through a pallet of these - 27 - and no issues. this was my process:
    boot into BIOS setup.
    Click enable UEFI network stack, scroll down to AHCI and click it. hit Apply.
    on the left, select secure boot. disable using checkbox - it will ask if you’re sure. hit yes, hit apply. hit exit.

    it reboots, hit f12, network boot ipv4
    it works

    if it doesn’t work for you, make sure your ipv4 UEFI boot settings are setup on your dhcp server (ipxe.efi instead of undionly.kpxe)



  • @george1421

    I just tried it with the Secure Boot off and it failed the same way it did before.

    It never even begins to load the iPXE.


  • Moderator

    @Joe-Gill said in brand new dell latitude 3500:

    I have secure boot enabled.

    Ah that’s it turn off secure boot because iPXE is not signed at all. So the firmware won’t load iPXE.



  • @george1421

    The BIOS says:

    Downloading NBP file...
    
    NBP file downloaded successfully.
    

    Than it returns to starting to load Windows. I never see a FOG PXE boot screen at all. I’m running the 4.19.48 32 and 64 Kernel Versions. I have secure boot enabled.

    I have the following enabled in UEFI:

    Boot Options:
    Onboard NIC (IPV4)

    System Configuration:
    Integrated NIC
    Enable UEFI Network Stack
    Enabled with PXE

    SATA Operation:
    AHCI

    Secure Boot:
    Enable Secure Boot
    Audit Mode (I tried this doesn’t make a difference)

    POST Behavior:
    FAST Boot Thorough


  • Moderator

    @Joe-Gill said in brand new dell latitude 3500:

    I can’t get it to PXE using UEFI

    What doesn’t it do? What errors are you seeing?

    You have to give us a bit more detail more that it doesn’t work (my words).



  • @p4cm4n

    Did you manage to get this figured out? My coworker ordered a pile of these and I can’t get it to PXE using UEFI… Any advice there?

    Thanks!

    Cheers!



  • THANK YOU @Sebastian-Roth

    just got a pallet of 67 of these and would hate to go back to pre-fog days…:)


  • Developer

    @p4cm4n Most probably some kind of Intel software RAID foo. See if you can change from RAID to AHCI somewhere in the UEFI firmware settings.


Log in to reply
 

447
Online

6.2k
Users

13.5k
Topics

127.5k
Posts