It is customary for me that when I update the OS to a new release something happens with the kernels and my nvidia.
This time things went much further than imagined, the Linux510 kernel simply disappeared, which by the way was the only one installed and therefore the Manjaro entry disappeared from the grub.
By chrooting after doing an update and everything unimaginable, the result is that when trying to install any available kernel the answer is simply: error: no targets specified (use -h for help).
I summarize what I have advanced so far…
Because sudo “mhwd-kernel -i linuxXX” was returning the error:
“No targets specified (use -h for help)”
when trying with all available kernels, I used
“Pacman -S linux419 linux419-headers”
and I was able to install said kernel and update GRUB, the only error it showed was:
"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. "
(I assume you were referring to the USB drive on the live CD).
Immediately afterwards, the entrance to Manjaro reappeared but when starting it only shows a black screen with a cursor and there it remained.
Again in “chroot” I installed:
“Pacman -S linux513 linux513-headers”
with the same results but this time it showed the two entries (linux419 and linux513), and when starting, black screen with cursor anyway.
Next I uninstalled “linux419” and installed:
“Pacman -S linux510 linux510-headers”
It showed the two entries (linux510 and linux513) with the same results.
Obviously the problem goes further and apparently I’m stuck with the graphics, so any help is welcome.
PS: I never mentioned the fact that I have Windows10 installed, that the boot is not by UEFI and that the GRUB always showed the corresponding entry.
From the chroot environment, try updating the mirrors first:
sudo pacman-mirrors --fasttrack 5
To select and use the 5 fastest (not necessarily closest) mirrors.
Now update the package list:
sudo pacman -Syyu
Followed by trying to install the kernel again:
sudo mhwd-kernel --install linux515
If that still doesn’t work, and since you’re comfortable with/able to chroot, I’m going to go ahead and ask you to please provide the output, from the chroot environment, of the following:
Total Download Size: 130.64 MiB
Total Installed Size: 236.07 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages…
linux515-5.15.2-… 99.6 MiB 951 KiB/s 01:47 [######################] 100%
linux515-headers… 31.0 MiB 1186 KiB/s 00:27 [######################] 100%
Total (2/2) 130.6 MiB 996 KiB/s 02:14 [######################] 100%
(2/2) checking keys in keyring [######################] 100%
(2/2) checking package integrity [######################] 100%
(2/2) loading package files [######################] 100%
(2/2) checking for file conflicts [######################] 100%
(2/2) checking available disk space [######################] 100%
:: Processing package changes…
(1/2) installing linux515 [######################] 100%
Optional dependencies for linux515
crda: to set the correct wireless channels of your country [installed]
(2/2) installing linux515-headers [######################] 100%
:: Running post-transaction hooks…
(1/5) Arming ConditionNeedsUpdate…
(2/5) Updating module dependencies…
(3/5) 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.2-2-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: [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.2-2-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: [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/5) Updating Kernel initcpios for Nvidia-DRM…
(5/5) Updating Grub-Bootmenu
Generating grub configuration file …
Found theme: /boot/grub/themes/Vimix/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.13-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.13-x86_64.img
Found initrd fallback image: /boot/initramfs-5.13-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.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
Found Windows 10 on /dev/sda1
done
[manjaro-gnome /]# mhwd-kernel --list
available kernels:
linux414
linux419
linux44
linux49
linux510
linux513
linux514
linux515
linux516
linux54
linux510-rt
linux515-rt
[manjaro-gnome /]# mhwd-kernel --listinstalled
Currently running: 5.13.19-2-MANJARO (linux513)
The following kernels are installed in your system:
linux510
linux513
linux515
[manjaro-gnome /]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 125.4M 1 loop
loop1 7:1 0 582M 1 loop
loop2 7:2 0 943.5M 1 loop
loop3 7:3 0 743.4M 1 loop
sda 8:0 0 953.9G 0 disk
|-sda1 8:1 0 549M 0 part
|-sda2 8:2 0 243.6G 0 part
|-sda3 8:3 0 123.8G 0 part / -sda4 8:4 0 585.9G 0 part /home sdb 8:16 0 186.3G 0 disk -sdb1 8:17 0 186.3G 0 part
sdc 8:32 1 7.5G 0 disk
|-sdc1 8:33 1 2.4G 0 part
`-sdc2 8:34 1 4M 0 part
sr0 11:0 1 1024M 0 rom
Now I’m going to restart and re-edit the post with the result…
As expected, the result of the above was the same.
New output:
sudo su
[manjaro-gnome manjaro]# manjaro-chroot -a
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
==> Mounting (ManjaroLinux) [/dev/sda3]
→ mount: [/mnt]
→ mount: [/mnt/home]
[manjaro-gnome /]# sudo ls /etc/mkinitcpio.d/*.preset
/etc/mkinitcpio.d/linux510.preset /etc/mkinitcpio.d/linux515.preset
/etc/mkinitcpio.d/linux513.preset
[manjaro-gnome /]# sudo mhwd-kernel -li
Currently running: 5.13.19-2-MANJARO (linux513)
The following kernels are installed in your system:
linux510
linux513
linux515
[manjaro-gnome /]# sudo ls /usr/bin/modules/
ls: cannot access ‘/usr/bin/modules/’: No such file or directory
Ok… After rebooting the system I tried to start the OS with linux515 and then with 510, the result was the same.
Now I am in Live USB with chroot and when trying to uninstall linux513 it is the same result as above, which means that it never changed the kernel when trying a new start…
[manjaro-gnome /]# mhwd-kernel -r linux513
Error: You can’t remove your current kernel.
