Are there any methods out there that allow Chromebooks to be reloaded with Haiku? I would assume it would need to be an x86 processor to begin with. I have a couple retired chromebooks I was looking to do something with.
Thanks!
Are there any methods out there that allow Chromebooks to be reloaded with Haiku? I would assume it would need to be an x86 processor to begin with. I have a couple retired chromebooks I was looking to do something with.
Thanks!
Yes, but you need to unlock the bootloader. You probably need to install the Custom Coreboot from mr.chromebox, which gives you a normal UEFI PC Firmware. You can then boot and install Haiku normally like you would on any other computer
Yep, thats exactly what I was looking at thanks!
Has there been any recent work with chromebooks that run ARM? Similar to the out of tree Mac work thats been going on lately? I have a couple of those too.
Yes!! It’s called LibreBoot, but it only works on some chromebooks : ( so make sure to check compatibility before trying it out!!
Thanks! What about from the Haiku side of things?
As of my knowledge, I’m not aware of an ARM port of Haiku yet, but I hope to be soon!!
Ahoy,
Regardin ARM/ARM64 Haiku … you can find unsupported images on Nightly build page.
Unsupported means it is for development purposes, these built especially for developers, who understand and resolve upcoming issues during boot and several crashes after even the Haiku desktop reached capable of debugging and other difficulties that much lesser occour on supported nightly builts like x86, x86_64 Haiku versions.
Haiku - ARM
-------VERY EARLY STAGE-------> ARM - Unsupported Builds | Haiku Files
Haiku - ARM64
-------VERY EARLY STAGE-------> ARM64 - Unsupported Builds | Haiku Files
There’s 2 attempts actually regarding Haiku ARM64 port -
targeted bare metal Apple Silicons
(ARM64 related Apple SoCs, like M1, M2, M3, and so on - those are integrated solutions, not only multicore CPU with different performance cores, but multicore GPU with shared RAM, and cores to support AI assisted solutions )
These are closed, cunsomer devices - the development actually happens in VMs on the affected hardwares.
targeted RPI 500+ (the ARM64 SoC, that built in a keyboard, it is also an integrated solution HW as well .. not like x86 or x86_64 with many expansions regarding PCI/PCI-X/PCI-e devices)
This is an open source targeted consumer/developer device - I mean as supported operating systems actually mostly rather Linux distributions, however as Windows has ARM64 versions, possibly some like device may have Windows instances on them - there are peoples who make sport of it to run OSes on devices not targeted primarily (look at Haiku ! - kallisti5 once experienced to run on smartphone and some others on tablets too !.. )
True for both of them :
Works in VM only actually - this way
→ Haiku early stages of boot, memory management, SMP, even filesystems handling
that differs in case ARM/ARM64 fixed improved by developers working on ports
→ virtio* VM devices heavily fixed/improved by developers, who works on ports to have a better developer environment, and also has additions to work closer as bare metal
→ Needs a firmware (bios, uefi like thing) as well, that support the Haiku bootloader on ARM boards, not just the Haiku install image
- → Right now there is no affected application repos - containing ARM/ARM64 ported apps.
First there will be ported that generally shipped with the image …
as the images already are built automatically - but they are just built, not ironed out on that affected ARM/ARM64 architecture.
… and that generally offered with Installer as additionally installed during install - I assume.
![]()