big oof. Do you happen to know at which MB mark? Mine freezes after writing around 1.4GB, @haurog’s at around 750MB mark.
update: there is a new image uploaded today with bianbu desktop, which works so far. No issues seen with the RAM freezes, applications work great and everything looks to be very snappy.
There were new bianbu images uploaded a few hours ago (release 20240802). No freezes or any other issues. These images work reliably. I guess it will take some time until the other images are updated. So with the 16GB version using this bianbu release is the way to go for the moment.
Hi If you don’t me asking how much did you pay for your 16gig board and where did you buy it?
Thanks Franco
I bought it trough one of their official aliexpress stores (Bipai). A link to the shop is at the bottom of the docs: Banana Pi BPI-F3 | BananaPi Docs
I paid 131$ plus 10$ shipping plus then VAT and import tax in my country which added another about 30$ for me.
the problem is localized to u-boot, in the latest version there are many changes in the settings of ddr memory.
changes
8388608000 bytes (8.4 GB, 7.8 GiB) copied, 141.805 s, 59.2 MB/
Thanks for the info. We still have issues when building Rust projects on our Banana Pi F3s. They fail with a SIGSEGV errors randomly. The board does not freeze anymore though. But it still looks like there needs to be improvements for the 16GB version of the boards. Lets hope they iron these problems out with future releases.
I will try it out, thanks alot, your work is amazing!
Currently, the SIGSEV build errors are not a real issue, as I can retry the build until it gets finished.
One big ask - do you know how can I overclock the CPU? I need a few more Mhz if possible. I am aware and it is my full responsibility if something goes wrong.
Thanks alot.
The best way to do this is through an overlay
everything is at your own risk
--- a/k1-x_opp_table.dtsi 2024-08-10 23:20:48.433989554 +0300
+++ b/k1-x_opp_table.dtsi 2024-08-10 23:25:03.735156581 +0300
@@ -11,6 +11,14 @@
clock-names = "ace0","ace1","tcm","cci","pll3";
cci-hz = /bits/ 64 <614000000>;
+ opp1800000000 {
+ opp-hz = /bits/ 64 <1800000000>, /bits/ 64 <1800000000>;
+ tcm-hz = /bits/ 64 <900000000>;
+ ace-hz = /bits/ 64 <900000000>;
+ opp-microvolt = <1160000>;
+ clock-latency-ns = <200000>;
+ };
+
opp1600000000 {
opp-hz = /bits/ 64 <1600000000>, /bits/ 64 <1600000000>;
tcm-hz = /bits/ 64 <800000000>;
Sorry for my noobiness, but how do I install docker and docker compose v2 on Irradium?
in the package manager, the work is described
search: prt-get search docker
package information: prt-get info docker
installation: prt-get -if -is depinst docker docker-compose
prt-get -if -is depinst docker The package 'docker' could not be found:
→ I assume there has to be something I need to do beforehand?
Do not want to hijack this thread, is there any better place to ask this question?
Thanks.
rename the files in /etc/ports
by deleting .inactive
and in the prt-get.conf
file uncomment
prtdir /usr/ports/irradium-core
prtdir /usr/ports/irradium-opt
prtdir /usr/ports/irradium-xorg
prtdir /usr /ports/irradium-xfce
prtdir /usr/ports/irradium-contrib
prtdir /usr/ports/core
prtdir /usr/ports/opt
prtdir /usr/ports/xorg
prtdir /usr/ports/contrib
run: ports -u
perhaps you can ask a question here
testing glibc 2.36 build:
SpaceMit K1 1.6 GHz
real 27m19.909s
user 77m42.387s
sys 11m38.361s
SpaceMit K1 1.8 GHz
real 26m23.577s
user 73m48.399s
sys 11m9.371s
XuanTie C910 TH1520 1.8 GHz
real 29m52.486s
user 67m10.085s
sys 18m35.219s
That is around what we saw as well. Overclocking to 1.8 GHz increases speed by a few percent. We got around 5-6% using stress-ng. Obviously, the speed increase highly depends on what kind of method is chosen. At the same time I saw about am 35% increase in power consumption 11 Watt vs 8 Watts. Quite an increase for a small speed increase. The temperature at the SoC seems to increase by roughly 10% under full stress with my cooling solution.
Thanks to write down how to overclock the BPiF3 with your instructions and the help from @lazyprogrammerio I was able to overclock my own device.
Currently I am playing with irradium. A bit of a learning curve, but it is really nice how I can build rust projects thanks to the patch you incorporated in the irradium kernel.
when using kernel 6.6.y this patch is not needed, in irradium images overclocking can be both enabled and disabled using overlay.
in principle you can use any distribution convenient for you by transferring the kernel from irradium or the official image.