Hi I downloaded and tried the Live CD and Haiku worked fine, looking really good so I thought I’d go through with a full install. I have Debian on this machine so adjusted the partitions - originally putting Haiku on an extended partition but after this not working it is now on it’s own primary partition. I’ve set up Grub to boot with the chainloader and it finds the partition fine and gets to the Haiku splash with the row of icons.
Boot continues until the image of the disk with the leaf at which point it hangs.
I’ve restarted and tried enabling all the Safe Mode options (and various combinations thereof) with no luck. Turning on the debug messages during boot gets a lot of repetition including lines such as:
ata error.RecoverLostInterrupt 0x50
…and various mentions of usb with lost interrupts/handling etc.
Does this sound familiar to anyone and is there a fix?
Also, is it possible to dump the boot debug messages somehow in order to post them here in more detail?
When you goto run the install, boot the live CD into safe mode and set the the drive to IDE. I have noticed issues with buffer overuns and corruption with high drive speeds from the CD rom to the HDD. Slowing things down seems to cure it for me.
Thanks for all the quick replies, appreciated. In the meantime I’ve downloaded the latest nightly build ( haiku-nightly-r38693-x86gcc4hybrid )to check if that improved the situation but it stops at the same point. Incidentally what is the different between gcc2,4 and the hybrid/non-hybrid versions.
I’m stuck on trying to get to the syslog. I have the drive mounted from linux but the path given for the syslog /boot/common/var/log/syslog does not exist. Taking boot as the root of the BFS partition (there is no folder boot) common exists, but there is no var. Is this perhaps the result of startup not completing? Or some failure in the install?
I will try the technique now to reset and save the syslog to a USB stick to post it here.
I’ve found another bug that appears to reflect pretty much what is going on here ( http://dev.haiku-os.org/ticket/4390 ). I will try and follow the debugging steps in that and see if I can get the information out.
In the meantime I rebooted and unfortunately Alt-SysReq-D did not work - the keyboard has apparently stopped responding by the time these errors appear with caps/num lock also not functional. Bit strange as it is working at the point where I push P to skip paging on the logs. As a result it is not possible to get the syslog out via a warm-reboot (even tapping the power button does nothing) so I’ve copied what appear to be the important bits below by hand:
During the boot there are a number of messages but the one consistent bit is as follows:
ata 2 error: timeout waiting for interrupt
ata 2 error: RecoverLostInterrupt: lost interrupt; status 0x50
These continue alongside the messages while it attempts to search (slowly) for the boot partition. Eventually it finds it after dumping all the partition data as follows:
[dump partitions/parameters]
Identified boot partition by partition offset
bfs: mounted Haiku (root node at 524288, device=/dev/dist/ata/2/master/2
Mounted boot partition
That is last interesting log entry before it continues indefinitely repeating the ata 2 error:
ata 2 error: timeout waiting for interrupt
ata 2 error: RecoverLostInterrupt: lost interrupt; status 0x50
I’m not sure what BIOS information would be useful but here are the specs available:
syslog gets created with first boot. Guess the var & log subfolders are also created at that time too.
I see your motherboard has 6 SATA ports but only 4 of those are AHCI compliant.
00:1f.2 IDE interface [0101]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA IDE Controller [8086:2920] (rev 02)
00:1f.5 IDE interface [0101]: Intel Corporation 82801I (ICH9 Family) 2 port SATA IDE Controller [8086:2926] (rev 02)
Your drive is likely connected to ICH9 (non-AHCI) - the 2 port one.
Two choices:
Try BIOS setting of switching SATA to ATA (Legacy/IDE) mode - quick & easy.
Connect to your ICH9R (AHCI) RAID controller and it should then work (check motherboard manual)
Try one of or both of these and see what happens for you. I think this is where your problem lies because of ata error you keep getting. Maybe something else but good place to start.
As suggested I looked up the (S)ATA options in the BIOS. In the Dell BIOS the settings are a bit strange, but under SATA Mode there are two options: IDE & RAID. It was set to IDE. According to the dell forums ( http://en.community.dell.com/support-forums/disk-drives/f/3534/t/18720750.aspx ) the IDE should say ‘ATA’.
So basically I think I’ve ended up doing the opposite of what was suggested by switching from IDE (ATA) to RAID. But this now works and it boots through the the Haiku desktop. I’ve booted into Linux also and it has had no effect on any of that setup (there is a little bit more text output during POST and it appears a little faster to boot but I may be just imagining this).
So anyway solved I guess!
Only downside is that I now realise that WPA is not available in Haiku yet so I can’t connect to the internet (otherwise I would be writing this post from there!) but I can wait - once I get the house to myself I’ll trail a cable downstairs and get it hooked up.
Thanks again for all the help, a really nice welcome to the Haiku community. Much appreciated.