Intel i350-T2 nor recognized by FreeNAS/ Sytem

[Crona]

I recently purchased an Intel i350-T2 NIC, as the built in ethernet on the motherboard was giving me issues when there was high network traffic, and the system/ FreeNAS doesn't recognize it at all. It isn't a fake card as far as I can tell, it has the proper stickers/ worked on another device. When I try ifconfig in shell it doesn't appear, I only see the re0 from the motherbaord's built in adapter. I've been searching all morning for a fix/ information and nothing has helped. Losing my mind here, help you be greatly appreciated

MB: Asrock B450 Pro4
CPU: AMD Ryzen 7 2700X
RAM: 32GB @ 3200

 

[Tigersharke]

I have not attempted to use a fiberoptic network device so I cannot speak to all of the details. However, it does appear that Freebsd does support the i350-T2 NIC card. What I believe is likely, is that this specific type of network device is not configured or setup for use by FreeNAS. As with any network card, you will need to load the driver and use ifconfig to initialize it. From the manpage above,

The igb driver supports Gigabit Ethernet adapters based on the Intel
82575 and 82576 controller chips:

+o Intel Gigabit ET Dual Port Server Adapter (82576)
+o Intel Gigabit VT Quad Port Server Adapter (82575)
+o Intel Single, Dual and Quad Gigabit Ethernet Controller (82580)
+o Intel i210 and i211 Gigabit Ethernet Controller
+o Intel i350 and i354 Gigabit Ethernet Controller

--snip--

place the
following line in loader.conf(5):

if_igb_load="YES"

There are other tunables and I cannot say how any of this would be done via FreeNAS but the above is how it is described for FreeBSD. There is also a manpage for ifconfig(8) that might be good to read.

I wish you success in your attempts to get networking instead of notworking.

 

[Samuel Tai]

See https://www.intel.com/content/www/u...007074/network-and-i-o/ethernet-products.html on how to validate YottaMark and BradyID stickers on the NIC. Your NIC could be fake.

Also this card should use the ixgbe driver.

 

[Crona]

See https://www.intel.com/content/www/u...007074/network-and-i-o/ethernet-products.html on how to validate YottaMark and BradyID stickers on the NIC. Your NIC could be fake.

Also this card should use the ixgbe driver.

All signs point to no, the card isn't fake

I have not attempted to use a fiberoptic network device so I cannot speak to all of the details. However, it does appear that freebsd does support the i350-T2 NIC card. What I believe is likely, is that this specific type of network device is not configured or setup for use by FreeNAS. As with any network card, you will need to load the driver and use ifconfig to initialize it. From the manpage above,

--snip--


There are other tunables and I cannot say how any of this would be done via FreeNAS but the above is how it is described for FreeBSD. There is also a manpage for ifconfig(8) that might be good to read.

I wish you success in your attempts to get networking instead of notworking.

I'm working on adding the tunable now, thank a ton! Will get back if it indeed works!

 

[Crona]

Adding a tunable to load the driver did not work and an ifconfig still doesn't show anything but re0.

 

[Tigersharke]

Adding a tunable to load the driver did not work and an ifconfig still doesn't show anything but re0.

Ok. So in FreeNAS there is some section where custom tunables can be added? I know nothing of this but even that *should* work. Have you tried locating the /boot/loader.conf file to add that line? Also, either way, you might need to reboot to be certain the driver is loaded, but if you can get to a shell prompt and type kldload if_igb it should either say it was already loaded or actually load the driver.

 

[Crona]

After running that command it said "kldload: can't load if_igb: No such file or directory"
I'm sorry I'm not sure how to locate the loader.conf file, when I enter "mount -rw /vi /boot/loader.conf " (what I found trying to figure it out before deciding to do a tunable) it just says no such file or directory.
I've rebooted a few times hoping that it loads and it doesn't. Do you think I need to add the drivers somehow?

 

[Elliot Dierksen]

I am pretty sure that the "igb" driver is complied into the FreeNAS kernel. I have i350 ports on the motherboard of my system that work just fine. kldstat reports that if_igb isn't loaded, so it must be compiled in.

Code:

root@freenas2:/ # kldstat
Id Refs Address            Size     Name
 1   75 0xffffffff80200000 2566f28  kernel
 2    1 0xffffffff82768000 100ee8   ispfw.ko
 3    1 0xffffffff82869000 fa60     ipmi.ko
 4    2 0xffffffff82879000 2d70     smbus.ko
 5    1 0xffffffff8287c000 32cc8    if_bnxt.ko
 6    1 0xffffffff828af000 2243e8   if_qlxgbe.ko
 7    1 0xffffffff82ad4000 f1440    ocs_fc.ko
 8    1 0xffffffff82bc6000 22150    smartpqi.ko
 9    1 0xffffffff82be9000 8a40     freenas_sysctl.ko
10    1 0xffffffff82e19000 330048   vmm.ko
11    1 0xffffffff8314a000 a84      nmdm.ko
12    1 0xffffffff8314b000 2ec      dtraceall.ko
13    9 0xffffffff8314c000 39a78    dtrace.ko
14    1 0xffffffff83186000 5c0      dtmalloc.ko
15    1 0xffffffff83187000 1898     dtnfscl.ko
16    1 0xffffffff83189000 1d61     fbt.ko
17    1 0xffffffff8318b000 53240    fasttrap.ko
18    1 0xffffffff831df000 bcc      sdt.ko
19    1 0xffffffff831e0000 6af0     systrace.ko
20    1 0xffffffff831e7000 6ac8     systrace_freebsd32.ko
21    1 0xffffffff831ee000 f9c      profile.ko
22    1 0xffffffff831ef000 39f4     geom_multipath.ko
23    1 0xffffffff831f3000 14320    hwpmc.ko
24    1 0xffffffff83208000 7140     t3_tom.ko
25    2 0xffffffff83210000 aa8      toecore.ko
26    1 0xffffffff83211000 f8d0     t4_tom.ko
root@freenas2:/ # ifconfig -a | grep igb
igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

 

[Tigersharke]

After running that command it said "kldload: can't load if_igb: No such file or directory"
I'm sorry I'm not sure how to locate the loader.conf file, when I enter "mount -rw /vi /boot/loader.conf " (what I found trying to figure it out before deciding to do a tunable) it just says no such file or directory.
I've rebooted a few times hoping that it loads and it doesn't. Do you think I need to add the drivers somehow?

Okay good. I think right now we need someone who truly knows FreeNAS to add their expertise because it sounds like the directory structure, layout, may be different than standard FreeBSD (to some degreee at least) and I really do not know how additional drivers would be added. What I described is how it would work for FreeBSD. I believe that the driver would be installed with base on FreeBSD, it may be default for the generic config of FreeBSD but I am not sure, many people do not use fiber networking. If it does not exist as part of a FreeNAS install then I am uncertain how it would be added because building or re-building parts of world (the software bundled as a set with the kernel but separate from it) would require the standard FreeBSD /usr/src to be included/added first/too.

Calling FreeNAS experts..

PS. It seems that the long time I took to be complete and correct various typos (always struggle to effectively press the shift key) meant that my answer above appears after another which offers contrary facts to a few of my suppositions.

 

[Tigersharke]

Ok, so we know the software driver should be present and we know the hardware is authentic. For the moment this leaves issues with hardware install or other hardware issues, and whether any other software needs to be set (does fiber work ootb for FreeNAS or not). I do not know if BIOS (or whatever they call it, I stick with BIOS because it makes sense as a name) has any settings that need to be adjusted. also, be sure the slot is proper for your use and clean and contacts of slot and card are clean, and obviously that the card is properly and completely seated.

Beyond that, it is still one for the more expert with fiber and FreeNAS.

 

[Samuel Tai]

According to https://www.freebsd.org/cgi/man.cgi?query=em&sektion=4, this NIC should use the em driver. What's the output of dmesg? Is the kernel detecting em, igb, or ixgbe drivers?

 

[Crona]

According to https://www.freebsd.org/cgi/man.cgi?query=em&sektion=4, this NIC should use the em driver. What's the output of dmesg? Is the kernel detecting em, igb, or ixgbe drivers?

Pretty sure it's just detecting re0 from the on board device

 

[Tigersharke]

I have never had a situation where the ethernet cable needed to be attached so that FreeBSD would detect the card, so I highly doubt that is the issue. If FreeBSD (or FreeNAS) doesn't detect the card for whatever reason, then it will not show up in dmesg at all, even with inaccurate details. If from the shell you can do dmesg | grep net you should get a result similar to below, which you can post:

root@ichigo:~ # dmesg | grep net
000.000023 [4336] netmap_init netmap: loaded module
em0: Ethernet address: 00:15:17:48:55:9a
em0: netmap queues/slots: TX 1/1024, RX 1/1024
em1: Ethernet address: 00:15:17:48:55:9b
em1: netmap queues/slots: TX 1/1024, RX 1/1024
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0x9000-0x90ff mem 0xd0304000-0xd0304fff,0xd0300000-0xd0303fff irq 21 at device 0.0 on pci10
re0: Ethernet address: e0:3f:49:6e:ca:6d
re0: netmap queues/slots: TX 1/256, RX 1/256

This will verify if there are any network devices in your system whether cards or on the motherboard. If you get only the realtek nic (re0) then we're back to needing to verify that the intel card is interfacing with your motherboard properly, getting power as well as relaying signals. You may need to try a different slot, or clean the contacts, or both.

 

[Crona]

Code:

root@Server[~]# dmesg | grep net
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
mlx5en: Mellanox Ethernet driver 3.5.1 (April 2019)
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0xd000-0xd0ff mem 0xf7504000-0xf7504fff,0xf7500000-0xf7503fff irq 35 at device 0.0 on pci9
re0: Ethernet address: a8:a1:59:15:2a:29
freenas_sysctl: adding network.
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
mlx5en: Mellanox Ethernet driver 3.5.1 (April 2019)
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0xd000-0xd0ff mem 0xf7504000-0xf7504fff,0xf7500000-0xf7503fff irq 35 at device 0.0 on pci9
re0: Ethernet address: a8:a1:59:15:2a:29
freenas_sysctl: adding network.
bridge0: Ethernet address: 02:bd:c4:dc:bc:00
epair0a: Ethernet address: 02:83:d0:00:04:0a
epair0b: Ethernet address: 02:dc:2e:00:05:0b
epair0a: changing name to 'vnet0.1'
vnet0.1: promiscuous mode enabled
vnet0.1: link state changed to DOWN
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
mlx5en: Mellanox Ethernet driver 3.5.1 (April 2019)
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0xd000-0xd0ff mem 0xf7504000-0xf7504fff,0xf7500000-0xf7503fff irq 35 at device 0.0 on pci9
re0: Ethernet address: a8:a1:59:15:2a:29
freenas_sysctl: adding network.
bridge0: Ethernet address: 02:bd:c4:dc:bc:00
epair0a: Ethernet address: 02:83:d0:00:04:0a
epair0b: Ethernet address: 02:dc:2e:00:05:0b
epair0a: changing name to 'vnet0.1'
vnet0.1: promiscuous mode enabled
vnet0.1: link state changed to DOWN
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
mlx5en: Mellanox Ethernet driver 3.5.1 (April 2019)
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0xd000-0xd0ff mem 0xf7504000-0xf7504fff,0xf7500000-0xf7503fff irq 35 at device 0.0 on pci9
re0: Ethernet address: a8:a1:59:15:2a:29
freenas_sysctl: adding network.
bridge0: Ethernet address: 02:bd:c4:dc:bc:00
epair0a: Ethernet address: 02:4e:d0:00:04:0a
epair0b: Ethernet address: 02:a4:e5:00:05:0b
epair0a: changing name to 'vnet0.1'
vnet0.1: promiscuous mode enabled
tap0: Ethernet address: 00:bd:a6:c5:14:00
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
mlx5en: Mellanox Ethernet driver 3.5.1 (April 2019)
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0xd000-0xd0ff mem 0xf7504000-0xf7504fff,0xf7500000-0xf7503fff irq 35 at device 0.0 on pci9
re0: Ethernet address: a8:a1:59:15:2a:29
freenas_sysctl: adding network.
bridge0: Ethernet address: 02:bd:c4:dc:bc:00
epair0a: Ethernet

Yeah I already knew that it was supposed to show up as em0, and wasn't being recognized by the system at all, as I said in the first post.

 

[Crona]

I swapped the GPU and the intel NIC and noe the NIC is working but the GPU isnt, which isnt a problem. Everything is working now (except the unneeded GPU) thanks everyone!

 

[Samuel Tai]

Looking at your motherboard, your Ryzen CPU may be grabbing PCI-E lanes from one of the x16 slots. Your GPU/NIC swap pretty much confirms this.

 

[Tigersharke]

Looking at your motherboard, your Ryzen CPU may be grabbing PCI-E lanes from one of the x16 slots. Your GPU/NIC swap pretty much confirms this.

So as I mentioned above a few posts previous, it might be good to try another slot.