- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Motherboard: Asus ROG STRIX B76-I Gaming Wifi (V2)
I have attached a SSU scan. I have tried several driver versions for the LAN adapter. I have tried every fricking iteration of energy management, wake-on-whatever, speed & duplex settings.
Like others have reported, the event viewer reports ef2fnexpress ID 27 and 32 over and over again. It can happen 1 time a day, or it can happen 40 times in the span of 10 minutes. It appears completely and utterly random. It doesn't matter if the PC is idling or if I'm gaming.
Fix yo **bleep** equipment.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This issue was said to be because of EEE (Energy Efficient Ethernet), when intel first admitted the issue, their workaround was to disable that. The workaround never worked for my issue, which was no connection 50% of the time I resumed from sleep.
Intel then said they have fixed this by means of an 'NVM' update which is a firmware update to the Network Adapter, separate from the driver. After this update, EEE can be used and there should be no disconnects.
Sadly, unlike when intel fixed the i225 firmware, they haven't released the NVM update to the public, and instead are forcing us to contact our OEM motherboard makers instead. In my case, MSI. In your case ASUS.
Sadly, as a customer this puts us in a bad place. Intel will not help beyond telling us to go elsewhere, and the OEMs won't help because their support doesn't care, or doesn't even know what an NVM update is.
The most you can do is contact Asus and explain and hope you get someone with half a brain, if not, hopefully they can escalate your case to someone who can.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@superdimitri wrote:This issue was said to be because of EEE (Energy Efficient Ethernet), when intel first admitted the issue, their workaround was to disable that. The workaround never worked for my issue, which was no connection 50% of the time I resumed from sleep.
Intel then said they have fixed this by means of an 'NVM' update which is a firmware update to the Network Adapter, separate from the driver. After this update, EEE can be used and there should be no disconnects.
Interesting! Is there an official documentation from Intel that this NVM update has been released and fixes the problem for good?
I'm still having issues with the power management with the I226V on my Odroid board. The network adapter freezes the entire system, when you try to enable power management under Linux. Is this maybe related to the EEE issue that's causing the disconnects?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I expect it is a similar issue. I think the i226v hardware is flawed and they are trying to patch it with firmware and workarounds.
An official announcement? No, of course not. This will mean they can be held liable.
I think you are probably having the issue with the disconnects that many others reported, that issue, oddly I have never had (probably my firmware revision is more recent, I can't tell). Many people reported disabling ASPM either on a BIOS level or in Windows fixes that. My issue is that the device doesn't detect a cable is connected after sleep 50% of the time.
I think in Linux you probably can use the same workaround by just disabling the ASPM power saving features.
For a fix, you'd likely need the new NVM firmware from your motherboard/PC manufacturer.
Here are some relevant threads, and posts from Intel Employees. They have closed threads saying issues have been fixed, when they have not.
Here's the confirmation of the NVM fix:
Another common trait is for Intel employees to point users to FAQs and fixes for issues with the older i225. Intel released the i225 NVM fix in their latest driver pack instead, but still suggested customers contact their OEMs to get the fix from them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As predicted, MSI have not released an NVM update, and aren't willing too.
They just state they will take the board in for an RMA which is useless because it's not going to fix the issue.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page