Thanks for the info. I am using 32 bit (BIOS), so nothing about EFI applies AFAIK. AQemu does show what Qemu command it launches the VM with, it’s in a menu. So I can compare it’s output to commands other people have used for comparison.
As for the installation, you should first initialise the disk, then create a partition on it, then format it as BFS, then close DriveSetup, and select the partition you created in the Installer.
Okidoki, Then I do not know how to resolve. As for 32bit my latest attempt also failed to create a bootable Haiku. It is known issue. There’s a ticket about it.
Unfortunately random occurs, so not pinpointed what cause this.
Some lucky, some not…
You may want to add entry in this ticket of your problem, and
also you can up vote the ticket as well.
You can find voting stuff : up above, left off ‘Previous ticket’. For voting you must have logged in, and so this way an account in Trac needed.
Well , in that case … also warn you …
some examples with QEMU here are about
ARM
or
RISC-V
platform emulation as well, as Haiku development happened/happens for those as well.
so devs shared their working configs with early adopters/curios people or other devs.
Have done initialize/partition/format as you suggest.
Thanks, I’ll have a look at that ticket, and add info if I can and it is applicable.
As a general reply to anyone who happens to read this thread, here is my current qemu command: using straight from the terminal, no AQemu or other GUI involved:
/usr/bin/qemu-system-i386 -monitor stdio -machine accel=kvm -m 2045 -cdrom /media/Ext4/haiku-r1beta4-x86_gcc2h-anyboot.iso -hda haiku-R1B4 -net nic -net user -rtc base=localtime -name “Haiku-R1B4”
It so far fails consistently to boot from HD, only CD, and pressing (spamming!) shift during boot to “select” HD as OS disk. As soon as CD is detached, no more booting.
Try formatting the whole disk as BFS instead of initialising it with a intel partition table, sometimes that helps in QEMU.
Thanks, I just read the ticket /KitsunePrefecture linked, it is mentioned in there. And while it may be a reasonable work-around for Qemu, it is horrible to see that it has been kicked down the road 13 years. Not to mention not exactly reasonable on bare metal, where no partition map = no multiple OSes!
Last time I installed Haiku 32-bit on bare metal, I had no problems.
I think that workaround is specific to QEMU.
It seems to be a pretty rare issue, and I am not convinced it is the one you are encountering,
and if you want to install bare-metal, if you have any issues I would recommend you use R1/Beta4 media, and then upgrade to nightly, rather than installing from a nightly media.
I had been using Haiku 32 bit on bare metal since Alpha 1 version (2009), always in multi-OS configuration, and the installation process always worked. This issue is appears only on some specifc cases. Note the comment # 35 in the ticket:
This bug only happens when creating a new partition and forgetting to check the “active partition” checkbox.
About your specific issue, I suggest to try some of the Youtube videos that shows the process to install on Qemu. Probably you are missing some step.
1 Like
I don’t understand why everyone insists on trying makebootable. Makebootable is never needed, Installer already takes care of this part.
The most likely problem is that you don’t have a valid master boot record on your disk. This is written when you do one of these operations:
- Create a Intel partition table using DriveSetup
- Use the writembr command
- Install the boot menu using the corresponding option in Installer
This is intentionally not done automatically, because, if you are setting up Haiku in dual boot with another system, it would erase the bootloader for that other system. So, we have decided to not touch anything by default, and you need some manual steps.
1 Like
I’m glad it worked for you and others and grateful to the developers for everything that does work. But is a comment number 35 (of 40) on a 13 year old bug, in a bug tracker that by the way refuses to log me in the best documentation possible? I think not, so I’m trying to do what little I can to at least document pitfalls (“gotchas”) so no one falls for them in the future.
If there is anything I can do without code to make your comment number 40 (automatically mark first/only partition active in drive setup) a reality, I’d be glad to help!
There is, indeed, an installation guide:
Installation Guide | Haiku Project (haiku-os.org)
Look at the step # 10:
> A panel opens to set the Partition size with the slider at the top. As Partition type choose Be File System and mark it as Active partition. Otherwise it cannot be booted.
Ahoy,
I used to do so, but the failure - mentioned above - had happened against that.
I had a successfully installed 32bit Haiku on bare metal, as Installer stated, but not booted, after reboot. It was BIOS boot, I selected the boot device, and : nothing happened as that was expected. No boot splash, no boot.
I installed onto a USB thumbdrive.
.
Currently forum and bug tracker accounts are not shared.
I think the makebootable thing is just a left over from people that got used to manually building and installing to a partition or who read those guides.
Haiku probably could detect a blank MBR as in the case of a fresh VM image or disk and just do the right thing… but yeah overwriting an existing one would be bad.
It already does. If you tell it to write an intel partition map in drivesetup.
The only case where it is not automatic is if you use an existing partition map.
2 Likes