[SOLVED] New dual boot system

colorpurple21859 · 03-17-2024, 02:58 PM

Quote:

For some reason the 40_custom file is not read so the menu cannot be updated.

That usually means there is something wrong in the file. Did you leave off the tailing } at the end of the menuentry?

Quote:

According to fdisk the OpenBSD root partition is at sdb4, so the set root line should be (hd1,4).

You're not chainloading the root partition, you're chainloading the drive (hd1)

yancek · 03-18-2024, 07:34 AM

Haven't used the BSD systems myself but the page at the link below gives several different suggestions that work, at least on FreeBSD, whatever difference that makes.

https://forums.freebsd.org/threads/h...sd-11-1.65992/

cahlucas · 03-18-2024, 11:36 AM

Quote:

Originally Posted by colorpurple21859

One problem fixed.
Post the contents of /etc/grub.d/40_custom

menuentry "OpenBSD" {
set root=(hd1,4)
chainloader +1
}

cahlucas · 03-18-2024, 11:39 AM

Quote:

Originally Posted by colorpurple21859

You're not chainloading the root partition, you're chainloading the drive (hd1)

What is the difference, and how should I make the correct setting?

colorpurple21859 · 03-18-2024, 12:11 PM

Did you put that after what was already in /etc/grub.d/40_custom?
Did you run update-grub after the editing 40_custom, and does your menuentry work? As Yancek mentioned earlier you can press c at the grub menu, and enter the following at the grub> prompt to see if it will work:

Code:

set root=(hd1,4)
chainloader +1
boot

cahlucas · 03-18-2024, 01:29 PM

Quote:

Originally Posted by colorpurple21859

Did you put that after what was already in /etc/grub.d/40_custom?
Did you run update-grub after the editing 40_custom, and does your menuentry work? As Yancek mentioned earlier you can press c at the grub menu, and enter the following at the grub> prompt to see if it will work:

Code:

set root=(hd1,4)
chainloader +1
boot

I passed on the complete contents of 40_custom earlier today. With that content I ran the update-grub command, and that had no effect. Pressing 'c' while the menu is visible does not bring up a command line, so it is not possible to execute commands.

colorpurple21859 · 03-18-2024, 05:22 PM

I don't know what you did, the /etc/grub.d/40_custom file should be like this after adding the bsd menuentry:

Code:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.

menuentry "OpenBSD" {
set root=(hd1,4)
chainloader +1
}

Another way to do this is create a /boot/grub/custom.cfg file with just this in it:

Code:

menuentry "OpenBSD" {
set root=(hd1,4)
chainloader +1
}

cahlucas · 03-18-2024, 07:09 PM

Quote:

Originally Posted by colorpurple21859

Another way to do this is create a /boot/grub/custom.cfg file with just this in it:

Code:

menuentry "OpenBSD" {
set root=(hd1,4)
chainloader +1
}

This gives me a menu entry with OpenBSD, and I can boot that too. The problem is that I can't use the arrow keys. I have to press 'c' first, after which the menu bar jumps to OpenBSD, but the arrow keys remain inactive. What can be done about this?

colorpurple21859 · 03-18-2024, 07:18 PM

I don't know the answer to that one. Maybe opening a new thread, someone else may know the answer.