Intel NIC vanished after reboot? Intel i211

kombat · 10 June 2022 17:25

Last night I was working on the PC just fine, rebooted from Plasma to my windows drive. When I came back, the Intel i211 NIC vanished and only my 2.5Gbit interface is showing. Both of these are on the board (X570-E).

There were no updates between reboot last night, no updates available. Windows works fine with both NIC, so it’s not a bad interface.

Looking for help in figuring out how to get it back, ideally without a format, even though it’s fairly painless, I want to find the cause vs nuclear.

Cheers

Edit: They all seem to come up. Realtek works fine, wifi works fine as well

lspci | egrep -i --color 'network|ethernet|wireless|wi-fi'
06:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller
08:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)

inxi --admin --verbosity=7 --filter --no-host --width                                       22 ✘ 
System:
  Kernel: 5.17.9-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.17-x86_64
    root=UUID=d388f54a-3c20-437f-aa23-84796a407aab rw quiet apparmor=1
    security=apparmor udev.log_priority=3
  Desktop: KDE Plasma v: 5.24.5 tk: Qt v: 5.15.4 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-E GAMING v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 4021
    date: 08/09/2021
Battery:
  Message: No system battery data found. Is one present?
Memory:
  RAM: total: 31.32 GiB used: 2.63 GiB (8.4%)
  RAM Report:
    permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3
    family: 0x19 (25) model-id: 0x21 (33) stepping: 0 microcode: 0xA201016
  Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
    L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB
    L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 2900 high: 3594 min/max: 2200/4950 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 3591 2: 3594
    3: 2873 4: 2871 5: 2876 6: 2875 7: 2871 8: 2870 9: 2484 10: 2233 11: 2789
    12: 2229 13: 3588 14: 3591 15: 2874 16: 2874 17: 2868 18: 3590 19: 2235
    20: 2231 21: 2558 22: 2580 23: 3592 24: 2866 bogomips: 177326
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists erms extapic
    extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt ht
    hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
    misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
    nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
    pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni popcnt
    pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sha_ni
    skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor
    svm svm_lock syscall tce topoext tsc tsc_scale umip v_spec_ctrl
    v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall vpclmulqdq wbnoinvd wdt
    xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: always-on, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
    driver: amdgpu v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: DP-1,DP-2,DP-3 empty: HDMI-A-1 bus-ID: 0e:00.0 chip-ID: 1002:731f
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.1
    compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
    alternate: fbdev,vesa gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 4481x2520 s-dpi: 96 s-size: 1185x666mm (46.65x26.22")
    s-diag: 1359mm (53.52")
  Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,top-left
    model: Dell S2721DGF serial: <filter> built: 2021 res: 2560x1440 dpi: 109
    gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9
    modes: max: 2560x1440 min: 720x400
  Monitor-2: DP-2 mapped: DisplayPort-1 pos: middle-c
    model: LG (GoldStar) ULTRAWIDE serial: <filter> built: 2016 res: 2560x1080
    dpi: 81 gamma: 1.2 size: 798x334mm (31.42x13.15") diag: 869mm (34.2")
    modes: max: 2560x1080 min: 720x400
  Monitor-3: DP-3 mapped: DisplayPort-2 pos: bottom-r model: Dell U2311H
    serial: <filter> built: 2010 res: 1920x1080 hz: 60 dpi: 96 gamma: 1.2
    size: 509x286mm (20.04x11.26") diag: 584mm (23") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  OpenGL:
    renderer: AMD Radeon RX 5700 (navi10 LLVM 13.0.1 DRM 3.44 5.17.9-1-MANJARO)
    v: 4.6 Mesa 22.0.4 direct render: Yes
Audio:
  Device-1: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0e:00.1 chip-ID: 1002:ab38
    class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 11:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Logitech USB Headset type: USB driver: snd-usb-audio
    bus-ID: 3-1:2 chip-ID: 046d:0a01 class-ID: 0102
  Sound Server-1: ALSA v: k5.17.9-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.51 running: yes
**Network:**
**  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2**
**    speed: 5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 8086:2723 class-ID: 0280**
**  IF: wlp6s0 state: up mac: <filter>**
**  IP v4: <filter> type: dynamic noprefixroute scope: global**
**    broadcast: <filter>**
**  IP v6: <filter> type: noprefixroute scope: link**
**  Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel**
**    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 07:00.0**
**    chip-ID: 10ec:8125 class-ID: 0200**
**  IF: enp7s0 state: up speed: 2500 Mbps duplex: full mac: <filter>**
**  Device-3: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel**
**    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 08:00.0**
**    chip-ID: 8086:1539 class-ID: 0200**
**  IF: enp8s0 state: up speed: 1000 Mbps duplex: full mac: <filter>**
**  IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>**
**  IP v6: <filter> type: noprefixroute scope: link**
**  WAN IP: <filter>**
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-6:7
    chip-ID: 8087:0029 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 2 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 4.38 TiB used: 1.9 TiB (43.4%)

Swap:
  Alert: No swap data was found.

USB:

Sensors:
  System Temperatures: cpu: 30.0 C mobo: 36.0 C gpu: amdgpu temp: 32.0 C
    mem: 36.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 65535
Info:
  Processes: 481 Uptime: 1m wakeups: 0 Init: systemd v: 250 tool: systemctl
  Compilers: gcc: 12.1.0 clang: 13.0.1 Packages: 1431 pacman: 1428 lib: 431
  flatpak: 3 Shell: Zsh v: 5.9 default: Bash v: 5.1.16 running-in: konsole
  inxi: 3.3.16

As you can see, enp8s0 state: up, but it’s not coming up in the GUI and I can’t seem to change it’s settings / access it.

Olli · 10 June 2022 17:42

Please read this:
[HowTo] Provide System Information
and press the three dots … below your post and press the to give us more information so we can see what’s really going on.
Now we know the symptom of the disease, but we need some more probing to know where the origin lies…
An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information for us to be able to help you. (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.

Hanzel · 10 June 2022 17:49

This might be the problem that windows has initialized the card and does not release it and because of this rebooting to linux will block the kernel from initializing it for the OS, resulting in no or weird hardware issues. A option to try (if you have not already) is disable fast startup option in Windows:

If this does not solve the issue, please read the link posted by @Olli on how to provide more info.

kombat · 10 June 2022 23:12

Updated the OP with more details like requested. Funny thing is, the interface enp8s0 it showing that it’s up, but it’s not accessible. Not in the GUI at least. But I can’t think of anything that I could have done to fix it.

@Hanzel I tried that, but didn’t have any luck.

Thanks!

kombat · 13 June 2022 16:08

Bump… Hoping somebody has a solution. Willing to provide whatever other info.

I just dont want to format as it’ll erase the issue vs figuring out what happened.

Cheers

Hanzel · 13 June 2022 17:34

I have not solutions to offer, the driver seems to load correctly and from what you have shown so far it should function. Providing more info would be helpfull.

I’m probably not able to help but other might be able to.

Start with the journal, check if journal reports info on it

journalctl --boot --priority=3 --catalog will print all messages that are errors or worse from the current booted session. Change the priority to lower to see more messages, eg warnings, events etc. You can use grep to filter the output eg. journalctl --boot | grep igb should report lines with igb (the driver for this card)

Another way is to pipe the output to a file journalctl --boot > error.txt and use a text editor to look for lines with the nic name, driver name etc and see if any of those lines in the log give you clues what could be going on. If unsure what it means, a quick search would probably give some insight into what is happening. Posting it here would give others a change so help solve the issue and /or explain.

Does the interface work when booting a 5.10 or 5.15 kernel?