Proxmox having trouble with booting into Kernel 6

[celdrith]

Hello everyone, I have a question about Proxmox and its booting process into kernel 6.

For some reason it works flawlessly with kernel 5, but this is not a fix forever. I recently have tried booting into later kernels, notably 6.x and the screen just goes to sleep with no signal and the server becomes unresponsive.

I have looked into the boot log, but it always ends with a initialization of journalctl, or something similar, nothing helpful, does anyone have suggestions why this would be happening?

Proxmox itself is installed on a 120GB Gigabyte SSD
With a AMD Ryzen 5 1600 CPU
32GB DDR4 RAM
Nvidia GT 710/730 (I do not remember)
ASUS B450 Motherboard.

Is the hardware sufficient for Kernel 6, I would like to believe so.
Thanks in advance.

 

[Moayad]

Hello,

Could you please provide us with the output of `pveversion -v` command? if you're running PVE 8.x you may have issue with the new kernel. This described in our Roadmap [0] However, I would check if there is update for BIOS firmware etc.


[0] https://pve.proxmox.com/wiki/Roadmap#Known_Issues_&_Breaking_Changes

 

[celdrith]

Here's the output

root@Osiris:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.1.10-1-pve)
pve-manager: 8.2.2 (running version: 8.2.2/9355359cd7afbae4)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.1: 7.3-4
proxmox-kernel-6.8: 6.8.4-3
proxmox-kernel-6.8.4-3-pve-signed: 6.8.4-3
pve-kernel-6.1.10-1-pve: 6.1.10-1
pve-kernel-5.15.143-1-pve: 5.15.143-1
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.6
libpve-cluster-perl: 8.0.6
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.2
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.2.1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.3-1
proxmox-backup-file-restore: 3.2.3-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.6
pve-container: 5.1.10
pve-docs: 8.2.2
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.0
pve-firewall: 5.0.7
pve-firmware: 3.11-1
pve-ha-manager: 4.0.4
pve-i18n: 3.2.2
pve-qemu-kvm: 8.2.2-1
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.3-pve2

Thanks in advance.

 

[Moayad]

Thank you for the output! Did you check if the BIOS and firmware are up-to-date? I would also test proxmox-kernel 6.5.x work as well?

 

[celdrith]

Do you mean check the motherboard itself and if the firmware is up-to-date? I have not done that since purchase so, a long time ago.

 

[Moayad]

Yes, it's recommended to upgrade your PVE Server's BIOS/Firmware.

 

[celdrith]

Yes, it's recommended to upgrade your PVE Server's BIOS/Firmware.

I've updated the bios but it still will not do the trick, I must say I see a graphical error just before it quits.