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

bnx2x fails to load firmware on Dell R430

Scheduled Pinned Locked Moved Solved
Hardware Compatibility
4
54
24.9k
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.
  • G
    grey @grey
    last edited by grey Sep 15, 2016, 5:09 PM Sep 15, 2016, 11:08 PM

    @grey ok just needed to hit enter… here is the relevant part of the syslog
    I have the whole log if I did’nt capture what you wanted.

    Sep 15 22:45:51 fogclient user.warn kernel: bnx2x 0000:04:00.1: Direct firmware load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
    Sep 15 22:45:51 fogclient user.err kernel: bnx2x: [bnx2x_init_firmware:13444(eth1)]Can't load firmware file bnx2x/bnx2x-e2-7.13.1.0.fw
    Sep 15 22:45:51 fogclient user.err kernel: bnx2x: [bnx2x_func_hw_init:5785(eth1)]Error loading firmware
    Sep 15 22:45:51 fogclient user.err kernel: bnx2x: [bnx2x_nic_load:2727(eth1)]HW init failed, aborting
    Sep 15 22:46:26 fogclient user.warn kernel: bnx2x 0000:05:00.0: Direct firmware load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
    Sep 15 22:46:26 fogclient user.err kernel: bnx2x: [bnx2x_init_firmware:13444(eth2)]Can't load firmware file bnx2x/bnx2x-e2-7.13.1.0.fw
    Sep 15 22:46:26 fogclient user.err kernel: bnx2x: [bnx2x_func_hw_init:5785(eth2)]Error loading firmware
    Sep 15 22:46:26 fogclient user.err kernel: bnx2x: [bnx2x_nic_load:2727(eth2)]HW init failed, aborting
    Sep 15 22:47:01 fogclient user.warn kernel: bnx2x 0000:05:00.1: Direct firmware load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
    Sep 15 22:47:01 fogclient user.err kernel: bnx2x: [bnx2x_init_firmware:13444(eth3)]Can't load firmware file bnx2x/bnx2x-e2-7.13.1.0.fw
    Sep 15 22:47:01 fogclient user.err kernel: bnx2x: [bnx2x_func_hw_init:5785(eth3)]Error loading firmware
    Sep 15 22:47:01 fogclient user.err kernel: bnx2x: [bnx2x_nic_load:2727(eth3)]HW init failed, aborting
    Sep 15 22:48:47 fogclient user.notice kernel: random: nonblocking pool is initialized
    
    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator @grey
      last edited by george1421 Sep 15, 2016, 5:09 PM Sep 15, 2016, 11:08 PM

      @grey When you do a debug capture the FOS engine will boot just like its going to do a capture, but instead of capturing it will print a bunch of instructions on the screen. You have to press enter a few times (on the target computer)

      … ok you just posted the logs that is a good find in the logs.

      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!

      G 1 Reply Last reply Sep 15, 2016, 11:19 PM Reply Quote 0
      • G
        grey @george1421
        last edited by Sep 15, 2016, 11:19 PM

        @george1421
        i’ve been reading through all this and i wanted to make this distinction

        this is the RJ45 1 gig ethernet nic, the one i’m using for imageing
        2:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:165f]

        this is a 10g fiberchannel port and is not important for imaging
        04:00.1 Ethernet controller [0200]: Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Ethernet [14e4:168e] (rev 10)

        just don’t want anyone to waste effort on the 10g port as its not being used for this.

        G 1 Reply Last reply Sep 15, 2016, 11:23 PM Reply Quote 0
        • G
          george1421 Moderator @grey
          last edited by george1421 Sep 15, 2016, 5:25 PM Sep 15, 2016, 11:23 PM

          @grey OK then, we are looking for device 02:00.0. If I understand the logs correctly you posted the error for device 04:00.0

          Just to make sure eth0 and eth1 are the 1GbE nics?

          I’ve also been searching on that error, I did find two posts that were similar errors
          https://github.com/coreos/bugs/issues/450
          https://lkml.org/lkml/2016/5/9/797

          I’m still trying to understand if the error -2 means the firmware doesn’t exist or its some other indication.

          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!

          G 1 Reply Last reply Sep 15, 2016, 11:35 PM Reply Quote 0
          • T
            Tom Elliott
            last edited by Sep 15, 2016, 11:32 PM

            You mind rerunning the installer? I’ve added the missing firmware to the kernel build.

            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

            G G 3 Replies Last reply Sep 15, 2016, 11:38 PM Reply Quote 1
            • G
              grey @george1421
              last edited by Sep 15, 2016, 11:35 PM

              @george1421

              I just got a moment to do the same thing, heres more of the logfile,

              the devices stuff is difficult for me to interprete, the device i need to work is Broadcom 5720 DP 1Gb Network Interface * I think*

              Sep 15 22:44:45 fogclient user.info kernel: tg3 0000:02:00.1 eth5: Link is up at 1000 Mbps, full duplex
              Sep 15 22:44:45 fogclient user.info kernel: tg3 0000:02:00.1 eth5: Flow control is off for TX and off for RX
              Sep 15 22:44:45 fogclient user.info kernel: tg3 0000:02:00.1 eth5: EEE is disabled
              Sep 15 22:45:15 fogclient user.warn kernel: bnx2x 0000:04:00.0: Direct firmware load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
              Sep 15 22:45:15 fogclient user.err kernel: bnx2x: [bnx2x_init_firmware:13444(eth0)]Can’t load firmware file bnx2x/bnx2x-e2-7.13.1.0.fw
              Sep 15 22:45:15 fogclient user.err kernel: bnx2x: [bnx2x_func_hw_init:5785(eth0)]Error loading firmware
              Sep 15 22:45:15 fogclient user.err kernel: bnx2x: [bnx2x_nic_load:2727(eth0)]HW init failed, aborting
              Sep 15 22:45:51 fogclient user.warn kernel: bnx2x 0000:04:00.1: Direct firmware load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
              Sep 15 22:45:51 fogclient user.err kernel: bnx2x: [bnx2x_init_firmware:13444(eth1)]Can’t load firmware file bnx2x/bnx2x-e2-7.13.1.0.fw
              Sep 15 22:45:51 fogclient user.err kernel: bnx2x: [bnx2x_func_hw_init:5785(eth1)]Error loading firmware
              Sep 15 22:45:51 fogclient user.err kernel: bnx2x: [bnx2x_nic_load:2727(eth1)]HW init failed, aborting
              Sep 15 22:46:26 fogclient user.warn kernel: bnx2x 0000:05:00.0: Direct firmware load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
              Sep 15 22:46:26 fogclient user.err kernel: bnx2x: [bnx2x_init_firmware:13444(eth2)]Can’t load firmware file bnx2x/bnx2x-e2-7.13.1.0.fw
              Sep 15 22:46:26 fogclient user.err kernel: bnx2x: [bnx2x_func_hw_init:5785(eth2)]Error loading firmware
              Sep 15 22:46:26 fogclient user.err kernel: bnx2x: [bnx2x_nic_load:2727(eth2)]HW init failed, aborting
              Sep 15 22:47:01 fogclient user.warn kernel: bnx2x 0000:05:00.1: Direct firmware load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
              Sep 15 22:47:01 fogclient user.err kernel: bnx2x: [bnx2x_init_firmware:13444(eth3)]Can’t load firmware file bnx2x/bnx2x-e2-7.13.1.0.fw
              Sep 15 22:47:01 fogclient user.err kernel: bnx2x: [bnx2x_func_hw_init:5785(eth3)]Error loading firmware
              Sep 15 22:47:01 fogclient user.err kernel: bnx2x: [bnx2x_nic_load:2727(eth3)]HW init failed, aborting
              Sep 15 22:48:47 fogclient user.notice kernel: random: nonblocking pool is initialized
              Sep 15 22:49:12 fogclient user.info kernel: usb 1-1.4: USB disconnect, device number 3
              Sep 15 22:49:20 fogclient user.info kernel: usb 1-1.4: new high-speed USB device number 5 using ehci-pci
              Sep 15 22:49:20 fogclient user.info kernel: usb-storage 1-1.4:1.0: USB Mass Storage device detected
              Sep 15 22:49:20 fogclient user.info kernel: scsi host6: usb-storage 1-1.4:1.0
              Sep 15 22:49:21 fogclient user.notice kernel: scsi 6:0:0:0: Direct-Access SanDisk Cruzer Blade 1.00 PQ: 0 ANSI: 6
              Sep 15 22:49:21 fogclient user.notice kernel: sd 6:0:0:0: [sdi] 15630336 512-byte logical blocks: (8.00 GB/7.45 GiB)
              Sep 15 22:49:21 fogclient user.notice kernel: sd 6:0:0:0: [sdi] Write Protect is off
              Sep 15 22:49:21 fogclient user.debug kernel: sd 6:0:0:0: [sdi] Mode Sense: 43 00 00 00
              Sep 15 22:49:21 fogclient user.notice kernel: sd 6:0:0:0: [sdi] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
              Sep 15 22:49:21 fogclient user.info kernel: sdi: sdi1
              Sep 15 22:49:21 fogclient user.notice kernel: sd 6:0:0:0: [sdi] Attached SCSI removable disk
              Sep 15 22:49:27 fogclient auth.info sshd[4338]: Server listening on 0.0.0.0 port 22.
              Sep 15 22:53:32 fogclient daemon.info init: starting pid 4575, tty ‘/dev/tty0’: ‘-/bin/bash’
              Sep 15 22:57:49 fogclient user.info kernel: usb 1-1.4: USB disconnect, device number 5
              Sep 15 23:00:41 fogclient user.info kernel: usb 1-1.4: new high-speed USB device number 6 using ehci-pci
              Sep 15 23:00:41 fogclient user.info kernel: usb-storage 1-1.4:1.0: USB Mass Storage device detected
              Sep 15 23:00:41 fogclient user.info kernel: scsi host7: usb-storage 1-1.4:1.0
              Sep 15 23:00:42 fogclient user.notice kernel: scsi 7:0:0:0: Direct-Access SanDisk Cruzer Blade 1.00 PQ: 0 ANSI: 6
              Sep 15 23:00:42 fogclient user.notice kernel: sd 7:0:0:0: [sdj] 15630336 512-byte logical blocks: (8.00 GB/7.45 GiB)
              Sep 15 23:00:42 fogclient user.notice kernel: sd 7:0:0:0: [sdj] Write Protect is off
              Sep 15 23:00:42 fogclient user.debug kernel: sd 7:0:0:0: [sdj] Mode Sense: 43 00 00 00
              Sep 15 23:00:42 fogclient user.notice kernel: sd 7:0:0:0: [sdj] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
              Sep 15 23:00:42 fogclient user.info kernel: sdj: sdj1
              Sep 15 23:00:42 fogclient user.notice kernel: sd 7:0:0:0: [sdj] Attached SCSI removable disk
              Sep 15 23:00:54 fogclient user.err kernel: FAT-fs (sdi1): unable

              1 Reply Last reply Reply Quote 0
              • G
                grey @Tom Elliott
                last edited by Sep 15, 2016, 11:38 PM

                @Tom-Elliott

                sure np

                1 Reply Last reply Reply Quote 0
                • G
                  george1421 Moderator @Tom Elliott
                  last edited by Sep 16, 2016, 12:00 AM

                  @Tom-Elliott said in bnx2x fails to load firmware on Dell R430:

                  You mind rerunning the installer? I’ve added the missing firmware to the kernel build.

                  So does that bring the current kernel to 4.7.4? Just for my knowledge.

                  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 Sep 16, 2016, 12:01 AM Reply Quote 0
                  • T
                    Tom Elliott @george1421
                    last edited by Sep 16, 2016, 12:01 AM

                    @george1421 No, it is the version of the current kernel (4.7.3) as on kernel.org

                    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

                    G 1 Reply Last reply Sep 16, 2016, 12:02 AM Reply Quote 0
                    • G
                      george1421 Moderator @Tom Elliott
                      last edited by george1421 Sep 15, 2016, 6:02 PM Sep 16, 2016, 12:02 AM

                      @Tom-Elliott Understood, thx.

                      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
                      • G
                        grey @Tom Elliott
                        last edited by Sep 16, 2016, 12:16 AM

                        @Tom-Elliott said in bnx2x fails to load firmware on Dell R430:

                        You mind rerunning the installer? I’ve added the missing firmware to the kernel build.

                        ok, re-installed fog rebooted on the new kernel, drivers loaded fine but all drivers say there is no link, although its running on a pxe kernel :-p. all the firmware errors are gone. I’m running out of time here today, but I’ll jump into tomorrow and see what the link issue is about. the debug kernel selection is still loading by default so i guess it will do that until i delete the task.

                        T G 2 Replies Last reply Sep 16, 2016, 12:22 AM Reply Quote 0
                        • T
                          Tom Elliott @grey
                          last edited by Sep 16, 2016, 12:22 AM

                          @grey The phandle messages are non-impacting, and you can probably turn back down the loglevel. The drivers with no link simply means the kernel can’t find a corresponding device for the driver being loaded.

                          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

                          1 Reply Last reply Reply Quote 0
                          • G
                            george1421 Moderator @grey
                            last edited by Sep 16, 2016, 12:27 AM

                            @grey Correct it will stay in debug capture until the capture completes or you cancel the task. its kind of handy for debugging your hardware.

                            As for the no link issue I would go back to the error logs on the FOS client. Also the lspci command (one of the switches) should show what kernel driver is managing which device.

                            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 Sep 16, 2016, 6:06 AM

                              @grey said:

                              ok, re-installed fog rebooted on the new kernel, drivers loaded fine but all drivers say there is no link, although its running on a pxe kernel :-p.

                              As we can see from your earlier posts you have four NICs in that one server. Which one is connected and how often do you see the message “no link”??

                              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

                              G 1 Reply Last reply Sep 16, 2016, 8:39 PM Reply Quote 0
                              • G
                                grey @Sebastian Roth
                                last edited by Sep 16, 2016, 8:39 PM

                                @Sebastian-Roth

                                ok PNX2X is the fiber ports so we can disregard them, oddly they where enumerated first so thats part of the problem as i thought the ethernet ports would be first, the TG3 driver is the ethernet port and the ones we are interested in. eth5 is the port thats active and does have link, although its not getting a DHCP assigment ( statically assigned to that mac ), even though at pexe boot it is.

                                Settings for eth1: PNX2X
                                Supported ports: [ FIBRE ]
                                Supported link modes: 1000baseT/Full
                                10000baseT/Full
                                Supported pause frame use: Symmetric Receive-only
                                Supports auto-negotiation: No
                                Advertised link modes: 10000baseT/Full
                                Advertised pause frame use: No
                                Advertised auto-negotiation: No
                                Speed: Unknown!
                                Duplex: Unknown! (255)
                                Port: FIBRE
                                PHYAD: 1
                                Transceiver: internal
                                Auto-negotiation: off
                                Supports Wake-on: g
                                Wake-on: d
                                Current message level: 0x00000000 (0)

                                Link detected: no
                                

                                Settings for eth2:PNX2X
                                Supported ports: [ FIBRE ]
                                Supported link modes: 1000baseT/Full
                                10000baseT/Full
                                Supported pause frame use: Symmetric Receive-only
                                Supports auto-negotiation: No
                                Advertised link modes: 10000baseT/Full
                                Advertised pause frame use: No
                                Advertised auto-negotiation: No
                                Speed: Unknown!
                                Duplex: Unknown! (255)
                                Port: FIBRE
                                PHYAD: 1
                                Transceiver: internal
                                Auto-negotiation: off
                                Supports Wake-on: g
                                Wake-on: d
                                Current message level: 0x00000000 (0)

                                Link detected: no
                                

                                Settings for eth3:PNX2X
                                Supported ports: [ FIBRE ]
                                Supported link modes: 1000baseT/Full
                                10000baseT/Full
                                Supported pause frame use: Symmetric Receive-only
                                Supports auto-negotiation: No
                                Advertised link modes: 10000baseT/Full
                                Advertised pause frame use: No
                                Advertised auto-negotiation: No
                                Speed: Unknown!
                                Duplex: Unknown! (255)
                                Port: FIBRE
                                PHYAD: 1
                                Transceiver: internal
                                Auto-negotiation: off
                                Supports Wake-on: g
                                Wake-on: d
                                Current message level: 0x00000000 (0)

                                Link detected: no
                                

                                Settings for eth4:
                                Supported ports: [ TP ]
                                Supported link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
                                Supported pause frame use: No
                                Supports auto-negotiation: Yes
                                Advertised link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
                                Advertised pause frame use: Symmetric
                                Advertised auto-negotiation: Yes
                                Speed: Unknown!
                                Duplex: Unknown! (255)
                                Port: Twisted Pair
                                PHYAD: 1
                                Transceiver: internal
                                Auto-negotiation: on
                                MDI-X: Unknown
                                Supports Wake-on: g
                                Wake-on: d
                                Current message level: 0x000000ff (255)
                                drv probe link timer ifdown ifup rx_err tx_err
                                Link detected: no


                                Settings for eth5:
                                Supported ports: [ TP ]
                                Supported link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
                                Supported pause frame use: No
                                Supports auto-negotiation: Yes
                                Advertised link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
                                Advertised pause frame use: Symmetric
                                Advertised auto-negotiation: Yes
                                Link partner advertised link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                Link partner advertised pause frame use: No
                                Link partner advertised auto-negotiation: Yes
                                Speed: 1000Mb/s
                                Duplex: Full
                                Port: Twisted Pair
                                PHYAD: 2
                                Transceiver: internal
                                Auto-negotiation: on
                                MDI-X: off
                                Supports Wake-on: g
                                Wake-on: d
                                Current message level: 0x000000ff (255)
                                drv probe link timer ifdown ifup rx_err tx_err
                                Link detected: yes


                                Settings for eth6:
                                Supported ports: [ TP ]
                                Supported link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
                                Supported pause frame use: No
                                Supports auto-negotiation: Yes
                                Advertised link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
                                Advertised pause frame use: Symmetric
                                Advertised auto-negotiation: Yes
                                Speed: Unknown!
                                Duplex: Unknown! (255)
                                Port: Twisted Pair
                                PHYAD: 1
                                Transceiver: internal
                                Auto-negotiation: on
                                MDI-X: Unknown
                                Supports Wake-on: g
                                Wake-on: d
                                Current message level: 0x000000ff (255)
                                drv probe link timer ifdown ifup rx_err tx_err
                                Link detected: no


                                Settings for eth7:
                                Supported ports: [ TP ]
                                Supported link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
                                Supported pause frame use: No
                                Supports auto-negotiation: Yes
                                Advertised link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
                                Advertised pause frame use: Symmetric
                                Advertised auto-negotiation: Yes
                                Speed: Unknown!
                                Duplex: Unknown! (255)
                                Port: Twisted Pair
                                PHYAD: 2
                                Transceiver: internal
                                Auto-negotiation: on
                                MDI-X: Unknown
                                Supports Wake-on: g
                                Wake-on: d
                                Current message level: 0x000000ff (255)
                                drv probe link timer ifdown ifup rx_err tx_err
                                Link detected: no

                                1 Reply Last reply Reply Quote 0
                                • G
                                  george1421 Moderator
                                  last edited by george1421 Sep 16, 2016, 3:12 PM Sep 16, 2016, 9:11 PM

                                  OK this is good promising news. eth5 is getting a link up but no IP address in FOS but you can pxe boot and iPXE is getting an IP address because the FOS kernel (bzImage) and VHD (init.xz) are being sent to the target computer. When we see this we typically see that spanning tree is turned on at the network switch. Spanning tree takes about 27 seconds for the port to start forwarding data. The FOS engine is so fast that it has already given up by the time spanning tree starts to forward data.

                                  On these ports you need to enable one of the fast spanning tree prototocols (port fast, fast stp, rstp, or what ever your switch mfg calls it). A quick check to see if its a spanning tree issue is to put an unmanaged switch between the building switch and the target computer. This unmanaged switch keeps the port on the building switch from winking as the iPXE kernel hands off the network interface to the FOS engine.

                                  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!

                                  G 1 Reply Last reply Sep 16, 2016, 9:27 PM Reply Quote 0
                                  • G
                                    grey @george1421
                                    last edited by Sep 16, 2016, 9:27 PM

                                    @george1421 said in bnx2x fails to load firmware on Dell R430:

                                    OK this is good promising news. eth5 is getting a link up but no IP address in FOS but you can pxe boot and iPXE is getting an IP address because the FOS kernel (bzImage) and VHD (init.xz) are being sent to the target computer. When we see this we typically see that spanning tree is turned on at the network switch. Spanning tree takes about 27 seconds for the port to start forwarding data. The FOS engine is so fast that it has already given up by the time spanning tree starts to forward data.

                                    On these ports you need to enable one of the fast spanning tree prototocols (port fast, fast stp, rstp, or what ever your switch mfg calls it). A quick check to see if its a spanning tree issue is to put an unmanaged switch between the building switch and the target computer. This unmanaged switch keeps the port on the building switch from winking as the iPXE kernel hands off the network interface to the FOS engine.

                                    its a cisco so its port fast, i’ll check right now,

                                    1 Reply Last reply Reply Quote 0
                                    • G
                                      george1421 Moderator
                                      last edited by george1421 Sep 16, 2016, 3:33 PM Sep 16, 2016, 9:33 PM

                                      Also pondering this a bit more since your first (usable) interface is eth5 I can see another issue.

                                      @Developers Does the FOS engine stop enumerating the network adapter at eth1 or will it keep going until it finds a network adapter with a link up state to use? OR Is there a kernel parameter we can pass that says to use ethX as the FOS network interface?

                                      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 Sep 16, 2016, 9:33 PM Reply Quote 0
                                      • T
                                        Tom Elliott @george1421
                                        last edited by Sep 16, 2016, 9:33 PM

                                        @george1421 It tries everything until it finds a link up I believe.

                                        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

                                        G 1 Reply Last reply Sep 16, 2016, 9:35 PM Reply Quote 0
                                        • G
                                          george1421 Moderator @Tom Elliott
                                          last edited by Sep 16, 2016, 9:35 PM

                                          @Tom-Elliott said in bnx2x fails to load firmware on Dell R430:

                                          @george1421 It tries everything until it finds a link up I believe.

                                          Great, I have never tried. But I just thought I can test this by creating a vm with 6 network adapters with eth5 being the only one connected. But I’m not sure if I can have it defined but not having the link up. I may have to play in my test lab later tonight.

                                          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 Sep 16, 2016, 9:36 PM Reply Quote 0
                                          • 1
                                          • 2
                                          • 3
                                          • 2 / 3
                                          2 / 3
                                          • First post
                                            35/54
                                            Last post

                                          116

                                          Online

                                          12.2k

                                          Users

                                          17.4k

                                          Topics

                                          155.5k

                                          Posts
                                          Copyright © 2012-2024 FOG Project