Intel i340-t4 nic not recognised - help?
-
Hi all,
First post (go easy). Currently putting together a simple pfsense router for home use. Build is based around an ASUS N3150I-C mobo, with an intel i340-T4 NIC as I read that these were well supported in pfsense.
I just installed pfsense (2.4.5 downloaded today from negate) to a usb stick, booted into pfsense for the first time and the nic card isn't being recognised, I had the card installed on a riser cable, so I took that out of the equation and no change.
Any ideas? I was under the impression these intel cards were supported 'out of the box' in pfsense, maybe it's something to do with 2.4.5 as I understand this is pretty new?
Thanks.
-
Hi @thepeginator -
I've got one of these cards running in a 2.4.5 based pfSense box with no issues. Should be using the igb driver. A couple questions for you:
Has the card been tested in another system already (i.e. is known to be in working)?
If you run pciconf -lv from the command prompt, do you see the card listed in the output?https://www.freebsd.org/doc/handbook/kernelconfig-devices.html
Hope this helps.
-
upgrade the bios of your motherboard to the latest, i had a similar problem with another asus motherboard
-
So I bought the card as working, in terms of testing, I don't own another mobo/machine I can test it in. When I plug an ethernet cable in, both orange and green LEDs light up solidly, so the card is obviously getting juice and doing something, just not being recognised by pfsense.
When you say "run pciconf -lv from the command prompt" - is this within the pfsense web config? I haven't been able to boot into it yet as without a usable network adapter it won't boot. I'd have to re-enable the onboard NIC and assign that to be able to boot, is that worth doing?
In terms of BIOS, it's up to date. At least the version matches the latest version I can find from ASUS, so I assume it's up to date.
-
Managed to get into pfsense using a usb nic I had and run pciconf, got the following;
Guessing these are the nics on the i340?
"none2@pci0:1:0:0: class=0x020000 card=0x00008086 chip=0x15098086 rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
class = network
subclass = ethernet
none3@pci0:1:0:1: class=0x020000 card=0x00008086 chip=0x15098086 rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
class = network
subclass = ethernet
none4@pci0:1:0:2: class=0x020000 card=0x00008086 chip=0x15098086 rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
class = network
subclass = ethernet
none5@pci0:1:0:3: class=0x020000 card=0x00008086 chip=0x15098086 rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
class = network
subclass = ethernet
re0@pci0:2:0:0: class=0x020000 card=0x86771043 chip=0x816810ec rev=0x15 hdr=0x00
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
class = network
subclass = ethernet" -
@thepeginator Pretty sure that "none" should be "igb". But I think someone who actually has this card installed could help you better. I use it, but in a Hyper-V host so it doesn't show the actual card in pfSense, just the virtual NIC. The re0 is the NIC on your MB.
-
@thepeginator said in Intel i340-t4 nic not recognised - help?:
card=0x00008086 chip=0x15098086
it should be ...
but now that i think about it, i had a i350-t4 not a i340-t4 nevertheless it should be supported
I doubt they forgot to build the kernel with the igb drivers
8086 is intel , 1509 First International Computer. taiwan manufacturer
any output fromdmesg | grep igb -C3?
-
@kiokoman No output from that command.
I did run dmesg and got a whole load of stuff including the following:
"pcib1: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pci1: <network, ethernet> at device 0.0 (no driver attached)
pci1: <network, ethernet> at device 0.1 (no driver attached)
pci1: <network, ethernet> at device 0.2 (no driver attached)
pci1: <network, ethernet> at device 0.3 (no driver attached)" -
which basiccaly says :
"I polled the PCI slots and didn't find that card".
Or
"Did find PCI cards but do not have a driver that could talk to it".I'll be betting on "NIC dead" (or the way to it = PCI related?)
-
uhm no, the network card is there, freebsd is just telling him that it know no driver for that card
maybe he need to upgrade the firmware of that network card or build the intel igb module -
@kiokoman said in Intel i340-t4 nic not recognised - help?:
uhm no, the network card is there, freebsd is just telling him that it know no driver for that card
maybe he need to upgrade the firmware of that network card or build the intel igb moduleIs there a way to install the driver for the card in pfsense? Intel do have a driver listed for freebsd. No idea how you go about installing it in pfsense though.
-
I remembered I had an old pro/1000 card knocking about, pulled the i340 out, stuck the pro/1000 in, instantly recognised by Pfsense.
So as already mentioned, either the cards defective, or the driver for the i340 in pfsense is defective/missing/incorrect etc.
-
you can try to build the igb driver, or i can build it for you but first i want to know if @stephenw10 have something to add ?
in the meantime.. i have compiled it but the problem is that igb is already loaded inside the kernel
[2.4.5-RELEASE][root@pfSense.trmultiservice.lab]/boot/kernel: kldload if_igb.ko kldload: can't load if_igb.ko: module already loaded or in kernel -
@thepeginator maybe you can boot a live linux from usb to check if the network card work?
-
@kiokoman appreciate your help, beings that the pro/1000 card is working, I'm going to run with that for the time being. I haven't really the time, nor the inclination, nor the skill set to start properly troubleshooting this myself or building drivers etc.
I mainly asked on here incase this was some kind of known issue or there was something relatively obvious I've overlooked, seems like it's just not compatible out of the box as I had read that it should be.
-
That card should be recognised out of the box. You should check the boot log for the exact errors where the driver fails to attach.
http://pci-ids.ucw.cz/read/PC/8086/1509
Edit: Actually it is not listed. You seem to have found an Intel card that is not supported:
https://github.com/pfsense/FreeBSD-src/blob/RELENG_2_4_5/sys/dev/e1000/e1000_hw.h#L44 -
@stephenw10 said in Intel i340-t4 nic not recognised - help?:
That card should be recognised out of the box. You should check the boot log for the exact errors where the driver fails to attach.
http://pci-ids.ucw.cz/read/PC/8086/1509
Edit: Actually it is not listed. You seem to have found an Intel card that is not supported:
https://github.com/pfsense/FreeBSD-src/blob/RELENG_2_4_5/sys/dev/e1000/e1000_hw.h#L44Are you are about that? The card is based on the 82580 controller chip which is supported by the igb driver:
https://ark.intel.com/content/www/us/en/ark/products/49186/intel-ethernet-server-adapter-i340-t4.html
https://www.freebsd.org/cgi/man.cgi?query=igb&apropos=0&sektion=4&manpath=FreeBSD+11.3-stable&arch=default&format=html
Is it not supported because the 0x1509 ID from the OP's card is not listed in the header file you linked to? Maybe I should check the ID on my card to see what it reports back. I have been running a quad port i340 based NIC with pfSense since early last year with no issues, so this is surprising.
-
@tman222 said in Intel i340-t4 nic not recognised - help?:
Maybe I should check the ID on my card to see what it reports back.
As said above : check this card in another device first. If it works, ask him for full ID ^^
-
Yup exactly, the chip device ID is not in the driver so it doesn't attach.
-
I thought so too when i saw "1509 First International Computer. taiwan manufacturer", but I didn't remember where to find that list
tnx for the clarification
