Odd kernel behavior 5.8.48 won't boot at all and 5.4.0-70 has dependencies in 5.8.38

[oshunluvr]

Two odd items: First off a month ago or so I manually installed 5.8.0-36 to move beyond the 5.4 series. I had left the last 5.4 kernel 5.4.0-69, on the system as a backup. A couple weeks later, an upgrade came the normal way for 5.8.0-38.

I hadn't seen any update since them so I checked and sure enough -40 to -48 were available but not offered as install candidates via apt. However, I was offered an update to 5.4.0-69 to -70 (which was new - I check updates daily). I decided to install 5.8.0-48 and totally remove the 5.4 series.

The install of 5.8.0-48 was no problem but trying to remove 5.4.0-60 was a mess. at least a dozen cross-depends with the 5.8 series like cloud-tools, modules-extra and more. This make no sense to me as they are different kernels and shouldn't be blended like that AFAIK. Especially when the conflicts were labeled 5.4.0-. Basically it wouldn't let me remove linux-image-5.4.0-69-generic without installing linux-image-5.4.0-69-unsigned in it's place.

Not to be dictated to, I did it anyway and uninstalled everything relating to the 5.4 series.

Then I installed 5.8.0-48 and rebooted - which failed. No problem, rebooted into 5.8.0-38 and restored my morning snapshot (took all of 15 seconds - BTRFS rocks and EXT4 sucks) and rebooted. This time I just installed the 5.8.0-48 kernel and rebooted - still failed. So apparently 5.8.0-48 is broken with regards to Neon.

I haven't gone back and tried again to remove 5.4.0-70 now (I let it upgrade) but it sure seems odd that 54. and 5.8 are that closely tired. Seems wrong actually.

[FONT=monospace][COLOR=#54FF54][B]stuart@office[/B][/COLOR][COLOR=#000000]:[/COLOR][COLOR=#54FFFF][B]~[/B][/COLOR][COLOR=#000000]$ remove --purge linux-image-5.4.0-70-generic[/COLOR]
Reading package lists... Done
Building dependency tree        
Reading state information... Done
Starting pkgProblemResolver with broken count: 2
Starting 2 pkgProblemResolver with broken count: 2
Investigating (0) linux-modules-extra-5.4.0-70-generic:amd64 < 5.4.0-70.78 @ii mK Ib >
Broken linux-modules-extra-5.4.0-70-generic:amd64 Depends on linux-image-5.4.0-70-generic:amd64 < 5.4.0-70.78 @ii pmP >
  Considering linux-image-5.4.0-70-generic:amd64 10002 as a solution to linux-modules-extra-5.4.0-70-generic:amd64 1
Broken linux-modules-extra-5.4.0-70-generic:amd64 Depends on linux-image-unsigned-5.4.0-70-generic:amd64 < none | 5.4.0-70.78 @un uH >
  Considering linux-image-unsigned-5.4.0-70-generic:amd64 1 as a solution to linux-modules-extra-5.4.0-70-generic:amd64 1
  Try Installing linux-image-unsigned-5.4.0-70-generic:amd64 < none | 5.4.0-70.78 @un uH > before changing linux-modules-extra-5.4.0-70-generic:amd64
  Or group remove for linux-modules-extra-5.4.0-70-generic:amd64
Investigating (0) linux-image-generic:amd64 < 5.4.0.70.73 @ii mK Ib >
Broken linux-image-generic:amd64 Depends on linux-image-5.4.0-70-generic:amd64 < 5.4.0-70.78 @ii pmP >
  Considering linux-image-5.4.0-70-generic:amd64 10002 as a solution to linux-image-generic:amd64 0
  Removing linux-image-generic:amd64 rather than change linux-image-5.4.0-70-generic:amd64
Done
The following packages were automatically installed and are no longer required:
  amd64-microcode intel-microcode iucode-tool linux-modules-extra-5.4.0-67-generic thermald
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  linux-image-unsigned-5.4.0-70-generic
Suggested packages:
  fdutils linux-doc | linux-source-5.4.0 linux-tools
The following packages will be REMOVED:
  linux-image-5.4.0-70-generic* linux-image-generic* linux-modules-extra-5.4.0-70-generic*
The following NEW packages will be installed:
  linux-image-unsigned-5.4.0-70-generic
0 upgraded, 1 newly installed, 3 to remove and 0 not upgraded.
Need to get 9,004 kB of archives.
After this operation, 202 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

[/FONT]

[claydoh]

How specifically did you install the 5.8? Using the linux-image-generic-hwe-20.04 meta-package?

I am still confused a little, but that is not unusual for me today (both a and a )

Here is my output, showing the expected removals of the meta-packages involved with the 5.4.0-70

$ sudo apt purge linux-image-5.4.0-70-generic
[sudo] password for claydoh:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Starting pkgProblemResolver with broken count: 2
Starting 2 pkgProblemResolver with broken count: 2
Investigating (0) linux-modules-extra-5.4.0-70-generic:amd64 < 5.4.0-70.78 @ii mK Ib >
Broken linux-modules-extra-5.4.0-70-generic:amd64 Depends on linux-image-5.4.0-70-generic:amd64 < 5.4.0-70.78 @ii pmP >
Considering linux-image-5.4.0-70-generic:amd64 10002 as a solution to linux-modules-extra-5.4.0-70-generic:amd64 2
Broken linux-modules-extra-5.4.0-70-generic:amd64 Depends on linux-image-unsigned-5.4.0-70-generic:amd64 < none | 5.4.0-70.78 @un uH>
Considering linux-image-unsigned-5.4.0-70-generic:amd64 1 as a solution to linux-modules-extra-5.4.0-70-generic:amd64 2
Try Installing linux-image-unsigned-5.4.0-70-generic:amd64 < none | 5.4.0-70.78 @un uH > before changing linux-modules-extra-5.4.0-70-generic:amd64
Or group remove for linux-modules-extra-5.4.0-70-generic:amd64
Investigating (0) linux-image-generic:amd64 < 5.4.0.70.73 @ii mK Ib >
Broken linux-image-generic:amd64 Depends on linux-image-5.4.0-70-generic:amd64 < 5.4.0-70.78 @ii pmP >
Considering linux-image-5.4.0-70-generic:amd64 10002 as a solution to linux-image-generic:amd64 1
Removing linux-image-generic:amd64 rather than change linux-image-5.4.0-70-generic:amd64
Investigating (0) linux-generic:amd64 < 5.4.0.70.73 @ii mK Ib >
Broken linux-generic:amd64 Depends on linux-image-generic:amd64 < 5.4.0.70.73 @ii mR > (= 5.4.0.70.73)
Considering linux-image-generic:amd64 1 as a solution to linux-generic:amd64 0
Removing linux-generic:amd64 rather than change linux-image-generic:amd64
Done
The following additional packages will be installed:
linux-image-unsigned-5.4.0-70-generic
Suggested packages:
fdutils linux-doc | linux-source-5.4.0 linux-tools
The following packages will be REMOVED
linux-generic* linux-image-5.4.0-70-generic* linux-image-generic* linux-modules-extra-5.4.0-70-generic*
The following NEW packages will be installed
linux-image-unsigned-5.4.0-70-generic
0 to upgrade, 1 to newly install, 4 to remove and 0 not to upgrade.
Need to get 9,004 kB of archives.
After this operation, 202 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

I don't have anything related to 5.4.0-60 on my system., though I do notice that since installing the HWE metapackage, autotremove stopped removing older 5.4 kernels, so I had a few: -56, 62, 64, 65, 66, and 70, plus the related modules, modules-extras, etc.
I have had no issue booting my PC with the current 5.8 kernel, and autoremove is keeping 6?? kernels there.

I do wish that Neon would move to the official HWE track like I think they did with 18.04, or at least move the iso to a 20.04.2 base, and thus get off the 5.4 track altogether. I am ready for a clean install here on my PC. or maybe Ill look at 20.04.2's apt and autoremove configs, look for differences and apply them to the clean Neon.

[oshunluvr]

No, I didn't install the meta package so I tried that. It produced this error

[FONT=monospace][COLOR=#000000]depmod: WARNING: could not open modules.order at /var/tmp/mkinitramfs_i5dObL/lib/modules/5.8.0-48-generic: No such file or directory[/COLOR]
depmod: WARNING: could not open modules.builtin at /var/tmp/mkinitramfs_i5dObL/lib/modules/5.8.0-48-generic: No such file or directory

[/FONT]

which might be why I couldn't boot it. Still working on it.

[oshunluvr]

OK, weird I installed a couple more 5.8 meta packages, then updated initramfs and got this:

[FONT=monospace][COLOR=#000000]depmod: WARNING: could not open modules.order at /var/tmp/mkinitramfs_VoofJK/lib/modules/5.8.0-48-generic: No such file or directory[/COLOR]
depmod: WARNING: could not open modules.builtin at /var/tmp/mkinitramfs_VoofJK/lib/modules/5.8.0-48-generic: No such file or directory

[/FONT]

Then again and got:

[FONT=monospace][COLOR=#000000]depmod: WARNING: could not open modules.order at /var/tmp/mkinitramfs_OYwa0D/lib/modules/5.8.0-48-generic: No such file or directory[/COLOR]
depmod: WARNING: could not open modules.builtin at /var/tmp/mkinitramfs_OYwa0D/lib/modules/5.8.0-48-generic: No such file or directory

[/FONT]

The letters in the middle after "mkinitramfs_"appear to be random.

[oshunluvr]

Tried a couple things and discovered this:

[FONT=monospace][COLOR=#54FF54][B]stuart@office[/B][/COLOR][COLOR=#000000]:[/COLOR][COLOR=#54FFFF][B]~[/B][/COLOR][COLOR=#000000]$ ll /lib/modules/5.8.0-38-generic/[/COLOR]
total 5992
drwxr-xr-x 1 root root     472 Mar 27 09:57 [COLOR=#54FFFF][B].[/B][/COLOR][COLOR=#000000]/[/COLOR]
drwxr-xr-x 1 root root     160 Mar 27 09:37 [COLOR=#54FFFF][B]..[/B][/COLOR][COLOR=#000000]/[/COLOR]
lrwxrwxrwx 1 root root      39 Jan 12 10:15 [COLOR=#FFFF54][B]build[/B][/COLOR][COLOR=#000000] -> [/COLOR][COLOR=#54FFFF][B]/usr/src/linux-headers-5.8.0-38-generic[/B][/COLOR][COLOR=#000000]/[/COLOR]
drwxr-xr-x 1 root root       0 Jan 12 10:15 [COLOR=#54FFFF][B]initrd[/B][/COLOR][COLOR=#000000]/[/COLOR]
drwxr-xr-x 1 root root     118 Jan 14 15:38 [COLOR=#54FFFF][B]kernel[/B][/COLOR][COLOR=#000000]/[/COLOR]
-rw-r--r-- 1 root root 1423207 Mar 27 09:57 modules.alias
-rw-r--r-- 1 root root 1402313 Mar 27 09:57 modules.alias.bin
-rw-r--r-- 1 root root    9975 Jan 12 10:15 modules.builtin
-rw-r--r-- 1 root root   25773 Mar 27 09:57 modules.builtin.alias.bin
-rw-r--r-- 1 root root   12521 Mar 27 09:57 modules.builtin.bin
-rw-r--r-- 1 root root   77263 Jan 12 10:15 modules.builtin.modinfo
-rw-r--r-- 1 root root  649022 Mar 27 09:57 modules.dep
-rw-r--r-- 1 root root  900049 Mar 27 09:57 modules.dep.bin
-rw-r--r-- 1 root root     330 Mar 27 09:57 modules.devname
-rw-r--r-- 1 root root  229525 Jan 12 10:15 modules.order
-rw-r--r-- 1 root root     885 Mar 27 09:57 modules.softdep
-rw-r--r-- 1 root root  616750 Mar 27 09:57 modules.symbols
-rw-r--r-- 1 root root  752670 Mar 27 09:57 modules.symbols.bin
drwxr-xr-x 1 root root      74 Jan 14 15:38 [COLOR=#54FFFF][B]vdso[/B][/COLOR][COLOR=#000000]/[/COLOR]

[/FONT]

vs this

[FONT=monospace][COLOR=#54FF54][B]stuart@office[/B][/COLOR][COLOR=#000000]:[/COLOR][COLOR=#54FFFF][B]~[/B][/COLOR][COLOR=#000000]$ ll /lib/modules/5.8.0-48-generic/[/COLOR]
total 4296
drwxr-xr-x 1 root root     350 Mar 27 09:40 [COLOR=#54FFFF][B].[/B][/COLOR][COLOR=#000000]/[/COLOR]
drwxr-xr-x 1 root root     160 Mar 27 09:37 [COLOR=#54FFFF][B]..[/B][/COLOR][COLOR=#000000]/[/COLOR]
lrwxrwxrwx 1 root root      39 Mar 20 09:05 [COLOR=#FFFF54][B]build[/B][/COLOR][COLOR=#000000] -> [/COLOR][COLOR=#54FFFF][B]/usr/src/linux-headers-5.8.0-48-generic[/B][/COLOR][COLOR=#000000]/[/COLOR]
drwxr-xr-x 1 root root     112 Mar 27 09:37 [COLOR=#54FFFF][B]kernel[/B][/COLOR][COLOR=#000000]/[/COLOR]
-rw-r--r-- 1 root root 1276451 Mar 27 09:38 modules.alias
-rw-r--r-- 1 root root 1252468 Mar 27 09:38 modules.alias.bin
-rw-r--r-- 1 root root       0 Mar 27 09:38 modules.builtin.alias.bin
-rw-r--r-- 1 root root       0 Mar 27 09:38 modules.builtin.bin
-rw-r--r-- 1 root root  431963 Mar 27 09:38 modules.dep
-rw-r--r-- 1 root root  642861 Mar 27 09:38 modules.dep.bin
-rw-r--r-- 1 root root     114 Mar 27 09:38 modules.devname
-rw-r--r-- 1 root root     426 Mar 27 09:38 modules.softdep
-rw-r--r-- 1 root root  344251 Mar 27 09:38 modules.symbols
-rw-r--r-- 1 root root  429916 Mar 27 09:38 modules.symbols.bin

[/FONT]

There's a lot missing from the 48 kernel modules

[claydoh]

I dunno.
Though at some point since updating to the latest 5.8 (and probably the latest 5.4) on my PC, I have lost bluetooth altogether, no matter which kernel I use. I have a realtek one using the rtl8821ce, which needs a dkms drver package, or a dkms build from git. Flaky at times but usually working and fixable.

[claydoh]

Odd. Mine looks the same as my other 5.8 kernels:

claydoh@hp:~$ ls -la /lib/modules/5.8.0-48-generic/
total 6012
drwxr-xr-x  6 root root    4096 Mar 27 09:36 .
drwxr-xr-x 11 root root    4096 Mar 26 17:47 ..
lrwxrwxrwx  1 root root      39 Mar 20 09:05 build -> /usr/src/linux-headers-5.8.0-48-generic
drwxr-xr-x  2 root root    4096 Mar 20 09:05 initrd
drwxr-xr-x 15 root root    4096 Mar 24 07:41 kernel
-rw-r--r--  1 root root 1425343 Mar 27 09:36 modules.alias
-rw-r--r--  1 root root 1404478 Mar 27 09:36 modules.alias.bin
-rw-r--r--  1 root root    9975 Mar 20 09:05 modules.builtin
-rw-r--r--  1 root root   25773 Mar 27 09:36 modules.builtin.alias.bin
-rw-r--r--  1 root root   12521 Mar 27 09:36 modules.builtin.bin
-rw-r--r--  1 root root   77339 Mar 20 09:05 modules.builtin.modinfo
-rw-r--r--  1 root root  649076 Mar 27 09:36 modules.dep
-rw-r--r--  1 root root  900127 Mar 27 09:36 modules.dep.bin
-rw-r--r--  1 root root     330 Mar 27 09:36 modules.devname
-rw-r--r--  1 root root  229525 Mar 20 09:05 modules.order
-rw-r--r--  1 root root     885 Mar 27 09:36 modules.softdep
-rw-r--r--  1 root root  616586 Mar 27 09:36 modules.symbols
-rw-r--r--  1 root root  752628 Mar 27 09:36 modules.symbols.bin
drwxr-xr-x  2 root root    4096 Mar 27 09:36 updates
drwxr-xr-x  3 root root    4096 Mar 24 07:41 vdso

and my oldest:

claydoh@hp:~$ ls -la /lib/modules/5.8.0-40-generic/
total 6008
drwxr-xr-x  5 root root    4096 Mar  1 16:53 .
drwxr-xr-x 11 root root    4096 Mar 26 17:47 ..
lrwxrwxrwx  1 root root      39 Jan 15 06:09 build -> /usr/src/linux-headers-5.8.0-40-generic
drwxr-xr-x  2 root root    4096 Jan 15 06:09 initrd
drwxr-xr-x 15 root root    4096 Jan 20 13:54 kernel
-rw-r--r--  1 root root 1423207 Mar  1 16:53 modules.alias
-rw-r--r--  1 root root 1402313 Mar  1 16:53 modules.alias.bin
-rw-r--r--  1 root root    9975 Jan 15 06:09 modules.builtin
-rw-r--r--  1 root root   25773 Mar  1 16:53 modules.builtin.alias.bin
-rw-r--r--  1 root root   12521 Mar  1 16:53 modules.builtin.bin
-rw-r--r--  1 root root   77263 Jan 15 06:09 modules.builtin.modinfo
-rw-r--r--  1 root root  649022 Mar  1 16:53 modules.dep
-rw-r--r--  1 root root  900049 Mar  1 16:53 modules.dep.bin
-rw-r--r--  1 root root     330 Mar  1 16:53 modules.devname
-rw-r--r--  1 root root  229525 Jan 15 06:09 modules.order
-rw-r--r--  1 root root     885 Mar  1 16:53 modules.softdep
-rw-r--r--  1 root root  616750 Mar  1 16:53 modules.symbols
-rw-r--r--  1 root root  752670 Mar  1 16:53 modules.symbols.bin
drwxr-xr-x  3 root root    4096 Jan 20 13:54 vdso

[oshunluvr]

OK, re-installing ALL the 5.8.0-48 packages added the missing modules and initramfs built without error.

[oshunluvr]

Boots fine to 48 now but still weird circular depends:

[FONT=monospace][COLOR=#54FF54][B]stuart@office[/B][/COLOR][COLOR=#000000]:[/COLOR][COLOR=#54FFFF][B]~[/B][/COLOR][COLOR=#000000]$ remove --purge linux-cloud-tools-common[/COLOR]
Reading package lists... Done
Building dependency tree        
Reading state information... Done
Starting pkgProblemResolver with broken count: 4
Starting 2 pkgProblemResolver with broken count: 4
Investigating (0) linux-hwe-5.8-cloud-tools-5.8.0-45:amd64 < 5.8.0-45.51~20.04.1 @ii mK Ib >
Broken linux-hwe-5.8-cloud-tools-5.8.0-45:amd64 Depends on linux-cloud-tools-common:amd64 < 5.4.0-70.78 @ii pmP >
  Considering linux-cloud-tools-common:amd64 10004 as a solution to linux-hwe-5.8-cloud-tools-5.8.0-45:amd64 1
  Removing linux-hwe-5.8-cloud-tools-5.8.0-45:amd64 rather than change linux-cloud-tools-common:amd64
Investigating (0) linux-hwe-5.8-cloud-tools-5.8.0-48:amd64 < 5.8.0-48.54~20.04.1 @ii mK Ib >
Broken linux-hwe-5.8-cloud-tools-5.8.0-48:amd64 Depends on linux-cloud-tools-common:amd64 < 5.4.0-70.78 @ii pmP >
  Considering linux-cloud-tools-common:amd64 10004 as a solution to linux-hwe-5.8-cloud-tools-5.8.0-48:amd64 1
  Removing linux-hwe-5.8-cloud-tools-5.8.0-48:amd64 rather than change linux-cloud-tools-common:amd64
Investigating (0) linux-hwe-5.8-cloud-tools-5.8.0-36:amd64 < 5.8.0-36.40~20.04.1 @ii mK Ib >
Broken linux-hwe-5.8-cloud-tools-5.8.0-36:amd64 Depends on linux-cloud-tools-common:amd64 < 5.4.0-70.78 @ii pmP >
  Considering linux-cloud-tools-common:amd64 10004 as a solution to linux-hwe-5.8-cloud-tools-5.8.0-36:amd64 1
  Removing linux-hwe-5.8-cloud-tools-5.8.0-36:amd64 rather than change linux-cloud-tools-common:amd64
Investigating (0) linux-hwe-5.8-cloud-tools-5.8.0-38:amd64 < 5.8.0-38.43~20.04.1 @ii mK Ib >
Broken linux-hwe-5.8-cloud-tools-5.8.0-38:amd64 Depends on linux-cloud-tools-common:amd64 < 5.4.0-70.78 @ii pmP >
  Considering linux-cloud-tools-common:amd64 10004 as a solution to linux-hwe-5.8-cloud-tools-5.8.0-38:amd64 1
  Removing linux-hwe-5.8-cloud-tools-5.8.0-38:amd64 rather than change linux-cloud-tools-common:amd64
Investigating (0) linux-cloud-tools-5.8.0-45-generic:amd64 < 5.8.0-45.51~20.04.1 @ii mK Ib >
Broken linux-cloud-tools-5.8.0-45-generic:amd64 Depends on linux-hwe-5.8-cloud-tools-5.8.0-45:amd64 < 5.8.0-45.51~20.04.1 @ii mR >
  Considering linux-hwe-5.8-cloud-tools-5.8.0-45:amd64 1 as a solution to linux-cloud-tools-5.8.0-45-generic:amd64 0
  Removing linux-cloud-tools-5.8.0-45-generic:amd64 rather than change linux-hwe-5.8-cloud-tools-5.8.0-45:amd64
Investigating (0) linux-cloud-tools-5.8.0-48-generic:amd64 < 5.8.0-48.54~20.04.1 @ii mK Ib >
Broken linux-cloud-tools-5.8.0-48-generic:amd64 Depends on linux-hwe-5.8-cloud-tools-5.8.0-48:amd64 < 5.8.0-48.54~20.04.1 @ii mR >
  Considering linux-hwe-5.8-cloud-tools-5.8.0-48:amd64 1 as a solution to linux-cloud-tools-5.8.0-48-generic:amd64 0
  Removing linux-cloud-tools-5.8.0-48-generic:amd64 rather than change linux-hwe-5.8-cloud-tools-5.8.0-48:amd64
Investigating (0) linux-cloud-tools-5.8.0-36-generic:amd64 < 5.8.0-36.40~20.04.1 @ii mK Ib >
Broken linux-cloud-tools-5.8.0-36-generic:amd64 Depends on linux-hwe-5.8-cloud-tools-5.8.0-36:amd64 < 5.8.0-36.40~20.04.1 @ii mR >
  Considering linux-hwe-5.8-cloud-tools-5.8.0-36:amd64 1 as a solution to linux-cloud-tools-5.8.0-36-generic:amd64 0
  Removing linux-cloud-tools-5.8.0-36-generic:amd64 rather than change linux-hwe-5.8-cloud-tools-5.8.0-36:amd64
Investigating (0) linux-cloud-tools-5.8.0-38-generic:amd64 < 5.8.0-38.43~20.04.1 @ii mK Ib >
Broken linux-cloud-tools-5.8.0-38-generic:amd64 Depends on linux-hwe-5.8-cloud-tools-5.8.0-38:amd64 < 5.8.0-38.43~20.04.1 @ii mR >
  Considering linux-hwe-5.8-cloud-tools-5.8.0-38:amd64 1 as a solution to linux-cloud-tools-5.8.0-38-generic:amd64 0
  Removing linux-cloud-tools-5.8.0-38-generic:amd64 rather than change linux-hwe-5.8-cloud-tools-5.8.0-38:amd64
Done
The following packages will be REMOVED:
  linux-cloud-tools-5.8.0-36-generic* linux-cloud-tools-5.8.0-38-generic* linux-cloud-tools-5.8.0-45-generic* linux-cloud-tools-5.8.0-48-generic*
  linux-cloud-tools-common* linux-hwe-5.8-cloud-tools-5.8.0-36* linux-hwe-5.8-cloud-tools-5.8.0-38* linux-hwe-5.8-cloud-tools-5.8.0-45*
  linux-hwe-5.8-cloud-tools-5.8.0-48*
0 upgraded, 0 newly installed, 9 to remove and 0 not upgraded.
After this operation, 2,952 kB disk space will be freed.
Do you want to continue? [Y/n] 

[/FONT]