Open accessiblepixel opened 2 years ago
Hmm. No that didn't fix it, booted right back into the standard kernel :/
I'm lost!
Okay, more head scratching and I just force purged the original proxmox kernel, and grub automagically got rid of the old entry.
dpkg --purge --force-depends pve-kernel-5.4.143-1-pve
(In my case)
Then I needed to fix the package to it tells apt that pve-kernel-5.4 is satisfied so had to rebuild the debian package with
dpkg-deb -x pve-kernel-5.4.124-1-pve-relaxablermrr_5.4.124-1_amd64.deb tmpdir
Then dpkg-deb --control pve-kernel-5.4.124-1-pve-relaxablermrr_5.4.124-1_amd64.deb tmpdir
Then edit tmpdir/DEBIAN/control And change the following line from Provides: linux-image, linux-image-2.6 to Provides: linux-image, linux-image-2.6, pve-kernel-5.4 Then go to the directory that contains tmpdir and build the debian package dpkg -b tmpdir pve-kernel-5.4-relaxablermrr.deb
Then install the new package dpkg -i pve-kernel-5.4-relaxablermrr.deb
Which should replace the existing package, but also convince apt that everything is working fine...
Hopefully this helps someone else out :)
Kind regards, Jessica
alternatively, I was able to select the default kernel in grub via this method: https://unix.stackexchange.com/a/327686
basically (on my system) setting /etc/default/grub
GRUB_DEFAULT="gnulinux-advanced-07bb498a-8a1f-4c75-964a-e1473b8fc610>gnulinux-5.4.124-1-pve-relaxablermrr-advanced-07bb498a-8a1f-4c75-964a-e1473b8fc610"
Hi!
I found a slight issue trying to do a fresh install of Proxmox 6 on top of Debian 10 on my G6.
The stock kernel with a new Proxmox 6 install has a higher version number than the kernel included here,
so after installing I had to edit my grub defaults.I've found this which lets me find out the string I need to add to /etc/grub/default to boot the right kernelIf you edit /etc/default/grub to containDEFAULT=savedGRUB_SAVEDEFAULT=trueThen I ran update-grub and rebooted.Then I selected 'Advanced Options' and then chose the relaxable-rmrr kernel from the list.and all should be fine(TM) for each reboot from then on.I think you could probably then remove the existing proxmox kernel, although last time I tried it wanted to remove all of proxmox-ve.Okay so none of that works. See my last post for what I finally did to get it working.
Kind regards, Jessica