Dual Boot so far no luck

[deano_ferrari]

@ozotto

So from my understanding the pointer starts with partition name then / then boot

Yeah, I had assumed that, but doesn’t seem the case. It looks for the kernel and initrd within the current root filesystem.

[ozotto]

@deano_ferrari

@deano_ferrari

ls /boot/efi/EFI/ubuntu/grubx64.efi

We covered that.

localhost:/ # ls /boot/efi/EFI/ubuntu/grubx64.efi
/boot/efi/EFI/ubuntu/grubx64.efi
localhost:/ # 

@deano_ferrari

It looks for the kernel and initrd within the current root filesystem.

I tried
set root=‘nvme0n1p6’
with
linux /boot/vmlinuz-6.14.0-37-generic ro root=dev/nvme0n1p6

i am 2nd guessing . However I think that is the way to explore

Have a great Saturday

[deano_ferrari]

@ozotto

We covered that.

With respect to chainloading, I was confusing it with systemd-bootd where the efi directive is a thing.

@ozotto

I tried
set root=‘nvme0n1p6’
with
linux /boot/vmlinuz-6.14.0-37-generic ro root=dev/nvme0n1p6

i am 2nd guessing . However I think that is the way to explore

No, that won’t work. The linux and initrd files must be physically visible to GRUB ie they need to reside on the same filesystem/root that GRUB is reading at boot (which is openSUSE in this case).

[ozotto]

@deano_ferrari
… it becomes too difficult. … for the time being
cheers from DownUnder

[deano_ferrari]

Two simple choices here:

1. Choose the OS from the UEFI boot menu
2. Use the Ubuntu Grub menu to boot from, and that should be able to chainload openSUSE if desired.

[conram]

@deano_ferrari

Use the Ubuntu Grub menu to boot from, and that should be able to chainload openSUSE if desired.

Yep, this is the easiest way. I have tumbleweed with grub2-efi then I tried installing a tumbleweed with grub-bls then used the tumbleweed with grub2-efi to chainload the one with grub-bls.