[SOLVED]: Intel i350-T4 can't be recognised
-
When you say you tried the card in Windows 7 and 2008 R2, is that with those operating systems on the Supermicro motherboard?
-
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.
-
screenshot of the error
-
Thanks for all the replies.
You guys are awesome! ;D
-
What was it?
-
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!
-
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?
-
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.
-
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)
-
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
-
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!
