Is Manjaro able to support Intel Gigabit killer E2500v2?

Hi there,

for now, Manjaro manage my Ethernet with r8169 driver. My concern, is when my laptop goes in hibernation, the network card never went back: I’ve to restart the PC.
Here is the link with specifications for DELL G7 7700 (rtx2060 version, so network card isn’t RTL8111H) : https://www.dell.com/support/manuals/fr-fr/g-series-17-7700-laptop/dell-g7-17-7700-setup-and-specifications/communications?guid=guid-00670079-10ab-40ff-a2a8-fb1af87bcf86

Thanks for any help

Technical details from Manjaro

lspci -k -nn | grep -A 3 -i net                                                                ✔ 
00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH CNVi WiFi [8086:06f0]
        Subsystem: Rivet Networks Device [1a56:1652]
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi
00:15.0 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH Serial IO I2C Controller #0 [8086:06e8]
--
3c:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. Device [10ec:2502] (rev 1f)
        Subsystem: Dell Device [1028:09f9]
        Kernel driver in use: r8169
        Kernel modules: r8169

then

inxi -Faz                                                                                      ✔ 
System:
  Kernel: 6.1.12-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=UUID=dca8cecc-c26f-4f8b-b39c-1a12c8ae0445 rw quiet apparmor=1
    security=apparmor resume=UUID=d97779d9-142d-430d-b9c0-e61a86feea80
    udev.log_priority=3
  Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: Dell product: G7 7700 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Dell model: 0M7GYR v: A00 serial: <superuser required> UEFI: Dell
    v: 1.21.0 date: 12/16/2022
Battery:
  ID-1: BAT0 charge: 72.2 Wh (100.0%) condition: 72.2/97.0 Wh (74.4%)
    volts: 12.0 min: 11.4 model: BYD DELL XYCW008 type: Li-poly serial: <filter>
    status: full
  Device-1: hidpp_battery_0 model: Logitech Wireless Mobile Mouse MX
    Anywhere 2S serial: <filter> charge: 100% (should be ignored)
    rechargeable: yes status: discharging
CPU:
  Info: model: Intel Core i7-10750H bits: 64 type: MT MCP arch: Comet Lake
    gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6
    model-id: 0xA5 (165) stepping: 2 microcode: 0xF4
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 1891 high: 2600 min/max: 800/5000 scaling:
    driver: intel_pstate governor: powersave cores: 1: 2600 2: 900 3: 2600
    4: 2600 5: 2600 6: 900 7: 2600 8: 900 9: 2600 10: 900 11: 900 12: 2600
    bogomips: 62431
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: Enhanced IBRS
  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: Enhanced IBRS, IBPB: conditional, RSB
    filling, PBRSB-eIBRS: SW sequence
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: Dell driver: i915
    v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
    active: eDP-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:9bc4
    class-ID: 0300
  Device-2: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Dell
    driver: nvidia v: 525.89.02 alternate: nouveau,nvidia_drm non-free: 525.xx+
    status: current (as of 2023-02) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 8
    link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:1f15 class-ID: 0300
  Device-3: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo
    bus-ID: 1-5:4 chip-ID: 0bda:565a class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8
    compositor: kwin_x11 driver: X: loaded: modesetting,nvidia unloaded: nouveau
    alternate: fbdev,nv,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 4480x1080 s-dpi: 96 s-size: 1182x285mm (46.54x11.22")
    s-diag: 1216mm (47.87")
  Monitor-1: HDMI-1-0 pos: left res: 2560x1080 dpi: 81
    size: 798x334mm (31.42x13.15") diag: 865mm (34.06") modes: N/A
  Monitor-2: eDP-1 pos: primary,right res: 1920x1080 hz: 144 dpi: 128
    size: 382x215mm (15.04x8.46") diag: 438mm (17.26") modes: N/A
  API: OpenGL v: 4.6 Mesa 22.3.5 renderer: Mesa Intel UHD Graphics (CML GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Comet Lake PCH cAVS vendor: Dell
    driver: sof-audio-pci-intel-cnl
    alternate: snd_hda_intel,snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
    chip-ID: 8086:06c8 class-ID: 0401
  Device-2: NVIDIA TU106 High Definition Audio vendor: Dell
    driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 8
    link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:10f9 class-ID: 0403
  Sound API: ALSA v: k6.1.12-1-MANJARO running: yes
  Sound Interface: sndio v: N/A running: no
  Sound Server-1: JACK v: 1.9.22 running: no
  Sound Server-2: PulseAudio v: 16.1 running: yes
  Sound Server-3: PipeWire v: 0.3.65 running: yes
Network:
  Device-1: Intel Comet Lake PCH CNVi WiFi vendor: Rivet Networks
    driver: iwlwifi v: kernel bus-ID: 00:14.3 chip-ID: 8086:06f0 class-ID: 0280
  IF: wlp0s20f3 state: up mac: <filter>
  Device-2: Realtek vendor: Dell driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 3c:00.0 chip-ID: 10ec:2502
    class-ID: 0200
  IF: enp60s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-14:8 chip-ID: 8087:0026 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
Drives:
  Local Storage: total: 1.38 TiB used: 480.93 GiB (34.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
    model: WDBRPG0010BNC-WRSN size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 102000WD temp: 44.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Toshiba model: KBG40ZNS512G
    NVMe KIOXIA 512GB size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 10410106 temp: 34.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 914.28 GiB size: 898.86 GiB (98.31%)
    used: 479.01 GiB (53.3%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 28.3 MiB (9.5%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 16.93 GiB used: 1.89 GiB (11.2%)
    priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  System Temperatures: cpu: 51.0 C pch: 46.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 327 Uptime: 34m wakeups: 4 Memory: 15.39 GiB
  used: 5.6 GiB (36.4%) Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: 1912
  pm: pacman pkgs: 1881 libs: 494 tools: pamac,yay pm: flatpak pkgs: 16
  pm: snap pkgs: 15 Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.25

Hi @Golfy,

  • Have you tried with an earlier kernel?
  • Do you know if it does the same in a live environment?

This NIC can be a hit or miss - it may even change from kernel to kernel - at some point it did for my Clevo N141WU - for my hardware the kernel driver works best - but back-in-time the r8168 module was necessary to have functional NIC.

There is a package extra/linux61-r8168 which you may try instead of the kernel driver r8169.

2 Likes

As I’m new on linux (I’ve left Microsoft one year ago), I don’t know how to use this package (I’ve installed it with PAMAC but it seems I’m using each driver).

lspci -k -nn | grep -A 3 -i net                                                                                    ✔ 
00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH CNVi WiFi [8086:06f0]
        Subsystem: Rivet Networks Device [1a56:1652]
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi
00:15.0 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH Serial IO I2C Controller #0 [8086:06e8]
--
3c:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. Device [10ec:2502] (rev 1f)
        Subsystem: Dell Device [1028:09f9]
        Kernel driver in use: r8169
        Kernel modules: r8169, r8168

I’ve tried this command without success (network card disappear) :

sudo modprobe -r r8169 && sleep 3 && sudo modprobe r8168 && systemctl restart NetworkManager

Here is the result of previous command, with r8168 driver:

spci -k -nn | grep -A 3 -i net                                                                            ✔  15s  
00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH CNVi WiFi [8086:06f0]
        Subsystem: Rivet Networks Device [1a56:1652]
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi
00:15.0 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH Serial IO I2C Controller #0 [8086:06e8]
--
3c:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. Device [10ec:2502] (rev 1f)
        Subsystem: Dell Device [1028:09f9]
        Kernel modules: r8169, r8168

If you mean the r8168 driver, then you have to blacklist the r6189 driver and then it should be used automagically:

echo "blacklist r8169" | sudo tee /etc/modprobe.d/r8169.conf

And reboot to see if it worked.

Note:

If it didn’t, just remove the file to reset everything to its current state:

sudo rm /etc/modprobe.d/r8169.conf
1 Like

As I recall the package automagically blacklist r8169

Just checked - it doesn’t - the install informs what to do

post_install() {
    rebuild_module_dependencies
    echo '>>> The module r8168 conflicts with r8169. You can blacklist it with:'
    echo '>>>  `echo "blacklist r8169" > /etc/modprobe.d/r8169_blacklist.conf`'
}

So @Mirdarthos is correct - after install you need to blacklist the kernel driver and restart your system

echo "blacklist r8169" | sudo tee /etc/modprobe.d/r8169_blacklist.conf

If it doesn’t help you will have to redo - that is

sudo rm -f /etc/modprobe.d/r8169_blacklist.conf
sudo pacman -Rns linux61-r8168
reboot
2 Likes

The r8169 driver is automagically blacklisted if r8168 driver is installed via Manjaro Settings Manager GUI or

sudo mhwd -i pci network-r8168
1 Like

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