Search results for query: r8169

...There is an r8125 DKMS package designed for Arch as well (https://aur.archlinux.org/packages/r8125-dkms) but even with it installed, the r8169 kernel module kept overriding it. And so the solution in Arch was to black list the r8169. For example (again this is in Arch, I don't know if in a...

...port 1(enp5s0) entered blocking state Jan 24 18:43:06 pve kernel: vmbr0: port 1(enp5s0) entered disabled state Jan 24 18:43:06 pve kernel: r8169 0000:05:00.0 enp5s0: entered allmulticast mode Jan 24 18:43:06 pve kernel: r8169 0000:05:00.0 enp5s0: entered promiscuous mode Jan 24 18:43:06 pve...

...and solve this as well as possibly explain a bit more behind it that would be amazing! Many thanks, Dom :) Jan 17 11:28:23 DSH-SRV-01 kernel: r8169 0000:06:00.0 enp6s0: NETDEV WATCHDOG: CPU: 6: transmit queue 0 timed out 9920 ms Jan 17 11:28:23 DSH-SRV-01 kernel: r8169 0000:06:00.0 enp6s0...

...install dkms 7) apt install proxmox-headers-6.8.12-6-pve 8) sudo dpkg -i realtek-r8126-dkms_10.014.01-1_amd64.deb 9) echo "blacklist r8169" | sudo tee /etc/modprobe.d/blacklist-r8169.conf 10) sudo update-initramfs-u 11) type "dkms status" for check if the driver 8126 has been installed...

...port 1(enp5s0) entered blocking state Jan 14 09:33:23 pve kernel: vmbr100: port 1(enp5s0) entered disabled state Jan 14 09:33:23 pve kernel: r8169 0000:05:00.0 enp5s0: entered allmulticast mode Jan 14 09:33:23 pve kernel: r8169 0000:05:00.0 enp5s0: entered promiscuous mode Jan 14 09:33:23 pve...

...and `ifdown/up vmbr0` to no avail, the IPv4 address never came back. Only a reboot helped. At this point I'm suspecting some issue with the r8169 Realtek kernel driver. I also tried `modprobe -r r8169` and `modprobe r8169` to try and unload and reload the driver, but that didn't fix it...

...usbhid hid dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c nvme xhci_pci spi_intel_pci xhci_pci_renesas nvme_core crc32_pclmul r8169 spi_intel ahci realtek i2c_i801 xhci_hcd nvme_auth i2c_smbus libahci video wmi [ 123.842136] CPU: 4 PID: 173 Comm: kworker/4:2 Tainted: P...

...(first instance was on PNP0C14:00) [ 1.141025] wmi_bus wmi_bus-PNP0C14:02: WQZZ data block query control method not found [ 1.174320] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control [ 1.493834] ata2.00: supports DRM functions and may not be fully accessible [...

...ps02 kernel: mfd_aaeon asus_wmi xhci_pci ledtrig_audio xhci_pci_renesas sparse_keymap platform_profile igb nvme sfc ahci crc32_pclmul xhci_hcd r8169 i2c_piix4 i2c_algo_bit libahci nvme_core mtd realtek video dca mdio nvme_auth wmi gpio_amdpt Jan 07 14:07:36 ps02 kernel: CPU: 9 PID: 513 Comm...

...zfs(PO) spl(0) btrfs blake2b_ generic xor raid ledtrig_audio 12c_1801 xhci_pci renesas sparse_keymap crc32_pcimul platform profile xhci_hcd r8169 i2c_smbus ehci_pci 1378793. 8264681 CR2: 0000000000000447 (378793.8264781 --- [ end trace 0000000000000000 ]--- (378795. 496753] RIP...

...root@pve:~# uname -a Linux pve 5.4.203-1-pve #1 SMP PVE 5.4.203-1 (Fri, 26 Aug 2022 14:43:35 +0200) x86_64 GNU/Linux root@pve:~# lsmod | grep r8169 r8169 90112 0 root@pve:~# lspci -k 0f:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8125 (rev 05)...

I cannot find the network interface name for a Realtek RTL8111/8168/8411 PCI card. The problem appear after rebooting updating proxmox to kernel 6.8.12-5. Card is reported OK with lspci -vnn: However, there is no ethernet interface available and the output of "ip a" just reports the...

...Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) root@beelink:~# ethtool -i enp1s0 driver: r8169 version: 6.8.12-5-pve firmware-version: rtl8168h-2_0.0.2 02/26/15 expansion-rom-version: bus-info: 0000:01:00.0 supports-statistics: yes...

...mfd_aaeon asus_wmi ledtrig_audio sparse_keymap xhci_pci nvme platform_profile xhci_pci_renesas crc32_pclmul sfc ahci nvme_core xhci_hcd igb r8169 i2c_piix4 libahci nvme_auth mtd i2c_algo_bit realtek video mdio dca wmi gpio_amdpt Dec 25 06:19:28 ps02 kernel: CPU: 4 PID: 1481 Comm: ovs-vswitchd...

...Driver [ 1.078997] igc 0000:02:00.0 eth0: MAC: 84:47:09:12:fe:16 [ 1.365857] igc 0000:02:00.0 enp2s0: renamed from eth0 [ 1.365919] r8169 0000:01:00.0 eth1: RTL8168h/8111h, 84:47:09:12:fe:15, XID 541, IRQ 142 [ 1.365924] r8169 0000:01:00.0 eth1: jumbo features [frames: 9194 bytes...

enp: [ 1.365857] igc 0000:02:00.0 enp2s0: renamed from eth0 [ 1.420681] r8169 0000:01:00.0 enp1s0: renamed from eth1 [ 4.611207] vmbr0: port 1(enp1s0) entered blocking state [ 4.611211] vmbr0: port 1(enp1s0) entered disabled state [ 4.611221] r8169 0000:01:00.0 enp1s0: entered...

...Driver [ 1.078997] igc 0000:02:00.0 eth0: MAC: 84:47:09:12:fe:16 [ 1.365857] igc 0000:02:00.0 enp2s0: renamed from eth0 [ 1.365919] r8169 0000:01:00.0 eth1: RTL8168h/8111h, 84:47:09:12:fe:15, XID 541, IRQ 142 [ 1.365924] r8169 0000:01:00.0 eth1: jumbo features [frames: 9194 bytes...

For me, it has been working since I adopted names which the systems wouldn't use (like lan0 and lan1).

...renamed from eth0 to enp2s0 and that's how systemd status networking and /etc/network/interfaces show it. However after a subsequent reboot, it is renamed from eth0 to enp3s0 and netowrking doesn't work anynmore. r8169 0000:03:00.0 enp3s0: renamed from eth0 Is there a way to avoid this...

...has newer hardware and uses RTL8226B_RTL8221B and igb network adapter drivers. All links are up: dmesg | grep -E "(igb|8169)" [ 0.920483] r8169 0000:0c:00.0 eth0: RTL8125B, d8:43:ae:b8:21:88, XID 641, IRQ 48 [ 0.920487] r8169 0000:0c:00.0 eth0: jumbo features [frames: 9194 bytes, tx...