DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD Installation and Upgrading

OpenBSD Installation and Upgrading Installing and upgrading OpenBSD.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 13th September 2022
HopingStar HopingStar is offline
Port Guard
 
Join Date: Sep 2020
Posts: 21
Default Dual boot OpenBSD UEFI with Linux

Not sure how to create Grub menuentry for it. Is there anyone here used to dual boot UEFI OpenBSD with Linux?
Reply With Quote
  #2   (View Single Post)  
Old 13th September 2022
HopingStar HopingStar is offline
Port Guard
 
Join Date: Sep 2020
Posts: 21
Default

I end up using efibootmgr to generate bootloader for it. This is the command I use
Code:
efibootmgr -c -p 1 -d /dev/nvme0n1p4 -L OpenBSD -l /EFI/Boot/bootx64.efi
Ah, no need grub or rEFInd anymore
Reply With Quote
  #3   (View Single Post)  
Old 13th September 2022
Head_on_a_Stick's Avatar
Head_on_a_Stick Head_on_a_Stick is offline
Real Name: Matthew
Bitchy Nerd Elitist
 
Join Date: Dec 2015
Location: London
Posts: 461
Default

OpenBSD's .efi loader should not need an NVRAM entry.

I think you should have just deleted any unused NVRAM boot entries, they were probably preventing /EFI/Boot/bootx64.efi from starting.

Use this to remove superfluous boot entries:
Code:
efibootmgr -b xxxx -B
Replace xxxx with the actual boot number, which can be found by examining the plain efibootmgr output.

EDIT: and this will generate a GRUB entry:
Code:
menuentry 'OpenBSD' {
   search.fs_uuid $uuid
   chainloader /EFI/Boot/bootx64.efi
}
Replace $uuid with the actual UUID of the EFI system partition (ie, the one containing bootx64.efi).

Last edited by Head_on_a_Stick; 13th September 2022 at 02:50 PM.
Reply With Quote
  #4   (View Single Post)  
Old 13th September 2022
hd77 hd77 is offline
Shell Scout
 
Join Date: Jan 2022
Posts: 97
Default

Quote:
Originally Posted by Head_on_a_Stick View Post
OpenBSD's .efi loader should not need an NVRAM entry.

I think you should have just deleted any unused NVRAM boot entries, they were probably preventing /EFI/Boot/bootx64.efi from starting.

Use this to remove superfluous boot entries:
Code:
efibootmgr -b xxxx -B
Replace xxxx with the actual boot number, which can be found by examining the plain efibootmgr output.

EDIT: and this will generate a GRUB entry:
Code:
menuentry 'OpenBSD' {
   search.fs_uuid $uuid
   chainloader /EFI/Boot/bootx64.efi
}
Replace $uuid with the actual UUID of the EFI system partition (ie, the one containing bootx64.efi).
yep, openbsd can be added with a openbsd partition (whom will be used as an aera for all slices) on the disk. I use tri/quadri boot with win/lmde by grub.

however, it's recommended to have also the bsd.rd within the 40_custom of grub.
Unfortunately, I dont have it on my laptop right now (bios, like others), but I did it on several efi laptops.
Reply With Quote
  #5   (View Single Post)  
Old 20th October 2022
shep shep is offline
Real Name: Scott
Arp Constable
 
Join Date: May 2008
Location: Dry and Dusty
Posts: 1,503
Default

As a caution, Redhat based distributions use /boot/efi/BOOTX64.EFI as their default location. This is also the default for OpenBSD and will result in Grub booting OpenBSD instead of Centos/RHEL/etc....
If you move OpenBSD location, as suggested in this thread, it will function but there will be an error generating the sha256 sum for the unique kernel. OpenBSD looks for /boot/efi/BOOTX64.EFI to update the sha256 sum and will fail if it is in a different location. OpenBSD will still run but not have a unique kernel with every boot.

Debian based derivatives and Arch Linux do not have this problem and the unique kernel checksum will work if you use /boot/efi/BOOTX64.EFI.

Last edited by shep; 21st October 2022 at 12:53 AM.
Reply With Quote
  #6   (View Single Post)  
Old 21st October 2022
Head_on_a_Stick's Avatar
Head_on_a_Stick Head_on_a_Stick is offline
Real Name: Matthew
Bitchy Nerd Elitist
 
Join Date: Dec 2015
Location: London
Posts: 461
Default

Quote:
Originally Posted by shep View Post
Debian based derivatives and Arch Linux do not have this problem and the unique kernel checksum will work if you use /boot/efi/BOOTX64.EFI.
Arch will overwrite bootx64.efi if systemd-boot is employed. There doesn't seem to be an option to prevent systemd doing this, which is a shame.

Debian will overwrite bootx64.efi if the "force installation to removable loader location" (force_efi_extra_removable) debconf option for GRUB is used.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
DUAL BOOT OPENBSD WINDOWS 11 vdavi81 OpenBSD Installation and Upgrading 12 14th September 2022 12:25 PM
Can not Boot FreeBSD NetBSD in Bare Metal, UEFI czachstd NetBSD Installation and Upgrading 5 28th July 2020 03:24 AM
FreeBSD 11.1 amd64 UEFI boot from ZFS mirror hanzer FreeBSD Installation and Upgrading 5 20th October 2017 10:53 PM
Invalid Signature when trying to boot Ubuntu 14.04 (Dual Boot) bsd007 FreeBSD General 7 18th September 2014 12:37 PM
Dual-boot laptop won't boot OpenBSD after upgrade to 4.3 kbeaucha OpenBSD Installation and Upgrading 17 30th May 2008 02:40 PM


All times are GMT. The time now is 08:56 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick