Kernel 5.16.2-1 installed but not running

@Mirdarthos & @stephane : From the terminal

type or pa    ~  sudo lsblk                                                                                               ✔ 
[sudo] password for snowdust: 
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0 232.9G  0 disk 
├─sda1        8:1    0   512M  0 part /boot/efi
├─sda2        8:2    0  32.1G  0 part /
├─sda3        8:3    0  16.5G  0 part /home
└─sda4        8:4    0   8.7G  0 part [SWAP]
sdb           8:16   0 232.9G  0 disk 
├─sdb1        8:17   0   512M  0 part 
├─sdb2        8:18   0  28.2G  0 part 
├─sdb3        8:19   0  20.4G  0 part 
└─sdb4        8:20   0   8.7G  0 part 
nvme0n1     259:0    0 465.8G  0 disk 
├─nvme0n1p1 259:1    0   512M  0 part 
├─nvme0n1p2 259:2    0  28.2G  0 part 
├─nvme0n1p3 259:3    0  20.4G  0 part 
└─nvme0n1p4 259:4    0  12.6G  0 part 
    ~  efibootmgr -v                                                                                     ✔  7s  
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0004,0001,0003,0002,0005,0006
Boot0000* manjaro       HD(1,GPT,5c59f532-b7b4-430d-91bc-750dca195d92,0x800,0x100000)/File(\EFI\manjaro\grubx64.efi)
Boot0001* UEFI OS       HD(1,GPT,5c59f532-b7b4-430d-91bc-750dca195d92,0x800,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0002* UEFI:CD/DVD Drive     BBS(129,,0x0)
Boot0003* UEFI OS       HD(1,GPT,018f67fc-1ad7-4e31-bf8f-d5953b74b354,0x800,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0004* UEFI OS       HD(1,GPT,c5d43113-7e60-4ec3-9478-1dfedafc9a69,0x800,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0005* UEFI:Removable Device BBS(130,,0x0)
Boot0006* UEFI:Network Device   BBS(131,,0x0)
    ~  sudo mkinitcpio -P                                                                                       ✔ 
==> 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
==> Building image from preset: /etc/mkinitcpio.d/linux516.preset: 'default'
  -> -k /boot/vmlinuz-5.16-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.16-x86_64.img
==> Starting build: 5.16.2-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> 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.16-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux516.preset: 'fallback'
  -> -k /boot/vmlinuz-5.16-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.16-x86_64-fallback.img -S autodetect
==> Starting build: 5.16.2-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> 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.16-x86_64-fallback.img
==> Image generation successful
ste code here

As stated in a previous post:

  1. M.2 is a back-up running freshly installed Manjaro KDE and a back-up of my thumb-key (documents)
  2. ssd(sda) is my daily go-to disk running Manjaro KDE
  3. ssd(sdb) running up-to-date Manjaro Cutefish following development because I am curious.

Curioser and curioser. I’m back to @Aragorn’s theory of a rogue…somethingortheother…And considering there’s a Manjaro Cutefish installation there, it does make sense…

1 Like

My guess is that this is the one whose GRUB you’re using, but it’s mounting the root filesystem of your /dev/sda installation. Possibly because of the /etc/fstab and /boot/grub/grub.cfg pointing to the UUID of the root filesystem on /dev/sda instead of the one on /dev/nvme0n1.

Or maybe it’s the other way around. But whatever’s going on, the GRUB configuration of the GRUB you’re using does not correspond to the system you’re booted into.

1 Like

This is quite similar to the situation when you dual boot two linux distros. In that case boot into the disk (kde on /dev/sda) that you want to want to use the grub loader from:

sudo grub-install /dev/sda
sudo update-grub
reboot

First of all, credits where credits due, thanks to you savvy members for sharing your knowledge. Here’s the solution. This is what I did:

  1. uninstalled kernel-516 and shut down the pc
  2. disconnected ssd(sdb) running Manjaro Cutefish
  3. booted to ssd(sda) running Manjaro KDE for so many moons and installed kernel-516 using the terminal and rebooted twice. MHWD settings showing kernel-516 installed and running. This is my first Bingo! moment.
  4. again shut down the pc and connected back ssd(sdb) running Manjaro Cutefish
  5. booted and selected (sda) Manjaro KDE (many moons) … Hooray! My second Bingo! moment.
    All is now sailing smoothly. Again many thanks to you guys, your comments got me thinking out of the box, so to speak. Hope this helps others experiencing a similar situation.

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