Will try! post update in a bit.
And please don’t post images of text. Use preformatted </> text.
The only thing you have to do in chroot is issue -Syu AND also reinstall kernels you have (well, had :p). Choosing faster/different mirror is optional.
2 Likes
This is the output for pacman-mirrors --geoip --fasttrack=5
[manjaro /]# pacman-mirrors --geoip --fasttrack=5
Version 4.24.0
USAGE:
pacman-mirrors [-h] [-f [NUMBER]] [-i [-d]] [-m METHOD] [--status]
[-c COUNTRY [COUNTRY...] | [--geoip] | [--continent]]
[-l] [-lc] [-q] [-t SECONDS] [-v] [-n]
[--api] [-S/-B BRANCH] [-p PREFIX]
[-P PROTO [PROTO...]] [-R] [-U URL]
pacman-mirrors: error: argument -f/--fasttrack: not allowed with argument --geoip
But does it needs to be exactly the kernel I had going before?
(think) It was 6.1, but now I guess its on 6.5, at least is what it says when I run
mhwd-kernel -li
Currently running: 6.5.5-1-MANJARO (linux65) The following kernels are installed in your system:;
Either way, maybe reinstalling grub on the Manjaro drive will do the trick? I saw some people commenting on this on another thread. I know It apparently has no problems, but I just can’t understand why it can’t recognize the Kernel after reinstalling it.
Also, now I don’t seem to be able to install new kernels at all:
[manjaro /]# mhwd-kernel -i linux61
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
error: no targets specified (use -h for help)
Is target the path to the device?
What is the output of… 
ls -l /boot
…?
I just found a thread about this 
But apparently I have no kernels installed, and can’t install them using mhwd-kernel
[manjaro /]# ls -l /boot
total 7200
drwxr-xr-x 3 root root 4096 Dec 31 1969 efi
drwxr-xr-x 6 root root 4096 Nov 15 15:38 grub
-rw-r--r-- 1 root root 7360512 Aug 8 15:19 intel-ucode.img
drwxr-xr-x 2 root root 4096 Jul 28 17:41 memtest86+
Let’s try it with pacman then.
pacman -S linux61
mkinitcpio -P
update-grub
… all assuming that you’re working from the chroot, of course.
1 Like
If you want easy life just learn pacman.
You’ll know how to search things you have, how to install things you want, etc. It’s easy, you just have to read pacman - ArchWiki and then apply things you read in situations like this.
Also, you can use same commands on any arch-based distro or even arch.
2 Likes
Ok, ran the commands from chroot, and now the Kernel installed! But trying to boot from it I get an error on Grub console:
error: symbol 'grub_is_shim_lock_enabled' not found.
error: symbol 'grub_is_shim_lock_enabled' not found.
Press any key to continue...
Failed to boot both default and fallback entries.
That suggests that you have Secure Boot enabled. Manjaro does not support this.
is that a motherboard configuration?
I’ve been reading the wiki a lot, and the community is really helpful aswell! I’m kinda new to Linux, and especially Arch. Posted this in the hopes of avoiding yet another reinstall, but at least this time It wasn’t my fault what happened (probably was tbh).
It’s in the UEFI settings. You must disable Secure Boot, as well as CSM (i.e. legacy BIOS emulation) if enabled, and if you dual-boot with Wintendo, make sure that Wintendo’s “fast startup” is disabled as well.
1 Like
It worked! Thanks!
I just am a bit confused as to why mhwd didn’t work, but anyway as @zbe said I’ll use pacman more from now on.
Thanks guys.
1 Like
@Anck8, what exactly was the solution to get rid of
error: symbol 'grub_is_shim_lock_enabled' not found.
error: symbol 'grub_is_shim_lock_enabled' not found.
running
# mkinitcpio -P
# update-grub
or disabling Secure Boot (why was it suddenly set before?), CSM (again why being set?) or Windoze Fast startup?
My BIOS didn’t had an option for CSM, but Fast Boot was enabled… Probably because I tinkered with the settings to try to make it work.
So after installing the Kernel with pacman, I still was getting the error, but after disabling Fast Boot it booted no problem 
.
But without running the installation through pacman like @Aragorn suggested Grub wouldn’t have recognized the newly installed Kernel, so the solution was his post:
# pacman -S linux61
# mkinitcpio -P
# update-grub
1 Like
To clarify, Fast Boot is an option often found in the BIOS; disabling it can sometimes be beneficial.
Fast Startup is a hibernation state induced by Windows, which causes many headaches in a multiboot environment. If you are multibooting Linux and Windows, disabling Fast Startup is necessary.
This is easily achieved by running:
powercfg /h off
… from an administrative prompt in Windows.
2 Likes
Installing kernel will automatically trigger the other two, hence, again, “-Syu AND kernel reinstall” is all that is needed.
Also keep in mind that if you (ever) need kernel headers you have to install those too, manually, with pacman. So now you know what to do if you ever get “headers missing” error while building something.
2 Likes
This topic was automatically closed 8 hours after the last reply. New replies are no longer allowed.