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

    brand new dell latitude 3500

    Scheduled Pinned Locked Moved Solved
    Hardware Compatibility
    8
    31
    6.3k
    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
      Joe Gill @Mountainmanmoore
      last edited by

      @Mountainmanmoore

      If by this you mean booting a Dell Latitude 3500 via UEFI, I was able to get that going by setting up my DHCP server correctly as indicated in the post here.

      1 Reply Last reply Reply Quote 0
      • T
        TheFunk35
        last edited by

        Sorry to dig up an old post but I have a lot of 30 of these laptops that need imaging.

        I get to the Fog menu, so I know my Windows DHCP server settings are okay, but the second I go to “Perform Quick Host Registration/Inventory” the server reports that bzImage loads and then immediately I receive an error that says Chainloading failed followed by the same message as the error posted here:

        https://forums.fogproject.org/topic/12108/could-not-select-exec-format-error-http-ipxe-org-2e008081

        I am using the laptop’s integrated ethernet NIC. In the laptop’s BIOS, the UEFI network stack is set to enabled w/PXE. The SATA controller is set to AHCI mode. Secure boot is disabled, as is the TPM and Absolute Guard.

        It should be noted that I had previously tried the SATA controller in RAID ON mode and tried a registration previously and those attempts proceeded to boot the registration menu but failed to find a hard drive, so I switched the controller, did a clean install because Windows didn’t like that, and tried again.

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

          @TheFunk35 What version of FOG, and is the firmware up to date on these 3500s?

          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!

          T 2 Replies Last reply Reply Quote 0
          • T
            TheFunk35 @george1421
            last edited by

            @george1421 Latest production version of Fog 1.5.8 running on CentOS 7. I don’t know about the firmware. I will try to update it tonight. I’m not hopeful that will help. It looks like my older Precision T3610 desktops are having a similar issue. They all reach the Fog menu but then trying to load anything from there is a no go.

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

              @TheFunk35 For sure the computer is in uefi mode? And you are double sure that safeboot is disabled?

              Just for grins what are you sending as a PXE boot file to this computer?

              While I seriously doubt is an ipxe menu issue if you go to a browser and call up this url, this is the program behind the iPXE menu. http://<fog_server_ip>/fog/service/ipxe/boot.php post the results here.

              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!

              T 1 Reply Last reply Reply Quote 0
              • T
                TheFunk35 @george1421
                last edited by

                @george1421 I went ahead and updated firmware. The 3500s received a firmware update on 3/13/20.

                After applying the latest firmware the issue still stands. Should I try with a different ethernet adapter or is this an ipxe issue? It looks like these laptops come with realtek NICs. They seem like junky NICs. They’re the kind with the little clip built into the laptop case that are always insanely difficult to pull an RJ-45 out of. Should I try with realtek.efi instead of ipxe.efi?

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

                  @TheFunk35 You can try the realtek.efi boot loader, but I don’t think that is the problem. What is happening is the bzImage file transferred by ipxe.efi file is not runnable on the target computer, maybe because its corrupt or something else is blocking it from running. Like always this error should not happen.

                  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!

                  T 1 Reply Last reply Reply Quote 0
                  • T
                    TheFunk35 @george1421
                    last edited by

                    @george1421 Info as requested. I do have a few custom menu items but the weird thing is, everything works perfectly when booting legacy. It seems I’m having this issue only with UEFI booting devices.

                    #!ipxe
                    set fog-ip 192.168.77.146
                    set fog-webroot fog
                    set boot-url http://${fog-ip}/${fog-webroot}
                    cpuid --ext 29 && set arch x86_64 || set arch i386
                    goto get_console
                    :console_set
                    colour --rgb 0x00567a 1 ||
                    colour --rgb 0x00567a 2 ||
                    colour --rgb 0x00567a 4 ||
                    cpair --foreground 7 --background 2 2 ||
                    goto MENU
                    :alt_console
                    cpair --background 0 1 ||
                    cpair --background 1 2 ||
                    goto MENU
                    :get_console
                    console --picture http://192.168.77.146/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
                    :MENU
                    menu
                    colour --rgb 0xff0000 0 ||
                    cpair --foreground 1 1 ||
                    cpair --foreground 0 3 ||
                    cpair --foreground 4 4 ||
                    item --gap Host is NOT registered!
                    item --gap -- -------------------------------------
                    item fog.local Boot from hard disk
                    item fog.memtest Run Memtest86+
                    item fog.reginput Perform Full Host Registration and Inventory
                    item fog.reg Quick Registration and Inventory
                    item fog.deployimage Deploy Image
                    item fog.multijoin Join Multicast Session
                    item fog.sysinfo Client System Information (Compatibility)
                    item Ghost Symantec Ghost Imaging Solution
                    item Windows_PE_x86 Install 32 bit Windows OS
                    item Windows_PE_x64 Install 64 bit Windows OS
                    item PMagic Parted Magic Utility OS - 32 bit
                    item PMagic64 Parted Magic Utility OS - 64 bit
                    item GParted_x64 GParted Live 64 Bit
                    choose --default fog.local --timeout 3000 target && goto ${target}
                    :fog.local
                    sanboot --no-describe --drive 0x80 || goto MENU
                    :fog.memtest
                    kernel memdisk initrd=memtest.bin iso raw
                    initrd memtest.bin
                    boot || goto MENU
                    :fog.reginput
                    kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://192.168.77.146/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.77.146:/images/ storageip=192.168.77.146 nvme_core.default_ps_max_latency_us=0 loglevel=4 mode=manreg
                    imgfetch init_32.xz
                    boot || goto MENU
                    :fog.reg
                    kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://192.168.77.146/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.77.146:/images/ storageip=192.168.77.146 nvme_core.default_ps_max_latency_us=0 loglevel=4 mode=autoreg
                    imgfetch init_32.xz
                    boot || goto MENU
                    :fog.deployimage
                    login
                    params
                    param mac0 ${net0/mac}
                    param arch ${arch}
                    param username ${username}
                    param password ${password}
                    param qihost 1
                    isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
                    isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
                    param sysuuid ${uuid}
                    :fog.multijoin
                    login
                    params
                    param mac0 ${net0/mac}
                    param arch ${arch}
                    param username ${username}
                    param password ${password}
                    param sessionJoin 1
                    isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
                    isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
                    param sysuuid ${uuid}
                    :fog.sysinfo
                    kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://192.168.77.146/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.77.146:/images/ storageip=192.168.77.146 nvme_core.default_ps_max_latency_us=0 loglevel=4 mode=sysinfo
                    imgfetch init_32.xz
                    boot || goto MENU
                    :Ghost
                    initrd http://${fog-ip}/Ghost/ghost-uni-new.iso
                    chain memdisk iso raw ||
                    param sysuuid ${uuid}
                    :Windows_PE_x86
                    kernel http://${fog-ip}/WinPE86/wimboot
                    initrd http://${fog-ip}/WinPE86/bootmgr bootmgr
                    initrd http://${fog-ip}/WinPE86/Boot/BCD BCD
                    initrd http://${fog-ip}/WinPE86/Boot/boot.sdi boot.sdi
                    initrd http://${fog-ip}/WinPE86/sources/boot.wim boot.wim
                    boot
                    param sysuuid ${uuid}
                    :Windows_PE_x64
                    kernel http://${fog-ip}/WinPE64/wimboot
                    initrd http://${fog-ip}/WinPE64/bootmgr bootmgr
                    initrd http://${fog-ip}/WinPE64/Boot/BCD BCD
                    initrd http://${fog-ip}/WinPE64/Boot/boot.sdi boot.sdi
                    initrd http://${fog-ip}/WinPE64/sources/boot.wim boot.wim
                    boot
                    param sysuuid ${uuid}
                    :PMagic
                    kernel http://${fog-ip}/PMagic/bzImage
                    initrd http://${fog-ip}/PMagic/initrd.img
                    initrd http://${fog-ip}/PMagic/fu.img
                    initrd http://${fog-ip}/PMagic/m32.img
                    initrd http://${fog-ip}/PMagic/files.cgz
                    boot
                    param sysuuid ${uuid}
                    :PMagic64
                    kernel http://${fog-ip}/PMagic/bzImage64
                    initrd http://${fog-ip}/PMagic/initrd.img
                    initrd http://${fog-ip}/PMagic/fu.img
                    initrd http://${fog-ip}/PMagic/m64.img
                    initrd http://${fog-ip}/PMagic/files.cgz
                    boot
                    param sysuuid ${uuid}
                    :GParted_x64
                    kernel http://${fog-ip}/GParted/vmlinuz vmlinuz boot=live config components union=overlay username=user noswap noeject ip= vga=788 fetch=tftp://${fog-ip}/GParted/filesystem.squashfs
                    initrd http://${fog-ip}/GParted/initrd.img
                    boot
                    param sysuuid ${uuid}
                    :bootme
                    chain -ar http://192.168.77.146/fog/service/ipxe/boot.php##params ||
                    goto MENU
                    autoboot
                    
                    george1421G 1 Reply Last reply Reply Quote 0
                    • T
                      TheFunk35 @george1421
                      last edited by

                      @george1421 could it have something to do with the fact that bzImage32 and init_32.xz sound like they are 32 bit? Maybe I should create a menu entry “Register 64 bit UEFI machine” and replace those values with bzImage and init.xz?

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

                        @TheFunk35 said in brand new dell latitude 3500:

                        bzImage32 and init_32.xz

                        That is just an artifact of calling the url directly instead of via the iPXE menu which defines the arch.

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

                          @TheFunk35 said in brand new dell latitude 3500:

                          :fog.reg
                          kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://192.168.77.146/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.77.146:/images/ storageip=192.168.77.146 nvme_core.default_ps_max_latency_us=0 loglevel=4 mode=autoreg
                          imgfetch init_32.xz
                          boot || goto MENU

                          Well that was about what I expected its just a standard registration menu item. I also wanted to see if you had any additional kernel parameters that might be interfering with the boot, but no to that too.

                          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
                          • S
                            Sebastian Roth Moderator
                            last edited by

                            @TheFunk35 said in brand new dell latitude 3500:

                            It should be noted that I had previously tried the SATA controller in RAID ON mode and tried a registration previously and those attempts proceeded to boot the registration menu

                            Are you sure this is the case? Can you switch RAID mode back on and it proceeds booting to registration again?!

                            As we are not really sure you are seeing the exact same problem here I’d ask you to open a new topic on this. Makes things more clear and we can still cross link topics. So please open a new topic and post a picture of the actual exec error on screen there. I can move the other posts over to that new topic then.

                            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

                            T 1 Reply Last reply Reply Quote 0
                            • T
                              TheFunk35 @Sebastian Roth
                              last edited by

                              @Sebastian-Roth I can do that. It is kind of the same issue. In RAID mode the registration option loads but it just never finds a hard drive. It errors out with the same error OP posted here (can’t find drives). I would assume because the Intel RAID controller hides the actual drives.

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

                              154

                              Online

                              12.1k

                              Users

                              17.3k

                              Topics

                              155.3k

                              Posts
                              Copyright © 2012-2024 FOG Project