Upgrade 26.1 to 26.7 - bnxt Driver fails

Started by RamShadow, September 04, 2026, 03:48:10 PM

Previous topic - Next topic
Hey,
we have a Dell PowerEdge R6625
with 540-BCRX : Broadcom 57504 10/25 GbE QuadPort Network Adapter Fw 38.11.38.06 and
Driver version 230.0.133.0 in OPNSense

After the update to 26.7 we see that the configuration could not be loaded:
bnxt0: <Broadcom BCM57504 NetXtreme-E 10Gb/25Gb/50Gb/100Gb/200Gb Ethernet> mem 0xef000000-0xef00ffff,0xeb000000-0xebffffff,0xef040000-0xef047fff at device 0.3 numa-domain 0 on pci1
[1] bnxt0: HWRM_FUNC_BACKING_STORE_CFG command returned INVALID_PARAMS error.
[1] bnxt0: Failed configuring context mem, rc = 22.
[1] bnxt0: attach: alloc_ctx_mem failed
[1] bnxt0: IFDI_ATTACH_PRE failed 22
[1] device_attach: bnxt0 attach returned 22

The gigabit adapters are working fine with the driver.

We had the Tunable if_bnxt_load = YES setted in the past.

After compiling and loading the Broadcom driver package with the version 238.1.136.0
we can see that the card is working after reboot.

Had anyone the same problem?

Is there an option to get the driver updated in OPNSense / FreeBSD?

Cheers & Thanks
Lex

Open a GitHub issue in OPNsense/src and mention this thread.

Apparently OPNsense uses the driver from bsd.

I see this driver you mentioned exists but I'm unclear what you had to do to get it...

https://docs.broadcom.com/doc/Release_Notes-238.1.138.6

September 05, 2026, 03:16:45 PM #3 Last Edit: September 05, 2026, 04:39:26 PM by pfry Reason: Yak!
Support Documents and Downloads

Edit: Verifying... Sheesh, the lousy search, "download agreement" and file format (tgz inside zip)... painful.

Ok but that means the bnxt driver on 15.1 is broken for the Broadcom 57504 chipset and a ticket needs to be opened upstream.


While using the driver provided by the manufacturer clearly works it clearly has issues - nontechnical - that prevent its redistribution both in FreeBSD and OPNsense.

The best path forward here is to have the driver maintainers look into this issue by opening a FreeBSD ticket.


As soon as this issue is addressed upstream you can be sure the next OPNsense release will include the patch.