Hi,
I have an I225-V chip on an MSI X670E motherboard. The problem is that this 2.5G network adapter is junk and has a history all over the internet with others and myself experiencing disconnects on and off. So this forces me to use the 10G Realtek network adapter but was wondering is there a way to flash upgrade the network adapter to the latest rom in hopes it will fix this issue??
BTW: I tried all the fixes recommended online like setting power management to off, etc.
Thanks
I did it this year to my ROG Strix Z490-H, ST has the needed files to NVM 1.89
You should first check the NVM image currently and make a backup, according the guide.
The issue was initially to older revisions of the Intel PHY rev.1 and 2 with NVM older than 1.68 according revisions (3 total of the Silicon Spec Code)
-Intel(R) Ethernet Controller I225-V 8086 15F3 B1 SLN9D/SLN9C
-Intel(R) Ethernet Controller (2) I225-V 8086 15F3 B2 SLNJY/ SLNJX
It is supposed not to happen in rev.3
Intel(R) Ethernet Controller (3) I225-V 8086 15F3 B3 SLNMH/SLMNG
Recently findings may get you to version 1.94
As the issue was âsupposedlyâ fixedâŚthereâs not too much new NVM images around after Intel FIX and Vendors seem also didnât publish more recent ones on newer board/chipsets support pages.
PAY very attention to details and web reports, cause thereâs plenty of âkilledâ PHY from users upon such operations.
I do not recall to see an MSI official package to download, besides other vendors done it, like Asus, Dell, Lenovo etcâŚ
EDIT: Use driver 1.1.4.43 (Win10) from ST or 2.1.4.3 (Win11) from (IntelÂŽ Network Adapter Driver) releases.
------------------------------------------------------------------------------------------------------------------------
This is my own keynote and part of the official Intel ÂŽ Ethernet Controller I225 NVM Release Note (March 2021) from Intel-Ethernet Controller I225 NVM Readme-WW12-21.pdf
Supported network card:
Intel(R) Ethernet Controller I225-LM 8086 15F2 B1 SLN9B/SLN9A
Intel(R) Ethernet Controller I225-V 8086 15F3 B1 SLN9D/SLN9C
Intel(R) Ethernet Controller (2) I225-LM 8086 15F2 B2 SLNJW/SLNJV
Intel(R) Ethernet Controller (2) I225-V 8086 15F3 B2 SLNJY/ SLNJX
Intel(R) Ethernet Controller (3) I225-LM 8086 15F2 B3 SLNNJ/SLNNH
Intel(R) Ethernet Controller (3) I225-V 8086 15F3 B3 SLNMH/SLMNG
Intel(R) Ethernet Controller (3) I225-IT 8086 0D9F B3 SLNNL/SLNNK
Intel(R) Ethernet Controller (3) I225-LMvP 8086 5502 B3 SLNNJ/SLNNH
NVM 1/2MB difference (Foxville_I225):
1MB: No PXE ROM/ drivers
2MB: Included PXE ROM/ drivers
NVM image 1.56(1.38 EEPROM)
NVM image (1.45 EEPROM) LM/V/IT (early I225 repair version provided by most board manufacturers)
NVM image (1.53 EEPROM) LM/V/IT (I225 v3 factory version)
NVM image 1.87(1.57 EEPROM) LM/V/IT/LMvP (I225 LMvP factory version)
NVM image (1.68 EEPROM)
NVM image (1.73 EEPROM) LM/V/IT
Update I225-LM/ I225-IT NVM to
NVM image (1.76 EEPROM) LM/V/IT
NVM image (1.77 EEPROM) LMvP
NVM image (1.79 EEPROM) LM/V/IT/LMvP
NVM image (1.81 EEPROM) LMvP
NVM image (1.82 EEPROM) LM/V/IT/LMvP
NVM image (1.85 EEPROM) LM/V/IT/LMvP
NVM image 1.137(1.89 EEPROM) LM/V/IT/LMvP
NVM image (1.93 EEPROM)
NVM image 1.148(1.94 EEPROM)
----------------------------------------------------------------------------------------------------------
Useable tools (to my knowledge): EEUPDATE v5.38.10.00 - NVM Update Tool 1.41.3.3
Required diagnostic driver (to my knowledge): Intel Connection Tool SDK driver (NALdevice 1.5.0.8)
These are all avaiable across the various NVM packages on the web from several vendors as also in the Intel Network Adapter Driver (Complete Driver Pack)
@MearWar,
Thanks a million for that write up. I will definitely give it a go but I wanted to say that before you could respond here I downloaded 1.89 Lenovo version and ran the install.bat file where it quickly failed to launch. Hopefully it didnât do anything as making a backup of the rom is a fantastic idea.
I also tried emailing msi support asking them for any updated firmware they may have but my experience with MSI regarding these things is not so great. Curious what firmware version is installed currently. Will check later today as not home at the moment. Its weird how it just sprung up on me. I certainly donât want to kill the controller though if the risk is substantial.
Also I checked out the guide on station drivers. Had to translate it. Hopefully someone will write a guide followed by user experiences here on Winraid as I feel one is needed here.
Thanks again.
Do you understand the procedure to flash up to 1.94? Been reading the instructions on: 1.94 instructions and heâs saying you need to copy Foxpond1_I225_15F3_V_1MB_1p94.bin and nvmupdate.cfg into the 1.89 NVM folder and then flash as normal according to guide like this âEEUPDATEW64e.exe /nic=1 /d NVM\Foxpond1_I225_15F3_V_1MB_1p94.binâ ??
Is that correct or do I have to flash up to 1.89 then go up to 1.94 in that order or can I straight flash to 1.94?
Thanks
Thanks
Just like quotes it âBelow you will find the original and modded firmware files and the flasher. So all you have to do is copy the modified fw file and nvmupdate.cfg to the firmware flasher folder, if the subdevice or subvendor is different, they must be changed accordingly and maybe ETrackId.â
An HEX editor will do the job and thatâs why you need to know/backup your own data for editing (Logs will be generated auto or manually with your NIC data). Your primary MAC and Vendor etc⌠all this can be customized in the cfg file, there is several pdfâs from Intel for the tools switches and all that we can edit/customize.
You did noticed that he merged in to the official Intel NMV update package 1.94 (15F2 - LM), thatâs the âflasherâ is talking about it.
You can ask this user more infoâŚwe should be on an MSI board i supposeâŚ
Intel I225-V/I225-LM Rev 1.x Lan Controllers Firmware 1.94 | MSI Global English Forum
EDIT: Oh a side note⌠iâm not using the 1.94 as this was a bit painful just getting the 1.89 on it and have lost the NIC comms several times but never death, still iâm very pleased and have nothing to report from the actual 1.89
Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.41.3.3
Copyright(C) 2013 - 2024 Intel Corporation.
nvmupdatew64e.exe -i -l 1043.log
Config file will not be read.
Inventory
[00:010:00:00]: Intel(R) Ethernet Controller (2) I225-V
Alternate MAC address is not set.
Flash inventory started.
Shadow RAM inventory started.
Shadow RAM inventory finished.
Flash inventory finished.
[00:010:00:00]: Intel(R) Ethernet Controller (2) I225-V
Vendor : 8086
Device : 15F3
Subvendor : 1043 (ASUS)
Subdevice : 87D2
Revision : 2 (Was 1 with the original 1.38)
LAN MAC :
Alt MAC :
SAN MAC : 000000000000
ETrackId : 800002FC
SerialNumber :
NVM Version : 1.137(1.89)
PBA :
VPD status : Not set
VPD size : 0
NVM update : No config file entry
checksum : Valid
EDIT:
The path for the NVM image can also be configured in the cfg file, the Vendor is always Intel as obvious, but not the SubVendor (You see mine 1043 as ASUS, personal data was removed for posting), anyway the SubV is irrelevant, i saw a lot of reports with flashed NVM images not matching the user mb brand. That user in MSI forum as well.
nvmupdatew64e.exe -i -l <file.log> can give you your current info on your adapter
or
EEUPDATEW64e /nic=1 /adapterinfo
So I guess I will start with 1.89 for now just to be safe. Checked out that msi forum post. Thanks for linking it. As far as customizing nvmupdate.cfg all I have to is put in my MAC address in there. Vendor will always be Intel? and copy those files into the NVM folder? If I go that routeâŚ
Thanks
Getting:
EEUPDATEW64e /nic=1 /adapterinfo
Unable to load the driver. Please close all other applications and try again
What gives?
Seems that you donât have âcuriosityâ enough to âdigâ inside the packagesâŚ
Have you tried to read the files âeeupdate.txtâ and/or "readme.txt from NVM tool.
Didnât you noticed inside this tools/NVM packages an iqvsw64e.inf (The NAL device driver) required for this tools?
This is the driver that enables the tools coms with the PHY
I hope not
I wasnât being sarcastic, users tend to get it wrong and donât see the goal of it, they see it and react as you didâŚbut i will not react as i would like to, for the sake of this forum sanity⌠and with that said, were done here, all the best.
I suffer from RTFM disease. Must be terminal. Thanks for pointing me in right direction.
@Meatwar
Ok well I was able to only go up to 1.89 because securefiles wouldnât work as perhaps the nvmupdate.cfg file was incorrect. I think this because according to nvmupdatew64e when I run secure it gives an error that device not found. I also noticed that the subvendor and subdevice and eepid codes donât match what nvmupdatew64e -i -l is telling me:
Flash inventory finished.
[00:014:00:00]: Intel(R) Ethernet Controller (3) I225-V
Vendor : 8086
Device : 15F3
Subvendor : 1462
Subdevice : 7D68
Revision : 3
The only thing is the ALT MAC address is missing according to the diagnostic but my main MAC address transfered over at least. Not sure if important. Anyhow when I tried to edit nvmupdate.cfg to match my sub vendor ids and reran secure.bat this time it showed my devicesaying update available but it would fail to find the device again to flash. Perhaps my edits are incomplete or I did something wrong.
I mean wouldnât it be simpler to just use EEUPDATEW64e on the modded 1.94 file than using nvmupdate.cfg?
Anyhow 1.89 is just as bad as my old firmware still getting disconnects.
Thanks
Almost every report i saw using flashed NVM packages outside the official Intel one, every users gets the ALT MAC blanked but it seems the PRI and ALT macs are identical, seems non critical as well the PBA
You can run EEUPDATE /GUI and edit several NVM memory maps, flash, compare, verify, etc
I used it for the 1.89 instead of NVM tool because this was the content of original Asus NVM package, since then never done it to any other board.
I cant specify to you or anyone a âgeneralâ guidance, because i see reports of a lot of âmodsâ to these NVM packages around.
Station-Drivers - Intel I225-V/I225-LM Rev 1.x Lan Controllers Firmware Version 1.89 - Forum
Search the web for: IntelÂŽ Ethernet Controller I225 Software User Manual 1.3 PDF
Vendor : 8086 (Intel) always will stick CRITICAL
Device : 15F3 (can be edited to match ex. 15F2) CRITICAL i225 Foxville Series)
Subvendor : 1462 (MSI) works if blanked/mismatch
Subdevice : 7D68 (MEG X670E Godlike) works if blanked/mismatch
ETrackID: (CRITICAL, must be present, this is the revisions update tracking)
From other recent reports i stumble, your not the 1rst one, seems that new chipset board owners like your X670, suffers similar issues, perhaps Intel/Vendors is âcookingâ a new NVM packageâŚbut no light at the end of the tunnel has yet to be seen.
Well I tried again to flash the 1.94 but it doesnât use EEUPDATEW64 and instead required nvmupdate64e and a securefiles.bat and nvmupdate.cfg file configured to your hardware. Thats where I am having issues. I would much prefer to use EEUpdatew64 like I did for 1.89. I think the guy that modded the 1.94 i225v file rom from the âLMâ version didnât correct the header to the point you can use EEupdatew64 but I donât know. All I know is in his write up he compared the two versions and made changes to convert it to â-vâ variant. Still why canât you use EEUpdate?
I am giving up for now as using the securefiles.bat file fails to access the rom correctly and giving up on my i225-v controller because its junk. I donât know what happened a few days ago to make it faulter maybe the latest bios messed it up. Who knows.
Thank you
The EEupdate can run without any configuration files/NVM images, contrary to the NVM tool that always requires it.
The /GUI is a little more intuitive but it requires to know the background of the CMDs of the tool, so its a bit risky for users without the correct knowledge of it, thatâs why advised to search for the mentioned Intel i225 PDF
PRI MAC
SubVENDOR dev (Asus board/device ID)
SuvVENDOR (Asus)
PHY ID (15F3 i225-V)
VENDOR (Intel)
NVM version 1.89 (10 89)
ETrackID 8000003C
I ran the gui and hit enter to view the eprom data and it was all zeros. 0000 0000 0000 0000.
Anyhow still I wonder why this âEEUPDATEW64e.exe /nic=1 /d NVM\FXVL_15F3_V_1MB_1.94.binâ will not work? Is it because the file is missing the eep and txt files that accompany such rom files?
Also good to know that my adapter has been stable now for last 10 minutes. Lol.
My friendâŚthese screen captures are my i225âŚ
So zerosâs and still working⌠donât know how, i bet will be death after a cold reboot, i may be wrong still.
I saw some users like that on ST forum (last link i posted)âŚthey all could recover as long as the adapter was still ID in the tools.
One thing i noticedâŚnot sure if its valid, as long as the system isnât rebooted, we can flash over and over, still it needs some time for the SDK driver (NAL device) to unload, between operations/recover.
âEEUPDATEW64e.exe /nic=1 /d NVM\FXVL_15F3_V_1MB_1.94.binâ will not workâ
What errors does the CMD display to screen?
Perhaps its because its an AMD board but its still âworkingâ after cold boot in that I still am experiencing those random disconnects (pre-dates flash attempt). I didnât try âEEUPDATEW64e.exe /nic=1 /d NVM\FXVL_15F3_V_1MB_1.94.binâ as according to 1.94 update guide he has to use a nvmupdate.cfg file to update the file and I am afraid to try âEEUPDATEW64e.exe /nic=1 /d NVM\FXVL_15F3_V_1MB_1.94.binâ until I have assurances it will work. Anyhow the port is back up and working despite the gui not being able to read the eprom for whatever reason. Will ask of SS forum if there is another way.
Thanks
This may sound a little foolish of me but I had a brilliant idea to use another ethernet cable going from the Cat 6 cable to a Cat5e cable and connected it directly to the source bypassing the Asustor 2.5G switch I was using. So far no disconnects!
Think it was the switch at fault. Some tolerance or incompatibility issue maybe.
So far so good.
Guess I need a new switch. Next step is to connect this cable to the switch and see the difference.
Edit: Cable maybe at fault.
IntelÂŽ Ethernet Controller I225-V does not recognize that there is a cable plugged in during initial integration on Asus Prime Z690A. Contacted manufacturer for replacement however, same issue occurs even on new motherboard.
Resolution
There you go⌠
I vaguely remember seen reported issues with i22x and some routersâŚ
Well looks like its the cable. The new 5e cable is working no issues. Can go on the internet no issues. So not going to worry about the eeprom data. Got a minor firmware upgrade out of the deal I guess. Glad its working non the less.
I must be a complete idiot as all this time it was the Marvel 10G AQtion network adapter that has been not working! This whole time it was the Marvel! I confused the two ports on the back assuming one was the other! The Intel port is fine and still works. Unlike the Marvel port when connected to the Asustor 2.5G ASW205T which I canât find firmware for anywhere!
Wow. Talk about a mixup.
Edit: Trying to figure out how to flash the Marvel 10G controller. No instructions.
EDIT: These changes I found on Reddit seem to have helped the Marvel controller:
Marvel 10Gbe Adapter - Advanced Configuration Changes:
Energy Efficient Ethernet: Off
Flow Control: Off
Interrupt Moderation: Disabled
Interrupt Moderation Rate: Disabled
Jumbo Packets: 9014 (Must be configured on all switches/routers on your network + internal servers must have matching MTU. If you donât have a NAS or some type of high network capacity server on your network, donât touch this setting.)
Receive Side Scaling: Disabled
