Hi all,
I was running package manager to install updates, it was OK, I restarted the machine.
Now when I boot up, it says:
error: file `/boot/vmlinuz-6.9-x86_64’ not found.
error: you need to load the kernel first.
Press any key to continue…
I saw the 6.10 kernel was installed, but I didn’t expect that could cause such issue.
So, what can I do now?
Maybe this
Always check the second Post in Announcements Topic:
Switch always to a supported Kernel, before you doing a upgrade.
If you don’t want to use a LTS (Long Time Support) Kernel, you can also use this:
Sorry, I don’t think downgrade would be the solution.
OK marked EOL.
But how can i use again my system?
You said you have installed 6.10 already?
Did you hold shift while booting and to go in the GRUB Menue>(advanced boot or how that option called) and choosed 6.10 Kernel instead the 6.9 Kernel?
If that is not working, do you have TTY access and can login with your sudo account after you pressed enter?
sudo mhwd-kernel -i linux66
Let you install LTS Kernel 6.6
If you have a nvidia GPU, you may want to reinstall your GPU driver also.
sudo mhwd --auto pci ${DRIVER} 0300
I my opening post I wrote: I saw the kernel 6.10 was installed.
If the first proposal doesn’t work, how can I get into the system to execute the second proposal?
For the third proposal show type that command with the exact string: ${DRIVER}
?
Really?
Now I try the first.
I don’t understand you, so you can’t reach Grub and you can’t reach TTY?
Then you have another option to use a bootstick and manjaro-chroot -a in live boot and use the commands above from there.
I don’t understand why you don’t understand me, but nevermind, I was able to boot like this:
I started the machine. I use the ‘e’ command in the GRUB menu. I saw at two places the 6.9 substring (linux and init) and I replaced them to 6.10.
After this the system was able to boot normally.
A new question. How can I make to persistent, to achieve that no more need to edit the GRUB?
Thanks in advance.
From my understanding, you don’t need to edit this in first place.
You can choose 6.10 in Grub menue under advance options, there it should be listed Kernel 6.9 and 6.10
And with your next boot it keep 6.10 as default option in Grub.
But if you prefer the way to edit Grub, as you did with e (Edit).
You can make this persistent after you boot normally. Then you open a Terminal:
sudo nano /etc/default/grub
You make the same changes there and after you done:
sudo update-grub
Thanks, I am going to make the changes in the terminal and update the grub.
@ZaeNae I’m suspicious that you had an incomplete upgrade. Even though you were able to boot by manually changing the version in grub, that shouldn’t have been necessary, and it seems to indicate that the upgrade to 6.10 did not finish.
I would look here for steps to fix.
When you edit grub while booting, those changes will not persist to the next boot. You can see here on Arch Wiki for making changes to grub configuration, but I really think your issue is a broken upgrade.
I have a bad news. This command works well:
sudo nano /etc/default/grub
but the file doesn’t contain any line with vmlinuz…blah.blah.blah.
Well, what is now?
Here are some interesting lines from /var/log/pacman.log:
[2024-10-14T16:32:26+0200] [ALPM-SCRIPTLET] ==> ERROR: Missing 6.10.13-3-MANJARO kernel headers for module v4l2loopback/0.13.2.
[2024-10-14T16:32:26+0200] [ALPM] running '90-mkinitcpio-install.hook'...
[2024-10-14T16:32:26+0200] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux610.preset: 'default'
[2024-10-14T16:32:26+0200] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-10-14T16:32:26+0200] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-6.10-x86_64 -g /boot/initramfs-6.10-x86_64.img
[2024-10-14T16:32:26+0200] [ALPM-SCRIPTLET] ==> Starting build: '6.10.13-3-MANJARO'
[2024-10-14T16:32:26+0200] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2024-10-14T16:32:27+0200] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2024-10-14T16:32:28+0200] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2024-10-14T16:32:28+0200] [ALPM-SCRIPTLET] -> Running build hook: [microcode]
[2024-10-14T16:32:28+0200] [ALPM-SCRIPTLET] -> Running build hook: [kms]
[2024-10-14T16:32:34+0200] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2024-10-14T16:32:35+0200] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2024-10-14T16:32:35+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'xhci_pci'
[2024-10-14T16:32:35+0200] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2024-10-14T16:32:35+0200] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2024-10-14T16:32:35+0200] [ALPM-SCRIPTLET] -> Running build hook: [consolefont]
[2024-10-14T16:32:35+0200] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2024-10-14T16:32:35+0200] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2024-10-14T16:32:35+0200] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2024-10-14T16:32:36+0200] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-10-14T16:32:36+0200] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.10-x86_64.img'
[2024-10-14T16:32:36+0200] [ALPM-SCRIPTLET] -> Early uncompressed CPIO image generation successful
[2024-10-14T16:32:37+0200] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2024-10-14T16:32:37+0200] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux610.preset: 'fallback'
[2024-10-14T16:32:37+0200] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-10-14T16:32:37+0200] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-6.10-x86_64 -g /boot/initramfs-6.10-x86_64-fallback.img -S autodetect
[2024-10-14T16:32:37+0200] [ALPM-SCRIPTLET] ==> Starting build: '6.10.13-3-MANJARO'
[2024-10-14T16:32:37+0200] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2024-10-14T16:32:37+0200] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2024-10-14T16:32:38+0200] [ALPM-SCRIPTLET] -> Running build hook: [microcode]
[2024-10-14T16:32:38+0200] [ALPM-SCRIPTLET] -> Running build hook: [kms]
[2024-10-14T16:32:48+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'ast'
[2024-10-14T16:32:49+0200] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2024-10-14T16:32:49+0200] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2024-10-14T16:32:49+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla1280'
[2024-10-14T16:32:50+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qed'
[2024-10-14T16:32:50+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'aic94xx'
[2024-10-14T16:32:50+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'wd719x'
[2024-10-14T16:32:50+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'bfa'
[2024-10-14T16:32:50+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla2xxx'
[2024-10-14T16:32:50+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'xhci_pci'
[2024-10-14T16:32:51+0200] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2024-10-14T16:32:52+0200] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2024-10-14T16:32:52+0200] [ALPM-SCRIPTLET] -> Running build hook: [consolefont]
[2024-10-14T16:32:52+0200] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2024-10-14T16:32:52+0200] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2024-10-14T16:32:57+0200] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2024-10-14T16:33:05+0200] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-10-14T16:33:05+0200] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.10-x86_64-fallback.img'
[2024-10-14T16:33:07+0200] [ALPM-SCRIPTLET] -> Early uncompressed CPIO image generation successful
[2024-10-14T16:33:07+0200] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
That is not where you look. The actual configuration is in /etc/grub.d/10_linux, but you shouldn’t change anything there. I don’t think you need to make any changes to your grub configuration.
It looks like you have everything working? My concern is only that if an incomplete upgrade is what caused your initial problem, then there might be hidden issues. There error about missing headers, for example.
I posted a link to deal with incomplete upgrade, because that seems to happen all too often. Also you attempted the upgrade to 6.10 after 6.9 was removed as a supported kernel, which complicated things. I strongly recommend following closely the notification and news. Manjaro had been warning about dropping 6.9 for months.
Because everything works well I don’t think the update is incomplete. At least until now it not turned out. The machine booted in well, the GUI works well, I am typeing in the browser right now my post.
But, I am confused where should I make the changes to be permanent the kernel file name for the GRUB. First you wrote: sudo nano /etc/default/grub.
Now, you wrote: /etc/grub.d/10_linux.
Which one is the good? Or there is a third one?
You can also reinstall Kernels under Taskbar>Settings>Manjaro Settings Manager>Kernel.
You may install LTS Kernel 6.6 and restart your system and after you done remove 6.9 and 6.10 kernel.
Since 6.10 is EOL also, you may choose between LTS Kernel 6.6 or Kernel 6.11
Nowhere.
You select which kernel to boot in the grub menu…then it will be remembered for next time, as long as /etc/default/grub contains GRUB_DEFAULT=saved.
EDIT:
Check which kernels you have installed:
mhwd-kernel -li
Make sure you remove any EOL kernels.
Once you are booted
you take the opportunity
(of not having a potential brick instead of a working computer in front of you)
and instantly install a new kernel
one that is supported -
or even two for good measure
one of them preferably a LTS kernel
then you can reboot into one of those
and remove the unsupported one
So, I should change to 6.11 through Setting/Kernel. OK.
Currently running: 6.10.13-3-MANJARO (linux610)
The following kernels are installed in your system:
* linux610
I am going to install the 6.11.