Expected result: Using onboard LAN, not using USB-tethering from phone.
Actual result:Days of trying to figure out why the onboard lan broke and why it won't load/bind the driver from the kernel module.
The affected hardware:
Gigabyte GA-Z87-UD3H - Onboard LAN - Intel Corporation Ethernet Connection I217-V (rev 05)
Have tried:I have tried this on three boots: the original kubuntu 18.04, a fresh install of pop_os 19.10, and a fresh 20.04 beta ubuntu-studio. Across these boots I've tried making this work with a plethora of kernels: 4.15.0-96-lowlatency (came with 18.04 ubuntu-studio)5.3.0-26/43/45/46-generic (original kubuntu, pop_os)5.4.0-21/23-lowlatency (ubuntu-studio 20.04).
It used to work on the kubuntu install for months. It has worked on the same device in win 8.1, win 10, macos maverick/sierra/high sierra as well as ubuntu 16.04, 18.04. The Pop_OS gui was annoying so got rid of that install and am currently trying to make the 20.04beta work with the 5.4 lowlatency kernel seeing as this machine is supposed to be an editing
sudo lshw -c network[sudo] password for ada: *-network UNCLAIMED description: Ethernet controller product: Ethernet Connection I217-V vendor: Intel Corporation physical id: 19 bus info: pci@0000:00:19.0 version: 05 width: 32 bits clock: 33MHz capabilities: pm msi cap_list configuration: latency=0 resources: memory:f7900000-f791ffff memory:f793d000-f793dfff ioport:f080(size=32) *-network description: Ethernet interface physical id: 2 bus info: usb@3:9.4 logical name: usb0 serial: d2:8b:c7:81:86:00 capabilities: ethernet physical configuration: broadcast=yes driver=rndis_host driverversion=22-Aug-2005 firmware=RNDIS device ip=192.168.42.172 link=yes multicast=yes
The top one being the
sudo lspci -nnk gives me
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I217-V [8086:153b] (rev 05) DeviceName: Onboard LAN Subsystem: Gigabyte Technology Co., Ltd Ethernet Connection I217-V [1458:e000] Kernel modules: e1000e
Notice the lack of the line "Kernel driver in use:" that I get on all devices/modules that do work.
After having tried modprobe e1000e modprobe -a e1000e
I figured it might have been a problem with the ubuntu premade kernel modules, so I went to Intel and got the latest version of the driver and compiled from source.(for the 5.4 module I followed steps from https://github.com/koljah-de/e1000e-dkms-debian to change a line in /usr/src/e1000e-3.6.0/src/kcompat.h:
line:command2799:#include <linux/pci-aspm.h>
to
line:command2799:#include <linux/pci.h>
which worked fine)
I tried to simply make make install
and reboot the system, nothing. I tried the deb install method from the previously mentioned git. I tried
dkms add -m e1000e -v 3.6.0dkms build -m e1000e -v 3.6.0dkms -m e1000e -v 3.6.0
Now, three days later I'm considering just buying a pci/usb ethernet interface and give up on this but since it has worked for 6 years for more or less daily use I find it a bit annoying that it should just stop working from what seems like a driver issue.
So I # apt install dpdk
and
sudo dpdk-devbind.py -b e1000e 0000:00:19.0[sudo] password for ada: Error: bind failed for 0000:00:19.0 - Cannot bind to driver e1000e
from journalctl I have these two relevant lines:
apr 10 19:55:43 ada-Z87X-UD3H kernel: e1000e: probe of 0000:00:19.0 failed with error -2apr 10 19:55:42 ada-Z87X-UD3H kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
And from dmesg these ones:
[ 2173.754182] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k[ 2173.754183] igb: Copyright (c) 2007-2014 Intel Corporation.[ 5735.904821] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode[ 5736.742509] e1000e: probe of 0000:00:19.0 failed with error -2[ 5736.742623] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode[ 5737.579534] e1000e: probe of 0000:00:19.0 failed with error -2
Judging from this dmesg the interface is loading the igb kernel module instead which has not showed up anywhere else, but this might be the cause of the problem. However, rmmod/modprobe -r hasnt managed to detach it as it's not technically loaded... I have also been unsuccessful in reproducing this dmesg. I'm stumped.
I'm gonna do a manjaro install and see if the problem is specific to debian/ubuntu. funfun...