On Sun, 20 Sep 2026 00:06:07 +0000 [email protected] wrote: > On Sat, 19 Sep 2026, Duke Normandin wrote: > > > OpenBSD noob here. Successfully installed the latest version of OpenBSD. > > Here's an overview of my setup: > > > > sd0 => antiX Linux & GRUB2 > > sd2 => openBSD > > > > On the first reboot after installation, I went into the BIOS first and > > selected "sd2" to boot from. > > Got to the boot prompt, but it simply chokes and repeats the boot process. > > It seems that it's not detecting "sd2". > > > > I'm sure I hosed something in the install process, but I'm not BSD savvy > > enough to figure it out on my own. Between the various HDD naming > > conventions - GRUB2 vs Linux vs OpenBSD/BSD - it's all a "cluster schmoz" > > at the moment for me. Clues please! > > > > [sidebar] my very introduction to the existence of OpenBSD was when I ran > > into Theo in a Calgary, Alberta, Canada computer store back in the early > > '90s or so. I'm almost 80 yrs on myself so my exact memory of dates etc is > > blurry, but Theo and I were both shopping for some hardware at this store. > > Kudos to him and the team! > > > > > > -- > > Duke > > Boot Mode Mismatch > The single most frequent cause. GRUB (BIOS/legacy) cannot chainload a > UEFI-installed OpenBSD, and vice versa. Both must use the same boot > mode. If your Linux is UEFI-booted, OpenBSD must also be installed in > UEFI mode (and GRUB must chainload the EFI file), or if both are > legacy/BIOS, OpenBSD must be installed to the MBR-style partition. > > Maybe the above?
I see - but Linux is on one HDD and OpenBSD on a completely different HDD. GRUB on the Linux HDD doesn't know anything about the 2nd HDD. For the time being, I'm select the boot drive from the BIOS boot order. Would this scenario still cause the "Boot Mode Mismatch"? TIA ... -- Duke
