March 23, 20206 yr Hi bro, I have a new build with ASUS Z270i motherboard, included i219v. but it can't work on unraid 6.8.1. root@Tower:/home/e1000e-3.6.0# dmesg | grep e1000e [ 13.948379] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k [ 13.949416] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 13.950097] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 14.171827] e1000e 0000:00:1f.6: The NVM Checksum Is Not Valid [ 14.212863] e1000e: probe of 0000:00:1f.6 failed with error -5 https://unix.stackexchange.com/questions/294753/intel-ethernet-connection-i219-v-not-working-under-linux-on-an-asuspro-b-laptop unfortunately, I can't use yum, apt, etc. so that I can't make it. is it possible to be solved?
March 24, 20206 yr i219v were common on Intel platform and I haven't problem too. Does mainboard BIOS already update ? Your provide link have two solution which seems can fix it in hardware level. https://superuser.com/questions/1104537/how-to-repair-the-checksum-of-the-non-volatile-memory-nvm-of-intel-ethernet-co/1106641#1106641 1. Write NVM Checksum word using ethtool 2. attempt to boot over the network with UEFI (IPv4) Edited March 24, 20206 yr by Benson
March 25, 20206 yr Author update my solutions fyi. 1. add "modprobe e1000 eeprom_bad_csum_allow=1" into go file, failed Problem with e1000: EEPROM Checksum Is Not Valid 2. modify i219v to i219-LM via eeupdate, now it works. hopefully can help someone. i hide the mac address. root@Tower:~# dmesg | grep e1000e [ 18.642910] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k [ 18.643344] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 18.643923] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 18.899380] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock [ 18.975021] e1000e 0000:00:1f.6 eth1: (PCI Express:2.5GT/s:Width x1) 88:88:88:88:88:88 [ 18.975024] e1000e 0000:00:1f.6 eth1: Intel(R) PRO/1000 Network Connection [ 18.975080] e1000e 0000:00:1f.6 eth1: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF [ 20.777124] e1000e 0000:00:1f.6 eth1: removed PHC [ 21.295254] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k [ 21.295256] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 21.295520] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 21.509554] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock [ 21.591988] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 88:88:88:88:88:88 [ 21.591993] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection [ 21.592048] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF [ 24.989268] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
May 2, 20206 yr On 3/26/2020 at 5:02 AM, jhyang said: update my solutions fyi. 1. add "modprobe e1000 eeprom_bad_csum_allow=1" into go file, failed Problem with e1000: EEPROM Checksum Is Not Valid 2. modify i219v to i219-LM via eeupdate, now it works. hopefully can help someone. i hide the mac address. root@Tower:~# dmesg | grep e1000e [ 18.642910] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k [ 18.643344] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 18.643923] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 18.899380] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock [ 18.975021] e1000e 0000:00:1f.6 eth1: (PCI Express:2.5GT/s:Width x1) 88:88:88:88:88:88 [ 18.975024] e1000e 0000:00:1f.6 eth1: Intel(R) PRO/1000 Network Connection [ 18.975080] e1000e 0000:00:1f.6 eth1: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF [ 20.777124] e1000e 0000:00:1f.6 eth1: removed PHC [ 21.295254] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k [ 21.295256] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 21.295520] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 21.509554] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock [ 21.591988] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 88:88:88:88:88:88 [ 21.591993] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection [ 21.592048] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF [ 24.989268] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx hello, i have the same issue. may i know how to modify i219v to i219-LM via eeupdate ? thanks
June 13, 20206 yr Author Hi, this is a brief steps 1. need a dos disk. I choose a portable disk with "rufus" 2. copy eeupdate (eg. 5.29.10.5) 3. start from the removable disk 4. key in eeupdate /gui. 5. select i219-v, enter. -> Raw EEPROM - Extended, enter 6. Editing EEPROM, at line 2, edit the fourth and sixth byte (0x0B & 0x0D) 7. backup first. F3-Dump To File product INTEL I219_LM 0x156f I219-LM Ethernet Connection product INTEL I219_V 0x1570 I219-V Ethernet Connection product INTEL I219_LM2 0x15b7 I219-LM Ethernet Connection product INTEL I219_V2 0x15b8 I219-V Ethernet Connection product INTEL I219_LM3 0x15b9 I219-LM Ethernet Connection product INTEL I219_LM7 0x15bb I219-LM Ethernet Connection product INTEL I219_V7 0x15bc I219-V Ethernet Connection product INTEL I219_LM6 0x15bd I219-LM Ethernet Connection product INTEL I219_V6 0x15be I219-V Ethernet Connection product INTEL I219_V5 0x15d6 I219-V Ethernet Connection product INTEL I219_LM4 0x15d7 I219-LM Ethernet Connection product INTEL I219_V4 0x15d8 I219-V Ethernet Connection product INTEL I219_LM5 0x15e3 I219-LM Ethernet Connection 8. I edit both to 0x15b7, then Checksums 9. esc and save. you can do 'eeprom test' to check if it pass. 10. 'Select A device' to see if it is effective. Edited June 13, 20206 yr by jhyang
November 24, 20232 yr Thank you very much jhyang for your steps - this was able to fix the NIC on my elderly Asrock H270M-ITX board which I have never been able to use the 2nd NIC in FreeNAS / TrueNAS / Unraid (currently on trial). On 6/14/2020 at 1:47 AM, jhyang said: Hi, this is a brief steps 1. need a dos disk. I choose a portable disk with "rufus" 2. copy eeupdate (eg. 5.29.10.5) 3. start from the removable disk 4. key in eeupdate /gui. 5. select i219-v, enter. -> Raw EEPROM - Extended, enter 6. Editing EEPROM, at line 2, edit the fourth and sixth byte (0x0B & 0x0D) 7. backup first. F3-Dump To File product INTEL I219_LM 0x156f I219-LM Ethernet Connection product INTEL I219_V 0x1570 I219-V Ethernet Connection product INTEL I219_LM2 0x15b7 I219-LM Ethernet Connection product INTEL I219_V2 0x15b8 I219-V Ethernet Connection product INTEL I219_LM3 0x15b9 I219-LM Ethernet Connection product INTEL I219_LM7 0x15bb I219-LM Ethernet Connection product INTEL I219_V7 0x15bc I219-V Ethernet Connection product INTEL I219_LM6 0x15bd I219-LM Ethernet Connection product INTEL I219_V6 0x15be I219-V Ethernet Connection product INTEL I219_V5 0x15d6 I219-V Ethernet Connection product INTEL I219_LM4 0x15d7 I219-LM Ethernet Connection product INTEL I219_V4 0x15d8 I219-V Ethernet Connection product INTEL I219_LM5 0x15e3 I219-LM Ethernet Connection 8. I edit both to 0x15b7, then Checksums 9. esc and save. you can do 'eeprom test' to check if it pass. 10. 'Select A device' to see if it is effective.
October 21, 20241 yr Hi there, jhyang I logged in simply to express my deepest gratitude for your solution above. I spent several days trying to understand why Unraid 6.12.13 couldn't recognize the I219-V in my ASUS Z170i Pro Gaming motherboard, but thanks to your post, I was able to resolve the issue. I have gone ahead and implemented the solution to other I219-V (e.g. ASRock H270M-ITX/AC as the other poster), and will share this information whenever I come across anyone dealing with this problem. Have a great one!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.