Am 18.08.19 um 21:19 schrieb Carlos E. R.:
On 18/08/2019 18.03, zb4ng wrote:
Am 18.08.19 um 15:44 schrieb Carlos E. R.:
On 17/08/2019 20.54, zb4ng wrote:
No, it doesn't.
You have to boot the system which controls grub and make it run os-prober so that it finds the actual kernel entries of the other system.
There are other ways.
You can manually edit the grub file that is intended for manual edit, and create an entry for the "vmlinuz" symlink this one is maintained by zypper.
Yeah it looks like I can use "menuentry" in /boot/grub2/custom.cfg and put the symlink in there?
Yes, that's the idea.
Or, after making sure that both installs have their own grub installed to the root partition, not to the MBR, add manually on each one (in the file intended for manual edit) an entry for the other grub, not to the kernel.
Maybe if I can't figure out grub configurationb , I'll try to add grub to my 15.1-system -(Do I have to move the existing Grub from MBR to 15.0?) - and see if they find each other.
Otherwise, I am ok with using the method mentioned in my earlier post.
This is one from me:
menuentry '--> ssd-test' --id cer-ssd-001 { insmod part_gpt insmod ext2 set root='hd0,gpt3' if search --no-floppy --fs-uuid --set=root 32392d31... ; then chainloader +1 else echo Could not find this OS instance, will not boot (3) sleep 1 fi }
This works now for me: /boot/grub2/custom.cfg menuentry "openSuSE 15.1 - Custom Configuration" --class gnu-linux --class gnu --class os { insmod part_msdos insmod ext2 set root='(hd0,10)' linux /boot/vmlinuz initrd /boot/initrd } ~\:14:44:35 > uname -a Linux linux-riut 4.12.14-lp151.28.13-default #1 SMP Wed Aug 7 07:20:16 UTC 2019 (0c09ad2) x86_64 x86_64 x86_64 GNU/Linux ~\:14:45:33 > -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org