Hi @martin,
Does the 5.3 test kernel come also with kernel-sources? Or is there some alternative way to run DKMS to install Wireguard on that kernel?
yes, just install the pve-headers via:
> apt install pve-headers-5.3
Hi @martin,
Does the 5.3 test kernel come also with kernel-sources? Or is there some alternative way to run DKMS to install Wireguard on that kernel?
Hi, i see 5.3 in no-subscription list, does that mean that it is out of test?
my current version
View attachment 12831
Is it save to update the kernel with version 5.4.3 ? What are advantages and/or risks ?
It's still opt-in, so not completely. But we had really good experience with it, and also got some positive feedback here so that it was decided that it's safe to open it up for more easier testing for a wider audience.
We will probably switch soon to 5.3 as default kernel, though.
So does this mean we don’t have to enable the test repository any more to install the 5.3 kernel and it can be installed using “apt install” if the no-subscription repository is enabled? I don't see the 5.3 Kernel listed as part of the "Available Updates" panel in the Web GUI?
Regarding the switch to the 5.3 kernel as default, would this be for PVE6 or expected in PVE6.1?
Thanks!
You can just install the respective headers package.
Code:apt install pve-headers-5.3
If you have a low priority Debian testing repo added, you can then also just do:
Code:apt install wireguard-dkms
Works good here since over a year
Wireguard is broken for me though with this version. I had wireguard-dkms already installed before the upgrade (The package itself was showing as "latest version installed"), and while dkms was compiling it failed with some unsupported data structure exception.
pve-headers-5.3
to get the 5.3 based headers.pve-headers
meta package still points to pve-headers-5.0
Off-topic but the number at the end refers to the plug type that is supplied with the NUC (US, EU, UK etc) ...Just curiosity ... What does the 2 at the end of your NUC model refer to? Is that some sort of 2nd version of that model?
wget "http://download.proxmox.com/debian/pve/dists/buster/pvetest/binary-amd64/pve-headers-5.3.10-1-pve_5.3.10-1_amd64.deb"
dpkg -i pve-headers-5.3.10-1-pve_5.3.10-1_amd64.deb
[ 16.273618] EDAC amd64: Node 0: DRAM ECC enabled.
[ 16.273620] EDAC amd64: F17h detected (node 0).
[ 16.273673] EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?)
[ 16.273718] EDAC amd64: Error: Error probing instance: 0
[ 16.346761] EDAC amd64: Node 0: DRAM ECC enabled.
Do you don't get the hangs anymore with kernel 5.3?
Me and some other Proxmox users (still on kernel kernel 5.0.21-4-pve) are affected by that bug too... see my post or other posts. I even tried Intels driver v3.6.0 but I get the same network issues with kernel-tree driver 3.2.6-k
Thanks.Off-topic but the number at the end refers to the plug type that is supplied with the NUC (US, EU, UK etc) ...
dpkg -s pve-kernel-5.3.10-1-pve