Can't boot after yesterday's update

[Philippe]

[Forpli]

Try to select Advanced options for Zorin in grub menu and then select an older kernel to boot from.
If the grub menu isn't displayed at boot, press continuosly esc key (or left shift key if you have a legacy BIOS) after start to show the grub menu.

[Philippe]

ok , got it to boot in older kernel , then i tried this :
sudo apt update && sudo apt upgrade linux-image-generic
Geraakt:1 Index of /ubuntu noble-security InRelease
Geraakt:2 Index of /ubuntu noble InRelease
Geraakt:3 https://brave-browser-apt-release.s3.brave.com stable InRelease
Geraakt:4 Index of /ubuntu noble-updates InRelease
Geraakt:5 Index of /debian noble InRelease
Geraakt:6 Index of /ubuntu noble-backports InRelease
Geraakt:7 Index of /zorinos/apps/ubuntu noble InRelease
Geraakt:8 Index of /zorinos/drivers/ubuntu noble InRelease
Geraakt:9 Index of /zorinos/patches/ubuntu noble InRelease
Geraakt:10 Index of /zorinos/stable/ubuntu noble InRelease
Geraakt:11 Index of /stable/ noble InRelease
Geraakt:12 Index of /patches/ noble InRelease
Geraakt:13 Index of /apps/ noble InRelease
Geraakt:14 Index of /drivers/ noble InRelease
Geraakt:15 Zorin OS Pro - Zorin OS noble InRelease
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd... Klaar
De statusinformatie wordt gelezen... Klaar
Alle pakketten zijn up-to-date.
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd... Klaar
De statusinformatie wordt gelezen... Klaar
linux-image-generic is reeds de nieuwste versie (6.8.0-136.136).
Opwaardering wordt doorgerekend... Klaar
De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig:
libfwupd2 libwoff1
Gebruik 'sudo apt autoremove' om ze te verwijderen.
0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd.
4 niet volledig geïnstalleerd of verwijderd.
Na deze bewerking zal er 0 B extra schijfruimte gebruikt worden.
Wilt u doorgaan? [J/n] j
Instellen van linux-image-7.0.0-28-generic (7.0.0-28.28~24.04.1) ...
Instellen van linux-headers-7.0.0-28-generic (7.0.0-28.28~24.04.1) ...
/etc/kernel/header_postinst.d/dkms:

• dkms: running auto installation service for kernel 7.0.0-28-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
make -j8 KERNELRELEASE=7.0.0-28-generic -C /lib/modules/7.0.0-28-generic/build M
=/var/lib/dkms/virtualbox/7.0.16/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 7.0.0-28-generic (x86_64)
Consult /var/lib/dkms/virtualbox/7.0.16/build/make.log for more information.
dkms autoinstall on 7.0.0-28-generic/x86_64 failed for virtualbox(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.

• dkms: autoinstall for kernel 7.0.0-28-generic
  ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: fout bij verwerken van pakket linux-headers-7.0.0-28-generic (--configure)
  :
  subproces van pakket linux-headers-7.0.0-28-generic werd script post-installati
  on geïnstalleerd gaf de foutwaarde 11 terug
  dpkg: vereistenproblemen verhinderen de configuratie van linux-headers-generic-h
  we-24.04:
  linux-headers-generic-hwe-24.04 is afhankelijk van linux-headers-7.0.0-28-gener
  ic; maar:
  Pakket linux-headers-7.0.0-28-generic is nog niet geconfigureerd.

dpkg: fout bij verwerken van pakket linux-headers-generic-hwe-24.04 (--configure
):
vereistenproblemen - blijft ongeconfigureerd
dpkg: vereistenproblemen verhinderen de configuratie van linux-generic-hwe-24.04
:
linux-generic-hwe-24.04 is afhankelijk van linux-headers-generic-hwe-24.04 (= 7
.0.0-28.28~24.04.1); maar:
Pakket linux-headers-generic-hwe-24.04 is nog niet geconfigureerd.

dpkg: fout bij verwerken van pakket linux-generic-hwe-24.04 (--configure):
vereistenproblemen - blijft ongeconfigureerd
Bezig met afhandelen van triggers voor linux-image-7.0.0-28-generic (7.0.0-28.28
~24.04.1) ...
/etc/kernel/postinst.d/dkms:

• dkms: running auto installation service for kernel 7.0.0-28-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
make -j8 KERNELRELEASE=7.0.0-28-generic -C /lib/modules/7.0.0-28-generic/build M
=/var/lib/dkms/virtualbox/7.0.16/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 7.0.0-28-generic (x86_64)
Consult /var/lib/dkms/virtualbox/7.0.16/build/make.log for more information.
dkms autoinstall on 7.0.0-28-generic/x86_64 failed for virtualbox(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.

• dkms: autoinstall for kernel 7.0.0-28-generic
  ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: fout bij verwerken van pakket linux-image-7.0.0-28-generic (--configure):
  subproces van pakket linux-image-7.0.0-28-generic werd script post-installation
  geïnstalleerd gaf de foutwaarde 11 terug
  Fouten gevonden tijdens verwerken van:
  linux-headers-7.0.0-28-generic
  linux-headers-generic-hwe-24.04
  linux-generic-hwe-24.04
  linux-image-7.0.0-28-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

[Philippe]

What do i do now before i reboot ? don't want to have to select a kernel every time i boot.

got a second pc with zorin , that one booted but screen brightness is gone , i brightest settings it looks like on lowest

[Aravisian]

You are not alone in this experience:

Kernel Panic after 7.0.0-28-generic Update

To fix my issue I had to download the updated version of virtualbox from their website as the Software Centre didn't have the most up to date version. Once I installed that ( ​Ubuntu 24.04 and re-enrolled for my Secure Boot MOK applied that and now I'm able to boot on Kernel 7.0.0-28

[Forpli]

[HOW TO] set an older kernel to default boot

You may need to use an earlier kernel than the current kernel used by Zorin. This method allows you to set the kernel that you will boot into by default. To set the new kernel to default: Boot into the kernel you wish to be Saved. Open terminal and run: sudo nano /etc/default/grub Change GRUB_DEFAULT=0 to GRUB_DEFAULT=saved Hit enter to drop down a line. Add GRUB_SAVEDEFAULT=true ctrl+x to exit, then the y key to say yes to save, then the enter key to save as current configuration. Ru…

You can set an older kernel as default for the next time to boot from until the next kernel updates will be released and then try it again with the new kernel 7.0.

[Philippe]

so uninstalling virtualbox would solve it for now ?

[Aravisian]

@Philippe

so uninstalling virtualbox would solve it for now ?

Probably. If you are not using it, then replacing it would not be necessary.

[Forpli]

Another users helped this:

Kernel Panic after 7.0.0-28-generic Update

To fix my issue I had to download the updated version of virtualbox from their website as the Software Centre didn't have the most up to date version. Once I installed that ( ​Ubuntu 24.04 and re-enrolled for my Secure Boot MOK applied that and now I'm able to boot on Kernel 7.0.0-28

Recent kernel update does not work (7.0.0-28-generic)

Hi! On my last kernel update, I had the same issue due to VirtualBox. All I did was boot from the old kernel in the advanced Grub options and update VirtualBox to the latest version (I used a Debian package). After rebooting with the new kernel, the error no longer occurred.

The kernel panics with kernel 7.0 seem often to be related to virtualbox.

[Philippe]

unfornunetly , it did not resolve my problem , still had to select the previous kernel 6.17

how do i remove the bad kernel and leave no trace of it ?

[Aravisian]

Interesting. Above, it gives a bad return only for VirtualBox:

@Philippe

make -j8 KERNELRELEASE=7.0.0-28-generic -C /lib/modules/7.0.0-28-generic/build M
=/var/lib/dkms/virtualbox/7.0.16/build....(bad exit status: 2)

The only other thing I can see is Secure Boot is blocking it.

[Philippe]

Its not turned on

[Aravisian]

@Philippe

Its not turned on

Ah. I assumed it could be because of:

@Philippe

dkms: running auto installation service for kernel 7.0.0-28-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Well, why not stick to the working kernel, then?
I suspect that the 7+ kernel does not offer new features you have been dying for.

[Philippe]

How to i delete this bad kernel and leave no trace of it ?
Dont want to get windows experience every time updates are there.
And i do need virtualbox atleast once a week.

[Aravisian]

@Philippe

How to i delete this bad kernel and leave no trace of it ?

While this is a practical and logical action; the updater will continue to want to offer it. This leaves you with deleting it, but also needing to block it, as well. You can do this...
But it is probably simpler to default boot to your working kernel and let the 7.0 kernel sit and twiddle its thumbs.
You can use this method:

[HOW TO] set an older kernel to default boot

You may need to use an earlier kernel than the current kernel used by Zorin. This method allows you to set the kernel that you will boot into by default. To set the new kernel to default: Boot into the kernel you wish to be Saved. Open terminal and run: sudo nano /etc/default/grub Change GRUB_DEFAULT=0 to GRUB_DEFAULT=saved Hit enter to drop down a line. Add GRUB_SAVEDEFAULT=true ctrl+x to exit, then the y key to say yes to save, then the enter key to save as current configuration. Ru…

If you really want that kernel nuked for satisfaction:

sudo apt purge linux-image-7.0.0-28-generic linux-modules-7.0.0-28-generic linux-headers-7.0.0-28-generic

sudo update-grub

Then block it from updating:

sudo apt-mark hold linux-image-7.0.0-28-generic linux-modules-7.0.0-28-generic linux-headers-7.0.0-28-generic

I would recommend a cleanup after:

sudo apt clean && sudo apt autoremove

[Ponce-De-Leon]

@Philippe

But on the last Option is a Marker:

[Philippe]

Thanks for the big help , i remove it and now boots as before
Much appreciated

[Lostmeis]

Hope this helps you!

To fix my issue I had to download the updated version of virtualbox from their website as the Software Centre didn't have the most up to date version. Once I installed that ( ​Ubuntu 24.04 and re-enrolled for my Secure Boot MOK applied that and now I'm able to boot on Kernel 7.0.0-28

[Philippe]

Thanks ,
I installed that one now , i'll wait and see what happen when i get that kernel update presented again

[Philippe]

the steps i used from post 15.

On startup i selected advanced the then selected the kernel just before the 7.0.
uninstalled virtualbox
ran the following commands:
sudo apt purge linux-image-7.0.0-28-generic linux-modules-7.0.0-28-generic linux-headers-7.0.0-28-generic

sudo update-grub

sudo apt clean && sudo apt autoremove

then rebooted

after that installed virtualbox 7.2 via the link https://download.virtualbox.org/virtualbox/7.2.12/virtualbox-7.2_7.2.12-174389~Ubuntu~noble_amd64.deb

up till now all is fine.

Did not get the update for the kernel again up till now.