kernel 7.0 and mainstream repo

[dorinxev]

Late friday I decided to upgrade my proxmox 9.1.
I'm using the no-subscription repo, none of the nodes has test repo enables.

Imagine my surprise when the update decided it's time to jump to kernel 7.0 and not remain on the 6.x

At the moment, there are few 3rd party kernel modules which are not compatible:
- i915 SRIOV (although I heard as I write this post that it's now supported)
- Any realtek driver that is not part of the kernel (r8127, r8159) - support up to kernel 6.15 IIRC

Was that a mistake or something?

My /etc/apt/ repos:

root@prox1:/etc/apt# cat sources.list.d/*
Types: deb
URIs: https://enterprise.proxmox.com/debian/ceph-squid
Suites: trixie
Components: enterprise
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
Enabled: false
Types: deb
URIs: http://deb.debian.org/debian/
Suites: trixie trixie-updates
Components: main contrib non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb
URIs: http://security.debian.org/debian-security/
Suites: trixie-security
Components: main contrib non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
Types: deb
URIs: https://enterprise.proxmox.com/debian/pve
Suites: trixie
Components: pve-enterprise
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
Enabled: false

 

[beisser]

7.0 is the new default kernel on no-subscription, but you can easily pin an older kernel with the proxmox-boot-tool.
the node will then boot with whatever kernel you pin until you remove the pin, even if a newer kernel is installed.

 

[dorinxev]

Which is what I did eventually, but my question - why no-subscription jumps a major kernel version? I can understand doing this on the test repo, but on no-subscription?

 

[leesteken]

Imagine my surprise when the update decided it's time to jump to kernel 7.0 and not remain on the 6.x

For the Linux kernel version 7.0 is not more special (or a bigger change) than 6.20 would be compared to 6.19. And the jump from 6.17 to 7.0 is similar to 6.14 to 6.17.

PVE 9.x has indeed seen more than one kernel version already: 6.14, 6.17 and 7.0. Maybe Ubuntu is also going through kernel versions more often than before instead of bigger jumps? Or maybe it's Proxmox that pulls in the Ubuntu kernel more often?

 

[beisser]

Which is what I did eventually, but my question - why no-subscription jumps a major kernel version? I can understand doing this on the test repo, but on no-subscription?

because that is how it works. as @leesteken already said, 7.0 is "just another new kernel", which happens to have a different major release number.
the order is "test", then "no-subscription" and then eventually "enterprise" after enough feedback has been received.
if you dont want kernel-upgrades, pin the kernel.
it is your own responsibility to make sure any 3rd-party modules (including nvidia-drivers) work on a new kernel before upgrading to it (by trying it out on a testnode maybe or even inside a vm).

 

[gfngfn256]

it's time to jump to kernel 7.0 and not remain on the 6.x

See my question on these forums & the answer given here.