Mellanox ConnectX-3 VPI MCX354A-FCBT not showing up in interfaces

[Timonator]

Hi all,

I installed a Mellanox MCX354A-FCBT dual 40Gbit card in my super micro X9. But I am having troubles getting the interface to show up in OPNsense.

I followed:
https://www.routerperformance.net/opnsense/mellanox-connecx-management-in-opnsense/


I followed the instructions and edited /boot/loader.conf.local. After a reboot the card seems to be detected.

Code Select Expand

mlx4_core0: <mlx4_core> mem 0xdfa00000-0xdfafffff,0xde000000-0xde7fffff irq 17 at device 0.0 on pci2
mlx4_core: Mellanox ConnectX core driver v3.7.1 (November 2021)
mlx4_core: Initializing 0000:02:00.0

From the guide it says, you can already change interfaces, but nothing is detected yet. Therefore I wanted to check the firmware on the cards.
I downloaded the latest firmware tool version, which seems to be 4.29.0-131

I can install everything fine, but when I try to run the following command

Code Select Expand

~/mft-4.29.0-131 # /usr/bin/mst status

I get permission denied, I already tried CHMOD on files inside mft folder and mst, but keep getting permission denied.

If I just run:

Code Select Expand

mst status
I just get:

Code Select Expand

MST devices:
------------




Most recent related post I could find was:
https://forum.opnsense.org/index.php?topic=31218.0
This was running on 22.7, currently I am on 24.7.3
Did anything change in between versions?

Anyone, any idea why the command doesn't work anymore?

[cheerbeer]

I had the same issue, no idea why the mst commands are not working but there are some things you can check.

Perhaps try the package version of mstflint per here: https://adventurist.me/posts/00309

There is also a pciconf command that should work for getting the pcie ids versus the mst command.

The tunable in loader.conf is no longer necessary, as opnsense loads the driver by default.

Things to check to get the interfaces to load:

1.  Make sure the card is in ethernet mode, as opnsense does not support IB driver.  I did this in windows.
2.  Make sure there is a link or at a minimum an ethernet transceiver in the QSFP port.  The interface will not show up until there is an actual ethernet interface to load.