Getting Intel i219-V to work in Debian 12

nkonko

nkonko

New Member
Joined
Jul 2, 2023
Messages
16
Reaction score
7
Credits
148
Hi,
This may not be debian specific at all.

I am trying to get my i219-V ethernet controller to work. This is more or less fresh install of Debian 12.

It does show up in pci list:

Code: 
sudo lspci | grep -i net
00:14.3 Network controller: Intel Corporation Tiger Lake PCH CNVi WiFi (rev 11)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (14) I219-V (rev 11)

However its not recognized by system:
Code: 
ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether a4:6b:b6:d8:39:7f brd ff:ff:ff:ff:ff:ff
    altname wlp0s20f3

It appears this device is kernel supported since some version of 4.*.

What can I try to get this to work?
 


can you post the output of

lspci -knn | grep -iA3 net

that applies to your ethernet controller? that should add a bit more info including whether or not the controller has a "Kernel driver in use" line. since your wifi adapter has an interface (wl01) and is shown to be UP, you should be able to compare that with the ethernet.
 
z7vl7abxc said:
can you post the output of
Click to expand...

Hi, thank you. Here it is:

Code: 
lspci -knn | grep -iA3 net
00:14.3 Network controller [0280]: Intel Corporation Tiger Lake PCH CNVi WiFi [8086:43f0] (rev 11)
    DeviceName: Onboard - Ethernet
    Subsystem: Intel Corporation Wi-Fi 6 AX201 160MHz [8086:0074]
    Kernel driver in use: iwlwifi
    Kernel modules: iwlwifi
--
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (14) I219-V [8086:15fa] (rev 11)
    DeviceName: Onboard - Ethernet
    Subsystem: Intel Corporation Ethernet Connection (14) I219-V [8086:0000]
    Kernel modules: e1000e
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA102 [GeForce RTX 3090] [10de:2204] (rev a1)
    Subsystem: eVga.com. Corp. GA102 [GeForce RTX 3090] [3842:3998]
 
since it is missing the "Kernel driver in use" line, you could try checking for system journal messages about the driver and pci bus to see if you can get an idea what the problem might be. you could try that search with something like

jornalctl -b | grep -E '00:1f.6|e1000e'
 
Code: 
sudo journalctl -b | grep -E '00:1f.6|e1000e'
Jul 02 13:36:05 larion kernel: pci 0000:00:1f.6: [8086:15fa] type 00 class 0x020000
Jul 02 13:36:05 larion kernel: pci 0000:00:1f.6: reg 0x10: [mem 0xa1500000-0xa151ffff]
Jul 02 13:36:05 larion kernel: pci 0000:00:1f.6: PME# supported from D0 D3hot D3cold
Jul 02 13:36:05 larion kernel: pci 0000:00:1f.6: Adding to iommu group 13
Jul 02 13:36:05 larion kernel: e1000e: Intel(R) PRO/1000 Network Driver
Jul 02 13:36:05 larion kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
Jul 02 13:36:05 larion kernel: e1000e 0000:00:1f.6: enabling device (0000 -> 0002)
Jul 02 13:36:05 larion kernel: e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Jul 02 13:36:05 larion kernel: e1000e 0000:00:1f.6: The NVM Checksum Is Not Valid
Jul 02 13:36:05 larion kernel: e1000e: probe of 0000:00:1f.6 failed with error -5
Jul 02 13:37:34 larion sudo[3354]:      max : TTY=pts/0 ; PWD=/home/max ; USER=root ; COMMAND=/usr/sbin/modinfo e1000e
Jul 02 13:38:59 larion sudo[3693]:      max : TTY=pts/0 ; PWD=/home/max ; USER=root ; COMMAND=/usr/sbin/modprobe e1000e

I'll see what i can find about this. Thank you for your help so far, very educational.
 
nkonko said:
Jul 02 13:36:05 larion kernel: e1000e: probe of 0000:00:1f.6 failed with error -5
Click to expand...
this line looks vaguely familiar from other support posts. do you know if you have fast startup disabled in windows?

https://www.windowscentral.com/how-disable-windows-10-fast-startup

i've usually only see that affect wifi and possibly bluetooth, but it might be worth a try to disable it and see if that helps.

i had meant to ask before: is this a desktop or laptop?
 
Ok so some recommendations from other instances of this are to:
  • power cycle the system completely (done).
  • disable / enable network stack (done, although only LAN)
  • Update BIOS, already on latest (EVGA z590 FTW WIFI)
Neither helped.
 
nkonko said:
power cycle the system completely (done).
Click to expand...
did that include holding down the power button while the system was unplugged and battery out (if laptop) to make sure all residual juice was absolutely drained? it sounds weird, but could be worth a try if you haven't already.

also, is fast startup disabled in windows 10?
 
z7vl7abxc said:
did that include holding down the power button while the system was unplugged and battery out (if laptop) to make sure all residual juice was absolutely drained? it sounds weird, but could be worth a try if you haven't already.

also, is fast startup disabled in windows 10?
Click to expand...
This is a custom built PC tower.

Sorry, I know you mentioned it twice, I've disabled it (fast boot) in bios first, then in windows 10 power options (had no idea this existed).

I did just hold down the power button after flipping PSU off, as you suggested, which completely reset my BIOS, and then sent the system into endless reboot loop via GRUB.

It would get stuck in "Welcome to GRUB", or make it to selection and get stuck after a selection, or on black screen, which would sometimes reboot by itself and sometimes needed a manual reset... this continued for a while until I unplugged (via PSU switch) the system again and held the button down again, resetting BIOS. But this time I got to boot into Windows and now in Debian.

Unfortunately "The NVM Checksum Is Not Valid" still persists.

Going to try a few more power / reset cycles. Maybe its just easier to get a standalone Linux compatible NIC.

Thank you again for the time taken to help.
 
i am sorry to hear holding the power button down had a bad effect on your system. i am glad you were able to recover. the only other posting i could find with those same two error messages also ended up replacing the nic unfortunately.
 
z7vl7abxc said:
i am sorry to hear holding the power button down had a bad effect on your system. i am glad you were able to recover. the only other posting i could find with those same two error messages also ended up replacing the nic unfortunately.
Click to expand...
Its alright, nothing is quiet right on this system. Should have probably gone with a different motherboard...
Will look for standalone NIC.
 
it's been a while since i had a desktop, but got to thinking after you said that about a bios reset that might mean your cmos battery is dead. that doesn't really help with your ethernet issue. just thought i would mention it in case: https://www.howtogeek.com/893809/how-to-test-and-replace-your-cmos-battery/

have you tested any other distributions on the system to see if they do better with the ethernet adapter? mx linux 21 is based on debian 11 and has lots of extra packages to try and work with more hardware out of the box. i believe their 23 version that is based on debian 12 is still in beta testing, but should be out before too very long: https://mxlinux.org/download-links/
 
You're probably right. I should order a new one. Its such a rare event for a CMOS battery to run out that since '97 this is my second time, if that's indeed what it is.

I've ordered a standalone NIC, its not a big deal. I'll check out MX when it goes stable. Gnome4 has me entranced, love the zen like simplicity.

Thanks again for the help!
 
you're welcome. agreed that those batteries rarely tap out, but resetting the bios triggered an old computer repair memory.

i never could get used to gnome though i appreciate what pop os did with the ubuntu version. i settled into xfce a few years back and appreciate having gotten to know where all the parts and bits are over time.

i hope things go better with your new nic and your eventual switch to linux if you decide to go that way. good luck!
 
It may not make any difference , but try disabling secure boot [w10/11]
 
Brickwizard said:
It may not make any difference , but try disabling secure boot [w10/11]
Click to expand...
Thank you, unfortunately still same result. But, new NIC works out of the box.


Code: 
05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
    Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:0123]
    Kernel driver in use: r8169
    Kernel modules: r8169
 
denvertan said:
Is your problem solved ?
I am also having the same problem.
Click to expand...
I ended up getting a standalone nic. Onboard Intel i219-V still doesn't work and shows same error message on boot, but I haven't pursued the issue since the previous post here.

If you do get it to work, please share your solution.
 
You must log in or register to reply here.

Members online

Total: 699 (members: 5, guests: 694)

Latest posts

Top