Partitioning works fine, tough. I created a BFS partition on the first hard drive (/dev/disk/scsi/0/0/0/raw) and set it active. Then, the installer did its thing and completed without error.
Is this because I have two hard drives in here? Or maybe because they are on an AHCI controller (ICH8-M)? Altough the drives are recognized just fine in DriveSetup. I also booted off an Linux livecd and ran parted to create MBR partition tables for both hard drives.
All this worked fine on an older Dell laptop (no SATA/AHCI, one IDE drive).
My system is an Acer Aspire 7720G (Core2Duo, ICH8 Chipset, InsydeH2O-BIOS, 2 HDDs).
Is there a way to work around that? I really want to try Haiku on this system, too
bootman installs to first drive MBR. It can only boot OS off the drive it is installed to. It seems that you installed Haiku to first drive so that shouldn’t be an issue.
Some partition software lays out the partition table in an unsupported way - ie: parted created an incompatible partition map. That’s why you’re getting that error. Usually re-partitioning the drive with the right program will fix it. Try a couple of different partition tools to see which one will do it. For instance, I had an issue with my partition layout and used Partition Magic to fix it but afterwords partition one, BeOS, became un-bootable. Delete entire partition map on the drive & start fresh trying different partition programs.ie: In Linux: cfdisk, fdisk, gparted, etc.; One or more of these will work.
You can actually use GRUB to boot Haiku if you have Linux installed. Or find another 3rd party boot manager and install that.
On a similar note, I installed Haiku on a 10 year old laptop. Intallation went smoothly enough. Then I tried to install a bootmanager. Bootman, GAG, Grub (via super_grub_disk) - all of them claim to have installed themselves succesfully, and not one of them actually works.
I’ve reformatted the disk with gparted-live. Twice. it is a 20 GB disk with nothing but one Haiku partition on it.
In the end, I just decided to leave my super_grub_disk in the CD drive permanently and when sgb’s menu comes up, I tell it to boot “windows”. Not very elegant, but it works.
I already solved the problem another way.
I temporarily set the SATA mode to IDE instead of AHCI. After that, I was able to install BootMan. Then, switched back to AHCI mode - the system boots just fine. BootMan shows up on startup and behaves like it should.
Maybe this is just an issue with this rather exotic BIOS (I think it is…)
Or maybe a bug in the BootMan installer when trying to install to AHCI/SCSI disks? Sadly, I do not have another AHCI/SCSI equipped PC to find out. Should I file a bug report for this?
EDIT: Alright, found out there is already a bug report for this. But how do I add my information to this report, too? Seems like I need special rights on Trac to do that…
