Same Probleme here with MinisForum HM80
AMD Ryzen 7 4800U and 188.8.131.52 Kernel - ifupdown Problem on start / no reboot
I can confirm I can boot with 5.15.5-1pve. (From metapackage as per reccomendation)
apt update apt install pve-kernel-5.15
apt-mark unhold 'pve-kernel-5.13'
Thanks for showing me how to rollback to 5.13.19-1-pve because 5.13.19-2-pve would cause my host to reboot when the Plex container tried to use the Nvidia card. I could not get the Nvidia drivers working on the 5.15 kernel so I had to roll back the earlier 5.13 kernel.Thanks All!
Just to Summarise this Thread:
If you have an issue with the latest Kernel "5.13.19-2-pve" and it won't boot properly with such Kernel (AMD Systems seem affected) use the following steps:
apt install pve-kernel-5.13=7.1-4
then remove the old kernel with the following
dpkg -P pve-kernel-5.13.19-2-pve
Set the kernel updates to avoid the latest 5.13 with
apt-mark hold 'pve-kernel-5.13'
if you're still having issues modify GRUB with:
nano /etc/default/grub And then value GRUB DEFAULT change from 0 to "1>2". (With quotes)
Note: "1>2" denotes the Advanced option with the second kernel installed.
Run the following to update your boot system
Special thanks to @tauceti @Kephin @nicedevil
Hi 150d,Because of this issue, I've just installed a new machine using Proxmox v7.0 (instead of v7.1) because I couldn't boot v7.1 on my Ryzen 7 4800U. Out of fear that an update could render my system unbootable I've since not enabled any updates.
Of course, this is not a permanent solution. How has this issue developed since January (prior post in this thread)? Perhaps the Proxmox repository has already been updated to skip the "problematic" kernel entirely in the meantime? (It just says "5.13" on the update page, which as I understand it could either be a fixed version or a non-fixed version.) If not, is it reasonable to wait for such an update, or could this be "a long wait"?