After the update, the 6.15.3-1 kernel does not appear in grub. It does appear in the kernel manager. I make an update to the GRUB, the console recognizes it. Restart but still not showing up. On the other hand I tried to uninstall the 6.15.3-1 kernel, but it gives me a message that it cannot be removed because it is dependent on another instance. For now it only works with kernel 6.12.lts. What could be happening?
what is the output of sudo mkinitcpio -P @gasll
"==> Building image from preset: /etc/mkinitcpio.d/linux612.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.12-x86_64 -g /boot/initramfs-6.12-x86_64.img
==> Starting build: '6.12.34-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: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.12-x86_64.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux612.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.12-x86_64 -g /boot/initramfs-6.12-x86_64-fallback.img -S autodetect
==> Starting build: '6.12.34-1-MANJARO'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'xhci_pci_renesas'
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.12-x86_64-fallback.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux615.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.15-x86_64 -g /boot/initramfs-6.15-x86_64.img
==> Starting build: '6.15.3-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: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.15-x86_64.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux615.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.15-x86_64 -g /boot/initramfs-6.15-x86_64-fallback.img -S autodetect
==> Starting build: '6.15.3-1-MANJARO'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'xhci_pci_renesas'
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.15-x86_64-fallback.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful"
Something he had not commented on. Kernel 14 and 13 are not installed, but they appear in the grub.
thank you very much
Mod edit: Added formatting (``` above and below pasted text) 
Then the Grub system you’re booting from might not be the same as the one updated with mkinitcpio -P.
Do you have more than one Linux installed?
I have Manjaro, where I performed the mkinitcipio, and deepin.
This suggests that the system is booting using Deepin’s GRUB instance. You’ll want to run the mkinitcpio from there.
Yeah. I did a GRUB update in Deepin and that’s it, all good. Taking advantage of this conversation, how do I leave manjaro handling the grub? Is it convenient? Thank you very much for the help. Resolved
1 Like
The last-installed OS will have the “controlling” GRUB.
What you could do is reinstall GRUB in your Manjaro installation, perhaps using install-grub which is available in the Core repo. 
2 Likes
It seems that the update of the grub in deepin (update-grub), is not permanent. I closed manjaro and when I started again, it didn’t recognize the 6.15 kernel. I had to enter Deepin to do the update-grub in deepin again, I closed it, and I was able to enter Manjaro. How can I make it permanent? Best regards.
There is an issue with GRUB in non-Manjaro distros in that they don’t play well with Manjaro. This is why I suggested reinstalling GRUB from your Manjaro OS. Did you try that?
Also, do you have more than one boot option in your BIOS/UEFI firmware settings?
1 Like
I do not work with btrfs, but roughly the logic will be: check the uefi boot variables and order, check the esp contents, check the btrfs subvolumes.
Your 2 oses write to different locations - either on the esp or on different subvolumes. Which is actually the way it should be.
You can try running refind, not sure if it supports btrfs but if it does will detect the kernels.
Otherwise you will always have one “master” system. You cannot use 2 grubs at the same time. At least name them differently and change between them using uefi menu.
Installing another bootloader such as refind - to boot any available GRUB on the system - is another useful strategy.
From that point, each OS will be responsible for it’s own GRUB, and there will be no further concern over how one GRUB affects another.
1 Like
But from that point on you may find that after each an every update the UEFI will point to refind (and not th the grub you used to start every day) 
1 Like
Indeed.
And, that is the point.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.