does "Hold Current Kernel" ensure it's not lost? Or prevent it from being used?
It executes apt-mark hold which will prevent the kernel from being updated by apt. Since you have 5.6 installed already, there is little reason to hold the kernel. Personally, I would try the proxmox kernel (will stay on 5.4) and if it is stable, remove the debian kernels.
Sure. But I consider the proxmox kernel to better tested than the Debian Backports kernel. Not only is it the Ubuntu LTS kernel but it is also tested against the Debian userland in Proxmox. So, it is very good for OMV.
Presume it gets updates and we can switch back?
Yep. I run it on almost all of my OMV systems.
i have kernel not updating automatically with apt update and apt-dist upgrade i saw there are no packages on hold with apt-mark showhold command but i see kernels in manual, how can i solve this?
root@openmediavault:~# sudo apt install linux-headers-5.9.0-0.bpo.2-amd64
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-headers-5.9.0-0.bpo.2-amd64 is already the newest version (5.9.6-1~bpo10+1).
linux-headers-5.9.0-0.bpo.2-amd64 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.5.9 headers are installed but nod in grub or updated by grub (actually i still use 5.7 for compatibility with veeam agent)
root@openmediavault:~# dpkg -l | grep linux-headers-
ii linux-headers-5.6.0-0.bpo.2-amd64 5.6.14-2~bpo10+1 amd64 Header files for Linux 5.6.0-0.bpo.2-amd64
ii linux-headers-5.6.0-0.bpo.2-common 5.6.14-2~bpo10+1 all Common header files for Linux 5.6.0-0.bpo.2
ii linux-headers-5.7.0-0.bpo.2-amd64 5.7.10-1~bpo10+1 amd64 Header files for Linux 5.7.0-0.bpo.2-amd64
ii linux-headers-5.7.0-0.bpo.2-common 5.7.10-1~bpo10+1 all Common header files for Linux 5.7.0-0.bpo.2
ii linux-headers-5.8.0-0.bpo.2-amd64 5.8.10-1~bpo10+1 amd64 Header files for Linux 5.8.0-0.bpo.2-amd64
ii linux-headers-5.8.0-0.bpo.2-common 5.8.10-1~bpo10+1 all Common header files for Linux 5.8.0-0.bpo.2
ii linux-headers-5.9.0-0.bpo.2-amd64 5.9.6-1~bpo10+1 amd64 Header files for Linux 5.9.0-0.bpo.2-amd64
ii linux-headers-5.9.0-0.bpo.2-common 5.9.6-1~bpo10+1 all Common header files for Linux 5.9.0-0.bpo.2
ii linux-headers-amd64 5.9.6-1~bpo10+1 amd64 Header files for Linux amd64 configuration (meta-package)
root@openmediavault:~# update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.8.0-0.bpo.2-amd64
Found initrd image: /boot/initrd.img-5.8.0-0.bpo.2-amd64
Found linux image: /boot/vmlinuz-5.7.0-0.bpo.2-amd64
Found initrd image: /boot/initrd.img-5.7.0-0.bpo.2-amd64
Found linux image: /boot/vmlinuz-5.6.0-0.bpo.2-amd64
Found initrd image: /boot/initrd.img-5.6.0-0.bpo.2-amd64
done5.9 headers are installed but nod in grub or updated by grub (actually i still use 5.7 for compatibility with veeam agent)
I don't understand what problem you are having. The headers don't have anything to do with grub. The kernel does. And the other problem is that some plugins depend on the linux-headers-amd64 package which will only point to the latest kernel. So, you will have issues trying to run the 5.7 kernel with the latest headers. You should have marked the headers and kernel packages on hold. Otherwise, the best option is to probably use the proxmox 5.4 kernel and remove the debian kernels altogether.
I don't understand what problem you are having. The headers don't have anything to do with grub. The kernel does. And the other problem is that some plugins depend on the linux-headers-amd64 package which will only point to the latest kernel. So, you will have issues trying to run the 5.7 kernel with the latest headers. You should have marked the headers and kernel packages on hold. Otherwise, the best option is to probably use the proxmox 5.4 kernel and remove the debian kernels altogether.
right i was looing to headers and not image for linux kernel, for some reason i have only 5.9 headers and not image, i'm still using kernel 5.7 because it works with veeam backup agent, which are the main advantages in using proxmox kernele against debian?
which are the main advantages in using proxmox kernele against debian?
The proxmox kernel is the Ubuntu 20.04 LTS kernel. In my opinion this is more tested than the Debian backports kernels. Also proxmox uses the Debian 10 userland. So, the proxmox kernel is a very good fit for OMV. I run it on almost all of my OMV systems.
The debian 5.9 kernel is having problems with Nvidia drivers. ( i need to figure out how to go back to 5.8. any ideas?)
Any idea how the proxmox kernels work with nvidia drivers. Mostly used for hardware transcoding.
Thanks,
ML
i need to figure out how to go back to 5.8. any ideas?)
That will be a pain since the nvidia driver needs to compile and will need headers.
Any idea how the proxmox kernels work with nvidia drivers. Mostly used for hardware transcoding.
Since the proxmox kernel is basically the Ubuntu kernel, it should work ok.
Thanks rye.
I'm going to restore disk image before nvidia. Nvidia was supposed to fix driver to work with 5.9 but hasn't yet. Do you know what nvidia driver works with proxmox? I know kernel 5.4 was available but getting rid of the nvidia drivers was not working. Lots of errors. Going to right to proxmox and try it.
Thanks again.
ML
Do you know what nvidia driver works with proxmox?
No. I haven't installed the nvidia driver in a while (I have no decent cards).
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
