Search results for query: r8169

Nov 14 17:31:59 pve kernel: Generic FE-GE Realtek PHY r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC) Nov 14 17:31:59 pve kernel: r8169 0000:02:00.0 enp2s0: Link is Down Nov 14 17:31:59 pve kernel: vmbr0: port 1(enp2s0) entered blocking state Nov 14 17:31:59 pve...

I was able to get it installed by following the install guide. I did loose the network setting on reboot though. I then set them manually and everything seems to be working. I probably didn't have something setup correctly the first time with my /etc/network/interfaces file. Here is how I set it...

...05) DeviceName: OnBoard LAN Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] Kernel driver in use: r8169 Kernel modules: r8169 03:00.0 Network controller [0280]: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter [14c3:0616]...

Hello, I booted my server without any machines up and it ended up freezing again. After the last freeze I managed to get maybe the error from journalctl -b -1 -o short-precise: The logs state a "general protection fault, probably for non-canonical address 0xff838e34192dff80", regarding CPU...

...from pve-blacklist.conf that I just added (didn't make any difference) When this node was in the newer MB, I had tried to use the blacklist r8169 procedure and installed the r8168 dkms. and as part of that install there was a created file in /etc/modprobe.d called r8168-dkms which has 2 pci...

...the NIC showed up and I was able to ping 8.8.8.8 and load the webUI. So that's a big yay. However, when I reboot, the NIC goes back to UNCLAIMED. modprobe r8169 systemctl restart networking brings the card back up to working as normal. perhaps I need to blacklist the r8168 driver?

...state [ 25.850754] vmbr1: port 1(eno1) entered blocking state [ 25.850761] vmbr1: port 1(eno1) entered disabled state [ 25.850785] r8169 0000:06:00.0 eno1: entered allmulticast mode [ 25.850865] r8169 0000:06:00.0 eno1: entered promiscuous mode [ 25.927156] Realtek Internal NBASE-T...

...Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 0c) Subsystem: ASUSTeK Computer Inc. Device 88e1 Kernel driver in use: r8169 Kernel modules: r8169 86:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)...

...PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) Subsystem: Dell Device [1028:06bb] Kernel driver in use: r8169 ETA: I tried compiling from source: https://www.realtek.com/Download/List?cate_id=584 Driver I tried: GBE Ethernet LINUX driver r8168 for kernel up to...

...dmi_sysfs ip_tables [ 297.289968] x_tables autofs4 zfs(PO) spl(O) btrfs blake2b_generic xor raid6_pq nvme xhci_pci xhci_hcd ahci nvme_core r8169 i2c_piix4 libahci i2c_smbus realtek nvme_keyring nvme_auth video wmi [ 297.290679] CR2: 0000000000000018 [ 297.290806] ---[ end trace...

...it's back in PVE9 with kernel 6.14.11-pve and my NIC randomly drops off requiring a restart. To be clear, I am experiencing the issue of r8169 dropping connectivity, NOT the issue of having installed r8168 and then the update rendering it unable to work. r8168-dkms is not available in the...

...Co., Ltd. Device 5000 (rev 04) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7e32 Kernel driver in use: r8169 Kernel modules: r8169, r8126 So I suppose no harm in leaving the dkms one there, even if it is (somehow?) not actually limited to 6.14. But I...

...Co., Ltd. Device 5000 (rev 04) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7e32 Kernel driver in use: r8169 Kernel modules: r8169 Previously, this said: Kernel modules: r8126 so I am pretty sure it's not still using the DKMS driver. But for good...

...efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 zfs(PO) spl(O) btrfs blake2b_generic xor raid6_pq nvme xhci_pci nvme_core ahci r8169 i2c_piix4 xhci_hcd i2c_smbus libahci realtek nvme_keyring nvme_auth video wmi [12772.024696] CR2: 0000000000000018 [12772.024697] ---[ end trace...

...Ethernet Controller (rev 06) 2.- Install kernel headers and compilation tools (pve-headers, dkms, etc.). 3.- Install r8168-dkms. Blacklist r8169. Load module r8168. 4.- reboot What could it be? Any suggestions? Is the card faulty or just a software issue? Thanks for your help! PD: I...

I have also been using the r8169 driver since version 9 and have not encountered any problems so far. What a relief! :)

May I ask why you'd like to use the r8125 driver instead of the mainline r8169 driver? Normally you do not have to install any custom driver to use the NIC

...blake2b_generic xor raid6_pq libcrc32c cdc_ncm cdc_ether usbnet r8152 mii xhci_pci xhci_pci_renesas nvme atlantic crc32_pclmul thunderbolt r8169 xhci_hcd nvme_core macsec i2c_piix4 realtek nvme_auth video wmi i2c_hid_acpi i2c_hid hid [Sun Jun 15 07:01:37 2025] RIP...

thank you , I'm was retrying to set this command : ethtool -K enp6s0 rx off tx off . I'm waiting for result ...

Hi, Realtek NICs using the r8169 driver often trigger transmit queue timeout errors due to driver instability with newer kernels. Try to switch to the r8168 driver or disable offloads.