I had a 13.0 system fully working. It has a Mellanox 10g ether card (ConnectX-3 I think) that worked without issue. I replaced the SSD and installed 13.1 and now the card doesn't work. It shows up in dmesg: mlx4_core0: mlx4_shutdown was called mlx4_core0: <mlx4_core> mem 0xfb700000-0xfb7fffff,0x7fff800000-0x7fffffffff irq 30 at device 0.0 on pci4 mlx4_core: Mellanox ConnectX core driver v3.7.1 (November 2021) mlx4_core: Initializing mlx4_core mlx4_core0: Unable to determine PCI device chain minimum BW mlx4_core0: mlx4_shutdown was called mlx4_core0: <mlx4_core> mem 0xfb700000-0xfb7fffff,0x7fff800000-0x7fffffffff irq 30 at device 0.0 on pci4 mlx4_core: Mellanox ConnectX core driver v3.7.1 (November 2021) mlx4_core: Initializing mlx4_core mlx4_core0: Unable to determine PCI device chain minimum BW mlx4_core0: mlx4_shutdown was called mlx4_core0: <mlx4_core> mem 0xfb700000-0xfb7fffff,0x7fff800000-0x7fffffffff irq 30 at device 0.0 on pci4 mlx4_core: Mellanox ConnectX core driver v3.7.1 (November 2021) mlx4_core: Initializing mlx4_core mlx4_core0: Unable to determine PCI device chain minimum BW But doesn't show up in ifconfig: crb@eclipse:294> ifconfig -a em0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=481049b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LRO,VLAN_HWFILTER,NOMAP> ether 00:1b:21:1d:12:ad inet6 fe80::21b:21ff:fe1d:12ad%em0 prefixlen 64 scopeid 0x1 inet6 2600:1700:5430:10b1:21b:21ff:fe1d:12ad prefixlen 64 autoconf inet 192.168.1.190 netmask 0xffffff00 broadcast 192.168.1.255 media: Ethernet autoselect (100baseTX <full-duplex>) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> igc0: flags=8822<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=4e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,NOMAP> ether 3c:7c:3f:4e:0b:c6 media: Ethernet autoselect status: no carrier nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff000000 groups: lo nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> I'm happy to build kernels, debug what ever is necessary to help fix the problem.
ASUS TUF GAMING X570-PRO motherboard AMD 5950 processor
*** Bug 264058 has been marked as a duplicate of this bug. ***
Hi, Did you try to set the port-type to ethernet, "eth" ? There is a SYSCTL somewhere, try to grep for it: sysctl -a | grep mlx4_port --HPS
seems to be already set: crb@eclipse:88> sysctl -a | grep mlx4_port sys.device.mlx4_core0.mlx4_port1_mtu: 4096 sys.device.mlx4_core0.mlx4_port1: eth
Is mlx4en loaded? --HPS
trimed: crb@eclipse:89> kldstat Id Refs Address Size Name 1 92 0xffffffff80200000 1f30590 kernel 14 1 0xffffffff82bbe000 3ef50 mlx4.ko
I think you need to load mlx4en aswell, try: kldload mlx4en --HPS
This error message is expected and not harmful. mlx4_core0: Unable to determine PCI device chain minimum BW --HPS
Ping --HPS
Sorry, I thought I left a message and closed this. I was, indeed, missing the module you suggested. When I loaded that the machine started working. Thank you!
Thank you! Then I'll close this issue. --HPS
^Triage: Assign to committer that resolved and correct resolution
I would not say this issue is "fixed and closed". Today I installed a new fbsd box with a 13.1 memstick, installation was not able to configure and use the network, because the mellanox module was missing. it does not make sense to build in a kernel driver that can detect the card, but to forget to load the dependency module too. So I would like to reopen this bug report and have somebody really think about how to prevent it in the future.
Maybe something can be done by devd and the device driver loading framework. Currently the mlx4en driver is old and not actively maintained.
(In reply to Hans Petter Selasky from comment #14) if old and not maintained does not really matter as long as it works. I doubt it would do any harm to be automatically be included as the main mlx4 driver is now. (I dont know why they are split) The cards are good and can be bought cheap as used ones. This allows low budget entries into the 10Gbe area, so I bet, they will stay on for another 10yrs or so.