Intel Ethernet Connection (2) I219-V Ethernet not Working

as a newly installed Fedora i have problem with motherboard ethernet device when im typing

lspci -knn | grep -i ethernet
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31)

device showing but when typing nmcli device status

DEVICE TYPE STATE CONNECTION
enp0s20f0u5 ethernet bağlandı Kablolu bağlantı 1 (THIS IS EXTERNAL ETHERNET ADAPTOR)
lo loopback bağlandı (dış) lo

not showing im searched many discussions about this problem but can’t find any solution how i would solve this ethernet device problem?

dmesg | grep e1000e
[ 7.063929] e1000e: Intel(R) PRO/1000 Network Driver
[ 7.063936] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 7.063969] e1000e 0000:00:1f.6: enabling device (0000 → 0002)
[ 7.064241] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mod

You haven’t mentioned the Fedora version you use, whether the system is booting any other OS, and whether ethernet has worked with some other Linux install. Internet searches are often overwhelmed by AI clickbait garbage. Try the LHDB to search for your hardware (system, ethernet controller vendor and subsystem ID’s) to see what others have experienced.

Please provide the output from lspci -knn | grep -iA3 'network controller' which should include a line for “Kernel driver in use”. You may get more details using journalctl --no-hostname -b -g e1000e.

You should make sure you have current vendor firmware.

look like my device not works fedora 41+ versions in this info Intel Ethernet Connection (2) I219-V

my hardware probe: HW probe of ASUSTek D520MT_D520SF_D320MT Desktop Computer #ccdf156a1b

im using Fedora 42

journalctl --no-hostname -b -g e1000e
May 08 22:04:43 kernel: e1000e: Intel(R) PRO/1000 Network Driver
May 08 22:04:43 kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
May 08 22:04:43 kernel: e1000e 0000:00:1f.6: enabling device (0000 → 0002)
May 08 22:04:43 kernel: e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conser>
May 08 22:04:43 kernel: e1000e 0000:00:1f.6: The NVM Checksum Is Not Valid
May 08 22:04:43 kernel: e1000e 0000:00:1f.6: probe with driver e1000e failed with error -5

sorry for im failed typing lspci -knn | grep -iA3 ‘network controller’

I have I219-LM that seems fine, but iirc there’s something about I219 devices, drivers, and revisions (mine’s rev 10 but rev 18+ drivers aren’t compatible).

I don’t have anything specific, but I’d clean the Ethernet ports (and use a different port on the router/switch) and change cables.

This is a long-standing issue for some versions of this controller. NVM (non-volatile memory) is where the controller firmware is stored. I think the “NVM Checksum Is Not Valid” error indicates that either the NVM has failed or the firmware is not the version expected by the linux e1000e driver. In the past, some distros added an option to ignore the error, but later removed it. Intel may have documents that tell you which firmware version are supported on your network controller. The copywrite dates are suspicious – how old is your network controller? Is the network controller a socketed card that could be replaced with a newer network controller?

There are multiple glyphs that resemple a single-quote. Pasting the above fails here, but editing the single-quotes works.

1 Like

The NVM checksum error is reported here also with LM: https://www.dell.com/community/en/conversations/precision-mobile-workstations/precision-7560-e1000e-module-error-the-nvm-checksum-is-not-valid/647f9784f4ccf8a8dea83444

I haven’t seen it rev 10, but a hardware report mentions Precision 7560 having rev 11.

A random page mentioned a UEFI OPROM update for the Ethernet on that Precision laptop. ASUS is about as-descriptive as Nintendo Switch updates with “Improve System Stability” between the two BIOS files :stuck_out_tongue: , but I’d try flashing non-beta 1403 in-case it does something different with the network OPROM.

I can’t find anything for firmware flashing Intel Ethernet directly (can probably be manually-modded in with BIOS editors and OPROM inject), but this implies there could be a NVM update.

Thanks for helping i will look other distros and kernels for now i dont know how old my ethernet device have a good days.

Im ticketed Intel this problem.