Messages

There is FreeBSD util in the Intel bundle, you need to dig it out of the I210 TGZ zip that's in the I210 folder.

\Release_30.6.zip\NVMUpdatePackage\I210\I210_NVMUpdatePackage_v2_00_Linux.tar.gz\I210_NVMUpdatePackage_v2_00_Linux.tar\I210\Linux_x64\

2nd, please post your nvm cfg file you are using with flash util.

3rd, with a hyper-v, do not flash from a vm, flash only from the host OS.

What can be the problem here?

Where did you get the flash tool from? If it's a legit i226v then there is no reason for the flashing to fail, but using the right util matters.

Another fast way to do it, get flash util from Intel bundle download, the one for linux. Download Ubuntu iso (any version), Rufus Ubuntu iso to USB, then copy your 226 util/cfg/bin to the USB. From there boot the device with usb using the "try it" mode option. Once booted make sure you can find the 226s with lspci -vvv |more

From there, just use the flash util that is on the usb. Simple.

@mikey313
ID 303 is a way old 2MB firmware, #2 in historical list of 6.

I know for sure, there's an enormous amount of 226's out there running on problematic NVM. If only more people knew about the fix. ;)

According to current community information, the latest version is v2.36.

I can only find v2.32.
Maybe Intel has a v2.36 hidden behind one of their community pages?
I myself find it ridiculous that Intel makes it very difficult to get at NVM's.


Just a side note, I am working on very new Beelink EQ14 that has i226v (2MB) with old NVM. Another bewildering scenario, hardware makers are failing to at least flash the hardware with latest firmware. But since we have this thread, all fixed in a jiffy. :)

Did you comb through BIOS settings looking for any Virtual settings that need to be enabled. What about a new version of BIOS?

What I suspect is, new NVM is not playing nice with the existing static driver KLM.

Depending on actual OS you might be able to unload the static KLM and then load in a new KLM for the 550.

This is one of my gripes, shoving a bunch of driver mods into the GENERIC build of kernel, which makes it very difficult to try out new KLM's in attempt to fix issues. An OS install should find the hardware and then activate the related KLM's, this way it's still "P&P" but you at least get to pull a mod out and put some in as you see fit. This also makes the kernel more lightweight.

This one says it can do crosstalk tests (but not sure what test for FEXT and NEXT). You can login to Amazon and use Rufus to post a question.
Amazon item B0DSHWHC7R "NOYAFA NF-8601S Network Cable Tester"

Another issue can be Alien Crosstalk, which is much harder to identify.

Crosstalk is an issue because it confuses the transceivers
https://www.flukenetworks.com/blog/cabling-chronicles/cable-testing-101-cross-talk-near-and-far

I find EFI version on NVM tool easier to use. Simply grab eeupdate64e.efi form Intel driver pack, boot into EFI shell and run command like:

Code Select Expand

eeupdate64e.efi /nic=1 /d=FXVL_125C_V_1MB_2.32.bin
You only specify nic number and name of NVM file to flash. No need to worry about configuration file.

What about doing a backup before it flashes, or just wanting to get NIC info, or create a log file. Does efi method do that?

So, I did a little more testing and replaced the Xfinity XB8 gateway with a Hitron CODA56. I'm not a fan of running ISP equipment especially Xfinity.

Well, perhaps you know or don't know, Xfinity hardware (cable boxes, extra outlet boxes) is transitioning to wifi6, later to wifi7, but they require the Xfinity wifi-modem to work. They use their own wifi-modem device to mux the wifi to cable, all in an effort to remove the requirement to have RG coax in every location and wired/split/amp'd correctly. They no longer offer the mini outlet box with RG (F) connection, it's now fully a 4kHD via wifi only. It's a brilliant idea, except for the reliance to use their wifi-modem.

@bbin,
Try this zip for v1.94. I think I got this out of an Intel bundle from back in Sept2025.
https://tinyurl.com/i225fw194

Unfortunately, using the bin from this zip with the bsd util doesn't always work that way, bin's can be compiled for use with specific flash utils, so you may need to boot into windoze and flash it from there. But I don't have any 225's so I am not sure if this specific v1.94 is the one for your 225.

....... I have not seen any issues with the N150 mini PC with the new firmware on a new build of OPNSense.

Mine too has be problem free. But I will note, the more features you run the higher the probability of an issue popping up. I don't run many features at all. Basoc stuff, boson, suricata, fw, and I am playing around with WireGuard, but that's it. My little N150 seems to run almost idle all the time.

Just one question when I ran "dmesg | grep IGC"  I am seeing some references to the older version?  I am assuming that this is a cumulative log that doesn't clear on reboot?

Welcome to freeBSD. You are seeing old boot info. You can change that behavior.

Use the flash utility to get info on all the nics it can address.

Please edit post #1, edit thread title with a "[SOLVED]" in front.

The SSIDs are already setup in the access point.

Is each SSID in it's own subnet (vlan), and you trunk the wifi device to the firewall?

Is the pi booting with randomized MAC?

https://raspberrypi.stackexchange.com/questions/68513/pi-using-a-random-mac-address-after-every-reboot-how-do-i-stop-this-behavior

Chrome? The ABC company, goole?

Self-signed certs is the issue for the notice. Try installing the cert as "trusted", then the notice will go away.

https://www.codegenes.net/blog/getting-chrome-to-accept-self-signed-localhost-certificate/