Attempting to follow danboid’s footsteps, I re-built and burned the image to my nvme drive.
I have tried just burning the image, as well as manually assigning a GTP table and writing the files to the partitions. I get the following error on the console:
ethernet@16030000 Waiting for PHY auto negotiation to complete… TIMEOUT !
phy_startup() failed: -110FAILED: -110ethernet@16040000 Waiting for PHY auto negotiation to complete… TIMEOUT !
phy_startup() failed: -110FAILED: -110ethernet@16030000 Waiting for PHY auto negotiation to complete… TIMEOUT !
phy_startup() failed: -110FAILED: -110ethernet@16040000 Waiting for PHY auto negotiation to complete… TIMEOUT !
phy_startup() failed: -110FAILED: -110StarFive #
U-Boot is configured to boot from NVMe using UEFI.
visionfive2 branch is used.
@minimum-mmc build target is used. @minimum-raw image need additional preparations like manually making ESP partition and copying Haiku EFI boot loader.
Haiku image is written to NVMe, not SD card. SD card is not supported yet by Haiku and you will get “no boot partitions!” KDL.
Well my “image” is just the compiled environment. None of the bugs have been fixed yet.
You will still need to tell U_Boot how to find the nvme volume. When I get home I will attempt to share my image with you, but you will still need to update the firmware.
If you scroll way up, using Arch Linux is pretty easy to update the firmware on the VisionFive2 following the well written steps.
After that, you’ll need a uart console capable of interacting with the board, I use Minicom from my laptop.
Make sure you rebuild before you upload anything- there’s been several updates over the last few days since you last posted about your success in building it.
I would recommend people learn to build it themselves. It really doesn’t take long on a relaltively decent x86 laptop or desktop - you can build both the tool chain and the Haiku image in less than 20 minutes on an average i7.
Be aware that even if you do get it to boot, you can’t install stuff from Haiku depot so if you’re not willing to type a few commands and get your hands dirty by building your own image, I don’t think Haiku on riscv is for you yet because making it useful currently requires building all your own packages.
The VF2 Haiku images contains next to nothing so no web browser, media players etc. You get Tracker, the Terminal and not much else.
I see your post when you got it to boot has had twice as many likes as mine when I got it to boot before you and also posted the build instructions, presumably because you posted a pic and I didn’t bother.
What we need for an official Haiku repository is a Risc-V machine to build the package. It doesn’t strictly need to be upstreamed, but it should be run by someone fully trusted (this probably mean someone with commit access?) since it will build packages that are hosted by haiku and distributed to all users.
The machine needs to be always on, and connected to the “buildmaster” service that schedules the builds and uploads the packages.
Of course, in the long term we’ll want the machine to run an official release of Haiku, but it doesn’t have to start that way. And it should be possible to do this in a virtual machine as well (it may even be easier to set it up that way?)
This is probably not a problem because @kallisti5 already have it. The problem is setup build infrastructure, various HaikuPorter build master things that I know nothing about.
It should be possible to run Haiku riscv64 in QEMU or RVVM with SSH access (SSH packages are compiled) or finally implement proper cross compilation in HaikuPorter.