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

    Can't deploy on Dell Latitude 5410

    Scheduled Pinned Locked Moved
    FOG Problems
    2
    20
    1.7k
    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.
    • A
      afaure
      last edited by afaure

      Thanks for your help George !

      1. No only legacy mode and switch to UEFI after deploy

      2. Yes, i choose quick registeration and i have the error

      3. Picture with error
        Picture

      4. Yes i have tried to update my kernel for amd64 (bzimage32) / version 64 (bzimage), same issue.

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

        @afaure Ah ok, in the firmware (bios) setup. Under disk mode, change it from raid-on to ahci mode and it will find the disk. Intel will not release the raid driver to the linux community so you need to switch the computer back to ahci (standard disk) mode. You can either leave it in ahci mode forever or change it after imaging back to raid-on. But what ever mode you pick it must stay in when and after OOBE/WinSetup runs.

        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!

        A 1 Reply Last reply Reply Quote 0
        • A
          afaure @george1421
          last edited by

          @george1421 same issue…
          My pc contact FOG and i have this message error:

          No network interfaces found, your kernel is most probably missing the correct driver!
          Please check your network setup and try again…

          After that, i have the same error message (picture).

          Do you have idea ?

          Thanks.

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

            @afaure how did we slip backwards here. The picture you posted before the issue was only with the disk now we have disk and network?? That is strange.

            Next steps for debugging. Schedule a capture/deploy task (doesn’t matter which) again, but before you hit the schedule task button, tick the debug checkbox then schedule the task. PXE boot the target computer again. Then after a few screens you have to clear with the enter key you should be dropped to the FOS Linux command prompt. You may still see error messages while booting but you will still be dropped to the command prompt.

            At the FOS Linux command prompt key in the following then take a picture of the results.

            uname -r (if that fails key in uname -a)
            lsblk
            ip a s
            lspci -nn | grep -i net
            lspci -nn | grep -i sata
            lspci -nn | grep -i raid

            Wait at this command prompt for additional commands based on the results of the above. if there is too much text for one screen you may need to take and post 2 pictures.

            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!

            A 1 Reply Last reply Reply Quote 0
            • A
              afaure @george1421
              last edited by

              @george1421 said in Can't deploy on Dell Latitude 5410:

              Next steps for debugging. Schedule a capture/deploy task (doesn’t matter which) again, but before you hit the schedule task button, tick the debug checkbo

              Hello George,

              The picture -> https://ibb.co/0ySfZNj

              Thanks for your help

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

                @afaure Ok the driver for that network adapter first appeared in linux 5.5. I’m missing the picture of the first 2 commands I asked for. The good thing the sata adapter is being seen by linux.

                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!

                A 1 Reply Last reply Reply Quote 0
                • A
                  afaure @george1421
                  last edited by

                  @george1421 said in Can't deploy on Dell Latitude 5410:

                  Ok the driver for that network adapter first appeared in linux 5.5. I’m missing the picture of the first 2 commands I asked for. The good thing the sata adapter is being seen by linux.

                  I have typed all commands:
                  uname -r
                  lsblk
                  ip a s
                  …

                  I have missed somethings 😮 ?

                  Thanks 🙂

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

                    @afaure I think from the picture you did too soon.

                    from the picture uname -r or uname -a should have returned a value. It should be a number like 5.6.18 or 4.19.65

                    The lsblk should have displayed the block devices in the system. It could be blank but it would be really rare.

                    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!

                    A 1 Reply Last reply Reply Quote 0
                    • A
                      afaure @george1421
                      last edited by

                      @george1421 said in Can't deploy on Dell Latitude 5410:

                      I think from the picture you did too soon.
                      from the picture uname -r or uname -a should have returned a value. It should be a number like 5.6.18 or 4.19.65
                      The lsblk should have displayed the block devices in the system. It could be blank but it would be really rare.

                      Ok, picture with info -> https://ibb.co/vzxGFdh
                      I’m off for few days, i’ll be back wednesday at office to read your message.

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

                        @afaure Ok from the new picture. You need to download the latest FOS Linux kernel using the Web UI FOG Configuration -> Kernel You need to install 5.6.18 kernel and the network adapter will work. You will need both 64 bit and 32 bit versions.

                        From the lsblk command the disk is there an available now.

                        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!

                        A 2 Replies Last reply Reply Quote 0
                        • A
                          afaure @george1421
                          last edited by

                          @george1421 thanks !!!
                          I try your solution wednesday !

                          1 Reply Last reply Reply Quote 1
                          • A
                            afaure @george1421
                            last edited by

                            @george1421 same issue with the kernel 5.6.18 😞

                            george1421G 1 Reply Last reply Reply Quote 0
                            • george1421G
                              george1421 Moderator @afaure
                              last edited by Sebastian Roth

                              @afaure So when you schedule a debug mode and then at the FOS Linux command prompt you key in uname -r or uname -a it says 5.6.18 now?

                              Leave it in debug mode because there are a few more debug commands we can use.

                              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!

                              A 1 Reply Last reply Reply Quote 0
                              • A
                                afaure @george1421
                                last edited by

                                @george1421
                                uname -a said 4.19.145
                                lsblk list all of partitions

                                If i try to register a new pc, same issue
                                PC contact fog but can’t deploy an image…

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

                                  @afaure said in Can't deploy on Dell Latitude 5410:

                                  4.19.145

                                  OK for some reason the upgraded to the kernel did not make it correctly. This uname command should have returned 5.6.18. So I understand why you have the same issue as before.

                                  Please use the FOG Configuration -> Kernel to update both bzImage and bzImage32 to 5.6.18. If the webgui method doesn’t work then we can use the manual update process. Follow the manual instructions here: https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update

                                  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!

                                  A 1 Reply Last reply Reply Quote 0
                                  • A
                                    afaure @george1421
                                    last edited by

                                    @george1421 i have tried manual update and doesn’t work.
                                    Same version, 4.19.145 !

                                    How i can download the latest version ?
                                    Do you have link for wget ?

                                    Thanks

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

                                      @afaure I don’t understand what is going wrong here.

                                      OK there is an alternate manual process. Go to this web site: https://fogproject.org/kernels/

                                      Download Kernel.TomElliott.5.6.18.64 and rename to bzImage (watch your case)
                                      Download Kernel.TomElliott.5.6.18.32 and rename to bzImage32 (watch your case).

                                      Move those files to your fog server in the following directory replacing the existing files. /var/www/html/fog/service/ipxe

                                      Once the file is there then run this command to confirm the right version is in place file bzImage it should say in the text 5.6.18

                                      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!

                                      A 1 Reply Last reply Reply Quote 0
                                      • A
                                        afaure @george1421
                                        last edited by

                                        @george1421 thanks dude !
                                        It’s works !!!

                                        Thanks for your help

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

                                        118

                                        Online

                                        12.1k

                                        Users

                                        17.3k

                                        Topics

                                        155.3k

                                        Posts
                                        Copyright © 2012-2024 FOG Project