gounthar

No, I'm not on any list or pre-order.
 
I'll wait until an all-in price is known (incl EU VAT en shipping). And an install procedure that is feasible for me.
 

I'm not. I'm still waiting for the Star64 to appear, and then I'll maybe take a decision.
Oh wait, stupid me has bought a coupon of some sort to get a rebate on this Lichee board...

Lichee Pi 4A is powered by a 2.5Ghz TH1520 RISC-V processor. It supports up to 16GB of RAM. It is on pre-order
It intends to support Debian
 
Is anyone else on the wait list for this ~$99 device (EST March 2023)
 
They may also do a CM4 footprint one (or they could just be humoring me)

Waiting for a RPi4 since Dec'21. So I just ordered the Nanopi R5C (which arrived by today). But it looks like there is no ARMbian for it, right now. Might it be compatible with another ARMbian image? Maybe the one for Nanoopii R5S?

Of course it's far from perfect, but can be used. I remember the start of rk3399 boards, that was pretty bad in comparison to today.
ARM64 and panfrost really made some serious progress.
 
JFYI, wayland progress on gnome was always more advanced than KDE's (and only choice if you wanted working wayland DE besides sway etc)

hi, got production Rock5b with 16GB, passive cooling, Rock A8 wifi6 card, Jammy with Cinnamon desktop, updated SPI so have SSD boot now, nice. Thank you Armbian team!
Even with hardware acceleration sw installed still mis 10% of frames in youtube both Chromium and FF, tab crashes now and then in Firefox.
Wifi works but bluetooth, no devices found ..
Bought new 1TB WD Black SN850X gen4 for euro 105.
@gounthar looks like SN850X is a mini bit faster than @mzbs Samsung 970 EVO Plus.
Looking at my earlier testing is on par with my AMD 2400G and 2-4x faster than my Nanopi4a RK3399, not bad!

 
hdparm -tT --direct /dev/nvme0n1 /dev/nvme0n1: Timing O_DIRECT cached reads: 3770 MB in 2.00 seconds = 1886.21 MB/sec Timing O_DIRECT disk reads: 5888 MB in 3.00 seconds = 1962.44 MB/sec
 
fio ... (summary) Run status group 0 (all jobs): WRITE: bw=3157MiB/s (3311MB/s), 3157MiB/s-3157MiB/s (3311MB/s-3311MB/s), io=185GiB (199GB), run=60041-60041msec Disk stats (read/write): nvme0n1: ios=0/379492, merge=0/1939, ticks=0/14926632, in_queue=14926644, util=99.81%  

FWIW: someone (an early bird) has received it: 
 
 

VisionFive v2 - an interesting sequel to VisionFive (StarFive) 
 
https://forum.rvspace.org/t/how-to-purchase-visionfive-2/665/9

Thanks again @balbes150for all the help and the great work!
I managed to boot and to configure everything properly on my Mango Pi MQ with the headless image you built on 1st of December.
However after a while (a few minutes only), if I'm not active on the command line, the wifi goes on sleep and it's impossible to wake it back up, only a reboot can fix it. It seems like a driver issue?
Am I the only one who experiences it? Do you have a workaround? Thanks!

I can add PR to the official Armbian build system for RISC-V (then the kernel will have an automatic update), but I'm not sure it will be accepted.

To automatically update the kernel, you need to have a network repository, I don't have such an opportunity yet. I've heard that someone is working on creating such a repository for this build system. If it is, then the kernel will be updated automatically. In principle, I can add kernel packages to the image directory for manual updates (in case there is a significant kernel change).

use an image without XFCE in the name .
Armbian_22.08.0-trunk_Nezha_jammy_current_6.1.0.img

You inattentively read the info earlier.
I specifically wrote that Debian (sid) requires ADDITIONAL manual work to run (copying additional files, editing the configuration file, etc.). Use Ubuntu versions, there is nothing you need to change after writing the image, it connects and will work.

Describe in detail what the problem is, what steps did you take? My system runs fine and runs on mangoPIMqpro.
 
All images from this theme are collected on a PC in cross-compilation mode. I also checked the full image build on StarFive1 (i.e. directly on the RISC-V device), it works the same, but so far I don't have a fast enough RISC-V device to switch to a fully native build. I know that there are some Discord-Risc-v participants who build on ARM devices (including in cluster mode on multiple devices at the same time). You can clarify all the details in the corresponding Disord topic.

Thanks a lot @balbes150for this new build! I got a Mango Pi MQ and one of the previous builds with xfce works extremely well, I am impressed both at the responsiveness of the (modest) hardware, and at your work to build a very decent desktop image!
I came back to this thread to look for a headless image, as this how I plan to use this board, and you just uploaded a new one today, which is great.
I downloaded this one: Armbian_22.08.0-trunk_Nezha_jammy_current_6.1.0.img.xz (version 20221201) but I have a question, I looked through the whole thread, what is the login/password 😄
The previous version I tried had a setup that let me setup the username and password, but this version doesn't offer it.
Thanks and keep up the great work!
 

I have already checked on MangoQ Pro, it works.
 
by the way, when testing on different D1 devices, I noticed that USB is always detected and works.

Version 20221201 for Allwinner D1.
The 6.1.0-rc3  kernel is used. It is important that it is possible to use DTB separately in the kernel regardless of u-boot.
Can manually configure which DTB to use, this is useful for using different hardware on different devices.
There is no Debian version yet, because the system has been switched to EFI, while there is no full EFI support in Debian.

If you turn off HDMI, the system resets the settings that were agreed upon when you turned it on. you can try specifying fixed settings in the startup command line or try switching via xrandr (search the Internet for how this is done).
 
This advice applies to working with u-boot and it needs to be done in u-boot (via the UART console).

@TaNGSoFT@gounthar Armbian has supported u-boot spi image since its initial support for rock5b. If you are using spi flash image from radxa wiki, you will failed to boot armbian because that is not a GPT image.  There are two ways to write the spi flash image from armbian to the spi nor flash:
1, Boot armbian from sdcard or emmc first, and use nand-sata-install to install the u-boot to spi flash.
2, You can download the u-boot deb file from the repo of armbian: https://mirrors.tuna.tsinghua.edu.cn/armbian/pool/main/l/linux-u-boot-rock-5b-legacy/linux-u-boot-legacy-rock-5b_22.08.6_arm64.deb. Extrat it using `dpkg -x linux-u-boot-legacy-rock-5b_22.08.6_arm64.deb`, and find the spi image file `rkspi_loader.img`, and write it to spi flash referring to radxa's wiki: https://wiki.radxa.com/Rock5/install/spi
Then use dd or ether to install armbian image to your NVME SSD.

Please don't misunderstand my question: I'm not asking for you to "hurry up and deliver the finished product so I can use it".
I do know how this game works, and I have seen evidence over the years of the colossal effort you put into this project.
You've done a great job, as usual, producing an image *THAT WORKS* (so well) in such a short time ... I'm very grateful.
It's because of efforts from you, and others in the Armbian project, that I get to use Debian on devices that probably wouldn't be supported otherwise.
 
I'm simply asking what is preventing us/me/you/everyone from using Bullseye with the kernel you've used for the Sid image?
Is there something in particular that's in the debian-sid (or armbian-sid?) userland that is required?
 
There are a number of things I'd like to try out on this board (headless), and running Debian-stable makes that a lot easier (eg: PHP) without having to containerise everything.

Yes, openjdk is available on Armbian Jammy. Actually it is from Ubuntu Jammy repositories. Default one is v11

I have been able to run armbian on a Samsung 970 Evo Plus 250GB SSD. Really nice...
 
It is though necessary to note that only a 5 Volt USB-C power supply is working with the Rock 5 Model B.

This is great so far, and I was able to get the image to work from the maskrom method to the eMMC.
 
Some things I've noticed:
 
- Video driver is the default software renderer, I've followed the steps here to use an alternative https://launchpad.net/~liujianfeng1994/+archive/ubuntu/panfork-mesa 
- That video driver seems to have some issues still, and does not feel very stable
- Chrome & FF will need some work to make use of the Mali video card, currently seems to be all software based render for the browsers 

It should work in both cases. I am running it from NVME. But with eMMC boot. SPI boot loader is broken.

https://www.armbian.com/rock-5b/