lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
<DC-IRC> <gambl0r> hi everyone, I just flashed a new armbian (wip) build to my orangepi 5 plus and performed armbian-install to the emmc, I've rebooted without the SD card plugged in and it looks like it's booting orange pi OS, I can see an orange pi splash screen.. what am I doing wrong?
<DC-IRC> <gambl0r> got it, had to flash bootloader to mtd
<DC-IRC> <gambl0r> wow, the load average goes below 1.0, that's amazing 🙂
<DC-IRC> <efectn> That's really weird issue
<DC-IRC> <gambl0r> no it's not, it should go below 1.0 load average if it's not being used..
<DC-IRC> <efectn> Isn't it meaning cpu is used 100%
<DC-IRC> <efectn> Normally it should between 0 and 1 while idling
<DC-IRC> <gambl0r> no not at all, load average 1.0 is nothing
<DC-IRC> <gambl0r> check that out, that's a proper load average when it's going hard
<DC-IRC> <tenkawa42> no.. there is a known issue right now with high cpu load too on that unit
<DC-IRC> <tenkawa42> at idle you should not have a load avg > 1.0
<DC-IRC> <tenkawa42> and we are seeing that right now with the OPi5/+
<DC-IRC> <tenkawa42> only with the .160 kernel from what I have been told though
<DC-IRC> <tenkawa42> looks like 6.3 might be exhibiting it as well
<DC-IRC> <tenkawa42> @gambl0r btw don't be planning on keeping that build
<DC-IRC> <tenkawa42> 6.3 is done and gone
<DC-IRC> <tenkawa42> stable: 6.3.13 [EOL] 2023-07-11
<DC-IRC> <gambl0r> that was on opi4lts
<DC-IRC> <gambl0r> the screenshot above
<DC-IRC> <tenkawa42> Yea.. just letting you know... we found some hiccups testing with the 5/5+ that are going to show up in other kernels I am about 90% sure now
<DC-IRC> <tenkawa42> but for yours its more important the second part... 6.3 is going away
<DC-IRC> <gambl0r> I built and installed an image with that .160 kernel, didn't notice any high load personally
<DC-IRC> <gambl0r> I'm looking forward to building with 6.4, just waiting
<DC-IRC> <tenkawa42> trust me.. your 36.* is already excessively high
<DC-IRC> <tenkawa42> that load average shoukd not be happeninf
<DC-IRC> <gambl0r> again, that was on an orange pi 4 lts when I was doing stupid things to it
<DC-IRC> <tenkawa42> that load average shoukd not be happening
<DC-IRC> <tenkawa42> *default don't burn up your board boiler plate speech lol*
<DC-IRC> <tenkawa42> lol
<DC-IRC> <tenkawa42> Can't count how many I have lol
<DC-IRC> <gambl0r> lol, losing an SBC is not a big deal
<DC-IRC> <gambl0r> I did have to sit it outside for while after that though, the aluminium case was nearly red hot
<DC-IRC> <tenkawa42> I believe it
<DC-IRC> <tenkawa42> heheh
<DC-IRC> <tenkawa42> (reminds me of how you could use raspberry pi's almost as space heaters)
<DC-IRC> <gambl0r> I couldn't believe the temps my rpi4b were hitting in the official case
<DC-IRC> <tenkawa42> Yeah scary isn it>?
<DC-IRC> <tenkawa42> Yeah scary isn't it?
<DC-IRC> <gambl0r> that thing is a joke, the case too 🙂
<DC-IRC> <tenkawa42> I have the fan cases so those helped a lot (although loud) and 2 Argon40 M.2 cases
<DC-IRC> <gambl0r> I ended up getting one of those flirc cases which are passively cooled, it does ok
<DC-IRC> <gambl0r> anyways, apologies rockhip people, this has gone off topic
<DC-IRC> <gambl0r> @rpardini love your work: https://github.com/armbian/build/pull/5465
<DC-IRC> <rpardini> looking forward to seeing what monsters we use that for... (I've one board needing `uboot_cflags_array+=("-Wno-error=array-bounds")`)
<DC-IRC> <tenkawa42> uboot cflags?? oh god... that's scary to see what someone is going to try
<DC-IRC> <gambl0r> anyways, apologies rockchip people, this has gone off topic
<DC-IRC> <rpardini> they end up being needed, since we use gcc 10/11/12/13 when a lot of those bootloaders are written for 7 or 8
<DC-IRC> <tenkawa42> good point
<DC-IRC> <tenkawa42> I was thinking more like -O2 and the ones to take out debugging etc
<DC-IRC> <tenkawa42> to try to squeeze every bit of size/perf
<DC-IRC> <tenkawa42> etc
<DC-IRC> <tenkawa42> you can go overboard with those and end up breaking things
<DC-IRC> <tenkawa42> @rpardini you might find this amusing... my arm64 compiler to build risc-v native kernels without any extra needed oddness
<DC-IRC> <tenkawa42> make -j 18 STRIP="/usr/bin/riscv64-linux-gnu-strip" OBJCOPY="/usr/bin/riscv64-linux-gnu-objcopy" LD="/usr/bin/riscv64-linux-gnu-ld" CC="/usr/lib/ccache/riscv64-linux-gnu-gcc-12" ARCH=riscv CXX="/usr/lib/ccache/riscv64-linux-gnu-g++-12" "$@"
<DC-IRC> <tenkawa42> I'm about to hook that up to a RK3588 cluster now that my rack chassis add on just arrived a few minutes ago (just putting it together now)
<DC-IRC> <tenkawa42> without the explicit defines... things weren't being found because ot doesn't see it as cross compiling
<DC-IRC> <tenkawa42> without the explicit defines... things weren't being found because it doesn't see it as cross compiling
<DC-IRC> <rpardini> I've recently encountered a SoC with a riscv 32-bit micro that's involved in BLxx
<DC-IRC> <rpardini> Debian/Ubuntu don't carry a gcc for that thing AFAIK
<DC-IRC> <rpardini> So ended up using SiFive's `xPack` gcc build
<DC-IRC> <tenkawa42> heh yeah... good thing they keep that around