Dual boot with Devuan Linux, patitioning, Grub2 bootloader

Thank you, @lorglas,
looks like a tutorial even I could follow… :relieved:
Greetings

Hi there,
It’s a old post but didnt see any clear answer and both links provided bt the otehr users are not avilable anymore.
Did you manager somehow to dual boot devuan & haiku?I’m actually trying the same with debian

cheers

those links have been moved to an archive

http://old.besly.de/index.html?/menu/search/archiv/sys/haiku_grub2_eng.html
http://old.besly.de/index.html?/menu/search/archiv/sys/haiku_grub2_de.html

1 Like

Thanks but it didnt fix my problem, unable to dual boot haiku over a debian linux which is what i’m intending
I tried to look for some post but they are either too old or not exactly what i need

The instructions are in Haiku installer welcome text. Or you can just follow the instructions for dual booting windows, the process is the same

Grub Legacy (aka Grub 1) configuration:

title Haiku
root (hdX,Y) # Replace X and Y with relevant values of disk and partition number (both start with 0).
chainloader +1

Grub 2 configuration

menuentry Haiku {
set root=’(hdX,msdosY)’ # X starts with 0, Y with 1
chainloader +1
}

The instructions didnt work for me unfo. Pls ee attached my partition scheme, unable to guess what im doing wrong

Can you try keep your things in one thread please?

my things are covered by both therads someone startup time ago, actually as I’m requesting help for DUAL BOOT LINUX and GRUB2. You can just disregard them

(I modified my previous comment - missed a line).

Your configuration for GRUB2 would be:

menuentry Haiku {
set root=’(hd0,msdos4)’
chainloader +1
}

Additionally, you can use GRUB2 interactively as a shell. When you are presented with GRUB2 menu, just press ‘c’ button to enter the shell. After that, you can manually write all the commands between braces one by one and see GRUB2 answers to ensure you selected BFS partition to boot. You can also press TAB key for autocomplete. This is useful to see what partitions exist on the selected disk. After the last command, just issue one more command to go on:

boot

I just succeeded in booting Haiku on my drive which has three Linux systems on other partitions. I followed the directions at https://www.haiku-os.org/guides/installing_haiku_image_disk_partition

A thread about my adventures is at [SOLVED] Where is haiku-anyboot.image?

The GRUB2 stanza that I’m using is:
menuentry ‘Haiku’ {
insmod chain
insmod eb
set root=‘hd0,msdos8)’
chainloader +1
}

Lane

1 Like

My onw Grub2 Bootloader have:

menuentry "Haiku" {
set root='(hd0,msdos1)'
chainloader +1
}

And Grub2 use the partition boot parameters (hd0,msdos5) for Debian
I don’t really understand why we must prefix msdos before the partition number. There is no msdos on my system to my knowledge.

I’m having trouble on my PC Tower and native install of Haiku :grimacing:. The OS launch but after few seconde - one minut passed on the desktop the system is crached.

I usually use virtualbox for this OS but I want test it on my native machine but it crash. (64bits ed)

This is how Grub calls the legacy MBR partitionning scheme. If you used GPT it would be (hd0,gpt1), for example.

1 Like

Thanks!

It seems that the instability of the system is related to the internet connection. But I’m not sure.
Freeze during Software Updater, WebPositive use and too pkgman is it possible?

I’m using a Wifi connection.

I got around this Software Updater failure on WebPositive by installing OtterBrowser and uninstalling WebPositive. I can get through the Update process only with WebPositive uninstalled. For testing WebPositive, I’d suggest installing it after system update and uninstalling it again before system update. At least for the time being or if someone else has a better idea.

The OS crash before I can install OtterBrowser…This is an Atheros (5008 or 5416) Wifi card.

This may have just been coincidence. I can’t imagine how the presence (more so if it’s not even running) of the Web+ app in your system can influence SoftwareUpdater or pkgman in any way…

1 Like

I can imagine one way. The current limitation in Updater that deletes downloaded packages and forces and complete re-download if the process fails at any point before the update is complete. I was running into a repeatable fail during update that happened while downloading Web+.

Still weird. :slight_smile:
The Web+ package is on the same server as all the other packages. Being below 500 KiB in size, larger packages should be much more probable to fail with a flaky connection.

1 Like

Yeah. I don’t get it either. Sometimes I have the problem. Sometimes I don’t. Its usually just downloading Web+. Sometimes other packages give problems. Sometimes everything works flawlessly. As in I can try it for a week solid and then give up due to persistent failure. Then I can try again the next week and it works fine. The joys of Beta software and picking which battles to fight and which to let go for the best forward productivity of the project. :slight_smile: