Installing 8.2 booting std Proxmox iso & mpt3sas-driver
- Thread starter blondie63
- Start date
Interesting. If you run the package updates on your new installation, does it come back up after rebooting?
But i no have enterprise subscription so i've disabled the two enterprise repo !
Can i update to latest VE the same ?
Ahhh. There's an "Add" button in the same page for adding a subscription to the "no-subscription" repository:
That's gives you access to the latest Proxmox packages, though it has warnings about it being "not recommended for production use".
If you're familiar with the difference between Fedora Linux and Red Hat Enterprise Linux, I think it's a similar kind of situation. That's just guessing though.
My tests:Ahhh. There's an "Add" button in the same page for adding a subscription to the "no-subscription" repository:
View attachment 68997
That's gives you access to the latest Proxmox packages, though it has warnings about it being "not recommended for production use".
If you're familiar with the difference between Fedora Linux and Red Hat Enterprise Linux, I think it's a similar kind of situation. That's just guessing though.
1. i upgraded from Debian repo only and reboot -> OK
2. I added pve-no-subscription, refresh packages and upgrade all -> on top i seen v8.2.2 -> OK
3. reboot -> BOOM !
Damn. If you reboot again, do you get the initial grub screen where you can pick an earlier version of the Proxmox kernel for booting with?
ok, choosing kernel 6.5.13-5-pve server start ! But, the Proxmox team know about this big bug ?
Can i set temporarily this as default kernel ?
Definitely.
Under the "Kernel 6.8" heading here, it gives a way to "pin" the version of the kernel you're using:
https://pve.proxmox.com/wiki/Roadmap#Known_Issues_&_Breaking_Changes
I'm also doing that for one of my boxes, which has an nvidia card in it that doesn't like the Linux 6.8 kernel either. This pinning approach seems to work fine.
I don't know.
I have not seen anyone else mention the megaraid driver not working though.
Probably the best approach is to look for an existing bug report about it on the Proxmox bug tracker:
https://bugzilla.proxmox.com
... and if there is not an existing bug report about it, then to create a new bug report for it.
I've not personally ever done that bit (yet), so I'm not sure of the steps you need to do for it.