Need sys.device.mlx4_core0.mlx4 in sysctl. Why?

amilis

amilis

I come a cross a “ting” today with a Mellanox ConnectX 40gbps card.

I had to put:
Code: 
 sys.device.mlx4_core0.mlx4_port1=eth
 sys.device.mlx4_core0.mlx4_port2=eth
in /etc/sysctl.conf on a little older server today, a Dell R430 so the network card booted up.

Without above I only got this:
# dmesg | grep mlx
mlx4_core0: <mlx4_core> mem 0x92400000-0x924fffff,0x91000000-0x917fffff irq 40 at device 0.0 numa-domain 0 on pci4
mlx4_core: Mellanox ConnectX core driver v3.7.1 (November 2021)
mlx4_core: Initializing 0000:05:00.0
mlx4_core0: Unable to determine PCI device chain minimum BW
I didn’t see the card, couldn’t use it etc.

I have
Code: 
mlx4en_load="YES"
in /boot/loader.conf.


I have a lot of this cards in newer Dell servers without this “fix?”. Also in some old HPE G9.
Why did I need this in this R430? This is the first time ever.
Can’t see any strange things in Bios and all firmware is up-to-date on the server (not on the Mellanox, but I have same FW on many cards).
OS: 14.2.
 
Yeaa.. the FW on the card is old, I know. It’s boring to update it. ;)
Naaa.. I haven't had this "problem" before, so didn’t do it. I have this FW on other cards that’s is running in 14.2, but in newer servers.

I don’t care If I need the rows in sysctl, just wonder.
 
You must log in or register to reply here.
Back
Top