Suppose to be “dumb” single quotes around print statement. Discourse substitutes “smart” quotes which fails. Manually type in the single quotes and it should work.
$ apt list ~i~nhwe
will produce the above metapackages I listed plus the actual image and header (and possibly module or tools ) packages pulled in by them.
thx, what do you think, everything should be there concerning 6.17 I guess :
(the 6.17 packages pasted only) :
linux-generic-hwe-24.04/noble-updates,noble-security,now 6.17.0-14.14~24.04.1 amd64 [geïnstalleerd]
linux-headers-generic-hwe-24.04/noble-updates,noble-security,now 6.17.0-14.14~24.04.1 amd64 [geïnstalleerd,automatisch]
linux-hwe-6.17-headers-6.17.0-14/noble-updates,noble-updates,noble-security,noble-security,now 6.17.0-14.14~24.04.1 all [geïnstalleerd,automatisch]
linux-hwe-6.17-tools-6.17.0-14/noble-updates,noble-security,now 6.17.0-14.14~24.04.1 amd64 [geïnstalleerd,automatisch]
linux-image-generic-hwe-24.04/noble-updates,noble-security,now 6.17.0-14.14~24.04.1 amd64 [geïnstalleerd]
Should that be a problem that linux-image-generic-hwe-24.04 is ‘installed’ and not ‘installed automatic’ ?
It would be nice if this was on the panic screen…
Looks ok now.
No, not really. That mostly becomes relevant for autoremoval purposes. You can use
$ sudo apt-mark auto linux-image-generic-hwe-24.04
to set it back to automatically installed. Use
$ sudo apt-mark minimize-manual
to reset all packages which should be marked auto-installed but for some reason were marked manual at some point or other.
Great! thanks a lot, learned a lot today :
most important for me : don’t touch anything (if you don’t know what’s really happening) 
“It would be nice if this was on the panic screen…” I totally agree! Having never encountered a panic error before, I switched kernels in GRUB but then purged all vestiges of the new kernel. Now I read that purging the faulty kernel sets me up for more headaches in the future. Why could this not be on the panic message? A few simple instructions or even a pointer to a help site would have been tremendous help.
Okay, now I think I shot myself in the foot - it appears that I may have clobbered the 6.17 headers:
mg@MGDesktopUnity:~$ apt list ~i~nhwe
Listing… Done
linux-hwe-6.11-headers-6.11.0-29/noble-security,noble-security,noble-updates,noble-updates,now 6.11
.0-29.29~24.04.1 all [installed,automatic]
linux-hwe-6.14-headers-6.14.0-36/noble-security,noble-security,noble-updates,noble-updates,now 6.14
.0-36.36~24.04.1 all [installed,automatic]
linux-hwe-6.14-headers-6.14.0-37/noble-security,noble-security,noble-updates,noble-updates,now 6.14
.0-37.37~24.04.1 all [installed,automatic]
linux-hwe-6.14-tools-6.14.0-36/noble-security,noble-updates,now 6.14.0-36.36~24.04.1 amd64 [install
ed,automatic]
linux-hwe-6.14-tools-6.14.0-37/noble-security,noble-updates,now 6.14.0-37.37~24.04.1 amd64 [install
ed,automatic]
systemd-hwe-hwdb/noble-updates,noble-updates,now 255.1.6 all [installed,automatic]
N: Ignoring file ‘ubuntu.sources.save.1’ in directory ‘/etc/apt/sources.list.d/’ as it has an inval
id filename extension
N: Ignoring file ‘ubuntu.sources.save.2’ in directory ‘/etc/apt/sources.list.d/’ as it has an inval
id filename extension
mg@MGDesktopUnity:~$
Can I get the 6.17 headers back. It sure would be nice if the Kernel panic screen would be more explanatory.
Thanks,
M…..
Maybe I am okay:
mg@MGDesktopUnity:~$ apt list ~i~nhwe
Listing… Done
linux-hwe-6.11-headers-6.11.0-29/noble-security,noble-security,noble-updates,noble-updates,now 6.11
.0-29.29~24.04.1 all [installed,automatic]
linux-hwe-6.14-headers-6.14.0-36/noble-security,noble-security,noble-updates,noble-updates,now 6.14
.0-36.36~24.04.1 all [installed,automatic]
linux-hwe-6.14-headers-6.14.0-37/noble-security,noble-security,noble-updates,noble-updates,now 6.14
.0-37.37~24.04.1 all [installed,automatic]
linux-hwe-6.14-tools-6.14.0-36/noble-security,noble-updates,now 6.14.0-36.36~24.04.1 amd64 [install
ed,automatic]
linux-hwe-6.14-tools-6.14.0-37/noble-security,noble-updates,now 6.14.0-37.37~24.04.1 amd64 [install
ed,automatic]
systemd-hwe-hwdb/noble-updates,noble-updates,now 255.1.6 all [installed,automatic]
N: Ignoring file ‘ubuntu.sources.save.1’ in directory ‘/etc/apt/sources.list.d/’ as it has an inval
id filename extension
N: Ignoring file ‘ubuntu.sources.save.2’ in directory ‘/etc/apt/sources.list.d/’ as it has an inval
id filename extensionmg@MGDesktopUnity:~$ apt info linux-generic-hwe-24.04
Package: linux-generic-hwe-24.04
Version: 6.17.0-14.14~24.04.1
Priority: optional
Section: kernel
Source: linux-meta-hwe-6.17
Origin: Ubuntu
Maintainer: Ubuntu Kernel Team kernel-team@lists.ubuntu.com
Bugs: OpenID transaction in progress
Installed-Size: 9,216 B
Depends: linux-image-generic-hwe-24.04 (= 6.17.0-14.14~24.04.1), linux-headers-generic-hwe-24.04 (=
6.17.0-14.14~24.04.1)
Recommends: linux-tools-6.17.0-14-generic, ubuntu-kernel-accessories
Download-Size: 1,728 B
APT-Sources: http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages
Description: Complete Generic Linux kernel and headers
This package will always depend on the latest complete generic Linux kernel
and headers.N: Ignoring file ‘ubuntu.sources.save.1’ in directory ‘/etc/apt/sources.list.d/’ as it has an inval
id filename extension
N: Ignoring file ‘ubuntu.sources.save.2’ in directory ‘/etc/apt/sources.list.d/’ as it has an inval
id filename extension
N: There is 1 additional record. Please use the ‘-a’ switch to see it
mg@MGDesktopUnity:~$
mg@MGDesktopUnity:~$
mg@MGDesktopUnity:~$ apt info linux-image-generic-hwe-24.04
Package: linux-image-generic-hwe-24.04
Version: 6.17.0-14.14~24.04.1
Priority: optional
Section: kernel
Source: linux-meta-hwe-6.17
Origin: Ubuntu
Maintainer: Ubuntu Kernel Team kernel-team@lists.ubuntu.com
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 9,216 B
Provides: ivsc-modules (= 0~git202311021215.73a044d9), spl-modules (= 2.3.4-1ubuntu2), v4l2loopback
-modules (= 0.15.0-0ubuntu2), virtualbox-guest-modules (= 6.17.0-14), wireguard-modules (= 1.0.0),
zfs-modules (= 2.3.4-1ubuntu2)
Depends: linux-image-6.17.0-14-generic, linux-modules-extra-6.17.0-14-generic, linux-firmware, inte
l-microcode, amd64-microcode
Recommends: thermald
Download-Size: 2,304 B
APT-Sources: Index of /ubuntu noble-security/main amd64 Packages
Description: Generic Linux kernel image
This package will always depend on the latest generic kernel image
available.N: Ignoring file ‘ubuntu.sources.save.1’ in directory ‘/etc/apt/sources.list.d/’ as it has an inval
id filename extension
N: Ignoring file ‘ubuntu.sources.save.2’ in directory ‘/etc/apt/sources.list.d/’ as it has an inval
id filename extension
N: There is 1 additional record. Please use the ‘-a’ switch to see it
mg@MGDesktopUnity:~$How does this look ? Maybe the Header for 6.17 is there.
Thanks,
M…
Let’s check your apt sources first.
$ add-apt-repository -L |grep -2 URIs
If the output looks similar to below (the url for main archive server may be different depending on your location), then you can delete the extraneous ubuntu.sources.save.* files.
Types: deb
URIs: http://security.ubuntu.com/ubuntu/
Suites: noble-security
Components: restricted main multiverse universe
--
Types: deb
URIs: http://us.archive.ubuntu.com/ubuntu/
Suites: noble noble-updates
Components: main universe restricted multiverse
Check for broken packages. (The second one is the one that’ll catch something, but the others might provide some other useful information. If the output is the same, just post result from which ever is the most informative)
$ dpkg -C
$ dpkg -l |grep -v ^ii
$ apt list ~b
$ sudo apt-get check
Check for installed header packages
$ apt list ~i~nheaders |cut -d/ -f1
Yikes, looks like I am missing 6.17 headers:
apt list ~i~nheaders |cut -d/ -f1
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Listing…
linux-headers-6.11.0-29-generic
linux-headers-6.14.0-36-generic
linux-headers-6.14.0-37-generic
linux-hwe-6.11-headers-6.11.0-29
linux-hwe-6.14-headers-6.14.0-36
linux-hwe-6.14-headers-6.14.0-37
Can get them back ?
Thanks,
M…
$ sudo apt install linux-headers-generic-hwe-24.04
I got an error to get 6.17 back (I purged it 
)
*Sub-process /usr/bin/dpkg returned an error code (1)
*
What I have to do now to get back the 6.17.0.-14 kernel?
I did the following and it solved the problem for me:
dpkg -l | grep linux-image
sudo apt-get purge linux-image-6.17.0-14-generic
sudo apt-get purge linux-headers-6.17.0-14-generic
I’ve used the following steps for my solution attempt:
kernel panic please reboot your computer vfs unable to mount root fs on unknown-block(0 0)
ESC until it skipped the GRUB menu and dropped me into the grub> terminal.normal, pressed Enter, and then pressed ESC.6.14.0-37-generic.$ sudo su
apt update; apt upgrade -y; apt dist-upgrade -y; apt autoremove --purge -y; apt autoclean -y;
make -j12 KERNELRELEASE=6.17.0-14-generic -C /lib/modules/6.17.0-14-generic/buil
d M=/var/lib/dkms/virtualbox/7.0.16/build...(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/virtualbox-dkms
.0.crash'
Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)
Consult /var/lib/dkms/virtualbox/7.0.16/build/make.log for more information.
dkms autoinstall on 6.17.0-14-generic/x86_64 succeeded for evdi nvidia
dkms autoinstall on 6.17.0-14-generic/x86_64 failed for virtualbox(10)
Error! One or more modules failed to install during autoinstall.
apt-get remove --purge virtualbox
6.17.0-14 kernel:sudo apt-get purge linux-image-6.17.0-14-generic linux-headers-6.17.0-14-generic linux-image-generic-hwe-24.04
# rmdir: failed to remove '/lib/modules/6.17.0-14-generic': Directory not empty
rm -rf /lib/modules/6.17.0-14-generic
# just to be sure:
find . -name 6.17.0-14
Reboot.
$ sudo su
apt-get build-dep linux
apt update; apt upgrade -y; apt dist-upgrade -y; apt autoremove --purge -y; apt autoclean -y;
There is no sign of the 6.17 kernel anymore, even after repeating step 6. The build-dep I have installed in case it will be needed to recompile new kernel.
I had exactly the same issue.
In my case it was installed VirtualBox.
So you have to remove it
sudo apt remove virtualbox virtualbox-dkms
sudo apt --fix-broken install
sudo dpkg --configure -a
Problem solved.
You’ll need to first remedy what caused the error during 6.17’s package install. AFAIK, currently for 24.04.x people are having issues with the dkms kernel module building for the Virtualbox package in Ubuntu (v. 7.016), and/or the broadcom-sta-dkms wireless driver. If the error message indicates another source of the problem, you’ll need provide more information.
…and if you actually need virtualbox?… I guess: Reinstall it and revisit this same issue immediately or soon…
Well, there are not much options in this case.
You can try to install the newest Virtualbox version from their site. Maybe they already fixed the issue.
OR
Wait for a kernel fix and meanwhile use the previous one (6.14.0) by choosing it at startup.
Thanks. I have not installed Virtualbox. This was my output:
Pakketlijsten worden ingelezen… Klaar
Boom van vereisten wordt opgebouwd… Klaar
De statusinformatie wordt gelezen… Klaar
Pakket ‘virtualbox’ is niet geïnstalleerd, en wordt dus niet verwijderd
Pakket ‘virtualbox-dkms’ is niet geïnstalleerd, en wordt dus niet verwijderd
0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd.
2 niet volledig geïnstalleerd of verwijderd.
Na deze bewerking zal er 0 B extra schijfruimte gebruikt worden.
Instellen van linux-headers-6.17.0-14-generic (6.17.0-14.14~24.04.1) …
/etc/kernel/header_postinst.d/dkms:
Building module:
Cleaning build area…
make -j4 KERNELRELEASE=6.17.0-14-generic KVER=6.17.0-14-generic…(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists: ‘/var/crash/broadcom-sta-dkms.0.crash’
Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)
Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information.
dkms autoinstall on 6.17.0-14-generic/x86_64 failed for broadcom-sta(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dpkg: fout bij verwerken van pakket linux-headers-generic-hwe-24.04 (–configure):
vereistenproblemen - blijft ongeconfigureerd
Er is geen apport-verslag weggeschreven omdat de foutmelding aangeeft dat de fout het gevolg is van een eerdere mislukking.
Fouten gevonden tijdens verwerken van:
linux-headers-6.17.0-14-generic
linux-headers-generic-hwe-24.04
E: Sub-process /usr/bin/dpkg returned an error code (1)
dennie@MekBoek:~$ sudo apt --fix-broken install
Pakketlijsten worden ingelezen… Klaar
Boom van vereisten wordt opgebouwd… Klaar
De statusinformatie wordt gelezen… Klaar
0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd.
2 niet volledig geïnstalleerd of verwijderd.
Na deze bewerking zal er 0 B extra schijfruimte gebruikt worden.
Instellen van linux-headers-6.17.0-14-generic (6.17.0-14.14~24.04.1) …
/etc/kernel/header_postinst.d/dkms:
Building module:
Cleaning build area…
make -j4 KERNELRELEASE=6.17.0-14-generic KVER=6.17.0-14-generic…(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists: ‘/var/crash/broadcom-sta-dkms.0.crash’
Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)
Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information.
dkms autoinstall on 6.17.0-14-generic/x86_64 failed for broadcom-sta(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dpkg: fout bij verwerken van pakket linux-headers-generic-hwe-24.04 (–configure):
vereistenproblemen - blijft ongeconfigureerd
Er is geen apport-verslag weggeschreven omdat de foutmelding aangeeft dat de fout het gevolg is van een eerdere mislukking.
Fouten gevonden tijdens verwerken van:
linux-headers-6.17.0-14-generic
linux-headers-generic-hwe-24.04
E: Sub-process /usr/bin/dpkg returned an error code (1)
Hallo Davi, ik kan nederlands but I change to English, you have the same issue as many here with the broadcom-sta (Wifi-driver) in combination with the 6.17.0-14 kernel. I had the exact same issue as you describe, please take a look at this post, the solution solved it in 1 minute : BCM4360 driver works on 25.10 but not on 24.04.3 LTS - #17 by Jeremy31
best regards,