Here are the steps I took to upgrade my nodes when the time came. Make sure that your apt upgrade and apt dist-upgrade don't have any errors.
Additionally, on one of my nodes, I had to confirm the grub install location. So It may be good to do this prior to upgrading by confirming the mount point of your boot disk.
apt remove --purge r8168-dkms -y
rm /etc/modprobe.d/blacklist-r8169.conf
sudo sed -i 's/GRUB_CMDLINE_LINUX="r8168.aspm=0 r8168.eee_enable=0 pcie_aspm=off loglevel=3"/GRUB_CMDLINE_LINUX=""/' /etc/default/grub
update-grub
proxmox-boot-tool refresh
apt update
apt upgrade -y
apt dist-upgrade -y
reboot -n
Updating the proxmox kernel will require you to remove this and potentially reapply https://forum.proxmox.com/threads/autoinstall-for-kernel-6-5-11-3-pve-failed.136818/
https://github.com/PragmaticEngineering/ansibleRole-proxmox-realtek
As part of proxmox 8.0 the realtek drivers are having issues where after a certain amount of time the node will go offline and lose connectivity. Here are the steps I took with a no-subscription repo.
to know if you could be affected by this issue, log into your proxmox host, either via ssh or keyboard and display and run:
lspci -nnk
if you are affected, you should see a Ethernet controller from Realtek Semiconductor Co. using the r8169 driver
for example
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:07a3]
Kernel driver in use: r8169
Kernel modules: r8169
vi /etc/apt/sources.list
deb http://ftp.us.debian.org/debian bookworm main contrib non-free non-free-firmware
deb http://ftp.us.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
# security updates
deb http://security.debian.org bookworm-security main contrib non-free non-free-firmware
deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription
apt update
apt install pve-headers -y
apt install r8168-dkms -y
apt upgrade -y
echo blacklist r8169 >> /etc/modprobe.d/blacklist-r8169.conf
sudo sed -i 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="r8168.aspm=0 r8168.eee_enable=0 pcie_aspm=off loglevel=3"/' /etc/default/grub
proxmox-boot-tool refresh
reboot -n
modify the repository source list. These repositories provide packages and updates for your system.
vi /etc/apt/sources.list
deb http://ftp.us.debian.org/debian bookworm main contrib non-free non-free-firmware
deb http://ftp.us.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
# security updates
deb http://security.debian.org bookworm-security main contrib non-free non-free-firmware
deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription
After modifying the sources.list file we need to make sure the system updates the package list from the repositories
apt update
Heres where most issues came up for me, we need to install the pve-headers pacakge. because without it, we will have issues compiling the realtek-dkms package. The -dkms suffix indicates that it's a Dynamic Kernel Module Support package, which means it can be automatically rebuilt whenever the kernel is updated. When you install this package, it uses the kernel headers (provided by pve-headers) to build and install the Realtek network card driver as a kernel module.
apt install pve-headers -y
Install the Realtek 8168 network card driver as a Dynamic Kernel Module Support package. It can automatically rebuild the driver when the kernel is updated.
apt install r8168-dkms -y
Then, for good measure I made sure my other packages were updated.
apt upgrade -y
blacklist the 8169 driver from being loaded
echo blacklist r8169 >> /etc/modprobe.d/blacklist-r8169.conf
Once all of this is completed we are going to update our GRUB to have some specific kernel parameters for our realtek driver
sed -i 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="r8168.aspm=0 r8168.eee_enable=0 pcie_aspm=off loglevel=3"/' /etc/default/grub
Finally, we are are going to refresh the boot configuration for Proxmox and reboot.
proxmox-boot-tool refresh
reboot -n
hi @SQLJames, I am using a pc as a server that has a msi b660m pro am4 board and an i5 12500 with a realtek 2. 5gbps but look when I run the command
lspci -nnkboth before and after running all commands still appears ther8169driver I have been using the server for 1 year and never gave me to look at this, I have contracted 1gbit at home and when I do a speedtest pro console on the host proxmox or a lxc only get 600mbits instead in a virtual machine gives me everything perfect that are about 920mbit, because it can be?apart from this next week I get a mini pc called FIREBAT-Mini PC T8 PRO PLUS that has an intel n100 and 2 ports 1 gbit that are realtek, I hope this guide will help me with that, but leaving that aside because this happens to me on my pc?
in the speedtest i am connected with a vpn wireguard in another place that is not the server but it doesn't matter because i am running the test inside proxmox from the interface so it should give me at least 800mbits.
Speedtest result in proxmox host panel:
