Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Intel i340-t4 nic not recognised - help?

    Scheduled Pinned Locked Moved Hardware
    22 Posts 6 Posters 3.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      thepeginator
      last edited by thepeginator

      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.

      1 Reply Last reply Reply Quote 0
      • T
        thepeginator
        last edited by

        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"

        provelsP 1 Reply Last reply Reply Quote 0
        • provelsP
          provels @thepeginator
          last edited by provels

          @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.

          Peder

          MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
          BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

          1 Reply Last reply Reply Quote 0
          • kiokomanK
            kiokoman LAYER 8
            last edited by kiokoman

            @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 from

            dmesg | grep igb -C3
            

            ?

            ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
            Please do not use chat/PM to ask for help
            we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
            Don't forget to Upvote with the 👍 button for any post you find to be helpful.

            T 1 Reply Last reply Reply Quote 0
            • T
              thepeginator @kiokoman
              last edited by

              @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)"

              1 Reply Last reply Reply Quote 0
              • GertjanG
                Gertjan
                last edited by

                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?)

                No "help me" PM's please. Use the forum, the community will thank you.
                Edit : and where are the logs ??

                1 Reply Last reply Reply Quote 0
                • kiokomanK
                  kiokoman LAYER 8
                  last edited by kiokoman

                  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

                  ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
                  Please do not use chat/PM to ask for help
                  we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
                  Don't forget to Upvote with the 👍 button for any post you find to be helpful.

                  T 1 Reply Last reply Reply Quote 0
                  • T
                    thepeginator @kiokoman
                    last edited by

                    @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 module

                    Is 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.

                    1 Reply Last reply Reply Quote 0
                    • T
                      thepeginator
                      last edited by

                      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.

                      1 Reply Last reply Reply Quote 0
                      • kiokomanK
                        kiokoman LAYER 8
                        last edited by kiokoman

                        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
                        

                        ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
                        Please do not use chat/PM to ask for help
                        we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
                        Don't forget to Upvote with the 👍 button for any post you find to be helpful.

                        1 Reply Last reply Reply Quote 0
                        • kiokomanK
                          kiokoman LAYER 8
                          last edited by

                          @thepeginator maybe you can boot a live linux from usb to check if the network card work?

                          ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
                          Please do not use chat/PM to ask for help
                          we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
                          Don't forget to Upvote with the 👍 button for any post you find to be helpful.

                          T 1 Reply Last reply Reply Quote 1
                          • T
                            thepeginator @kiokoman
                            last edited by

                            @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.

                            1 Reply Last reply Reply Quote 0
                            • stephenw10S
                              stephenw10 Netgate Administrator
                              last edited by

                              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

                              T 1 Reply Last reply Reply Quote 0
                              • T
                                tman222 @stephenw10
                                last edited by tman222

                                @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#L44

                                Are 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.

                                GertjanG 1 Reply Last reply Reply Quote 0
                                • GertjanG
                                  Gertjan @tman222
                                  last edited by

                                  @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 ^^

                                  No "help me" PM's please. Use the forum, the community will thank you.
                                  Edit : and where are the logs ??

                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    Yup exactly, the chip device ID is not in the driver so it doesn't attach.

                                    1 Reply Last reply Reply Quote 1
                                    • kiokomanK
                                      kiokoman LAYER 8
                                      last edited by kiokoman

                                      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

                                      ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
                                      Please do not use chat/PM to ask for help
                                      we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
                                      Don't forget to Upvote with the 👍 button for any post you find to be helpful.

                                      1 Reply Last reply Reply Quote 0
                                      • T
                                        tman222
                                        last edited by

                                        I just doublechecked the ID and my card is ID'd as 0x150E, which is supported. If I recall correctly, the quad i340 NIC I got was an Lenovo OEM.

                                        @thepeginator - where did you obtain your i340-T4 from?

                                        1 Reply Last reply Reply Quote 0
                                        • stephenw10S
                                          stephenw10 Netgate Administrator
                                          last edited by

                                          Yeah, interesting.

                                          0x1509 - Quad port EEPROM-less Device ID (Default) 1
                                          0x150E - Quad port 10/100/1000 Mb/s Ethernet controller, x4 PCIe,
                                          copper.
                                          

                                          So no EEPROM, or not readable, on the OPs card. Maybe it's damaged or missing. Or a jumper got moved etc.

                                          Steve

                                          1 Reply Last reply Reply Quote 0
                                          • First post
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.