It was fixed in new dm2 branch versions. But latest version seems have vf2 boot regression.
No, latest firmware have broken UEFI GOP framebuffer driver, so it require OS graphics driver for VisionFive 2 that is currently not implemented. Even after graphics driver will be implemented, there will be no bootsplash because it use firmware framebuffer and graphics driver is not started yet.
Haiku hrev57311+155 (dm2):
(needs further review and testing)
What is this fox about?
May require a bit of cunningness or cleverness to find the issue(s).
Problem is quite clear: new versions of firmware shutdown GPU framebuffer after exiting UEFI boot services, so generic Haiku graphics driver is not working. In order to fix problem it is needed to make firmware to not shutdown framebuffer as dictated by UEFI specification (need changes on firmware side that Haiku have no control) and/or implement Haiku graphics driver for VisionFive 2.
Ah, nice, makes senseā¦
We will meet the Fox then more often now, I suppose!
Get the bugs, get them all:
what is better, native haiku gfx driver or UEFI framebuffer driver?
The efi framebuffer driver does not allow to change resolution after booting. At the moment this is pretty much the only difference.
Would it be crazy to wrap the Linux modesetting driver for that (and for any other simple modesetting drivers)?
In old computers work on vga driver and switch do ādesktopā gfx driver when system is loading. Now in computers world use a UEFI Gfx Driver on desktop ?
IāThink beter is primary solution with a framebuffer (VGA driver) itās to be a compatibility with older post-embbeded (SBC) systems.
This could be developed into a separate topic.
When a mmc will be work ? I work on hrev āofficalā version of image on NVME. Both of power led shine and green led shine, when loading a Haiku Riscv version. Thatās all. And donāt see a desktop screen.
Insulting people is a curious way to expect help from them. Feel free to edit your post to remove the incivilityā¦
I donāt own a VF2. Iād like to know from people owning it how it feels, how it performs. What does Haiku riscv lack compared with standard Haiku x86?
Iāve not tried it in a couple of months but it was very unstable, I couldnār get any sofrware to build (the Haiku dev package doenāt get installed by default) and there are no pre-built packages for it beyond whats included in a bare Haiku install and not even all of the standard Haiku nighly packages are available on rv64 yet such as web+.
The ethernet kinda works but you have to have a serial cable attached to activate the eternet adapter in u-boot before you boot into Haiku and so on.
TLDR; its not really usable yet.
Iāve not used it a ton but have not seen crashes other than the known issue with disconnecting USB devices. USB and input devices have been problematic for me since out of all the devices I tried many that have worked in other Haiku installs refused to here. Iāve been thinking Iād like to try compiling Barrier (ex-Synergy) to get over that particular hurdle for now.
Greetings all. I have a moved into a new house, and now have a few minutes to play with things. On my new linux system, I receive the following error. Iāve been searching for some reason uversion.h canāt be found, but nothing helps. Any chance anyone has seen this before?
ā¦/src/kits/locale/Collator.cpp:8:10: fatal error: unicode/uversion.h: No such file or directory
8 | #include <unicode/uversion.h>
| ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
I have tried to checkout X547 device_manager2, rvvm, and several other branches to see if they help, but they do not.
I have tried to compile iuc from source, installed all the dev libraries, but nothing seems to work. Iām sure its a file placement issue, please advise.
EDIT: Ok, with jam -q it immediately fails, with out -q, it will complete the ācreating the packageā, but the build will still fail. Thoughts?
-q means quit on fail, without it it continues after a fatal error.
Sorrry, it was late and I was unclear. I should say that is the only error, and I am unable to resolve it. It fails multiple times, so even if I find the uversion.h file, I am unsure where to put it so the compiler is happy.
So, that file is found in the icu66_devel package, so you should make sure you have it (or another version of icu_devel) installed.
If you already have it installed, then you may need to run ./configure again.
It seems my branch use old ICU version that do not match upstream one. Updating repo definition file is needed.