Intel i219-V problems in Debian 12

rheaalleen

New Member
Joined
Dec 10, 2023
Messages
3
Reaction score
0
Credits
42
After trying to troubleshoot yesterday I´m out of ideas

Bought some Tiny M710q to install Bookworm on them but having troubles to get the ethernet going.

I´ve confirmed that my switch configuration is correct by installing W10 onto one and plugging it in. DHCP worked and machine had access to internet.

But installing Bookworm leads to having an UP interface but no IP address.

During the installation when selecting the ethernet it says it successfully got DHCP and proceeds but fails at downloading packages from mirror with no connectivity.

Tried installing the driver manually with https://www.linux.org/threads/getting-intel-i219-v-to-work-in-debian-12.45761/post-208583 or resetting/flashing driver https://www.linux.org/threads/intel-i219v-gigabit-lan-controller-not-working.43844/post-183953 but no success.

Configuration/Information:

Code:
lspci -nn | grep -i net 
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8]

ip a 
enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
        link/ether 6c:4b:90:6b:14:1a brd ff:ff:ff:ff:ff:ff
        inet6 fe80::6e4b:90ff:fe6b:141a/64 scope link
        valid_lft forever preferred_lft forever

modinfo e1000e | grep ver
    
filename:       /lib/modules/6.1.0-14-amd64/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
description:    Intel(R) PRO/1000 Network Driver
vermagic:       6.1.64 SMP preempt mod_unload modversions

dmesg | grep firmware
[    2.774397] platform regulatory.0: firmware: direct-loading firmware regulatory.db
[    2.774878] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s
[    2.818654] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-8265-36.ucode
[    2.819602] iwlwifi 0000:02:00.0: loaded firmware version 36.ca7b901d.0 8265-36.ucode op_mode iwlmvm
[    3.245677] i915 0000:00:02.0: firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[    3.245970] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)


dmesg | grep e1000e
[    1.107312] e1000e: loading out-of-tree module taints kernel.
[    1.107440] e1000e: module verification failed: signature and/or required key missing - tainting kernel
[    1.113271] e1000e: Intel(R) PRO/1000 Network Driver
[    1.113273] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.113500] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    1.191340] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock
[    1.256344] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 6c:4b:90:6b:14:1a
[    1.256354] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
[    1.256420] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF
[    1.279465] e1000e 0000:00:1f.6 enp0s31f6: renamed from eth0
[    7.590249] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

/etc/network/interfaces
    
auto enp0s31f6
iface enp0s31f6 inet dhcp
    
auto wlp2s0
iface wlp2s0 inet dhcp
            wpa-ssid YXZ
            wpa-psk ZXY

Tainted kernel comes from manually adding the driver

Other stuff already tried:
  • Enabling/Disabling Secure Boot
  • Manually adding IP without DHCP

I see the DHCP query going out and arriving at my OPNSense DHCP but the machine receives nothing back.
The WLAN connection works fine and is used.
 


osprey

Well-Known Member
Joined
Apr 15, 2022
Messages
1,381
Reaction score
1,396
Credits
13,314
It's worth noting that the ethernet driver, e1000e, is in the kernel, so it's best to allow the system to use that driver and so remove any other driver/module that is trying to drive the ethernet. The problem described doesn't sound like a driver problem if the kernel is saying the ethernet is Up.

To see if the ethernet interface works, you could comment out the wireless interface in /etc/network/interfaces, so as to just run the ethernet on the network. Since the kernel says the ethernet link is Up, it should be working. It is not unknown for a problem to occur when both ethernet and wireless are both trying to get up simultaneously. In any case, the idea is to see whether the ethernet can work, and presumably get an IP address from the router since it'd be the only interface requesting. It's best to try and sort one problem at a time.
 

f33dm3bits

Gold Member
Gold Supporter
Joined
Dec 11, 2019
Messages
6,639
Reaction score
5,072
Credits
48,763
But installing Bookworm leads to having an UP interface but no IP address.
My desktop system has that NIC and I also run Proxmox, which is basically Bookworm with some extra's installed.

Proxmox:
Code:
root@pve:~# uname -r
6.5.11-6-pve

Desktop:
Code:
 uname -r
6.1.66-1-lts

[root@lilith ~]# lspci |grep -i ethernet
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10)
So my desktop which has a lower version kernel then Debian it works.
Code:
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10)
        DeviceName: Onboard - Ethernet
        Subsystem: Micro-Star International Co., Ltd. [MSI] Ethernet Connection (7) I219-V
        Flags: bus master, fast devsel, latency 0, IRQ 142
        Memory at a3300000 (32-bit, non-prefetchable) [size=128K]
        Capabilities: [c8] Power Management version 3
        Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Kernel driver in use: e1000e
        Kernel modules: e1000e
Code:
[root@lilith ~]# dmesg | grep e1000e
[   19.725476] e1000e: Intel(R) PRO/1000 Network Driver
[   19.725479] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[   19.725611] e1000e 0000:00:1f.6: enabling device (0000 -> 0002)
[   19.725997] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[   19.950974] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock
[   20.036162] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 00:d8:61:9f:f1:ad
[   20.036166] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
[   20.036317] e1000e 0000:00:1f.6 eth0: MAC: 13, PHY: 12, PBA No: FFFFFF-0FF
[   20.047480] e1000e 0000:00:1f.6 eno2: renamed from eth0
[   24.079859] e1000e 0000:00:1f.6 eno2: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
As someone else in this thread suggested, unplug your system and hold the power but down for 30-60 seconds and then try again. If that doesn't work, try resetting your UEFI and if that doesn't work try updating your motherboard's UEFI to the latest version available from the manufacturer's website.
 
Last edited:
OP
rheaalleen

rheaalleen

New Member
Joined
Dec 10, 2023
Messages
3
Reaction score
0
Credits
42
It's worth noting that the ethernet driver, e1000e, is in the kernel, so it's best to allow the system to use that driver and so remove any other driver/module that is trying to drive the ethernet. The problem described doesn't sound like a driver problem if the kernel is saying the ethernet is Up.

To see if the ethernet interface works, you could comment out the wireless interface in /etc/network/interfaces, so as to just run the ethernet on the network. Since the kernel says the ethernet link is Up, it should be working. It is not unknown for a problem to occur when both ethernet and wireless are both trying to get up simultaneously. In any case, the idea is to see whether the ethernet can work, and presumably get an IP address from the router since it'd be the only interface requesting. It's best to try and sort one problem at a time.

Problem was found. The configuration for VLANs and PVID was working with Windows but not for Linux. Had to re-do the port configuration, guess next time I do some network testing I have a spare Linux machine.
 

Staff online


Top