Navigation

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

    [SOLVED]: Intel i350-T4 can't be recognised

    Hardware
    6
    17
    9044
    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
      TokyoExpress last edited by

      Hi gurus,

      Finally my girlfriend allowed me to spend $300 on a network interface card at Christmas time ;) After digging the forum I decided to go for a Intel i350-T4. A local guy sold me one of this nic for only $220. However, my nightmare comes alive.

      I have a Supermicro X10SBA as a Christmas gift from my girlfriend. It works smooth with pfSense 2.1.5 AMD 64 version. After I adding the i350-TX in the system, pfSense showed "Fatal Trap 12" error. So I did the NIC buffer tuning as shows in this document https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards. Nothing changed at all. Then I tried the pfSense version 2.1.5 i386. i350-T4 still can't be recognised by pfSense. But the interesting thing was, the onboard NIC id changed from "igb0, igb1" to "igb4, igb5". Somehow "igb0" to "igb3" were occupied by the i350-T4?

      During the holiday, I tried pfSense version RC 2.2 AMD64, Release 2.1.3 AMD64/i386, and Release 2.1.5 AMD/i386 again and again. And used my desktop as second hardware platform. I got no lucky at all. All AMD64 versions shows "Fatal Trap 12" then freezes and i386 version shows no NIC.

      I can confirm that the i350-T4 NIC works fine. I tried it in both Windows 7 and Windows Server 2008 R2. It works properly.

      What should I do now? A lot of people use this NIC in the board but why can't I? What's the trick here?

      Thank you for your time.

      TokyoExpress

      ==================================================================

      UPDATE:

      THE PROBLEM IS SOLVED. I TRIED TO USE  Ethernet Flash Firmware Utility (BootUtil) TO UPDATE THE FIRMWARE OF THE I350-T4. FINALLY GET LUCKY. IT WORKS NOW!

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

        the board I have:

        http://www.supermicro.com/products/motherboard/celeron/x10/x10sba.cfm

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

          The nic I have.




          1 Reply Last reply Reply Quote 0
          • R
            rkelleyrtp last edited by

            Have you tried disabling the onboard NICs to see if that makes a difference?  According to the following URL, a guy had the same problem as you that was fixed by removing the NIC from the BIOS:

            https://forums.freebsd.org/threads/pfsense-hard-locks-panics-and-fatal-trap-12s-unless-apic-disabled-at-bootup.9798

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

              @rkelleyrtp:

              Have you tried disabling the onboard NICs to see if that makes a difference?  According to the following URL, a guy had the same problem as you that was fixed by removing the NIC from the BIOS:

              https://forums.freebsd.org/threads/pfsense-hard-locks-panics-and-fatal-trap-12s-unless-apic-disabled-at-bootup.9798

              Thank you so much for your reply.

              I've tried to disable the onboard NICs. Get no lucky  :(

              1 Reply Last reply Reply Quote 0
              • R
                rkelleyrtp last edited by

                No problem.

                If you google "FreeBSD Fatal Trap 12", you will see a bunch of hits.  I would follow those hits and see if you can pinpoint anything.  My gut feeling tells me this is a BIOS related issue…

                1 Reply Last reply Reply Quote 0
                • 0
                  0x10C last edited by

                  When you say you tried the card in Windows 7 and 2008 R2, is that with those operating systems on the Supermicro motherboard?

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

                    @0x10C:

                    When you say you tried the card in Windows 7 and 2008 R2, is that with those operating systems on the Supermicro motherboard?

                    Thank you for reply.

                    No. it isn't.  I tried on my desktop and a server at work.

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

                      screenshot of the error


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

                        Thanks for all the replies.

                        You guys are awesome! ;D

                        1 Reply Last reply Reply Quote 0
                        • Derelict
                          Derelict LAYER 8 Netgate last edited by

                          What was it?

                          Chattanooga, Tennessee, USA
                          The pfSense Book is free of charge!
                          DO NOT set a source port in a port forward or firewall rule unless you KNOW you need it!
                          Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

                            @Derelict:

                            What was it?

                            I've directly edited the first post for convenience.

                            THE PROBLEM IS SOLVED. I TRIED TO USE  Ethernet Flash Firmware Utility (BootUtil) TO UPDATE THE FIRMWARE OF THE I350-T4. FINALLY GET LUCKY. IT WORKS NOW!

                            1 Reply Last reply Reply Quote 0
                            • G
                              Gimli last edited by

                              Would you have a link to a page with more detailed instructions on what you did to solve your problem please? Just the name of the tool isn't very useful. What firmware did you load on your NIC?

                              1 Reply Last reply Reply Quote 0
                              • C
                                corvey last edited by

                                @Gimli:

                                Would you have a link to a page with more detailed instructions on what you did to solve your problem please? Just the name of the tool isn't very useful. What firmware did you load on your NIC?

                                That's funny, I'm at this point too.  I'm looking for a way to update the firmware on my i350-t4 so it will hopefully work with ESXI.  Right now it is hanging at"Setting up interfaces microcode." on the IGB drivers.

                                pfSensational™

                                1 Reply Last reply Reply Quote 0
                                • C
                                  corvey last edited by

                                  Apparently, it needs to be flashed in order for it to work and not hang! The NIC is flashed and PFSENSE booted in ESXI!  It's a miracle!  ;D

                                  Step 1.

                                  Download Preboot.exe and extract in a folder:

                                  https://downloadcenter.intel.com/download/19186

                                  Step 2.

                                  Open this file and you can see the commands to use, but I'm going to list exactly what you need to do:

                                  C:\Intel20.4.1\APPS\BootUtil\Docs\bootutils.txt

                                  Make sure all of your ports on the QUAD NIC are enabled in Windows. (I'm using Windows 7 64bit)

                                  Run command prompt as administrator and navigate to this path and run the file once to see what is going on:

                                  C:\Intel20.4.1\APPS\BootUtil\Winx64\BOOTUTILW64E.EXE

                                  Look for your NIC ports that you want to update and then, for example, run this command line:

                                  (LOCAL LAN WOULD BE PORT 1)

                                  BOOTUTILW64E.EXE -NIC2 -FLASHENABLE
                                  BOOTUTILW64E.EXE -NIC3 -FLASHENABLE
                                  BOOTUTILW64E.EXE -NIC4 -FLASHENABLE
                                  BOOTUTILW64E.EXE -NIC5 -FLASHENABLE

                                  (NOTE: I also copied BootIMG.FLB from C:\Intel20.4.1\APPS\BootUtil to C:\Intel20.4.1\APPS\BootUtil\Winx64.  Just did this for a quick shortcut to access it.  You may or may not need to do this, but the tidbit is there for you if you need to.)

                                  Now is the time to REBOOT the machine.

                                  Step 3.

                                  Once rebooted, go to the Device Manager and under Network adapters, select the first i350-T4 adapter, RIGHT MOUSE on it and select PROPERTIES.    Then click on the BOOT OPTIONS tab at the top.  Click on Flash information.  Update Flash.    I chose EFI+PXE, but you can choose what you need to at this point and make a backup of you original rom.    I did this process on all 4 to be absolutely sure, but I think you can do this step just once because it shows the update revision number as the new one on the next nic.

                                  Reboot.

                                  Give me a thumbs up/thanks if this helps anyone in the future.  8)

                                  pfSensational™

                                  1 Reply Last reply Reply Quote 0
                                  • G
                                    Gimli last edited by

                                    Thanks Corvey. I ended up finding some else's guide while you were writing this up but it's pretty much what I did. After downloading the tool you have in section 1 of your post I followed the following guide, except I used a DOS boot usb stick instead of what's in there, but the commands are the same:

                                    http://support.bull.com/ols/product/platforms/bullion/bullionExtendedMemory/dl/no-frmf/g/adapt_fw/FW-I350_X520/Ethernet_Intel_I350-X520_PreBoot_ReadMe.pdf

                                    My i350-T4 works great with FreeBSD and pfSense now.

                                    ;D

                                    1 Reply Last reply Reply Quote 0
                                    • C
                                      corvey last edited by

                                      @Gimli:

                                      Thanks Corvey. I ended up finding some else's guide while you were writing this up but it's pretty much what I did. After downloading the tool you have in section 1 of your post I followed the following guide, except I used a DOS boot usb stick instead of what's in there, but the commands are the same:

                                      http://support.bull.com/ols/product/platforms/bullion/bullionExtendedMemory/dl/no-frmf/g/adapt_fw/FW-I350_X520/Ethernet_Intel_I350-X520_PreBoot_ReadMe.pdf

                                      My i350-T4 works great with FreeBSD and pfSense now.

                                      ;D

                                      Cool, Gimli.  I researched and figured it out myself and made some quick sloppy directions on the way I did it, but that link you posted is probably better and more
                                      detailed to get the job done.    Someone had to post a how to  ;D  so now there are multiple sources to choose from!

                                      pfSensational™

                                      1 Reply Last reply Reply Quote 0
                                      • First post
                                        Last post