Search results for query: r8169

...vfio iommufd efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq nvme nvme_core ahci nvme_auth libahci r8169 realtek xhci_pci i2c_i801 spi_intel_pci i2c_mux spi_intel intel_lpss_pci i2c_smbus xhci_hcd intel_lpss idma64 vmd video wmi pinctrl_alderlake...

...RealTek 1g (management network) didn't work. Surprisingly wifi did work but I don't configure that cuz it's wifi. Doing a modprobe -r r8169 and modprobe r8169 resulted in this message: "kernel: r8169 0000:2a:00.0: error -ENODEV: no MMIO resource found". Let me know if I can get you any...

Update on this, for anyone interested: Issue moved with the movement from the Realtek 10GBe R8169 driver to a different NIC (different chipset and different kernel driver Realtek 2.5GBe,) but still on the motherboard. Anecdotally, it appeared to get better with the most recent Proxmox...

...with similar issues in the past. For the record, My suspicion is it is the driver on this 'newish' Realtek 10GBe nic (driver being used is R8169 by the way, which I've researched to have been updated with a limited number of lines of code to make it compatible with this new 10GBe version...

...ich weiß was hier los ist. Du nutzt hier eine Realtek Karte auf deinem Board (rtl8168), das siehst Du bei deiner ethtool Ausgabe: driver: r8169 version: 6.17.2-2-pve firmware-version: rtl8168h-2_0.0.2 02/26/15 Nun gibt es bei dieser Karte in Kombination mit dem r8169 Treiber. Das ist genau...

...MDI-X: Unknown Supports Wake-on: pumbg Wake-on: d Link detected: yes root@proxmox:/# ethtool -i nic0 driver: r8169 version: 6.17.2-2-pve firmware-version: rtl8168h-2_0.0.2 02/26/15 expansion-rom-version: bus-info: 0000:05:00.0 supports-statistics: yes supports-test: no...

...Failed to send SIGKILL via pidfd 16 for process 9964 startup for container '102' failed When I delete the VLAN tag and give it a native IP, the CT starts up normally. The initial driver for my NIC was r8169. I already changed it to r8125 - with no effect concerning the above error. What is...

...entered blocking state Dec 02 15:20:52 proxmox-ha kernel: vmbr0: port 1(enp1s0) entered forwarding sta> Dec 02 15:21:02 proxmox-ha kernel: r8169 0000:01:00.0 enp1s0: Link is Down Dec 02 15:21:02 proxmox-ha kernel: vmbr0: port 1(enp1s0) entered disabled state Dec 02 15:21:05 proxmox-ha kernel...

...No such device Settings for nic2: Supports Wake-on: pumbg Wake-on: d Link detected: no root@server5:~# ethtool -i nic2 driver: r8169 version: 6.17.2-1-pve firmware-version: expansion-rom-version: bus-info: 0000:07:00.0 supports-statistics: yes supports-test: no...

...usbmouse usbkbd usbhid hid uas usb_storage mlx5_core mlxfw xhci_pci psample tls nvme i2c_piix4 ahci i2c_smbus xhci_hcd libahci pci_hyperv_intf r8169 nvme_core realtek nvme_keyring nvme_auth video wmi gpio_amdpt Nov 24 03:45:09 pve2 kernel: CPU: 10 UID: 0 PID: 2378 Comm: bash Tainted: P...

...show enp4s0" shows the packet count no longer increasing when it drops out, and vmbr1 state up. It appears the DGE-528T is using the RealTek r8169 drivers, the same driver as the onboard NIC. The only way to recover from the dropout is to reboot Proxmox, which isn't ideal. Questions. 1)...

I'm also running Podman in LXC and ran into this issue and can't use 6.17 therefore. It's good that there's a fix but you didn't report this anywhere but here yet @jaminmc?

...perfectly stable when I force the link speed to 1 Gbps. Troubleshooting Steps Already Taken Driver Change: Attempted to blacklist the default r8169 kernel module and successfully installed and forced the proprietary r8125 DKMS driver. Result: The high latency/packet loss issue persisted. (I...

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