Hi. I wanted to test Haiku on a B550M motherboard. It successfully boots from the USB installer, but fails to boot from any drive after installation.
It’s an ASRock B550M Pro4. I’ve tried all the different safe mode options, and tried various BIOS settings, including enabling the CSM.
I tried installing on UEFI and Intel partition map drives, with EFI and MBR booting, on nvme and sata. Everything installs OK, but when booting, none of the initial icons light up, and it seems frozen.
I haven’t seen anything recent about this chipset, but it seems others have been able to boot Haiku on it. Is there some BIOS setting or something else that will help? I don’t think the storage controller is incompatible as everything seems to read/write/install OK.
Edit: found forum post with similar symptoms. They mentioned boot log. I will see if I can get more information. I also see that someone reported similar hardware that worked with no issues, but they were using rEFInd. I guess I’ll try that, but it would be nice if Haiku could have a working boot menu with EFI booting, with support for entries on multiple drives.
The boot menu will offer to boot several partitions if it can detect them.
For booting other OS, I’d say it’s not worth making an Haiku specific menu, because rEFInd does a great job already. Maybe we could have a nice easy to use installer for rEFInd?
Even if using rEFInd, maybe it could be modified to look like BeOS bootman without having to manually customize. And yes, Haiku bootman can boot from multiple partitions, but only from 1 drive.
@_AP Something you might want to do is to go look for an off the shelf branded system that uses that motherboard, the “AMD B550 chipset for AM4 socket processors”, or lists one of the AMD Ryzen CPU’s that your board+chipset support.
Then you can see if there is an entry for it (or a similar system) over here:
PS -----
Just filtering the list of system for “Ryzen” CPUs turned up ~15 entries listing a Ryzen cpu of some sort, although the only ones that seem likely to be a relevant are these. Granted that I find AMD’s product naming a bit confusing.
The AMD Ryzen 5 3400G is an AM4 socket processor that I think ought to be compatible with your motherboard, at least in principle, but there might be a problem with some of the hardware that you actually have.
Google’s AI overview claims that the a B550M motherboard should support the following Ryzen desktop processors (AM4 socket):
@_AP Have you tried installing Haiku to another USB flash drive? It seems odd that a drive attached via SATA wouldn’t work, but maybe the SATA controller isn’t getting initialized properly?
Also, if your board is the same one as Newegg is selling (see link below), it probably has a motherboard header for a COM port (usually that term refers to regular old 9 pin Serial).
If you have another working computer with an OS installed that also happens to have a hardware serial port then you could get a serial port “adapter” (a ribbon cable with a DE-9 serial port on one end and a female header plug on the other that goes into the motherboard header).
By connecting that machine to the one you’re trying to boot Haiku on, you should be able to get access to debugging output on the serial port with some software like Putty or TeraTerm.
Anyway. I stand by what I said about needing bootman support on UEFI booting systems. It appears this system doesn’t boot via MBR, even with CSM enabled.
I installed bootman (x86_64), after I red many times here in the forum - from several people - they booted Haiku 64 bit in Legacy boot. It was the missing piece that was not shared and highlighted to install for successful boot without UEFI, but Legacy mode !
It failed for me since then, when I switched my actual machine to UEFI directly, as I installed Linux to this Dell Precision M680 laptop - switching to Legacy and right boot order (USB first) made it work again.
I installed bootman (one common USB thumbdrive for Beta5 and one common for nightly 64 bit, no separately used for another machines) as I got another Dell Precision with core2 Quad Extreme, there were no UEFI BIOS, but Legacy - but I wanted to use 64 bit Haiku there. It succeed, but there were some input quirks and weirness with touchpad trackpoint and so on, so I stopped experimenting with … I wanted a no frustration period for me
So this way now share my time between Linux (Works as I want, not so much I miss there) and Haiku (Love the look and feel, the colors of the system, and some more well written little or even cute details ! it’s my favourite, so I can forgive if it’s still a little raw somewhere or if something is missing.)
Maybe I am forgetting something since last time I played around.
MBR booting is different on 64 bit vs 32 bit? Also, I completely forgot to try 32 bit. I forgot that I wanted to use BeOS apps, so I will want to use 32 bit.
Haiku x86 – legacy BIOS boot , by default.
bootloader is in the main dir on the same partition like the whole install : ia_32_bios_trallala - so this is legacy bios bootloader for 32 bit Haiku.
On the install media there is a 32 bit URFI bootloader, but there’s no so much 32 bit, but UEFI firmware board - some early instances - I had never met such, I just had red about it in the forum. Also there are some where the UEFI is 32 bit, but the platform itself 64 bit. Those members are interested a more matured 32 bit UEFI bootloader.
If I know well, my co-patriot, David Karoly worked on a hybrid UEFI bootloader, 32-64 bit also - that would have helped ARM stuff loading as there are 32 bit and 64 bit ARM systems, and in 2022?- 2023? he worked on ARM stuff strongly. Devs found his knowledge good enough to get commit right as well.
Haiku x86_64– UEFI (BIOS) boot , by default.
If there is Legacy CSM support in this UUEFI ROM, then you can switch to , and organize legacy bootorder - by bootable devices.
Then you need Bootman – installed onto the drive’s MBR – for booting 64 bit Haiku , and select bootable partitions in Bootman configuration. Recommended to put as first partition, if possible - well I created the Haiku esp as first partition - I had not noticed that in the anyboot image the UEFI System Partition always the second.
Anyway Bootman works well, just have the machine in Legacy CSM and right boot order with devices, target set as first drive to boot from.
I used the 64-bit installer, installed to first partition of MBR disk, and installed bootman. Legacy CSM is enabled. I couldn’t get that to work. I’ll test 32-bit and see if it makes a difference.
