• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

PSA: Intel I226-V 2.5GbE on Raptor Lake Motherboards Has a Connection Drop Issue: No Fix Available

Guys I am a new user I signed up here becouse this seems the place where this topic was examinated in deep, in these days, Asus renewed the motherboards lineup with Z90 refresh, but nobody telling us if the problem was issued, so what is the truth?
Somebody know if there are a new I226V revision for istance, to resolve the problem?

Thanks
 
There's no new revision of the i226 because there's nothing wrong with the hardware.
 
Potentially something with the driver software and/or the way it interacts with windows if you even have a problem at all. I haven't used one long enough on windows to say one way or another I can just say that with pfsense (FreeBSD) and TrueNAS Scale (Debian) I've had zero issues. The pfsense box is one of the CWWK router boards out of china and truenas is a w680 motherboard.
 
In my case to remove the problem, i hav e bought a Z790-p asus with Realtek chipset, do you hint me to stay with this to avoid all problems then? :)
 
I don't really think onboard NIC is a metric I'd use to determine a board purchase, but so long as the board works for you it's fine.
 
I don't really think onboard NIC is a metric I'd use to determine a board purchase, but so long as the board works for you it's fine.
I understand your point of view, but I realize computers builds with glass, so if I buy a mobo I'd like to see all clean, I don't like an extern nic. I think you understand me too.

For the moment I will stay with my z790-p we will see in future.

Thanks
 
Problem? Once again, I have motherboard with 4 onboard I226-V working with no issues in FreeBSD.
Most users will use windows, hence, problem if it drops there.
 
Most users will use windows, hence, problem if it drops there.

You can set up a VM with FreeBSD, use PCIe passthrough to let FreeBSD in the VM manage the network card and then route network traffic from Windows through the VM.
 
You can set up a VM with FreeBSD, use PCIe passthrough to let FreeBSD in the VM manage the network card and then route network traffic from Windows through the VM.
That won't work for a lot of use cases and is quite an overhead for no reason. Personally, I'd just get another NIC rather than muck about with that.
 
Most users will use windows, hence, problem if it drops there.
May be. But least that means the problem is not with the hardware.
 
So, in other words Intel can't write a stable Windows network driver to save their lives.
 
So, in other words Intel can't write a stable Windows network driver to save their lives.
Probably, but we don't know whether the fault lies with the driver or some other component in Windows.
 
Probably, but we don't know whether the fault lies with the driver or some other component in Windows.
But if Realtek has a driver that works properly, then I'm going to say that Intel is the party that's at fault here.
 
But if Realtek has a driver that works properly, then I'm going to say that Intel is the party that's at fault here.
Intel also has drivers that work properly for other network solutions. But you are free to say whatever you want.
 
That won't work for a lot of use cases and is quite an overhead for no reason. Personally, I'd just get another NIC rather than muck about with that.

I was joking. But only mostly. People do things like that and the performance should be easily good enough for 2.5 Gb/s.

Keep in mind your Internet packets go through many routers like that anyway. Of course not for LAN.

May be. But least that means the problem is not with the hardware.

I didn't read the whole thread. To me this smells like power management getting in the way. That would be a possible explanation of the difference to the FreeBSD driver, which probably has very little power management. Definitely turn off all powersaving features in the Windows driver.
 
I didn't read the whole thread. To me this smells like power management getting in the way. That would be a possible explanation of the difference to the FreeBSD driver, which probably has very little power management. Definitely turn off all powersaving features in the Windows driver.
I believe that was actually the initially suggested workaround.
 
I didn't read the whole thread. To me this smells like power management getting in the way. That would be a possible explanation of the difference to the FreeBSD driver, which probably has very little power management. Definitely turn off all powersaving features in the Windows driver.
I posted a solution earlier in the thread to uncheck the box for allowing the device to save power and someone replied that fixed it for them. (for I225 anyway)
 
Hi,
Likely memory issues
Intel nic has never liked blk oc;ing ddr5 probably just added more pain I'd bet
I've never seen any issues personally on wired when others were and I've been using built in wifi exclusively for a year and still no issues mostly on win-10 though.
 
Hi,
Likely memory issues
Intel nic has never liked blk oc;ing ddr5 probably just added more pain I'd bet
I've never seen any issues personally on wired when others were and I've been using built in wifi exclusively for a year and still no issues mostly on win-10 though.

It's not that. The Foxville controller has severe errata that causes it to crash and reset, losing packets/dropping connection when in high-speed modes. Intel has provided firmware updates for the earlier steppings to attempt to mitigate the problem, and the i226-V is just a reckless and shameless re-release of the i225-V B3. It obviously has the same problems.
 
i226-V is just a reckless and shameless re-release of the i225-V B3.
It's not even that, because by most accounts the b3 stepping is drastically better. It's like they went backwards again.
 
And that's why I'll insist on having a Realtek Ethernet chip on my boards.
 
Back
Top