Is the Broadcom BCM957414A4142CC (BCM57414) 25G NIC supported?

stephenw10

Ah, yes, like that!

Mmm, definitely not a 32bit module?

Yves_

@stephenw10 well I used FreeBSD 12.3 Stable amd64 should I use FreeBSD 12.0 i386?

stephenw10

No, it should be 64bit but if you'd accidentally used 32bit it would have presented similarly to that.

Try building against 12.3-release instead, assuming you are running 2.6?

Or update to a 2.7 snapshot and try the 12-stable module there.

Steve

Yves_

@stephenw10 I made a little mistake I used 12.3-Release amd64... if I do it with that one. Which I did. Can it happen that I mistakely compiled it 32bit? is just ran "make kernel"

stephenw10

No it will have built a 64bit module.

Do you actually see an updated module though? The file dates from when you compiled it?
The default install will already have the old module?

I would just try whatever you can. It might be that driver requires an absolute specific kernel version in which case you're probably out of luck.

Steve

Yves_

@stephenw10 said in Is the Broadcom BCM957414A4142CC (BCM57414) 25G NIC supported?:

Do you actually see an updated module though? The file dates from when you compiled it?
The default install will already have the old module?

I would just try whatever you can. It might be that driver requires an absolute specific kernel version in which case you're probably out of luck.

Steve

I see the new date on the if_bnxt.ko so I guess this means it compiled the new module. But I did it on 12.3 Release now I downloaded 12.3 Stable and will do it again.

Yves_

@yves_ Soooo I recompiled the driver again. With 12.3-Stable AMD64, the version 12.0-Stable I could not find.

-r-xr-xr-x  1 root  wheel   225K Jul 27 18:33 if_bnxt.ko

Unfortunatly same result:

KLD if_bnxt.ko: depends on kernel - not available or version mismatch
linker_load_file: /boot/kernel/if_bnxt.ko - unsupported file type

stephenw10

Hmm, damn. Can you try loading any of those into a 2.7 snapshot?

Yves_

@stephenw10 This is from the system I used to compile the driver

root@freebsd-12-3-stable:~ # kldload /boot/kernel/if_bnxt.ko
root@freebsd-12-3-stable:~ # kldstat -v | grep if_bnxt
 5    1 0xffffffff82725000    162a0 if_bnxt.ko (/boot/kernel/if_bnxt.ko)
root@freebsd-12-3-stable:~ # ls -lh /boot/kernel/if_bn*
-r-xr-xr-x  1 root  wheel   225K Jul 27 18:33 /boot/kernel/if_bnxt.ko

As you can see it worked to load it on this system the drivers was compiled :-(

I will start a VM with 2.7 snapshot and try to load it into that one.

Yves_

@yves_ Or you can try the file yourself if_bnxt.ko

stephenw10

Shows as deleted. What was/is that compiled against?

Yves_

@stephenw10 sorry, stupid file provider :-) here you go: if_bnxt.zip its compiled against

FreeBSD freebsd-12-3-stable 12.3-STABLE FreeBSD 12.3-STABLE GENERIC  amd64

Yves_

@yves_ can I compile it on 2.6.0? some how? how do I get the source inside of the /usr/src folder? its currently empty

stephenw10

Mmm, still fails in 2.7.

Compiling pfSense is non-trivial. There are some guides about if you search but it's not something I can go into detail on here.

Steve

Yves_

@stephenw10 okay... not compiling pfsense... more compiling the driver ON pfsense. Like this is would be compiled against the FreeBSD from pfSense

What workaround do we have else? is there a possibility to always run a script as soon as pfsense is booted up which runs this command

ifconfig bnxt0 promisc

stephenw10

Yes, you can definitely do that:
https://docs.netgate.com/pfsense/en/latest/development/boot-commands.html#shellcmd-option

Steve

Yves_

@stephenw10 Okay, I did that. Worked out flawlessly. Now the Server also survives a reboot. But I still like to fix the driver somehow

The tutorial says "When doing this, install a version of FreeBSD that matches up with the version of pfSense software currently in use. A list can be found here: Versions of pfSense software and FreeBSD"

According to the data table is is: 12.3-STABLE@ef1e43df92c6 now the big question is where can I get excatly that version of 12.3-STABLE... or is it possible that it does not matter at all, since it is linked in the kernel module?

stephenw10

Yeah it seems that driver is linked to the kernel in a closer way than others.

When we move to a newer FreeBSD version you should get that patch anyway.

Steve