On 26/04/2019 22.02, Knurpht-openSUSE wrote:
Op vrijdag 26 april 2019 21:58:20 CEST schreef Carlos E. R.:
On 26/04/2019 21.49, Darryl Gregorash wrote:
On 2019-04-26 01:41 PM, Carlos E. R. wrote:
On 26/04/2019 21.32, Knurpht-openSUSE wrote:
Op vrijdag 26 april 2019 19:49:32 CEST schreef Carlos E. R.:
On 26/04/2019 15.56, Mark Misulich wrote: > I did find a way to resolve this problem, however. The computer > is a multiboot, with Opensuse 15.0 on a separate partition.
You failed to say that before.
Booting two different Linux on the same disk is not plug and play, you have to do work yourself.
Eh, I have both Leap 15.0 and TW on the same SSD, never had any issues. The only thing I did, since TW is my workhorse, have TW have control over GRUB. I wouldn't call that work.
You have to know that the second install must not install GRUB on the MBR or it destroys the boot of the first install. And YaST will complain that the system is not bootable, has to be booted from the first system.
That's a bit of work. To improve it you must do further work :-)
Is anyone even installing the boot loader into the MBR anymore? (well, except for Windows, of course)
I don't know, or don't remember. I always watch for it and change it if so.
On a BIOS machine with Windows any automatic setup will have problems, IMHO. The /correct/ way is described here:
<https://nwrickert2.wordpress.com/2015/06/15/generic-boot-code/> From 2015, and nothing changed since then ...... These days most machines are UEFI based. Why do you stick to outdated methods.
Well, this machine is not UEFI, nor is my main laptop. And I suspect that the OP's is neither. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org