Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Unable to use BCM57810 properly, need new drivers

    Scheduled Pinned Locked Moved Hardware
    4 Posts 2 Posters 159 Views
    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
      Gradius
      last edited by Gradius

      I'm trying to using my BCM57810 (2x SFP+ ports) and pfSense with FTTH again.

      It was working perfectly fine on older version, Proxmox v8.0.4, then around 6 months ago, I lost all data (bad HDD), and I didn't care as I wasn't using it at that time (totally busy with work).

      Now, it refuses to work installing everything from scratch (and up-to-date). I even tried to compile the driver, so far no luck:
      https://github.com/JAMESMTL/snippets/tree/master/bnx2x/proxmox

      Yes, the one there for v8.0.4 will NOT load/works.

      Under proxmox it "seems" fine, but when I try to use on pfSense v2.8, I got a lot of errors:

      [2.8.0-RELEASE][admin@pfSense.home.arpa]/: dmesg | grep -i bxe
bxe0: <QLogic NetXtreme II BCM57810 10GbE (B0) BXE v:1.78.91> mem 0xfa000000-0xfa7fffff,0xfa800000-0xfaffffff,0xfc000000-0xfc00ffff irq 16 at device 0.0 on pci1
bxe0: PCI BAR0 [10] memory allocated: 0xfa000000-0xfa7fffff (8388608) -> 0xfffff800fa000000
bxe0: PCI BAR2 [18] memory allocated: 0xfa800000-0xfaffffff (8388608) -> 0xfffff800fa800000
bxe0: PCI BAR4 [20] memory allocated: 0xfc000000-0xfc00ffff (65536) -> 0xfffff800fc000000
bxe0: ERROR: Invalid SHMEM validity signature: 0x00000008
bxe0: ERROR: Invalid phy config in NVRAM (PHY1=0x00000008 PHY2=0x00000008)
bxe0: Unknown media!
bxe0: IFMEDIA flags : 20
bxe0: Using defaults for TSO: 65518/35/2048
bxe0: ERROR: FW failed to respond!
bxe0: ERROR: MCP response failure, aborting
bxe0: ERROR: Failed to unload previous driver! time_counter 10 rc -1
bxe1: <QLogic NetXtreme II BCM57810 10GbE (B0) BXE v:1.78.91> mem 0xfb000000-0xfb7fffff,0xfb800000-0xfbffffff,0xfc010000-0xfc01ffff irq 17 at device 0.1 on pci1
bxe1: PCI BAR0 [10] memory allocated: 0xfb000000-0xfb7fffff (8388608) -> 0xfffff800fb000000
bxe1: PCI BAR2 [18] memory allocated: 0xfb800000-0xfbffffff (8388608) -> 0xfffff800fb800000
bxe1: PCI BAR4 [20] memory allocated: 0xfc010000-0xfc01ffff (65536) -> 0xfffff800fc010000
bxe1: ERROR: Invalid SHMEM validity signature: 0x00010008
bxe1: ERROR: Invalid phy config in NVRAM (PHY1=0x00010008 PHY2=0x00010008)
bxe1: Unknown media!
bxe1: IFMEDIA flags : 20
bxe1: Using defaults for TSO: 65518/35/2048
bxe1: ERROR: FW failed to respond!
bxe1: ERROR: MCP response failure, aborting
bxe1: ERROR: Failed to unload previous driver! time_counter 10 rc -1
bxe0: WARNING: No power capability
bxe0: ERROR: Failed to create dma tag for 'ECORE_ILT' (22)
bxe0: ERROR: ecore_ilt_mem_op ILT_MEMOP_ALLOC failed
bxe0: ERROR: Initialization failed, stack notified driver is NOT running!
bxe0: WARNING: No power capability
bxe0: ERROR: Failed to create dma tag for 'ECORE_ILT' (22)
bxe0: ERROR: ecore_ilt_mem_op ILT_MEMOP_ALLOC failed
bxe0: ERROR: Initialization failed, stack notified driver is NOT running!
bxe0: WARNING: No power capability
bxe0: ERROR: Failed to create dma tag for 'ECORE_ILT' (22)
bxe0: ERROR: ecore_ilt_mem_op ILT_MEMOP_ALLOC failed
bxe0: ERROR: Initialization failed, stack notified driver is NOT running!
bxe0: WARNING: No power capability
bxe0: ERROR: Failed to create dma tag for 'ECORE_ILT' (22)
bxe0: ERROR: ecore_ilt_mem_op ILT_MEMOP_ALLOC failed
bxe0: ERROR: Initialization failed, stack notified driver is NOT running!
bxe0: WARNING: No power capability
bxe0: ERROR: Failed to create dma tag for 'ECORE_ILT' (22)
bxe0: ERROR: ecore_ilt_mem_op ILT_MEMOP_ALLOC failed
bxe0: ERROR: Initialization failed, stack notified driver is NOT running!
vlan0: changing name to 'bxe0.20'
bxe0: WARNING: No power capability
bxe0: ERROR: Failed to create dma tag for 'ECORE_ILT' (22)
bxe0: ERROR: ecore_ilt_mem_op ILT_MEMOP_ALLOC failed
bxe0: ERROR: Initialization failed, stack notified driver is NOT running!
bxe0: promiscuous mode enabled
bxe0.20: promiscuous mode enabled
bxe0: WARNING: No power capability
bxe0: ERROR: Failed to create dma tag for 'ECORE_ILT' (22)
bxe0: ERROR: ecore_ilt_mem_op ILT_MEMOP_ALLOC failed
bxe0: ERROR: Initialization failed, stack notified driver is NOT running!
bxe0: WARNING: No power capability
bxe0: ERROR: Failed to create dma tag for 'ECORE_ILT' (22)
bxe0: ERROR: ecore_ilt_mem_op ILT_MEMOP_ALLOC failed
bxe0: ERROR: Initialization failed, stack notified driver is NOT running!
bxe0: promiscuous mode disabled
bxe0.20: promiscuous mode disabled
bxe0: WARNING: No power capability
bxe0: ERROR: Failed to create dma tag for 'ECORE_ILT' (22)
bxe0: ERROR: ecore_ilt_mem_op ILT_MEMOP_ALLOC failed
bxe0: ERROR: Initialization failed, stack notified driver is NOT running!
bxe0: WARNING: No power capability
bxe0: ERROR: Failed to create dma tag for 'ECORE_ILT' (22)
bxe0: ERROR: ecore_ilt_mem_op ILT_MEMOP_ALLOC failed
bxe0: ERROR: Initialization failed, stack notified driver is NOT running!
bxe0: promiscuous mode enabled
[2.8.0-RELEASE][admin@pfSense.home.arpa]/:

      ATM, I'm only using one port (first one) with an ODI DFP-34X-2C2, the other one is disconnected for now.

      Keep in mind, I had it working perfectly before data loss with older Proxmox version (v8.0.4), and older pfSense.

      Any help in this matter is greatly appreciated!

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        @Gradius said in Unable to use BCM57810 properly, need new drivers:

        https://github.com/JAMESMTL/snippets/tree/master/bnx2x/proxmox

        That driver appears to be for Proxmox directly but your pfSense log implies you're passing the NIC hardware through to pfSense so any Proxmox driver would not be used.
        Is that what you're doing?

        Can I assume what you're attempting to do here is use an incompatible GPON SFP module in the NIC? That seems to be a common use case there.

        If so that code was just added to the driver and will be in the next point release:
        https://github.com/pfsense/FreeBSD-src/commit/1222560f07264e3beda9bdd2f7116b6dc6f0d204

        G 1 Reply Last reply Reply Quote 0
        • G
          Gradius @stephenw10
          last edited by

          @stephenw10 said in Unable to use BCM57810 properly, need new drivers:

          @Gradius said in Unable to use BCM57810 properly, need new drivers:

          https://github.com/JAMESMTL/snippets/tree/master/bnx2x/proxmox

          That driver appears to be for Proxmox directly but your pfSense log implies you're passing the NIC hardware through to pfSense so any Proxmox driver would not be used.
          Is that what you're doing?

          Can I assume what you're attempting to do here is use an incompatible GPON SFP module in the NIC? That seems to be a common use case there.

          If so that code was just added to the driver and will be in the next point release:
          https://github.com/pfsense/FreeBSD-src/commit/1222560f07264e3beda9bdd2f7116b6dc6f0d204

          That's correct. I'm directly passing the card by "PCI device" from Proxmox to pfSense.

          It worked before (old version). Now it's really good news to see a new driver (patched) is planned!

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Hmm, interesting. Hard to see how that driver could ever have made in difference when passed through like that.

            If you don't pass it through you could use the modified driver in Proxmox and then present it to pfSense as a virtual NIC until we get the patched driver in pfSense. Except you're saying the modified driver no longer loads in Proxmox.... 🤔

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.