Search results for query: r8169

Thanks mate you solved my issue. This line was not needed for me: sudo update-initramfs-u As you mentioned I had to use: apt install proxmox-headers-6.8.12-8-pve

...dm_bio_prison Feb 26 11:39:49 pve-corp-010-dc kernel: dm_bufio libcrc32c hid_generic usbkbd usbhid hid crc32_pclmul xhci_pci r8169 xhci_pci_renesas realtek xhci_hcd i2c_piix4 ahci libahci video wmi gpio_amdpt Feb 26 11:39:49 pve-corp-010-dc kernel: CR2: 0000000000000620 Feb 26 11:39:49...

...[0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) Subsystem: Dell RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [1028:080c] Kernel driver in use: r8169 Kernel modules: r8169 6)...

...Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06) Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000] Kernel driver in use: r8169 Kernel modules: r8169 please...

Solution - Looked into the journalctl and there it says, `could not find module by name = r8168`. But I remember I am using r8169 and went back to the /etc/modprobe.d and removed r8168.conf file from that location. And voila, it worked.

I found the solution: It was the fault of all Kernel-Version > 5.15 Because the ASPM-friendly driver R8168 wasn't used anymore, instead driver R8169, which isn't suiteable for the Realtek chipset 8111. So parts of the system had ASPM disabled and powertop didn't reach lower states than C3.

...-i realtek-r8125-dkms_9.014.01-1_amd64.deb (or latest available from here - Realtek r8125 DKMS) Blacklist the old driver - echo "blacklist r8169" > /etc/modprobe.d/blacklist-r8169.conf sudo update-initramfs -u reboot install lshw if not already there apt install lshw check driver with lshw...

...Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] Kernel driver in use: r8125 Kernel modules: r8169, r8125 This is the output of the ethool comand on the card: root@bigboi:~# ethtool enp6s0 Settings for enp6s0: Supported ports: [ TP...

...motherboard with a on-board 2.5G r8125, and it wasn't shown on the setting, I only saw it from lspci command. And after typing: lsmod | grep r8169 I got the output with 0 at the end as well, which indicated that the r8169 driver is loaded but not in use. And after several try, I've managed...

The cable is new, got it from IT yesterday. I'll try to talk to them to see if I can get a network with unrestricted access. I tried a PCIe NIC but got the same result. Maybe because it was using R8169? Unsure. I'll get back to you about it.

...usbhid hid nvme ahci nvme_core libahci nvme_auth mfd_aaeon asus_wmi xhci_pci ledtrig_audio xhci_pci_renesas sparse_keymap platform_profile r8169 crc32_pclmul xhci_hcd i2c_i801 spi_intel_pci intel_lpss_pci realtek i2c_smbus spi_intel intel_lpss vmd idma64 video wmi pinctrl_alderlake Jan 28...

I tried this method when I first meet this problem, but it didn't work. We can confirm that the network card is working under the r8125 driver using lspci -a.

...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 [...