Search results for query: r8169

...way that you would for GPU passthrough. On reboot, I checked the dmesg, and I see this: root@prox2:~# dmesg | grep eth0 [ 2.411928] r8169 0000:01:00.0 eth0: RTL8125B, 00:e0:4c:b0:1e:a9, XID 641, IRQ 34 [ 2.411933] r8169 0000:01:00.0 eth0: jumbo features [frames: 9194 bytes, tx...

...tap efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c xhci_pci xhci_pci_renesas crc32_pclmul r8169 Aug 15 22:37:57 Server kernel: ahci i2c_piix4 realtek xhci_hcd libahci video wmi gpio_amdpt Aug 15 22:37:57 Server kernel: CR2: ffffffffc18466b0 Aug...

Experts, please help me. I have a GK3 mini PC on intel n5105, the r8169 network driver is installed. I launched the proxmox update from 8.04 to 8.2, everything was updated normally. But after reboot, everything freezes when booting Linux 6.8.12-1-pve. In grub, I chose the old 6.2.16-20 kernel. I...

...vhost vhost_iotlb tap efi_pstore dmi_sysfs ip_tables x_tables autofs4 zfs(PO) spl(O) btrfs blake2b_generic xor raid6_pq libcrc32c crc32_pclmul r8169 ahci i2c_piix4 realtek libahci wmi Aug 11 21:06:12 pve kernel: gpio_amdpt Aug 11 21:06:12 pve kernel: CPU: 13 PID: 2264 Comm: CPU 0/KVM...

...ist good. I tested it with a few Servers, Ubuntu is one of the fastest server i know. But, i thought i know what the problem ist: The R8169 Chipset from Realtek I found a few Threads but not a solution for the lastest Proxmox Server/Kernel. root@proxmox:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP>...

Have you tried the new driver? 8.053.00 https://www.realtek.com/Download/List?cate_id=584 If you succeed please tell me how you did it? Also how did you get access to wifi. No matter what I try I cannot. You mentioned wpa supplicant. How to use that. Sorry I’m a newbie.

HI, What commands did you use to remove and add the r8169? Can you please share your method. Thank s in advance. I only have access to the command line connected via hdmi to a screen.

Sorry for the newbie question, how do you copy the files from src to the /usr/src/r8168-8.053.00/? USB? I did a new install and my ethernet card doesn't even show up. I need some manual way to fix this.

It would appear that you are suffering from the old Linux r8168/r8169 troubles. See here. It appears that fixes like this, actually work.

...drm_buddy i2c_algo_bit drm_suballoc_helper drm_ttm_helper ttm drm_display_helper cec nvme xhci_pci rc_core nvme_core ahci xhci_pci_renesas r8169 video crc32_pclmul xhci_hcd libahci i2c_piix4 realtek nvme_auth wmi gpio_amdpt z3fold zstd Aug 04 21:39:23 proxbeast-pve kernel: CR2...

...ip a and /etc/network/interfaces and the interfaces seem to match still: The network kernel driver seems to be ok (I previously had problems with r8169 and I had to swap to r8168 driver, but I swapped back to the default kernel driver a while back): Any suggestions on how I can resolve this?

Nothing is appearing in the journalctl logs. Powered on the system with new GPU at 20:20, powered off at 20:25. Powered on system with old GPU at 20:31. However, I see a jump from 20:02, when it was previously on, to 20:31 with the old GPU. Tested the Ubuntu installer trick which worked with...

No, it mean the name of your network device is enp3s0 (and the driver is r8169). The other renames are from guests. From your logs, I doubt that the network not working is caused by name changing (as they are all enp3s0). Maybe check the same log for error messages that might give a clue (about...

...grep "rename" Gives me the following output (when filtered for correct times): Am I reading this correctly that `Jul 27 17:56:01 pve kernel: r8169 0000:03:00.0 enp3s0: renamed from eth0` refers to renaming 'enp3s0' to 'r8169' ? I can confirm that the system does shut down "gracefully"...

...xor raid6_pq dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c hid_generic usbhid hid xhci_pci xhci_pci_renesas crc32_pclmul r8169 ahci xhci_hcd i2c_piix4 realtek libahci wmi gpio_amdpt [ 1710.535033] CR2: 0000000000000000 [ 1710.535246] ---[ end trace 0000000000000000 ]--- [...

...appear to be the same issue I am having. Regardless I tried to perform the fix they mentioned (installing the older driver r8168 instead of r8169 via https://gist.github.com/SQLJames/fe6fcd5e819d864986ce2eff6ad350da, but ran into errors during that process). Didnt want to go down the rabbit...

...xor raid6_pq simplefb dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c nvme crc32_pclmul xhci_pci nvme_core i2c_piix4 r8169 xhci_pci_renesas nvme_common ahci realtek libahci xhci_hcd video wmi gpio_amdpt Jul 20 16:29:20 prox07 kernel: CPU: 0 PID: 166 Comm: kworker/u64:6...

After upgrading to Proxmox 8 with a clean install and creating a guest VM I experience random (~24-48h) freezes of the guest VM i.e. no ping/ssh and VNC show unresponsive login screen. I can't find any clues in the logs. Last freeze today at 12:28: More information: - The host is not...

...Controller [10ec:8125] (rev 04) Subsystem: ASUSTeK Computer Inc. RTL8125 2.5GbE Controller [1043:87d7] Kernel driver in use: r8169 Kernel modules: r8169 07:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch...

...Controller [10ec:8125] (rev 04) Subsystem: ASUSTeK Computer Inc. RTL8125 2.5GbE Controller [1043:87d7] Kernel driver in use: r8169 Kernel modules: r8169 07:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch...