chandlerkc

https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ
 
All the latest images from this theme have a new u-boot with support for launching from USB (and also have the correct launch from an SD card, which does not block if there is a problem with NVMe, as happens with the official versions of radha and armbian). Just run this image and select the installation in SPI\MTD in armbian-config, the system will write a new u-boot. You can also install this system immediately on NVMe along with the u-boot update.

http://ix.io/4rod
 
 
$ dmesg | grep pvtm [ 4.064598] rockchip-pvtm fda40000.pvtm: pvtm@0 probed [ 4.064657] rockchip-pvtm fda50000.pvtm: pvtm@1 probed [ 4.064717] rockchip-pvtm fda60000.pvtm: pvtm@2 probed [ 4.064770] rockchip-pvtm fdaf0000.pvtm: pvtm@3 probed [ 4.064821] rockchip-pvtm fdb30000.pvtm: pvtm@4 probed [ 4.360207] cpu cpu0: pvtm=1499 [ 4.360292] cpu cpu0: pvtm-volt-sel=4 [ 4.374085] cpu cpu4: pvtm=1734 [ 4.382508] cpu cpu4: pvtm-volt-sel=5 [ 4.397347] cpu cpu6: pvtm=1745 [ 4.405565] cpu cpu6: pvtm-volt-sel=6 [ 4.487909] mali fb000000.gpu: pvtm=885 [ 4.487947] mali fb000000.gpu: pvtm-volt-sel=3 [ 4.568549] RKNPU fdab0000.npu: pvtm=887 [ 4.572941] RKNPU fdab0000.npu: pvtm-volt-sel=4  
 
neofetch output:
$ neofetch chandler@rock-5b ---------------- █ █ █ █ █ █ █ █ █ █ █ OS: Armbian (23.02.2) aarch64 ███████████████████████ Host: Radxa ROCK 5B ▄▄██ ██▄▄ Kernel: 5.10.110-rockchip-rk3588 ▄▄██ ███████████ ██▄▄ Uptime: 1 day, 3 hours, 29 mins ▄▄██ ██ ██ ██▄▄ Packages: 2101 (dpkg) ▄▄██ ██ ██ ██▄▄ Shell: bash 5.2.15 ▄▄██ ██ ██ ██▄▄ Terminal: /dev/pts/0 ▄▄██ █████████████ ██▄▄ CPU: (8) @ 1.800GHz ▄▄██ ██ ██ ██▄▄ Memory: 470MiB / 7688MiB ▄▄██ ██ ██ ██▄▄ ▄▄██ ██ ██ ██▄▄ ▄▄██ ██▄▄ ███████████████████████ █ █ █ █ █ █ █ █ █ █ █  
The download speed at https://disk.yandex.ru/d/V5AxXNN2yJnOfg/20230320-edge is horrible...
 
Can you, please, tell me where is the download link and the u-boot flash instructions? 😊

Thanks in advance!!

Version 20230320-edge with pancsf-midstream core (6.2).
To enable HW acceleration, install the mesa package with the forced overwrite option 
 
dpkg -i --force-overwrite mesa_23.0.0-dev-2_arm64.deb 
 
After installation and reboot, HW acceleration will work in x11 and wayland.
Please note, this is a test version of mesa for the initial evaluation of the work, some of the functions do not work in it and there may be bugs.
With x11, the system works more stably, but the test results are lower than in gnome+wayland.

It turns out it wasn't my power supply. I had partitioned my NVMe into two, one for /boot and one for root, and told it to install to the root partition on /dev/nvme0n1p2 . Had the same issue: hang at boot time with the blue light on continuously (but not looping through a power cycle: the blue LED never turned off, as it would in a boot loop). Then I had a flash of "maybe..." and repartitioned the NVMe as one partition, then installed to it with armbian-config. Success! I get a lot of messages at boot time scrolling through the console that I can't read (I use a 4K monitor, and it's tiny text), but it does run without the SD card in place. Yay!
 
Now to see how fast it runs the application I got it for.

Yes. To use Name, start the system from the SD card and perform the installation using arm bin-config (use the SPI + NVMe\SATA installation option). Please note - my version does NOT support PD power supplies

Version 20230209 with kernel 5.10.110 with added HW support.
Test results.
 
[function] fragment-complexity=medium:fragment-steps=5: FPS: 4379 FrameTime: 0.228 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 4636 FrameTime: 0.216 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 4973 FrameTime: 0.201 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 4869 FrameTime: 0.205 ms ======================================================= glmark2 Score: 3851 ======================================================= user@rock-5b:~$ PAN_MESA_DEBUG=gofaster glmark2-es2-wayland arm_release_ver of this libmali is 'g6p0-01eac0', rk_so_ver is '6'. arm_release_ver of this libmali is 'g6p0-01eac0', rk_so_ver is '6'. ======================================================= glmark2 2021.02 ======================================================= OpenGL Information GL_VENDOR: ARM GL_RENDERER: Mali-LODX GL_VERSION: OpenGL ES 3.2 v1.g6p0-01eac0.ba52c908d926792b8f5fe28f383a2b03 ======================================================= [build] use-vbo=false: FPS: 4336 FrameTime: 0.231 ms [build] use-vbo=true: FPS: 4783 FrameTime: 0.209 ms [texture] texture-filter=nearest: FPS: 4729 FrameTime: 0.211 ms [texture] texture-filter=linear: FPS: 5175 FrameTime: 0.193 ms [texture] texture-filter=mipmap: FPS: 5091 FrameTime: 0.196 ms [shading] shading=gouraud: FPS: 4258 FrameTime: 0.235 ms [shading] shading=blinn-phong-inf: FPS: 4404 FrameTime: 0.227 ms [shading] shading=phong: FPS: 3972 FrameTime: 0.252 ms [shading] shading=cel: FPS: 4183 FrameTime: 0.239 ms [bump] bump-render=high-poly: FPS: 2528 FrameTime: 0.396 ms [bump] bump-render=normals: FPS: 5949 FrameTime: 0.168 ms [bump] bump-render=height: FPS: 6005 FrameTime: 0.167 ms [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 4548 FrameTime: 0.220 ms [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 3866 FrameTime: 0.259 ms [pulsar] light=false:quads=5:texture=false: FPS: 5457 FrameTime: 0.183 ms [desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 1829 FrameTime: 0.547 ms [desktop] effect=shadow:windows=4: FPS: 4512 FrameTime: 0.222 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 528 FrameTime: 1.894 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 495 FrameTime: 2.020 ms [buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 817 FrameTime: 1.224 ms [ideas] speed=duration: FPS: 2543 FrameTime: 0.393 ms [jellyfish] <default>: FPS: 3489 FrameTime: 0.287 ms [terrain] <default>: FPS: 299 FrameTime: 3.344 ms [shadow] <default>: FPS: 3963 FrameTime: 0.252 ms [refract] <default>: FPS: 633 FrameTime: 1.580 ms [conditionals] fragment-steps=0:vertex-steps=0: FPS: 4990 FrameTime: 0.200 ms [conditionals] fragment-steps=5:vertex-steps=0: FPS: 4897 FrameTime: 0.204 ms [conditionals] fragment-steps=0:vertex-steps=5: FPS: 4423 FrameTime: 0.226 ms [function] fragment-complexity=low:fragment-steps=5: FPS: 4529 FrameTime: 0.221 ms [function] fragment-complexity=medium:fragment-steps=5: FPS: 4752 FrameTime: 0.210 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 4532 FrameTime: 0.221 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 4175 FrameTime: 0.240 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 4724 FrameTime: 0.212 ms ======================================================= glmark2 Score: 3800 =======================================================  
 
For details of the new features, see this topic.
 
https://forum.armbian.com/topic/22986-firefly-station-m3-rk3588s/?do=findComment&comment=159554
 

Hard to say, I've had so many different configurations on this board in the last 6 weeks. Here's how I did it last time.
 
- The 1st time I started with an unformatted nvme SSD. Then using https://github.com/armbian/build/releases/download/23.02.0-trunk.0186/Armbian_23.02.0-trunk.0186_Rock-5b_jammy_legacy_5.10.110_minimal.img.xz burnt to SD.
- Booted the SD then used arbian-install and selected the 3rd option (i think) to flash the boot loader to SPI flash. It's a slow operation, be patient.
- Then selected option 1, install to mmc, nvme, or something like that.
- Power cycle after removing the SD card.
 
The downside of this configuration is that you can no longer boot from SD, as pointed out previously. This leads to problem with consecutive installs. To workaround the problem I zero out the 1st few blocks of the nvme before shutting down prior to the install.
 
That said, for the time being I've given up on Armbian for the rock-5b and have reverted to to Radxa's Ubuntu server image. I run exclusively headless, except for installs, and that configuration best meets my needs. I've alsways had a trouble free experience with Armbian running on all my previous Rockchip based SBCs so this is a 1st!
 

I think the power supply might deserve it's own topic.
 
Like balbes mentioned PD is meant for devices with internal battery. There it saves the battery during fast charging by preventing overcharging.
The Rock 5B is further 'borked' since the negotiation starts after the system starts. The advantage is it can be open source (more or less), but the big disadvantage it is so slow most PD chargers stop negotiating during system start in the meantime.
 
If you realise that the power supply in the Rock 5B (IP2315) is just a step-down converter with some logic and a PD car-adapter adds an step-up adapter to the equation you might realise it makes no sence to operate the power input at 20V. While the resistance in the cable might be minimized the power loss in the step-down and the step-up converters are maximized. Most power supplies can achieve 95% efficiency, but cheap step-up/step-down converters can only achieve that when V_in is almost equal to V_out. Normal PD-adapter should work more efficient than 12V car-adapters, but even then if they very efficiently produce 20V which the R5B very inefficiently transformes to 3.3-5V does that make sense?
 
A 20W PD car-adapter adds roughly 0.5W to the power consumption. With a 65W/20V PD car-adapter the adapter might add more, but the step-down converter in the R5B will definitely work more inefficient than at 9V.

These are the official versions, please contact the appropriate section with all questions. Modified versions are discussed in this topic, they differ from the official ones.