<divad27182>
waddlesplash: multiboot is a common boot image format, use by many systems. A multiboot image is something that can be given to grub and many other boot systems to boot something.
<divad27182>
I'm looking to be able to boot haiku from something other than raw disk.
<divad27182>
and there are some odd things implemented using it. There is this thing called "grub invaders" that is a multiboot implementation of space invaders.
<divad27182>
waddlesplash: I take it patch 9501 isn't going to make tonight's build? I certainly agree with your second comment.
<x512[m]>
divad27182: Haiku do not use multiboot spec in any form.
<divad27182>
That's what I feared. I wish it would. :-)
<x512[m]>
Multiboot is not needed today, UEFI exists already.
<divad27182>
but doesn't UEFI also require UEFI infrastructure be provided?
<x512[m]>
You can boot Haiku with any tool that supports UEFI such as Refind.
<divad27182>
that's interesting.
<divad27182>
I could only find things about chain loading.
<x512[m]>
What do you mean by "UEFI infrastructure"? Your hardware likely already support UEFI.
<x512[m]>
And you can run UEFI application from another UEFI application.
<divad27182>
there is a library of functions UEFI provides to boot loader...
<x512[m]>
It is already provided in firmware if PC is not too old.
<divad27182>
if you are running on hardware, and the PC is not too old.
<x512[m]>
Haiku also have no concept of kernel arguments like in Linux.
<x512[m]>
Kernel arguments in Haiku is binary structure, not string.
<divad27182>
right, which is what the bootload presumably sets up.
<x512[m]>
What are you trying to achieve? If you want to make boot menu, you can use rEFInd.
<divad27182>
I will look at that...
<divad27182>
actually, I was hoping to have something to load in Xen.
<x512[m]>
Multiboot is kinda obsolete x86-only thing from Linux ecosystem.
<divad27182>
other than saying "boot the first disk"
<x512[m]>
You need to check for UEFI support in your virtual machine.
<divad27182>
but I would still have to say "boot the first disk". :-(
<divad27182>
I want "boot this image".
<x512[m]>
Where image is located?
<divad27182>
outside the VM.
<divad27182>
(yes, I would need to copy it.)
<x512[m]>
If it is a file on host OS, you can register it as virtual disk in VM.
<divad27182>
but what image can I use?
<x512[m]>
And you can have multiple virtual disks.
<x512[m]>
Yes. It is both BIOS and UEFI compatible.
<x512[m]>
Not really an ISO file system.
<divad27182>
I'm looking for a BOOTLOADER image
<x512[m]>
There are no such thing in Haiku.
<x512[m]>
Maybe you are looking Linux-only option.
<x512[m]>
You need disk image, not kernel or initrd.
<divad27182>
I see /boot/system/haiku_loader.bios_ia32
<divad27182>
of course, that is probably second or third stage...
<x512[m]>
Do you need 32 bit Haiku?
<divad27182>
No. I also see /boot/system/kernel_x86_64
<x512[m]>
haiku_loader.bios_ia32 use custom loading protocol, it is not multiboot-compatible.
<divad27182>
but booting doesn't start out 64 bit...
<x512[m]>
Again, you need to pass whole OS image, not some single file inside Haiku.
<x512[m]>
Linux do not understand format of Haiku boot loader or kernel in any way.
<divad27182>
but that would get THAT image running, not my installed disk.
<divad27182>
It doesn't need to.
<divad27182>
"load file X at address Y, jump to it."
<divad27182>
that is a simple boot....
<x512[m]>
Then you need to properly install Haiku boot loader on installed disk.
<divad27182>
I have that now. I want BETTER!
<x512[m]>
You have too Linuxish way of thinking. Haiku do not work in this way.
<divad27182>
in many ways "Haiku do not work".
<divad27182>
haiku can recognise 3 or 4 types of disks...
<x512[m]>
Imagine running Windows.
<divad27182>
but stuffs them all into PATA
<x512[m]>
Haiku support NVMe disks.
<x512[m]>
Probably one of best options for virtual machines.
<divad27182>
and it shows up where? /dev/disk/ata/1/master ?
<x512[m]>
tree /dev/disk may be helpful.
<x512[m]>
Also #haiku chat is better suited for this problem.
<divad27182>
Is there a way to make a "safe mode" option permanent?
<x512[m]>
Do you mean save video mode? If so, yes, it can be added to config file.
<divad27182>
no, I mean safe mode, as set in the bootloader
<divad27182>
I'm trying some of them to see if they help.
<divad27182>
and if so, I would like to make them permanent
<x512[m]>
Permanent settings are stored in /boot/home/config/settings/kernel
<divad27182>
in this case, apparently /boot/home/config/settings/kernel/drivers/kernel
<x512[m]>
I am not sure that it is currently possible to enable fail safe mode as whole permanent. Individual options such as video mode, ACPI, APM are possible.
<divad27182>
some aren't. I was hoping the don't call the bios option would help.
<PulkoMandy>
Mmu_man had started work on making haiku_loader launchable from multiboot (so you'd use multiboot to start our own bootloader and then the bootloader will load the kernel as usual). It's unfinished, untcuched for many years, but probably still archived somewhere...
jmairboeck has joined #haiku-3rdparty
jmairboeck has quit [Ping timeout: 480 seconds]
jmairboeck has joined #haiku-3rdparty
david has joined #haiku-3rdparty
divad27182 has quit [Remote host closed the connection]
david has quit []
divad27182 has joined #haiku-3rdparty
divad27182 has quit [Ping timeout: 480 seconds]
divad27182 has joined #haiku-3rdparty
divad27182 has quit [Ping timeout: 480 seconds]
jmairboeck has quit [Quit: Konversation terminated!]