Intel onboard NIC not functioning

kinghat · 7 June 2021 19:43

Not exactly sure when this started happening but my onboard NIC doesn’t work anymore so I’m using a USB hub/NIC combo. id like to try to get the NIC to work as my sshfs fstab mounts are failing earlier than the USB network is established.

The output to inxi -Fxxxza is:

System:    Kernel: 5.12.8-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.12-x86_64 root=UUID=9a42e25a-b919-4124-818e-156d0815793e rw quiet 
           cryptdevice=UUID=de08aa3e-5d1c-4c5d-be13-31eb3c503e56:luks-de08aa3e-5d1c-4c5d-be13-31eb3c503e56 
           root=/dev/mapper/luks-de08aa3e-5d1c-4c5d-be13-31eb3c503e56 apparmor=1 security=apparmor 
           resume=/dev/mapper/luks-7b369d27-a1ed-4e4b-9036-d8f421c7bd8a udev.log_priority=3 intel_iommu=on 
           kvm_intel.enable_apicv=0 
           Desktop: KDE Plasma 5.21.5 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM Distro: Manjaro Linux base: Arch Linux 
Machine:   Type: Desktop System: Hewlett-Packard product: HP Z440 Workstation v: N/A serial: <filter> Chassis: type: 6 
           serial: <filter> 
           Mobo: Hewlett-Packard model: 212B v: 1.01 serial: <filter> UEFI: Hewlett-Packard v: M60 v02.50 date: 11/07/2019 
CPU:       Info: Quad Core model: Intel Xeon E5-1620 v3 bits: 64 type: MT MCP arch: Haswell family: 6 model-id: 3F (63) 
           stepping: 2 microcode: 44 cache: L2: 10 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 55894 
           Speed: 1398 MHz min/max: 1200/3600 MHz Core speeds (MHz): 1: 1398 2: 1197 3: 1425 4: 1197 5: 2981 6: 1197 7: 1197 
           8: 1197 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] vendor: ASUSTeK 
           driver: amdgpu v: kernel bus-ID: 02:00.0 chip-ID: 1002:67df class-ID: 0300 
           Display: x11 server: X.Org 1.20.11 compositor: kwin_x11 driver: loaded: amdgpu,ati unloaded: modesetting 
           alternate: fbdev,vesa display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 4080x1920 s-dpi: 96 s-size: 1076x506mm (42.4x19.9") s-diag: 1189mm (46.8") 
           Monitor-1: HDMI-A-0 res: 1920x1080 hz: 60 dpi: 92 size: 531x299mm (20.9x11.8") diag: 609mm (24") 
           Monitor-2: DVI-D-0 res: 1080x1920 hz: 60 
           Monitor-3: DVI-D-1 res: 1080x1920 hz: 60 
           OpenGL: renderer: AMD Radeon RX 470 Graphics (POLARIS10 DRM 3.40.0 5.12.8-1-MANJARO LLVM 11.1.0) v: 4.6 Mesa 21.1.2 
           direct render: Yes 
Audio:     Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus-ID: 02:00.1 chip-ID: 1002:aaf0 class-ID: 0403 
           Device-2: Texas Instruments PCM2902 Audio Codec type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-6:2 
           chip-ID: 08bb:2902 class-ID: 0300 
           Sound Server-1: ALSA v: k5.12.8-1-MANJARO running: yes 
           Sound Server-2: JACK v: 0.125.0 running: no 
           Sound Server-3: PulseAudio v: 14.2 running: yes 
           Sound Server-4: PipeWire v: 0.3.28 running: yes 
Network:   Device-1: Intel Ethernet I218-LM vendor: Hewlett-Packard driver: N/A modules: e1000e port: 2040 bus-ID: 00:19.0 
           chip-ID: 8086:15a0 class-ID: 0200 
           Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 bus-ID: 3-12.4:8 chip-ID: 0bda:8153 
           class-ID: 0000 serial: <filter> 
           IF: enp0s20u12u4 state: up speed: 100 Mbps duplex: full mac: <filter> 
           IF-ID-1: br-67bd357b1b01 state: up speed: 10000 Mbps duplex: unknown mac: <filter> 
           IF-ID-2: docker0 state: down mac: <filter> 
           IF-ID-3: vethad51ccc state: up speed: 10000 Mbps duplex: full mac: <filter> 
           IF-ID-4: virbr0 state: down mac: <filter> 
Bluetooth: Device-1: Broadcom BCM20702A0 Bluetooth 4.0 type: USB driver: btusb v: 0.8 bus-ID: 3-12.1:5 chip-ID: 0a5c:21e8 
           class-ID: fe01 serial: <filter> 
           Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends 
Drives:    Local Storage: total: 1.51 TiB used: 146.52 GiB (9.5%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:2 model: PCIe SSD size: 476.94 GiB block-size: physical: 512 B logical: 512 B 
           speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: ECFM13.3 scheme: GPT 
           ID-2: /dev/nvme1n1 maj-min: 259:1 vendor: SK Hynix model: BC501 HFM128GDJTNG-8310A size: 119.24 GiB block-size: 
           physical: 512 B logical: 512 B speed: 15.8 Gb/s lanes: 2 rotation: SSD serial: <filter> rev: 80002C00 
           ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Sabrent model: N/A size: 953.87 GiB block-size: physical: 512 B 
           logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: RKT303.3 scheme: GPT 
Partition: ID-1: / raw-size: 884.56 GiB size: 869.6 GiB (98.31%) used: 146.52 GiB (16.8%) fs: ext4 dev: /dev/dm-0 
           maj-min: 254:0 mapped: luks-de08aa3e-5d1c-4c5d-be13-31eb3c503e56 
           ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 448 KiB (0.1%) fs: vfat dev: /dev/nvme2n1p1 
           maj-min: 259:7 
Swap:      Kernel: swappiness: 60 (default) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 69 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/dm-1 maj-min: 254:1 
           mapped: luks-7b369d27-a1ed-4e4b-9036-d8f421c7bd8a 
Sensors:   System Temperatures: cpu: 49.0 C mobo: N/A gpu: amdgpu temp: 49.0 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 1277 
Info:      Processes: 419 Uptime: 32m wakeups: 0 Memory: 62.73 GiB used: 6.8 GiB (10.8%) Init: systemd v: 247 tool: systemctl 
           Compilers: gcc: 11.1.0 Packages: 1378 pacman: 1343 lib: 340 flatpak: 27 snap: 8 Shell: Bash v: 5.1.8 
           running-in: yakuake inxi: 3.3.04

When I do a:

sudo modprobe -r e1000e
echo 1 | sudo tee "/sys/bus/pci/devices/0000:00:19.0/reset"
1
sudo modprobe e1000e
sudo dmesg | grep e1000e

I get:

[   10.711960] e1000e: Intel(R) PRO/1000 Network Driver
[   10.711964] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[   10.712015] e1000e 0000:00:19.0: enabling device (0140 -> 0142)
[   10.712206] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[   11.484698] e1000e: probe of 0000:00:19.0 failed with error -2
[ 1026.555839] e1000e: Intel(R) PRO/1000 Network Driver
[ 1026.555841] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 1026.556060] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 1027.402024] e1000e: probe of 0000:00:19.0 failed with error -2
[ 1138.313998] e1000e: Intel(R) PRO/1000 Network Driver
[ 1138.314001] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 1138.314196] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 1139.070385] e1000e: probe of 0000:00:19.0 failed with error -2

The output to echo 'file drivers/net/ethernet/intel/e1000e/* +p' | sudo tee /sys/kernel/debug is:

/dynamic_debug/control
file drivers/net/ethernet/intel/e1000e/* +p
$ echo '0000:00:19.0' | sudo tee /sys/bus/pci/drivers/e1000e/unbind
0000:00:19.0
tee: /sys/bus/pci/drivers/e1000e/unbind: No such device
$ echo '0000:00:19.0' | sudo tee /sys/bus/pci/drivers/e1000e/bind
0000:00:19.0
tee: /sys/bus/pci/drivers/e1000e/bind: No such device

The output to sudo dmesg | grep e1000e is:

[   10.711960] e1000e: Intel(R) PRO/1000 Network Driver
[   10.711964] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[   10.712015] e1000e 0000:00:19.0: enabling device (0140 -> 0142)
[   10.712206] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[   11.484698] e1000e: probe of 0000:00:19.0 failed with error -2
[ 1026.555839] e1000e: Intel(R) PRO/1000 Network Driver
[ 1026.555841] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 1026.556060] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 1027.402024] e1000e: probe of 0000:00:19.0 failed with error -2
[ 1138.313998] e1000e: Intel(R) PRO/1000 Network Driver
[ 1138.314001] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 1138.314196] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 1139.070385] e1000e: probe of 0000:00:19.0 failed with error -2
[ 1485.037028] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 1485.037099] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): reading PHY page 0 (or 0x0 shifted) reg 0x2
[ 1485.134669] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): MDI Read did not complete
[ 1485.134673] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): reading PHY page 0 (or 0x0 shifted) reg 0x2
[ 1485.232142] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): MDI Read did not complete
[ 1485.287164] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): reading PHY page 0 (or 0x0 shifted) reg 0x2
[ 1485.384651] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): MDI Read did not complete
[ 1485.384656] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): reading PHY page 0 (or 0x0 shifted) reg 0x2
[ 1485.482122] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): MDI Read did not complete
[ 1485.573864] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): reading PHY page 0 (or 0x0 shifted) reg 0x2
[ 1485.671387] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): MDI Read did not complete
[ 1485.671392] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): reading PHY page 0 (or 0x0 shifted) reg 0x2
[ 1485.768824] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): MDI Read did not complete
[ 1485.768829] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): reading PHY page 0 (or 0x0 shifted) reg 0x2
[ 1485.769288] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): MDI Error
[ 1485.769289] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): reading PHY page 0 (or 0x0 shifted) reg 0x2
[ 1485.866720] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): MDI Read did not complete
[ 1485.877333] e1000e: probe of 0000:00:19.0 failed with error -2

I have tried kernels 5.10 and 5.12 and the problem remains.

How should I proceed?

Fabby · 8 June 2021 07:36

In the future, when providing code/output, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text so that the output looks like this:
```
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
```
instead of like this:

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.`

(as that makes both our lives much easier)
No need to do anything right now as I’m an editor here on this site and have fixed it for you already. However, in the future I might not see your post so review my edits by pushing the orange pencil above the post I just fixed.
Please install a spell checker in your browser.
Have you tried kernel 54-RT already?

stephane · 8 June 2021 11:44

4 - add these kernels linux54 and linux 510 lts , check result after boot

Fabby · 8 June 2021 14:26

OP tried 5.10 LTS already, so that’s why I asked for 5.4 RT as the Real-Time kernels get updated more slowly…

kinghat · 8 June 2021 14:53

i will try 5.4 RT but ive never used that and all kernels worked fine until the last month. even 5.9 and 5.10

sorry about the formatting. firefox has builtin spell checking. didnt think it was that bad

kinghat · 8 June 2021 16:57

@stephane @Fabby no connection can be made on 5.4RT either.

Fabby · 8 June 2021 16:59

Looks like a dead card. Do you have a dual-boot and can you check under another OS?

kinghat · 8 June 2021 17:01

i have win10 on an nvme drive in this system that i passthrough to a vm. also live usb i guess.

Fabby · 8 June 2021 17:03

That will have the same issue.

As you don’t know how long ago this was, not certain this will work with Manjaro.
Try an old distro like Lubuntu and don’t update anything and see it it works there.

kinghat · 8 June 2021 17:07

it doesnt get claimed by the system at boot so afaict i can just select that win 10 drive in boot menu, though ive never tried it

its a kde neon live usb.

Fabby · 8 June 2021 17:10

As long as it’s older than when the problem started, it’s fine…

kinghat · 8 June 2021 17:43

must be borked. couldnt get it working under neon or win10

Fabby · 9 June 2021 08:48

I’ve marked this answer as the solution to your question as it is by far the best answer you’ll get.

However, if you disagree with my choice, please feel free to take any other answer as the solution to your question or even remove the solution altogether: You are in control! (If you disagree with my choice, just send me a personal message and explain why I shouldn’t have done this or or if you agree)

P.S. In the future, please don’t forget to come back and click the 3 dots below the answer to mark a solution like this below the answer that helped you most:

so that the next person that has the exact same problem you just had will benefit from your post as well as your question will now be in the “solved” status.

system · 24 June 2021 08:49

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.