You are not logged in.
Pages: 1
Hello,
Because other operating systems don't see Arch install I have decided to create a 40_custum menu entry following grub archwiki instructions.
This is the model I followed:
menuentry "Other Linux" {
# assuming that UUID is 763A-9CB6
search --set=root --fs-uuid 763A-9CB6
# search by label OTHER_LINUX (make sure that partition label is unambiguous)
#search --set=root --label OTHER_LINUX
linux /boot/vmlinuz (add other options here as required, for example: root=UUID=763A-9CB6)
initrd /boot/initrd.img (if the other kernel uses/needs one)
}
And this is the modified version reflecting my system:
menuentry "Arch LinuxLXQT" {
search --set=root --fs-uuid 853208ae-2734-48ef-bfdd-918e34c9cab5
linux /boot/efi/vmlinuz-linux root=UUID=853208ae-2734-48ef-bfdd-918e34c9cab5 rw quiet
initrd /boot/efi/intel-ucode.img
}
But this doesn't work.
This is my /boot structure:
[mak@myhost ~]$ ls /boot
efi grub
[mak@myhost ~]$ ls /boot/grub
grub.cfg
[mak@myhost ~]$ ls /boot/efi
EFI grub initramfs-linux-fallback.img initramfs-linux.img intel-ucode.img startup.nsh vmlinuz-linux
[mak@myhost ~]$ ls /boot/grub
grub.cfg
[mak@myhost ~]$
Can anyone suggests what did I do wrong.
Thank you.
Offline
which is the other operating system u have installed
Offline
which is the other operating system u have installed
Manjaro!
Offline
What exactly does "But this doesn't work" mean? (how does it fail, what error messages do you see)
https://bbs.archlinux.org/viewtopic.php?id=57855
(edit) And if you are using GRUB from Manjaro I suspect this thread will be closed soon.
Last edited by 2ManyDogs (2017-07-03 15:28:55)
Offline
What exactly does "But this doesn't work" mean? (how does it fail, what error messages do you see)
https://bbs.archlinux.org/viewtopic.php?id=57855
(edit) And if you are using GRUB from Manjaro I suspect this thread will be closed soon.
I get a message that "press a key to continue..."
And I am back to the grub menu
EDIT:
Arch can't boot manjaro either.
When I try to do it I get kernel panic.
The only way I can boot them from the Firmware, which is ok but it shouldn't be like that.
EDIT:
If I set in efibootmgr Arch as current, than I can boot arch from the grub boot menu as normal. In that case I have to boot Manjaro from the firmware.
If I set manjaro as current then I have to boot arch from the firmware.
EDIT:
For me it doesn't matter what grub set as current in efibootmgr as far as it works.
I created the 40_custom entry in Manjaro because I followed archwiki instructions and I thought the settings are better tuned for arch.
I can repeat the same thing by creating 40_custom in arch with manjaro setting, see how does it work the other way around.
Last edited by jmak (2017-07-03 16:37:39)
Offline
Now, I ended up unable to boot into arch from firmware. So I can't boot into arch at all.
After creating 40_custom file to try I run:
grub-mkconfig -o /boot/efi/grub/grub.cfg
rather than local grub.cfg like this:
grub-mkconfig -o /boot/grub/grub.cfg
because the firmware reads the former grub.cfg
However, Arch didn't make an entry for itself only for the other operating systems like windows and the other linux distributions. How is it possible?
Now, I can't launch arch at all because the other distros don't see it.
How can I recover arch?
Offline
Can you use Arch installation cd, chroot into Arch system, reconfigure MBR, install os-prober and update grub.cfg. In short, start configure grub from the beginning.
Do you have uefi motherboard?
Offline
Can you use Arch installation cd, chroot into Arch system, reconfigure MBR, install os-prober and update grub.cfg. In short, start configure grub from the beginning.
Do you have uefi motherboard?
Yes, I have uefi installation.
Yes, I will do that and see what happens.
Offline
Can you use Arch installation cd, chroot into Arch system, reconfigure MBR, install os-prober and update grub.cfg. In short, start configure grub from the beginning.
Do you have uefi motherboard?
Thanks the idea,
I reinstalled grub like when I installed the system at the first time and I got back arch into the firmware. Now, at least I can launch it from the firmware like before.
However, Arch can't create proper entries for other Linux distros, so when I click the entry it creates I get errors like, "kernel panic".
In the meantime, I read on the internet that this is because "os-prober" is a poorly written software and it can't cope with distros where "intel-ucode" is installed .
So I guess because "intel-ucode" is installed on my system as well, the other distros don't detect it. When I say don't detect, I mean they don't even list arch partition in their grub menu.
This is a new laptop.
My old one, which had no uefi motherboard I've never experienced problems like this.
Offline
Pages: 1