[solved] Intel i226 Firmware (see post #39)

[Seimus]

Testing a new N355 system,

It came with the i226-V firmware:

Code Select Expand

[1] igc0: EEPROM V2.22-0 eTrack 0x80000371
[1] igc1: EEPROM V2.22-0 eTrack 0x80000371
[1] igc2: EEPROM V2.22-0 eTrack 0x80000371
[1] igc3: EEPROM V2.22-0 eTrack 0x80000371

Upgraded to 2.32 using the 2MB file, process was without problems.

Code Select Expand

CURRENT FAMILY: 1.0.0
CONFIG VERSION: 1.20.0

; NIC device
BEGIN DEVICE
DEVICENAME: Intel(R) Ethernet Controller I226-V
VENDOR: 8086
DEVICE: 125C
SUBVENDOR: 8086
SUBDEVICE: 0000
NVM IMAGE: FXVL_125C_V_2MB_2.32.bin
EEPID: 80000422
RESET TYPE: REBOOT
REPLACES: 80000371
END DEVICE


Code Select Expand

[1] igc0: EEPROM V2.32-0 eTrack 0x80000422
[1] igc1: EEPROM V2.32-0 eTrack 0x80000422
[1] igc2: EEPROM V2.32-0 eTrack 0x80000422
[1] igc3: EEPROM V2.32-0 eTrack 0x80000422


Code Select Expand

[00:004:00:00]: Intel(R) Ethernet Controller I226-V
        NVM Version            : 2.50(2.32)
[00:005:00:00]: Intel(R) Ethernet Controller I226-V
        NVM Version            : 2.50(2.32)
[00:006:00:00]: Intel(R) Ethernet Controller I226-V
        NVM Version            : 2.50(2.32)
[00:007:00:00]: Intel(R) Ethernet Controller I226-V
        NVM Version            : 2.50(2.32)


Thanks for the guide!

Regards,
S.

[Seimus]

Upgraded today as well on my main N100 FW

It came with the i226-V firmware:

Code Select Expand

[1] igc0: EEPROM V2.13-0 eTrack 0x80000284
[1] igc1: EEPROM V2.13-0 eTrack 0x80000284
[1] igc2: EEPROM V2.13-0 eTrack 0x80000284
[1] igc3: EEPROM V2.13-0 eTrack 0x80000284

Upgraded to 2.32 using the 2MB file, process was without problems.

Code Select Expand

CURRENT FAMILY: 1.0.0
CONFIG VERSION: 1.20.0

; NIC device
BEGIN DEVICE
DEVICENAME: Intel(R) Ethernet Controller I226-V
VENDOR: 8086
DEVICE: 125C
SUBVENDOR: 8086
SUBDEVICE: 0000
NVM IMAGE: FXVL_125C_V_2MB_2.32.bin
EEPID: 80000422
RESET TYPE: REBOOT
REPLACES: 80000284
END DEVICE


Code Select Expand

[1] igc0: EEPROM V2.32-0 eTrack 0x80000422
[1] igc1: EEPROM V2.32-0 eTrack 0x80000422
[1] igc2: EEPROM V2.32-0 eTrack 0x80000422
[1] igc3: EEPROM V2.32-0 eTrack 0x80000422

Regards,
S.

[Seimus]

Upgraded today as well on my N5105 PRX node

It came with the i226-V firmware:

Code Select Expand

NVM Version            : 2.20(2.14)
NVM Version            : 2.20(2.14)
NVM Version            : 2.20(2.14)
NVM Version            : 2.20(2.14)

Upgraded to 2.32 using the 1MB file + the flashing utility for linux, process was without problems.

Code Select Expand

CURRENT FAMILY: 1.0.0
CONFIG VERSION: 1.20.0

; NIC device
BEGIN DEVICE
DEVICENAME: Intel(R) Ethernet Controller I226-V
VENDOR: 8086
DEVICE: 125C
SUBVENDOR: 8086
SUBDEVICE: 0000
NVM IMAGE: FXVL_125C_V_1MB_2.32.bin
EEPID: 80000425
RESET TYPE: REBOOT
REPLACES: 80000290
END DEVICE


Code Select Expand

NVM Version            : 2.50(2.32)
NVM Version            : 2.50(2.32)
NVM Version            : 2.50(2.32)
NVM Version            : 2.50(2.32)

Regards,
S.

[fjleon]

i'm late to the party, but i also have a N150 mini pc with i226-v (rev 4). I don't have opnsense right now, but will do via VM on proxmox.

Using ethtool -i, i get the firmware listed as "2017:888d". dmesg does not list the firmware (on linux). Does this map to the 2.17 version reported?

The reason I am interested in the firmware upgrade is that i am getting massive packet loss and up to 200 ms latency, even when pinging a device on the LAN. Seems to be completely random and if i unplug / replug the cables it might start working fine. Notably these nics support 2.5gbit but my switches are 1 gbit, though apparently autosensing is working as expected

[Seimus]

You need to do it directly on the underlying OS. If you would like to do in on VM you have to pass-thru the NIC top the VM.

Regards,
S.

[RobertoZ]

Successful upgrade from an Intel i350 two port to a i226 two port. This is a Fenvi i226 two port card that I ordered from Aliexpress.   

Card was on a etrackid that didn't correspond to any of the firmware. It was on v2.23 but the etrackid showed 8000397.   

Tried flashing 80000425 from the 1MB.  No go.  Tried in Arch linux, then booted into windows.  Would not flash and kept giving a security error in the log file.

Finally tried the 2MB version and that worked. 

Renamed the igb0/igb1 to igc0/igc1 in the config.xml file and installed the card.  At first, was able to get into Opnsense via web, but gateway was not showing.

Rebooted modem and everything seems to be working as it should be.

Thank you!!!!!

[OPNenthu]

Teh chart says

Perhaps word salad that makes no sense.

Teaming1* & VLAN2* Support = NO

Where vlan2* is
"Ethernet VLANs are virtual LANs that separate and isolate a physical network at the data link layer (OSI layer 2). 3rd party software is required."

So that says the 226v controller itself does not support .1q, but you can get .1q using 3rd party software? What's the software, is that the igc driver?

Just came across this: https://www.intel.com/content/www/us/en/support/articles/000005593/ethernet-products.html

I wonder if Windows clients need this "Intel® PROSet" tool to expose these functions in Device Manager and that's maybe what the reference was in regard to.