Update kernel and was wondering if this is good news or not

Hello,

Today I was reading somewhere that kernel 5.14 and lower aren’t supported. Went to 5.15 rebooted and everything seemed fine. Ran sudo mhwd -r Linux510 and got this output


[gumbo@manjaro ~]$ sudo mhwd-kernel -i linux515
:: Synchronizing package databases...
 core                  167.7 KiB   211 KiB/s 00:01 100%
 extra                1900.0 KiB  1258 KiB/s 00:02 100%
 community               6.9 MiB   783 KiB/s 00:09 100%
 multilib              174.3 KiB   513 KiB/s 00:00 100%
resolving dependencies...
looking for conflicting packages...

Packages (1) linux515-5.15.16-1

Total Download Size:    99.64 MiB
Total Installed Size:  104.15 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 linux515-5.15.16...    99.6 MiB  1175 KiB/s 01:27 100%
(1/1) checking keys in keyring                     100%
(1/1) checking package integrity                   100%
(1/1) loading package files                        100%
(1/1) checking for file conflicts                  100%
(1/1) checking available disk space                100%
:: Processing package changes...
(1/1) installing linux515                          100%
Optional dependencies for linux515
    crda: to set the correct wireless channels of your
    country [installed]
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating module dependencies...
(3/4) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: 5.15.16-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: 5.15.16-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64-fallback.img
==> Image generation successful
(4/4) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done

[gumbo@manjaro ~]$ mhwd-kernel -li                      Currently running: 5.15.16-1-MANJARO (linux515)
The following kernels are installed in your system:
   * linux510
   * linux515
[gumbo@manjaro ~]$ uname -r
5.15.16-1-MANJARO
[gumbo@manjaro ~]$ sudo mhwd-kernel -r linux510
[sudo] password for gumbo:
checking dependencies...

Packages (1) linux510-5.10.93-1

Total Removed Size:  78.33 MiB

:: Do you want to remove these packages? [Y/n] y
:: Running pre-transaction hooks...
(1/1) Removing linux initcpios...
:: Processing package changes...
(1/1) removing linux510                            100%
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Updating module dependencies...
(3/3) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done

nvme0n1 is where grub was installed. I haven’t rebooted so I was asking here to be safe.

You should install more than one kernel.
E.g.: 5.15 and 5.10.

The last line /usr/bin/grub-probe: warning: unknown device type nvme0n1. can be ignored.

Uh … just to note a few things:

Dont attempt to remove the running kernel.
(ps - check running kernel with inxi or uname -a, etc)

Not true. 5.14, 5.13, 5.12, 5.11 are all EOL … but 5.4 and 5.10 are LTS and still supported.
While this is upstream and doesnt match perfectly, here is the kernel page: kernel.org

Can I go back and install 5.10? Would that mess anything up?

Ok I should be safe then? I’m on 5.15

You can have 5.4,5.10,5.15,and 5.16 is experimental/development/new.
I always suggest folks keep at least 1 good working LTS plus whatever ‘newer’ kernel they are trying out.

So to install the LTS do it the same way as i did 5.15 mhwd?

Yup … I would suppose given your previous posts that you are aiming to have 5.10 and 5.15 ?

  • view current running kernel
    uname -r
  • check mhwd installed kernels
    mhwd-kernel -li
  • install desired kernel
    sudo mhwd-kernel -i linux510
  • remove unwanted kernel
    sudo mhwd-kernel -r linux513

As with most things you can also check the help flag:
mhwd-kernel --help -or- mhwd-kernel -h

side note: if you don’t actual intend to set a console font at that level, you can remove it from the list of hooks to use in /etc/mkinitcpio.conf and stop seeing the error.

Is this for me as I am the OP

If it is this is what I have for my hooks

HOOKS="base udev autodetect modconf block keyboard keymap consolefont

Which one do I remove?

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