brahma
16 February 2023 22:33
21
just to be sure, first check with:
mhwd-kernel -li
and only the linux515 should be listed… if it is, remove the leftovers:
sudo rm /etc/mkinitcpio.d/linux510.preset
sudo rm /etc/mkinitcpio.d/linux513.preset
sudo rm -r /boot/vmlinuz-5.10-x86_64
sudo rm -r /boot/vmlinuz-5.13-x86_64
sudo rm -r /usr/lib/modules/5.10.167-1-MANJARO
sudo rm -r /usr/lib/modules/5.13.19-2-MANJARO
sudo rm -r /usr/lib/modules/extramodules-5.10-MANJARO
sudo rm -r /usr/lib/modules/extramodules-5.13-MANJARO
rerun again:
sudo update-grub
and only linux 5.15 should be detected, but post the output anyway
1 Like
blp92
16 February 2023 22:42
22
Looks like I still have 2 others:
[~]$ mhwd-kernel -li
Currently running: 5.15.93-1-MANJARO (linux515)
The following kernels are installed in your system:
* linux510
* linux513
* linux515
should I still run what you have above?
brahma
16 February 2023 22:44
23
no remove the linux 513 and keep the 5.10 as a backup:
sudo mhwd-kernel -r linux513
and reinstall the 5.10, since it was not detected in mkinitcpio:
sudo pacman -S linux510
1 Like
blp92
16 February 2023 22:56
24
Done, and now it looks as expected.
[~]$ mhwd-kernel -li
Currently running: 5.15.93-1-MANJARO (linux515)
The following kernels are installed in your system:
* linux510
* linux515
now I’m free to run those commands earlier to clean things up?
Thank you so much for all your help, you’re saving me a world of trouble!
brahma
16 February 2023 22:57
25
no, its done, you have now installed 2 kernels: the 5.15 and the 5.10, and thats it…
but just to be sure post output from:
sudo mkinitcpio -P && sudo update-grub
1 Like
blp92
16 February 2023 23:06
26
[~]$ sudo mkinitcpio -P && sudo update-grub
[sudo] password for sage:
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'default'
-> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64.img
==> Starting build: 5.10.167-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: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.10-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'fallback'
-> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64-fallback.img -S autodetect
==> Starting build: 5.10.167-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla1280
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.10-x86_64-fallback.img
==> Image generation successful
==> 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.93-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: [resume]
-> 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.93-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla1280
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [resume]
-> 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
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/amd-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/amd-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.
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
brahma
16 February 2023 23:10
27
good, both kernels are detected, the 5.13 is gone, so thats it, it is done
1 Like
system
Closed
19 February 2023 13:17
29
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.