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

Maj bzimage

Scheduled Pinned Locked Moved
Hardware Compatibility
4
34
4.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.
  • J
    jps
    last edited by Sep 15, 2020, 8:29 AM

    When I use the “unofficial” 5.6.18 kernel I can’t connect the machine Dell 5500/5300 in 100 MB or 1 GB.

    G 1 Reply Last reply Sep 15, 2020, 11:45 AM Reply Quote 0
    • G
      george1421 Moderator @jps
      last edited by Sep 15, 2020, 11:45 AM

      @jps said in Maj bzimage:

      “unofficial” 5.6.18

      Just so I’m clear, what do we mean unofficial? Is this the one that is downloaded from the FOG servers using the built in FOG web ui or my one-off kernel?

      For these Dell 5500’s can you provide the hardware IDs of this network adapter? It will be in device manager -> device -> details -> hardware IDs. The value we need looks like this PCI\VEN_8086&DEV_15BB&CC_0200 Also how are these network adapters connect to the computer? Are they built in, usb dongle, WD19 port replicator, how?

      Lastly what do you mean you can’t connect? Do you see the FOG iPXE menu, or you can see the menu but when you pick an option FOS Linux can’t see the network adapter?

      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
      • J
        jps
        last edited by Sep 15, 2020, 12:55 PM

        I repeat what Sebastian says “unoffical”, I mean “Kernel.TomElliott.5.6.18.64” . The hardware IDs is PCI\VEN_8086&DEV_15BE&CC_0200 built in. When I pick an option FOS Linux can’t get an adresse IP from DHCP and don’t know if FOS see the network adapter.

        G 1 Reply Last reply Sep 15, 2020, 1:17 PM Reply Quote 0
        • G
          george1421 Moderator @jps
          last edited by george1421 Sep 15, 2020, 7:18 AM Sep 15, 2020, 1:17 PM

          @jps The network adapter 8086:15BE first appeared in the linux kernel 4.12 and exists in these kernels [ 4.12–4.20, 5.0–5.8 ]. With that said 5.6.18 should have the required driver installed. (it should just work).

          To debug this issue schedule another deploy/capture task but before you hit the schedule task button tick the debug checkbox then schedule the task.

          PXE boot the 5300 or 5500 computer. After a few screens of text you need to clear with the enter key you will be dropped to a linux command prompt on the target computer. This is the FOS Linux command prompt.

          Please post the results of the following commands. (a clear screen shot of the text taken with a mobile phone will work here).

          lspci -nn | grep -i net

          ip a s

          uname -a

          Lets start with those. I have another command for you to key in but lets make sure we are getting an output of those first.

          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
          • J
            jps
            last edited by Sep 17, 2020, 2:53 PM

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • J
              jps
              last edited by Sep 17, 2020, 2:56 PM

              Here they are :

              WP_20200917_003.jpg WP_20200917_002.jpg WP_20200917_001.jpg

              G 1 Reply Last reply Sep 17, 2020, 5:28 PM Reply Quote 0
              • G
                george1421 Moderator @jps
                last edited by george1421 Sep 17, 2020, 11:29 AM Sep 17, 2020, 5:28 PM

                @jps Ok looking at the pictures everything looks good (it should be working), but do see for eno2 there is no carrier (cable not plugged in). I am a little surprised as its named eno2 but if that is what the hardware selected its ok, because its a logical name.

                Do we know why its saying the network cable isn’t plugged in? I would think that it had to be if the system pxe booted this far.

                If you are still at the fos linux command prompt you can test this command and see what it produces
                /sbin/udhcpc -i eno2 --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!

                1 Reply Last reply Reply Quote 0
                • J
                  jps
                  last edited by jps Sep 18, 2020, 2:48 AM Sep 18, 2020, 8:41 AM

                  Here it is
                  I specify I re-run “ip a s” and there is no “no-carrier”

                  WP_20200918_002.jpg

                  G 1 Reply Last reply Sep 18, 2020, 12:08 PM Reply Quote 0
                  • G
                    george1421 Moderator @jps
                    last edited by Sep 18, 2020, 12:08 PM

                    @jps Ok this is interesting an also makes me think.

                    I want you to do this in sequence step by step. If you are still at the command prompt just reboot the target computer the job will still exist in FOG.

                    1. PXE boot the computer in debug mode.
                    2. As soon as you get to the FOS Linux command prompt key in ip a s. Confirm that you do not have an IP address
                    3. Wait ~30 seconds.
                    4. Key in /sbin/udhcpc -i eno2 --now
                    5. Confirm that it detects an IP address.

                    If the above does work then time resolves the problem. This is usually an indication of spanning tree being used on your building network switch. I want you to check with your network team to ensure on of the fast spanning tree protocols (portfast, RSTP, MSTP, fast-stp, or what ever your switch mfg calls it) is used on the network port where the computer is. Standard spanning tree reacts to slowly because FOS Linux boots in 10 seconds and standard spanning tree doesn’t start forwarding data for 27 seconds. By the time standard spanning tree starts forwarding data FOS Linux has already given up. That is what I think.

                    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
                    • J
                      jps
                      last edited by Sep 23, 2020, 12:27 PM

                      I could not reiterate the case where I have no ip address. On the other hand at boot (not as a debug task) I have this: WP_20200923_001.jpg

                      1 Reply Last reply Reply Quote 0
                      • J
                        jps @Sebastian Roth
                        last edited by Sep 23, 2020, 1:11 PM

                        This post is deleted!
                        1 Reply Last reply Reply Quote 0
                        • J
                          jps @Sebastian Roth
                          last edited by Sep 23, 2020, 1:15 PM

                          @Sebastian-Roth When I reboot the machine to it’s installed OS it runs on gigabit.

                          1 Reply Last reply Reply Quote 0
                          • S
                            Sebastian Roth Moderator
                            last edited by Sep 23, 2020, 4:49 PM

                            @jps command not found…?! Possibly and issue in the scripts?! I will take a look.

                            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 0
                            • T
                              Tom Elliott
                              last edited by Sep 23, 2020, 5:50 PM

                              What version of FOG are you running?

                              I ask because the “Starting eno2 interface” hasn’t been around since 1.3.0 was released.

                              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

                              J 1 Reply Last reply Sep 25, 2020, 8:17 AM Reply Quote 1
                              • J
                                jps @Tom Elliott
                                last edited by Sep 25, 2020, 8:17 AM

                                @Tom-Elliott Version: 5929

                                1 Reply Last reply Reply Quote 0
                                • S
                                  Sebastian Roth Moderator
                                  last edited by Sep 25, 2020, 8:21 AM

                                  @jps While you can go with just updating kernel and init files with some manual adjustments in the config I am wondering if a proper upgrade to 1.5.9 would be the better choice in your case. We fixed hunderds of bugs since then.

                                  Why so you still use such an old version?

                                  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 0
                                  • 1
                                  • 2
                                  • 2 / 2
                                  2 / 2
                                  • First post
                                    28/34
                                    Last post

                                  158

                                  Online

                                  12.0k

                                  Users

                                  17.3k

                                  Topics

                                  155.2k

                                  Posts
                                  Copyright © 2012-2024 FOG Project