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

Started by BrandyWine, August 31, 2025, 05:21:07 PM

Previous topic - Next topic
Quote from: BrandyWine on May 21, 2026, 05:15:41 PMMore like those who email you a Word doc with subject line "some pics for you", you open the doc and there's no pics, just a https link where you can go see the pics.

That's how absurd a lot of Intel docs online are. ;)
But "The Stupidity Level" is the same and that's what I was aiming for :D
Weird guy who likes everything Linux and *BSD on PC/Laptop/Tablet/Mobile and funny little ARM based boards :)

Quote from: CGrisamore on September 14, 2025, 01:24:11 PMAfter successfully flashing my Lenovo box I remembered that one of the 2.5gb ports on my Minisforum MS-01 is an i226v. I ran the Intel flash utility in 'inventory' mode just to get a look at the firmware version and I got this in the log:

Warning: Cannot initialize port: [00:087:00:00] Intel(R) Ethernet Controller I226-V

Error:  The selected adapter (location:[87:00:00]) cannot be updated due to inaccessible device memory.
Update the device driver and reboot the system before running this utility again.
Consult the utility documentation for more information.

I'm going to poke around in the Minisforum BIOS to see if there's a setting there that's preventing access to the NIC.

I had the same issue on a Minisforum 773 Lite - I went into the BIOS (Del on startup) and just disabled all the trusted computing settings I could find, and hey voila it started working.

I have a Protectli VP2430 with coreboot that would just skip the flash, complaining about a secure boot certificate. Adding
-AllowMissingCert to the command allowed it to continue.

Today at 09:17:09 AM #228 Last Edit: Today at 01:37:41 PM by and
Hi, have an MSI box with 2x i226-v onboard

Current NVM is 2.23 etrack is 80000397 and it's not listed on the github but ITT it's reported as being a 2MB so got that version and this happens:

./nvmupdate64e -b -l nvm.log -m D843AEB4FB21 -f -u -c nvm.cfg

Config file read.
Error:   Failed to load FXVL_125C_V_2MB_2.32.bin. Please verify if the file is valid.

This is the nvm.cfg

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: 1462
SUBDEVICE: b0b1
NVM IMAGE: FXVL_125C_V_2MB_2.32.bin
EEPID: 80000422
RESET TYPE: REBOOT
REPLACES: 80000397
END DEVICE

Tried the 1MB:

./nvmupdate64e -b -l nvm.log -m D843AEB4FB21 -f -u -c nvm.cfg

Config file read.
Inventory
[00:088:00:00]: Intel(R) Ethernet Controller I226-V
Alternate MAC address is not set.
Flash inventory started.
Shadow RAM inventory started.
Shadow RAM inventory finished.
Flash inventory finished.
OROM inventory started.
OROM inventory finished.
Update
[00:088:00:00]: Intel(R) Ethernet Controller I226-V
Creating backup images in directory: D843AEB4FB21.
Backup images created.
Flash update started.
Error:    Flash update failed.
Device update failed.
Update security revisions
[00:088:00:00]: Intel(R) Ethernet Controller I226-V
Skipping update minimum security revisions.
Update VPD with VPD template
[00:088:00:00]: Intel(R) Ethernet Controller I226-V
Skipping VPD update with VPD template.
[code/]
For brevity this is half the inventory.log

[code][00:088:00:00]: Intel(R) Ethernet Controller I226-V
Vendor                 : 8086
Device                 : 125C
Subvendor              : 1462
Subdevice              : B0B1
Revision               : 4
LAN MAC                : D843AEB4FB21
Alt MAC                : 000000000000
SAN MAC                : 000000000000
ETrackId               : 80000397
SerialNumber           : D843AEFFFFB4FB21
NVM Version            : 2.35(2.23)
PBA                    : G23456-000
VPD status             : Not set
VPD size               : 0
NVM update             : No config file entry
  checksum             : Valid
OROM update            : No config file entry
  CIVD                 : 0.0.0
  EFI                  : 0.1.5, checksum None

Any ideas? Have read the this thread in its entirety - thanks to all for the contributions, especially BrandyWine - but I appear to be the first to encounter this error