Got the message that there was a newer kernel. So, attempted to move from 6.11 to 6.12. It failed, noting nvidia driver issues.
System appeared to continue at that point, presumably with currently loaded 6.11.
But, upon boot, grub claims it can’t find 6.11.
Is there a “how to” to get up and running at this point?
Hi @drmacro,
I believe this is what you’re looking for:
In such a case, Manjaro has a special feature that can save you from having to use dfas in the future. It is possible to have several kernels installed. Then when booting in Grub you can select which one you want to use.
If one of them is “broken” at some point, that’s no problem at all. Simply stop Grub, select one of the other kernels and the system is ready to run.
More details are explained in: Manjaro Kernels - Manjaro
Grub lists other kernels, but attempting boot them it just says it couldn’t find the associated kernel file.
Then there are remnants from previously installed kernels, however that happened. I recommend booting into a live environment, from there entering a chroot environment and fixing it from there:
Ensure you’ve got a relatively new ISO or at least one with a still supported LTS kernel.
Write/copy/dd the ISO to a USB thumb drive.
When done, boot with the above mentioned USB thumb drive into the live environment.
Once booted, open a terminal and enter the following command to enter the chroot environment:
manjaro-chroot -a
When done, you should now be in the chroot environment.
But, be careful, as you’re now in an actual root environment on your computer, so any changes you make will persist after a restart.
Once there, run the following and provide the output here:
ls -lAh /boot
And
mhwd-kernel --listinstalled
In this case the update did not complete !
Then use the link above provided by Mirdarthos
Output from chroot:
manjaro-chroot -a
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
==> Mounting (ManjaroLinux) [/dev/sda2]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
From ls -lAh /boot
ls -lAh /boot
total 7.8M
drwxr-xr-x 3 root root 4.0K Dec 31 1969 efi
drwxr-xr-x 6 root root 4.0K Nov 30 07:22 grub
-rw-r--r-- 1 root root 7.8M Nov 12 12:20 intel-ucode.img
-rw-r--r-- 1 root root 22 Nov 25 00:29 linux611-x86_64.kver
-rw-r--r-- 1 root root 21 Nov 22 19:48 linux66-x86_64.kver
drwxr-xr-x 2 root root 4.0K Jan 13 2024 memtest86+
And mhwd:
mhwd-kernel --listinstalled
Currently running: 6.10.13-3-MANJARO (linux610)
The following kernels are installed in your system:
* linux611
* linux66
AHA!
First install the latest grub installation script from Manjaro:
pamac install install-grub
Then uninstall uninstall 6.11, 6.6 is an LTS and you can always install an other one if you want later:
mhwd-kernel --remove linux611
That should, in theory, update your grub as well so a reboot should be all that’s necessary further.
@Mirdarthos
most important thing is:
there is no kernel and no initrd
He needs to install at least one.
I didn’t notice the initrd is missing, my apologies. I am stoopid.
But yes, @drmacro after uninstalling 6.11, (re)install 6.6:
mhwd-kernel --install linux66
… no you are not - don’t do that (to yourself)
So, at this point I’m running live and have charooted.
I install install-grub (and this installs grub-install on the disk in the system?)
Then remove 611, then install 66 and 611?
Don’t bother with removing - install one.
mhwd-kernel -l
lists what is there to choose from
But as I noted earlier, neither shown will boot, saying the kernel file is not found.
Sigh…
Attempt: pamac install install-grub
pamac install install-grub
Preparing...
Synchronizing package databases...
Failed to synchronize AUR database
Checking v86d dependencies...
Checking python-pyrsistent dependencies...
Warning: plymouth: local (24.004.60-6) is newer than extra (22.02.122-18)
Resolving dependencies...
Checking inter-conflicts...
To install (1):
install-grub 2:2.12-3 core 6.5 kB
To build (2):
python-pyrsistent 0.20.0-1 (0.19.3-4) AUR
v86d 0.1.10-13 (0.1.10-8) AUR
Total download size: 6.5 kB
Total installed size: 6.9 kB
Edit build files : [e]
Apply transaction ? [e/y/N] y
Cloning python-pyrsistent build files...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to system scope bus via local transport: Host is down
Error: Failed to prepare transaction: Failed to clone python-pyrsistent build files
I honestly think you mirror list is screwed-up. Rebuild it, from th e chroot environment:
pacman-mirrors -f 5
And then try it again:
pacman -Syyu
And see what happens, because I’ve got to run now, so @andreas85 is welcome to take over.
Same with pamac install install-grub:
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to system scope bus via local transport: Host is down
Error: Failed to prepare transaction: Failed to clone python-pyrsistent build files
Now step by step:
The kernels have been installed, but where are they ?
Here a command, to find out:
ls -lA /boot
total 7972
drwxr-xr-x 3 root root 4096 Dec 31 1969 efi
drwxr-xr-x 6 root root 4096 Nov 30 07:22 grub
-rw-r--r-- 1 root root 8139776 Nov 12 12:20 intel-ucode.img
-rw-r--r-- 1 root root 22 Nov 25 00:29 linux611-x86_64.kver
-rw-r--r-- 1 root root 21 Nov 22 19:48 linux66-x86_64.kver
drwxr-xr-x 2 root root 4096 Jan 13 2024 memtest86+
The kernels are missing, but the .kver-files are there. This is odd
How it should look:
ls -lA /boot
insgesamt 1779676
-rw-r--r-- 1 root root 81920 12. Nov 20:44 amd-ucode.img
drwx------ 3 root root 4096 1. Jan 1970 efi
drwxr-xr-x 1 root root 184 30. Nov 15:01 grub
-rw------- 1 root root 277370880 30. Nov 09:55 initramfs-5.15-x86_64-fallback.img
-rw------- 1 root root 41082880 30. Nov 09:55 initramfs-5.15-x86_64.img
-rw------- 1 root root 439234560 30. Nov 09:57 initramfs-6.11-x86_64-fallback.img
-rw------- 1 root root 110131200 30. Nov 09:56 initramfs-6.11-x86_64.img
-rw------- 1 root root 442521600 30. Nov 09:58 initramfs-6.12-x86_64-fallback.img
-rw------- 1 root root 109864960 30. Nov 09:57 initramfs-6.12-x86_64.img
-rw------- 1 root root 309268480 30. Nov 09:56 initramfs-6.1-x86_64-fallback.img
-rw------- 1 root root 42762240 30. Nov 09:56 initramfs-6.1-x86_64.img
-rw-r--r-- 1 root root 23 17. Nov 22:29 linux515-x86_64.kver
-rw-r--r-- 1 root root 22 25. Nov 06:29 linux611-x86_64.kver
-rw-r--r-- 1 root root 21 25. Nov 06:36 linux612-x86_64.kver
-rw-r--r-- 1 root root 22 23. Nov 01:48 linux61-x86_64.kver
drwxr-xr-x 1 root root 22 13. Jan 2024 memtest86+
-rw-r--r-- 1 root root 10920960 30. Nov 08:58 vmlinuz-5.15-x86_64
-rw-r--r-- 1 root root 13550080 30. Nov 08:58 vmlinuz-6.11-x86_64
-rw-r--r-- 1 root root 13787648 30. Nov 08:58 vmlinuz-6.12-x86_64
-rw-r--r-- 1 root root 11710976 30. Nov 08:58 vmlinuz-6.1-x86_64
For my info please:
uname -a
So please try now to install another kernel (like 6.12 or 6.1) with mhwd-kernel