BeOS R5 can run on Pentium D and the very first generation Core multicore processors; and can even use the 2 or 4 cores if the BIOS supports the right MP implementation.
Do you know what processor family the “first generation Core” processors are? I have a machine with the Core Duo U2500 based on Intel Yonah.
Interesting. A lot more GPU talk than CPU talk in there. But I see some success with Core 2 processors (Core 2 Quad Q6700 (Kentsfield family), which are slightly later than the first generation Core Duo/Core Quad. From what I seem to have gathered is that it is more likely for a Core 2 Duo/Quad to function under BeOS, than it is for a Non-2 Core system to work, primarily because those original Cores lacked MPS support. But that seems weird considering that my chipset was based of M to begin with. But I did confirm that my processor/chipset does not support MPS, so I believe that is why I couldn’t run Deved 1.1 or Max on the D420.
There are reports of people running R5 on first and second gen Core, up to Core2Quad - but exceptionally motherboard dependent. Most won’t work.
I remember some people needing to use PCI Promise 133 IDE cards, or supported SCSI, to get any disks to work as very few onboard IDE/SATA controllers were still working with R5 by then.
I’ve never seen any Core i3/5/7/9 reported, even the first of those/third gen Core (ix-xxx models)
Zeta 1.5 runs on slightly newer hardware than R5; I’ve had it running on Core2 era stuff pretty easily that R5 fails on. As far as I remember it uses Haiku’s IDE and SATA drivers from the time; and also has much better USB support, potentially also taken from Haiku…
I’ve had luck with the P35-P45 chipsets, between Abit, Asus, and MSI. Make sure it has MPS setting in BIOS though. Q6700 works great. I tried a newer better one with different stepping and couldn’t get it to work. Check Wikipedia and make sure the one you use has G0 stepping.
Built in IDE support would involve an older motherboard that uses the ICH4 southbridge I believe for IDE support, if I remember correctly. I just use a promise TX2.