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

    Dell Latitude 5510 No network interface found! Kernel might not have the correct driver!

    Scheduled Pinned Locked Moved Solved
    General Problems
    10
    29
    11.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.
    • R
      rodrigonm @george1421
      last edited by

      @george1421 Thanks a lot for your reply. Sorry, this was my first time and I will create a new post.

      1 Reply Last reply Reply Quote 1
      • L
        LaChagnasse
        last edited by LaChagnasse

        Hi everyone, we have exactly the same issue on the same computer (latitude 5510). I updated the kernel by 5.6.18 for 32 and 64 but still have the same issue (fog 1.5.9).

        lspci output :

        00:14.3 Network Controller [0280]: Intel Corporation Device [8086:02f0]
        00:1f.6 Ethernet Controller [0200]: Interl Corporation Ethernet Connection (10) I219-V [8086:0d4f}

        Any help would be much appreciated

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

          @lachagnasse said in Dell Latitude 5510 No network interface found! Kernel might not have the correct driver!:

          [8086:0d4f]

          Is/was first supported in linux kernel 5.5 so the 5.6.18 kernel should be working for you.

          On the fog server’s host OS console key in the following.

          cd /var/www/html/fog/service/ipxe
          file bzImage
          

          The file command will print out the kernel version. Make sure it says 5.6.18.

          Also when you pxe boot directly into image or pick registration from the FOG iPXE menu make sure it says bzImage that gets transferred to the target computer. You will have to read fast but it will say bzImage … OK then init.xz … OK. The key is to make sure its bzImage that gets transferred and not some other name like bzImage4152 or such.

          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!

          L B 2 Replies Last reply Reply Quote 0
          • L
            LaChagnasse @george1421
            last edited by

            @george1421
            Thank you for your help, so it seems it’s okay :
            bzImage: Linux kernel x86 boot executable bzImage, version 5.6.18 (sebastian@Tollana) #1 SMP Tue Jun 16 16:55:16 CDT 2020, RO-rootFS, swap_dev 0x8, Normal VGA

            And yes we can see bzImage … OK then init.xz… OK

            (We tried with the custom file earlier and could see bzImage553 before, we read the thread by date descending… Set the original back after.)

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

              @lachagnasse said in Dell Latitude 5510 No network interface found! Kernel might not have the correct driver!:

              Hi everyone, we have exactly the same issue on the same computer (latitude 5510).

              Please take a picture if the error on screen and post 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

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

                @lachagnasse Ok this one is new/strange.

                I want you to schedule a new capture/deploy (doesn’t matter) but before you hit the schedule task button, tick the debug checkbox then schedule the task.

                PXE boot the target computer. You will still get the error but after a few screens of text you need to clear with the enter key, you should be dropped to the FOS Linux command prompt.

                At the fos linux command prompt key in the following ip a s see if it lists more than the loopback network adapter. Hopefully there is more than just the loop back.

                If it only shows the loop back then key in the following. lspci -nn | grep -i net. I know you have already done that because you have posted the results. I’m putting this here for others that might find this post.

                Using the output you already provided.

                00:14.3 Network Controller [0280]: Intel Corporation Device [8086:02f0]
                00:1f.6 Ethernet Controller [0200]: Interl Corporation Ethernet Connection (10) I219-V [8086:0d4f}
                

                Beyond the device ID that says its an i219-v network adapter the hardware location is important for this next bit {00:1f.6}
                Key in the following command (similar to before but with different details) lspci -k -nn | more

                With that command look through the output for the hardware location 00:1f.6. With a mobile phone take a clear shot of that line. I need to see the line with the 00:1f.6 on it plus the following 2-3 lines. I need to see the kernel driver that is being used.

                And finally key in uname -r that should return the kernel version 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!

                1 Reply Last reply Reply Quote 0
                • L
                  LaChagnasse @Sebastian Roth
                  last edited by

                  @sebastian-roth Sorry, i was updating the firmware but in the wrong directory. I messed up something in the www path and there was two service/ipxe directory, so stupid mistake, my bad

                  thank you for the help again

                  1 Reply Last reply Reply Quote 0
                  • Chris WhiteleyC
                    Chris Whiteley @asbenavides
                    last edited by

                    @asbenavides we have imaged the Latitude 5510’s. I am trying to remember if we just used the USB-C to ethernet adapters or if we used the onboard ethernet. It was a while ago.

                    1 Reply Last reply Reply Quote 0
                    • G
                      guilherme.leme 0
                      last edited by guilherme.leme 0

                      Guys, I have some Dell Latitude 5510 with the same problem, I tested it with a USB-C adapter, and it really works, I don’t know what the explanation is but it works !!

                      1 Reply Last reply Reply Quote 0
                      • B
                        Birgit Godfrey @george1421
                        last edited by

                        @george1421 we had the same issue with an HP ProBook 650. We updated the kernel initially with the latest update from Sept 7, v. 4.19.143, and no go. Scrolling further down we see the higher version of 5.6.18 and it works. Any reason why the newest version is back to 4.xx? Thanks.

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

                          @birgit-godfrey said in Dell Latitude 5510 No network interface found! Kernel might not have the correct driver!:

                          Any reason why the newest version is back to 4.xx?

                          Yes there is a reason. The developers are sticking to a release strategy that stays in line with the linux kernel developers and the latest Long Term Support kernel. The latest linux kernel LTS release is 4.19.x. Realizing that new drivers are added to the “current” linux kernel releases the developers have released 5.6.18 where there was many new drivers added to linux 5.5.x series. The FOG developers were told that the next LTS kernel would be 5.10.x. When LTS has been set on 5.10.x the FOG Developers will release a new “current” release.

                          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!

                          B 1 Reply Last reply Reply Quote 0
                          • B
                            Birgit Godfrey @george1421
                            last edited by

                            @george1421 Perfect, thanks for the quick reply.

                            1 Reply Last reply Reply Quote 0
                            • J
                              jmanen @george1421
                              last edited by

                              @george1421
                              Merci cela à fonctionner avec bzImage553 👍
                              Bonne continuation
                              JCH

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

                              187

                              Online

                              12.0k

                              Users

                              17.3k

                              Topics

                              155.2k

                              Posts
                              Copyright © 2012-2024 FOG Project