Just applied the update that was available for the kernel update only to have it fail and give a Kernel Panic. I have attempted a couple options to purge the update and have it retry, but have had no luck removing the failed update so that I can accomplish that even attempted an "update-initramfs" to see if that would help, but no luck. Currently booted to 6.17.0-40-generic with no issues. Any help with this would be greatly appreciated.
Outputs: sudo update-initramfs -k all
update-initramfs: Generating /boot/initrd.img-7.0.0-28-generic
libkmod: ERROR ../libkmod/libkmod-file.c:136 zstd_decompress_block: zstd: Restored data doesn't match checksum
dpkg: dependency problems prevent removal of linux-image-7.0.0-28-generic:
linux-signatures-nvidia-7.0.0-28-generic depends on linux-image-7.0.0-28-generic | linux-image-unsigned-7.0.0-28-generic; however:
Package linux-image-7.0.0-28-generic is to be removed.
Package linux-image-unsigned-7.0.0-28-generic is not installed.
linux-modules-nvidia-595-7.0.0-28-generic depends on linux-image-7.0.0-28-generic | linux-image-unsigned-7.0.0-28-generic; however:
Package linux-image-7.0.0-28-generic is to be removed.
Package linux-image-unsigned-7.0.0-28-generic is not installed.
sudo dpkg -P linux-image-7.0.0-28-generic
dpkg: error processing package linux-image-7.0.0-28-generic (--purge):
dependency problems - not removing
Errors were encountered while processing:
linux-image-7.0.0-28-generic
sudo apt autoremove
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up linux-image-7.0.0-28-generic (7.0.0-28.28~24.04.1) ...
depmod: ERROR: ../libkmod/libkmod-file.c:136 zstd_decompress_block() zstd: Restored data doesn't match checksum
Setting up 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 -j32 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 succeeded for nvidia
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: error processing package linux-headers-7.0.0-28-generic (--configure):
installed linux-headers-7.0.0-28-generic package post-installation script subprocess returned error exit status 11
Processing triggers for 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 -j32 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 succeeded for nvidia
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: error processing package linux-image-7.0.0-28-generic (--configure):
installed linux-image-7.0.0-28-generic package post-installation script subprocess returned error exit status 11
Errors were encountered while processing:
linux-headers-7.0.0-28-generic
linux-image-7.0.0-28-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
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
As a newbie user, can I know if its safe to run updates? I am not sure if I can handle it if the system gets broken totally... Whats the main reasoins for this? What to look for and what to avoid?
I know thats av ery general question, but I wouldnt know how to ask it differently...
Or is there another thread or even tutorial how to handle the "update topic?
One thread about the current kernel update problem is pinned at the top of the thread list.
If you don't want to take the risk, it's best not to install the kernel 7.0 updates at this time, stay with kernel 6.17 and wait until two or three updates will have been released for the new kernel. In update-manager, you can deselect the kernel 7.0 updates if any are available there, so that you recieve all other updates but not the kernel 7.0.
Thank you. It seems I am on 6.17 still, but the update manager say I need to reboot for some changes to occur. Might be the Kernel update as I run sudo apt update & upgrade frequently as I thought thats generally recommended
Can I do something (easily...) about that at this stage?
You can also simply access Zorin's Advanced Options every time you boot up and select a kernel from there. If you don't reboot that often, this is the easiest way if booting with older kernels is only temporary. It's just something that can happen quickly: you might forget it.
Hmm ... The Sentence ''Der Rechner muss zum Abschließen der Aktualisierungen neu gestartet werden.'' makes me a bit ... cautious. I got the same Update and I didn't had to reboot.
When You type in Terminal sudo apt update && sudo apt upgrade what Output do You get? Don't apply any Updates. Only show the Output.
Again, I think the reboot comes from the updates before and is still "open".
I just saw that my lat terminal was still open, seems there is the Kernel update included:
Zusammenfassung
sudo apt upgrade
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Paketaktualisierung (Upgrade) wird berechnet… Fertig
Das folgende Paket wurde automatisch installiert und wird nicht mehr benötigt:
libfwupd2
Verwenden Sie »sudo apt autoremove«, um es zu entfernen.
Die folgenden NEUEN Pakete werden installiert:
libllvm19 linux-headers-7.0.0-28-generic linux-hwe-7.0-headers-7.0.0-28
linux-hwe-7.0-tools-7.0.0-28 linux-image-7.0.0-28-generic
linux-modules-7.0.0-28-generic linux-tools-7.0.0-28-generic
Die folgenden Pakete werden aktualisiert (Upgrade):
libntfs-3g89t64 linux-generic-hwe-24.04 linux-headers-generic-hwe-24.04
linux-image-generic-hwe-24.04 linux-libc-dev linux-tools-common ntfs-3g tar
vivaldi-stable
9 aktualisiert, 7 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 377 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 482 MB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n] j
Holen:1 Index of /ubuntu/ noble-updates/main amd64 tar amd64 1.35+dfsg-3ubuntu0.3 [256 kB]
Holen:2 Index of /stable/deb/ stable/main amd64 vivaldi-stable amd64 8.1.4087.55-1 [132 MB]
Holen:3 Index of /ubuntu/ noble-updates/main amd64 ntfs-3g amd64 1:2022.10.3-1.2ubuntu3.2 [406 kB]
Holen:4 Index of /ubuntu/ noble-updates/main amd64 libntfs-3g89t64 amd64 1:2022.10.3-1.2ubuntu3.2 [160 kB]
Holen:5 Index of /ubuntu/ noble-updates/main amd64 libllvm19 amd64 1:19.1.1-1ubuntu1~24.04.2 [28,7 MB]
Holen:6 Index of /ubuntu/ noble-updates/main amd64 linux-modules-7.0.0-28-generic amd64 7.0.0-28.28~24.04.1 [168 MB]
Holen:7 Index of /ubuntu/ noble-updates/main amd64 linux-image-7.0.0-28-generic amd64 7.0.0-28.28~24.04.1 [16,7 MB]
Holen:8 Index of /ubuntu/ noble-updates/main amd64 linux-generic-hwe-24.04 amd64 7.0.0-28.28~24.04.1 [1.726 B]
Holen:9 Index of /ubuntu/ noble-updates/main amd64 linux-image-generic-hwe-24.04 amd64 7.0.0-28.28~24.04.1 [2.324 B]
Holen:10 Index of /ubuntu/ noble-updates/main amd64 linux-hwe-7.0-headers-7.0.0-28 all 7.0.0-28.28~24.04.1 [14,8 MB]
Holen:11 Index of /ubuntu/ noble-updates/main amd64 linux-headers-7.0.0-28-generic amd64 7.0.0-28.28~24.04.1 [4.176 kB]
Holen:12 Index of /ubuntu/ noble-updates/main amd64 linux-headers-generic-hwe-24.04 amd64 7.0.0-28.28~24.04.1 [2.166 B]
Holen:13 Index of /ubuntu/ noble-updates/main amd64 linux-tools-common all 6.8.0-136.136 [416 kB]
Holen:14 Index of /ubuntu/ noble-updates/main amd64 linux-hwe-7.0-tools-7.0.0-28 amd64 7.0.0-28.28~24.04.1 [9.247 kB]
Holen:15 Index of /ubuntu/ noble-updates/main amd64 linux-libc-dev amd64 6.8.0-136.136 [1.575 kB]
Holen:16 Index of /ubuntu/ noble-updates/main amd64 linux-tools-7.0.0-28-generic amd64 7.0.0-28.28~24.04.1 [1.636 B]
Es wurden 377 MB in 19 min 18 s geholt (325 kB/s).
(Lese Datenbank ... 483312 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../tar_1.35+dfsg-3ubuntu0.3_amd64.deb ...
Entpacken von tar (1.35+dfsg-3ubuntu0.3) über (1.35+dfsg-3ubuntu0.2) ...
tar (1.35+dfsg-3ubuntu0.3) wird eingerichtet ...
(Lese Datenbank ... 483312 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../00-ntfs-3g_1%3a2022.10.3-1.2ubuntu3.2_amd64.d
eb ...
Entpacken von ntfs-3g (1:2022.10.3-1.2ubuntu3.2) über (1:2022.10.3-1.2ubuntu3.1)
...
Vorbereitung zum Entpacken von .../01-libntfs-3g89t64_1%3a2022.10.3-1.2ubuntu3.2
_amd64.deb ...
Entpacken von libntfs-3g89t64:amd64 (1:2022.10.3-1.2ubuntu3.2) über (1:2022.10.3
-1.2ubuntu3.1) ...
Vorbereitung zum Entpacken von .../02-vivaldi-stable_8.1.4087.55-1_amd64.deb ...
Entpacken von vivaldi-stable (8.1.4087.55-1) über (8.1.4087.53-1) ...
Vormals nicht ausgewähltes Paket libllvm19:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../03-libllvm19_1%3a19.1.1-1ubuntu1~24.04.2_amd6
4.deb ...
Entpacken von libllvm19:amd64 (1:19.1.1-1ubuntu1~24.04.2) ...
Vormals nicht ausgewähltes Paket linux-modules-7.0.0-28-generic wird gewählt.
Vorbereitung zum Entpacken von .../04-linux-modules-7.0.0-28-generic_7.0.0-28.28
~24.04.1_amd64.deb ...
Entpacken von linux-modules-7.0.0-28-generic (7.0.0-28.28~24.04.1) ...
Vormals nicht ausgewähltes Paket linux-image-7.0.0-28-generic wird gewählt.
Vorbereitung zum Entpacken von .../05-linux-image-7.0.0-28-generic_7.0.0-28.28~2
4.04.1_amd64.deb ...
Entpacken von linux-image-7.0.0-28-generic (7.0.0-28.28~24.04.1) ...
Vorbereitung zum Entpacken von .../06-linux-generic-hwe-24.04_7.0.0-28.28~24.04.
1_amd64.deb ...
Entpacken von linux-generic-hwe-24.04 (7.0.0-28.28~24.04.1) über (6.17.0-40.40~2
4.04.1) ...
Vorbereitung zum Entpacken von .../07-linux-image-generic-hwe-24.04_7.0.0-28.28~
24.04.1_amd64.deb ...
Entpacken von linux-image-generic-hwe-24.04 (7.0.0-28.28~24.04.1) über (6.17.0-4
0.40~24.04.1) ...
Vormals nicht ausgewähltes Paket linux-hwe-7.0-headers-7.0.0-28 wird gewählt.
Vorbereitung zum Entpacken von .../08-linux-hwe-7.0-headers-7.0.0-28_7.0.0-28.28
~24.04.1_all.deb ...
Entpacken von linux-hwe-7.0-headers-7.0.0-28 (7.0.0-28.28~24.04.1) ...
Vormals nicht ausgewähltes Paket linux-headers-7.0.0-28-generic wird gewählt.
Vorbereitung zum Entpacken von .../09-linux-headers-7.0.0-28-generic_7.0.0-28.28
~24.04.1_amd64.deb ...
Entpacken von linux-headers-7.0.0-28-generic (7.0.0-28.28~24.04.1) ...
Vorbereitung zum Entpacken von .../10-linux-headers-generic-hwe-24.04_7.0.0-28.2
8~24.04.1_amd64.deb ...
Entpacken von linux-headers-generic-hwe-24.04 (7.0.0-28.28~24.04.1) über (6.17.0
-40.40~24.04.1) ...
Vorbereitung zum Entpacken von .../11-linux-tools-common_6.8.0-136.136_all.deb .
..
Entpacken von linux-tools-common (6.8.0-136.136) über (6.8.0-134.134) ...
Vormals nicht ausgewähltes Paket linux-hwe-7.0-tools-7.0.0-28 wird gewählt.
Vorbereitung zum Entpacken von .../12-linux-hwe-7.0-tools-7.0.0-28_7.0.0-28.28~2
4.04.1_amd64.deb ...
Entpacken von linux-hwe-7.0-tools-7.0.0-28 (7.0.0-28.28~24.04.1) ...
Vorbereitung zum Entpacken von .../13-linux-libc-dev_6.8.0-136.136_amd64.deb ...
Entpacken von linux-libc-dev:amd64 (6.8.0-136.136) über (6.8.0-134.134) ...
Vormals nicht ausgewähltes Paket linux-tools-7.0.0-28-generic wird gewählt.
Vorbereitung zum Entpacken von .../14-linux-tools-7.0.0-28-generic_7.0.0-28.28~2
4.04.1_amd64.deb ...
Entpacken von linux-tools-7.0.0-28-generic (7.0.0-28.28~24.04.1) ...
libllvm19:amd64 (1:19.1.1-1ubuntu1~24.04.2) wird eingerichtet ...
linux-hwe-7.0-headers-7.0.0-28 (7.0.0-28.28~24.04.1) wird eingerichtet ...
libntfs-3g89t64:amd64 (1:2022.10.3-1.2ubuntu3.2) wird eingerichtet ...
linux-libc-dev:amd64 (6.8.0-136.136) wird eingerichtet ...
linux-headers-7.0.0-28-generic (7.0.0-28.28~24.04.1) wird eingerichtet ...
vivaldi-stable (8.1.4087.55-1) wird eingerichtet ...
ntfs-3g (1:2022.10.3-1.2ubuntu3.2) wird eingerichtet ...
linux-modules-7.0.0-28-generic (7.0.0-28.28~24.04.1) wird eingerichtet ...
linux-headers-generic-hwe-24.04 (7.0.0-28.28~24.04.1) wird eingerichtet ...
linux-tools-common (6.8.0-136.136) wird eingerichtet ...
linux-hwe-7.0-tools-7.0.0-28 (7.0.0-28.28~24.04.1) wird eingerichtet ...
linux-tools-7.0.0-28-generic (7.0.0-28.28~24.04.1) wird eingerichtet ...
linux-image-7.0.0-28-generic (7.0.0-28.28~24.04.1) wird eingerichtet ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-6.17.0-40-generic
I: /boot/initrd.img.old is now a symlink to initrd.img-6.17.0-40-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-7.0.0-28-generic
I: /boot/initrd.img is now a symlink to initrd.img-7.0.0-28-generic
linux-image-generic-hwe-24.04 (7.0.0-28.28~24.04.1) wird eingerichtet ...
linux-generic-hwe-24.04 (7.0.0-28.28~24.04.1) wird eingerichtet ...
Trigger für desktop-file-utils (0.27-2build1) werden verarbeitet ...
Trigger für initramfs-tools (0.142ubuntu25.8) werden verarbeitet ...
update-initramfs: Generating /boot/initrd.img-6.17.0-40-generic
Trigger für gnome-menus (3.36.0-1.1ubuntu3) werden verarbeitet ...
Trigger für libc-bin (2.39-0ubuntu8.7) werden verarbeitet ...
Trigger für man-db (2.12.0-4build2) werden verarbeitet ...
Trigger für mailcap (3.70+nmu1ubuntu1.24.04.1) werden verarbeitet ...
Trigger für linux-image-7.0.0-28-generic (7.0.0-28.28~24.04.1) werden verarbeite
t ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-7.0.0-28-generic
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/zorin/theme.txt
Found linux image: /boot/vmlinuz-7.0.0-28-generic
Found initrd image: /boot/initrd.img-7.0.0-28-generic
Found linux image: /boot/vmlinuz-6.17.0-40-generic
Found initrd image: /boot/initrd.img-6.17.0-40-generic
Found linux image: /boot/vmlinuz-6.17.0-35-generic
Found initrd image: /boot/initrd.img-6.17.0-35-generic
Found linux image: /boot/vmlinuz-6.17.0-14-generic
Found initrd image: /boot/initrd.img-6.17.0-14-generic
Found linux image: /boot/vmlinuz-6.8.0-101-generic
Found initrd image: /boot/initrd.img-6.8.0-101-generic
Found memtest86+x64 image: /boot/memtest86+x64.bin
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
But I dont want to keep you guys busy, I see there are some thread taking care of the issue already.
thanks for all you support, that makes it feel much better being someone relying on it...
And to be honest, I'll probably go for it and find it out.
I have an old system (amongst others) but most stuff is just working fine (Lenovo with Intel CPU).
To be clear to everyone that may be concerned about updating to the new Kernel, DO NOT WORRY! The reasons for my troubles are namely of my own doing. As a power user with a number custom settings and running applications, I am more likely to experience such problems than the typical user.
I have performed the Kernel update on at least 6 other machines for people that are local to me with absolutely "0"problems. Each of these other systems (Including my own), have shown a noticeable performance uplift amongst the other benefits of the newer kernel.
I would personally like to thank everyone that uses and supports Zorin OS, and especially those with the knowledge and experience that are so willing to help the rest of us when needed. You all are amazing, and I'm proud to be part of this community.
My Kernel update went fine in the end too!
After the first reboot I had some code on the display during the boot and then after login a black screen, so first I thought "everything is broken and I am such an idiot" but after another reboot everything is fine again. Thanks Zorin!
