I think I may have too many kernels - need help

MAYBL8 · 15 March 2024 13:17

Here is what I am seeing from updating this morning:

( 8/13) Install DKMS modules
==> dkms install --no-depmod nvidia/550.54.14 -k 6.7.2-1-MANJARO
==> dkms install --no-depmod nvidia/550.54.14 -k 6.7.6-1-MANJARO
Module version 550.54.14 for nvidia.ko.zst
exactly matches what is already found in kernel 6.7.6-1-MANJARO.
DKMS will not replace this module.
You may override by specifying --force.
Module version 550.54.14 for nvidia-uvm.ko.zst
exactly matches what is already found in kernel 6.7.6-1-MANJARO.
DKMS will not replace this module.
You may override by specifying --force.
Module version 550.54.14 for nvidia-modeset.ko.zst
exactly matches what is already found in kernel 6.7.6-1-MANJARO.
DKMS will not replace this module.
You may override by specifying --force.
Module version 550.54.14 for nvidia-drm.ko.zst
exactly matches what is already found in kernel 6.7.6-1-MANJARO.
DKMS will not replace this module.
You may override by specifying --force.
Module version 550.54.14 for nvidia-peermem.ko.zst
exactly matches what is already found in kernel 6.7.6-1-MANJARO.
DKMS will not replace this module.
You may override by specifying --force.
Error! Installation aborted.
==> WARNING: `dkms install --no-depmod nvidia/550.54.14 -k 6.7.6-1-MANJARO' exited 6
==> dkms install --no-depmod nvidia/550.54.14 -k 6.6.8-2-MANJARO
==> dkms install --no-depmod nvidia/550.54.14 -k 6.7.4-1-MANJARO
==> dkms install --no-depmod nvidia/550.54.14 -k 6.7.4-2-MANJARO
==> dkms install --no-depmod nvidia/550.54.14 -k 6.6.9-1-MANJARO
==> dkms install --no-depmod nvidia/550.54.14 -k 6.7.0-2-MANJARO
==> dkms install --no-depmod nvidia/550.54.14 -k 6.7.5-1-MANJARO
==> dkms install --no-depmod nvidia/550.54.14 -k 6.6.8-1-MANJARO
==> dkms install --no-depmod nvidia/550.54.14 -k 6.7.1-1-MANJARO
==> dkms install --no-depmod nvidia/550.54.14 -k 6.7.7-1-MANJARO
Module version 550.54.14 for nvidia.ko.zst
exactly matches what is already found in kernel 6.7.7-1-MANJARO.
DKMS will not replace this module.
You may override by specifying --force.
Module version 550.54.14 for nvidia-uvm.ko.zst
exactly matches what is already found in kernel 6.7.7-1-MANJARO.
DKMS will not replace this module.
You may override by specifying --force.
Module version 550.54.14 for nvidia-modeset.ko.zst
exactly matches what is already found in kernel 6.7.7-1-MANJARO.
DKMS will not replace this module.
You may override by specifying --force.
Module version 550.54.14 for nvidia-drm.ko.zst
exactly matches what is already found in kernel 6.7.7-1-MANJARO.
DKMS will not replace this module.
You may override by specifying --force.
Module version 550.54.14 for nvidia-peermem.ko.zst
exactly matches what is already found in kernel 6.7.7-1-MANJARO.
DKMS will not replace this module.
You may override by specifying --force.
Error! Installation aborted.
==> WARNING: `dkms install --no-depmod nvidia/550.54.14 -k 6.7.7-1-MANJARO' exited 6
==> dkms install --no-depmod nvidia/550.54.14 -k 6.6.10-1-MANJARO
==> dkms install --no-depmod nvidia/550.54.14 -k 6.6.7-1-MANJARO
==> dkms install --no-depmod nvidia/550.54.14 -k 6.6.21-1-MANJARO
==> dkms install --no-depmod nvidia/550.54.14 -k 6.6.11-1-MANJARO
==> dkms install --no-depmod nvidia/550.54.14 -k 6.7.9-1-MANJARO
==> depmod 6.6.21-1-MANJARO
==> depmod 6.6.7-1-MANJARO
depmod: ERROR: fstatat(5, extramodules): No such file or directory
==> depmod 6.7.2-1-MANJARO
==> depmod 6.7.0-2-MANJARO
depmod: ERROR: fstatat(5, extramodules): No such file or directory
==> depmod 6.7.5-1-MANJARO
==> depmod 6.6.8-1-MANJARO
depmod: ERROR: fstatat(5, extramodules): No such file or directory
==> depmod 6.6.11-1-MANJARO
depmod: ERROR: fstatat(5, extramodules): No such file or directory
==> depmod 6.7.4-1-MANJARO
==> depmod 6.7.9-1-MANJARO
==> depmod 6.7.4-2-MANJARO
==> depmod 6.6.9-1-MANJARO
depmod: ERROR: fstatat(5, extramodules): No such file or directory
==> depmod 6.6.8-2-MANJARO
depmod: ERROR: fstatat(5, extramodules): No such file or directory
==> depmod 6.7.1-1-MANJARO
depmod: ERROR: fstatat(5, extramodules): No such file or directory
==> depmod 6.6.10-1-MANJARO
depmod: ERROR: fstatat(5, extramodules): No such file or directory
( 9/13) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-4.19-x86_64 -g /boot/initramfs-4.19-x86_64.img
==> Starting build: '4.19.309-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-4.19-x86_64.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-4.19-x86_64 -g /boot/initramfs-4.19-x86_64-fallback.img -S autodetect
==> Starting build: '4.19.309-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-4.19-x86_64-fallback.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64.img
==> Starting build: '6.6.21-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.6-x86_64.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64-fallback.img -S autodetect
==> Starting build: '6.6.21-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.6-x86_64-fallback.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux67.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.7-x86_64 -g /boot/initramfs-6.7-x86_64.img
==> Starting build: '6.7.9-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.7-x86_64.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux67.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.7-x86_64 -g /boot/initramfs-6.7-x86_64-fallback.img -S autodetect
==> Starting build: '6.7.9-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.7-x86_64-fallback.img'
==> Initcpio image generation successful
(10/13) Reloading system bus configuration...
(11/13) Updating icon theme caches...
(12/13) Checking which packages need to be rebuilt
foreign	khotkeys
(13/13) Updating the desktop file MIME type cache...

Where should I start to troubleshoot this?

zbe · 15 March 2024 13:20

Aren’t you here long enough to know how to remove them then? 6.7… seriously?

MAYBL8 · 15 March 2024 13:37

You are right but I’m not comfortable enough to know that I am making the right decision on how best to approach the problem.
What would you do?

Erim · 15 March 2024 14:16

What exactly are you not comfortable with?

If you open the GUI settings manager you can manage the kernels there. (At least on KDE and XFCE).

MAYBL8 · 15 March 2024 15:01

Well first of all from the errors that you see in my post does the answer lead to removing kernels or could there be some other reason for the errors? Maybe I just don’t know how to ask my question properly. I can remove the kernels but is that the correct answer? I’ll compare this post like if I went to the auto mechanic and said I have this check engine light on and say I need to change the oil. That might not be the right answer. It might need shocks or something. Does that make sense?

zbe · 15 March 2024 15:20

Oops, I misread 6.7 for 5.7.

Anyway, are you updated? Show:

uname -a
pacman -Q dkms mkinitcpio linux{66,67}
ls -l /usr/lib/modules/

Arrababiski · 15 March 2024 15:26

Run this command and copy here the results:

mhwd-kernel -li

And then:

MAYBL8 · 15 March 2024 15:54

[demo@Manjaro Downloads]$ uname -a
Linux Manjaro 6.7.9-1-MANJARO #1 SMP PREEMPT_DYNAMIC Thu Mar  7 13:40:11 UTC 2024 x86_64 GNU/Linux

[demo@Manjaro Downloads]$ ls -l /usr/lib/modules/
total 144
drwxr-xr-x 3 root root 4096 Oct 16  2022 5.18.19-3-MANJARO
drwxr-xr-x 3 root root 4096 Oct 12  2022 5.19.14-1-MANJARO
drwxr-xr-x 3 root root 4096 Oct 15  2022 5.19.15-1-MANJARO
drwxr-xr-x 3 root root 4096 Oct 26  2022 5.19.16-4-MANJARO
drwxr-xr-x 3 root root 4096 Nov  6  2022 5.19.17-1-MANJARO
drwxr-xr-x 3 root root 4096 Dec 14  2022 6.0.12-1-MANJARO
drwxr-xr-x 3 root root 4096 Dec 19  2022 6.0.13-1-MANJARO
drwxr-xr-x 3 root root 4096 Dec 21  2022 6.0.14-1-MANJARO
drwxr-xr-x 4 root root 4096 Jan 24  2023 6.0.15-1-MANJARO
drwxr-xr-x 3 root root 4096 Jan  7  2023 6.0.16-1-MANJARO
drwxr-xr-x 3 root root 4096 Jan  9  2023 6.0.17-1-MANJARO
drwxr-xr-x 3 root root 4096 Jan 13  2023 6.0.18-1-MANJARO
drwxr-xr-x 4 root root 4096 Jan 17  2023 6.0.19-1-MANJARO
drwxr-xr-x 3 root root 4096 Oct 26  2022 6.0.3-1-MANJARO
drwxr-xr-x 3 root root 4096 Oct 29  2022 6.0.5-1-MANJARO
drwxr-xr-x 3 root root 4096 Oct 31  2022 6.0.6-1-MANJARO
drwxr-xr-x 3 root root 4096 Nov  3  2022 6.0.6-2-MANJARO
drwxr-xr-x 3 root root 4096 Nov  6  2022 6.0.7-1-MANJARO
drwxr-xr-x 3 root root 4096 Jan 24  2023 6.1.1-1-MANJARO
drwxr-xr-x 4 root root 4096 Feb 26  2023 6.2.0-1-MANJARO
drwxr-xr-x 5 root root 4096 Mar 15 09:07 6.6.10-1-MANJARO
drwxr-xr-x 5 root root 4096 Mar 15 09:07 6.6.11-1-MANJARO
drwxr-xr-x 5 root root 4096 Mar 15 09:07 6.6.21-1-MANJARO
drwxr-xr-x 5 root root 4096 Mar 15 09:07 6.6.7-1-MANJARO
drwxr-xr-x 5 root root 4096 Mar 15 09:07 6.6.8-1-MANJARO
drwxr-xr-x 5 root root 4096 Mar 15 09:07 6.6.8-2-MANJARO
drwxr-xr-x 5 root root 4096 Mar 15 09:07 6.6.9-1-MANJARO
drwxr-xr-x 5 root root 4096 Mar 15 09:07 6.7.0-2-MANJARO
drwxr-xr-x 5 root root 4096 Mar 15 09:07 6.7.1-1-MANJARO
drwxr-xr-x 5 root root 4096 Mar 15 09:07 6.7.2-1-MANJARO
drwxr-xr-x 5 root root 4096 Mar 15 09:07 6.7.4-1-MANJARO
drwxr-xr-x 5 root root 4096 Mar 15 09:07 6.7.4-2-MANJARO
drwxr-xr-x 5 root root 4096 Mar 15 09:07 6.7.5-1-MANJARO
drwxr-xr-x 5 root root 4096 Mar  5 08:14 6.7.6-1-MANJARO
drwxr-xr-x 5 root root 4096 Mar  7 18:41 6.7.7-1-MANJARO
drwxr-xr-x 5 root root 4096 Mar 15 09:07 6.7.9-1-MANJARO

[demo@Manjaro Downloads]$ mhwd-kernel -li

Currently running: 6.7.9-1-MANJARO (linux67)
The following kernels are installed in your system:
   * linux66
   * linux67

zbe · 15 March 2024 15:59

You can remove all those dirs that are older than current kernel versions.

MAYBL8 · 15 March 2024 21:52

So I must be not doing some kind of regular maintenance for those to be there.
Is there a place to read on how to do kernel maintenance so those get deleted on a regular basis?
Thanks

zbe · 15 March 2024 22:01

None that I know of. Do you still get those warnings?

Arrababiski · 15 March 2024 23:56

I told you before…

MAYBL8 · 16 March 2024 00:38

no I don’t get them anymore

zbe · 16 March 2024 07:47

Also just accidentally found you were given this exact answer 2 years ago already: Can anyone else confirm if modules from already uninstalled kernels are leftover? - #7 by freggel.doe

MAYBL8 · 16 March 2024 13:27

Man you guys are tough here.
I can’t remember what I did yesterday and from 2 years ago wow.
Well thanks for the help.
Look I’ve learned allot but there is an expectation here that I will probably NEVER live up to.
I hope I can get help in the future.
I do research before asking for help but sometimes previous answers don’t seem like the problem I have.
In this case I was looking for answers from errors during an update and I thought it might have to do with having too many kernels.

nikgnomic · 16 March 2024 16:36

I have similar memory problems, but I can recall past events by checking:

journalctl and /var/log/pacman.log
text files with links for anything that may be useful in the future (personal journal/changelog)
searching previous posts on forum

Users of Unstable branch are expected to be:

proficient, motivated and have no problem solving minor isssues on your own.

Testing branch is for

the knowledgeable user looking for a way to contribute to keep Manjaro running at it’s best.

I am on Testing branch but I follow Unstable update announcements
(best for my Music/Linux balance)

If you mention what has been tried before in requests for help it can save time finding a working solution and shows that you have tried to work it out for yourself

@cscs is working on a script for cleaning old and unused files
Maclean - a small script to automate (safe) cleaning functions
The script does not appear to include option to remove old kernel modules
So a feature request to add this check should at least get some consideration

system · 18 March 2024 04:37

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.