It looks like indeed there is a mismatch of the checksum of the non-volatile memory of I219-V. Just in case I tried using the latest version 3.3.4 of e1000e, but the error was the same: "The NVM Checksum Is Not Valid." However, e1000e is listed as supporting I218-V, and I've got a confirmation from e1000-devel mailing list that e1000e should support I219-V. I have searched for "official" Linux drivers, but none is listed as supporting I219-V. Under Windows 7 Ethernet port works fine: I can connect to the Internet.Īccording to Windows, I have Intel(R) Ethernet Connection I219-V.
e1000e 0000:00:1f.6: The NVM Checksum Is Not Valid e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode The driver used is e1000e, it reports: $ dmesg | grep e1000e This intel one is buggy.I have a problem with an ASUSPRO B8430UA laptop: when I boot it with Ubuntu 16.04 (or NixOS 16.03) the Ethernet port does not work. Im lucky enough that my Z490 board also has a Aquantia 10gb lan aswell. Im not that impressed to be honest with you. There is already a V3 expected later this year. The problem has to do with compatibility with certain switches from what I understand.
But that it just MIGHT be possible Intel can try to mitigate the issue in the future with new firmware releases. Issues that according to some are still on a hardware level. People have found the V2 still suffers from issues. I dunno but but i feel something isnt right.Īlso I hate to be the bearer of bad news but who ever on reddit is saying the V2 is fully bug fixed is wrong. With that being said ive also seen some people say its working fine for them. I spend a few weeks trying to figure it out, including a completely new motherboard. Myself and a few others that ive found on various forums have experienced throttling on high speed internet and the intel I225-V. I still really believe the NIC isnt acting as good as it should. While your initial issue with complete disconnects has disappeared by rolling back driver. At the end will have a V2 if you got a V2.
You can check what controller you got by looking at the HW ids. It is sad that it appears to be a Hardwire problem with controller. Will do further testing and post if any issues.But we need this fix from intel ASAP. Ran a few test for packet loss- 0% so far. I've just rolled back to 1.0.0.13 and set manually to 1.0 gbits full duplex. V1 or updated V2? Someone on reddit told all new boards have this bug fixed and updated with the new version of I225V. It might depend on which controller we got.
0 kommentar(er)
