Werner

Cinnamon is more on the conservative side. For elderly people  (that DE is my daily driver). Budgie for visually impaired since there are large icons OOB. Best looking is DDE, which is sadly not in a good enough state to be shipped ...
 
 
Looked better is subjective. I can agree their UI is well polished. After all this is all what most of the distros do - polish their appearance to sell. But I don't like Saint Patrick's day 356 days in a year  Also whenever I tried how is Manjaro doing, it doesn't boot or doesn't survive first run. Ofc I don't try it on mainstream devices which might even work to some degree with a kernel from the trunk.

Great news. I guess it is decided for me what'll be my next video. I just finished a video about Manjaro on RPi4. Many people choose that just because it looked better out of the box.
Good I just bought a bunch of sd-cards.
I never tried Cinnamon and Budgie to my knowledge. I'm curious.

Also anything that has "pi" in the name or looks like "pi" and costs between 20 - 50 is the same sh*, right?  From technical perspective, things which you are comparing, they are very different ... 32 vs 64 bit soc, different generation, dual fast lan, dual gigabit lan, internal fast lan, internal gigabit lan, usb2 vs usb3, allwinner vs rockchip ....
 

This means you didn't check this? https://github.com/ThomasKaiser/sbc-bench/blob/master/Results.md

Suggestion for a (near future) product.
 
We're still lacking a good SBC out in the wild for small clusters.. Recent SoC performance is good.. Currently all the homelab and k8s nerds are just using RPI4s because they have a header for POE support.    We know there are better options.

We had pitched this to orange pi but weren't receptive. Just sharing my idea here.
 
A Lean SBC exclusively for server tasks.
"The Ultimate Homelab SBC"

Real 802.11at POE+ means only 1 cable for your compute node
Use SPI flash for custom provisioning configuration
 
Optimized for Compute
"Ready for clustering and kubernetes"
Has the Performance and Storage you need to easily deploy for clustered computing

Suggested Reference Specs
RK3399K or similar performant SoC Gigabit Ethernet 4G Dual Channel LPDDR4 16-32gig EMMC SPI flash 128mbit/16megabyte No Wifi No bluetooth No audio No CSI No HDMI USB 3 802.11af/at support or support for RPI4 style 6 pin POE hat All Ports in rear? holes for additional heatsink mounting options

After several months of development, we finally bring desktop development to the daily driver state. Our desktop builds follow KISS philosophy. They are build around proven technology, we are not touching things that are done well. Just fixing things here and there and removing most / hopefully all bloatware that is added upstream. We are preparing a wide selection of desktop variants
 
 
while we will officially only support a few of them but anyone is welcome to join and tweak / support its desktop of choice. We will support you in best possible manner! And this way things starts the voyage to become officially supported one day. Only if you join. We can't take more load.
 
        

We support XFCE since early days and that will remain primary desktop since it represent a best combination between functionality, speed and beauty. Second desktop, which we are adding now is Gnome because its clean and most stable among advanced / bulky desktops. It can ran fairly smooth as low as on Allwinner H5 / 1Gb memory, while it runs very well on some RK3399 hardware. In both cases it uses open source 3D acceleration - Lima and Panfrost. New desktop option will be added gradually, but for now:

Orange pi 4: Budgie, Gnome, Cinnamon, Gnome, Mate
https://www.armbian.com/orange-pi-4/
 
Pinebook PRO: Gnome
https://www.armbian.com/pinebook-pro/
 
Nanopi T4: Budgie, Gnome, Cinnamon, Gnome, Mate
https://www.armbian.com/nanopc-t4/
 
Nanopi M4V2: Budgie, Gnome, Cinnamon, Gnome, Mate
https://www.armbian.com/nanopi-m4-v2/
 
What about others?

- ASAP. Those are semi manual builds, some are manually tested and it takes a lot of time. On top of that we are having some infrastructure troubles ATM ...
- we still need to fix few minor bugs, before we put on stamp as "supported" even those builds are IMO generally in a better shape then other images on the market
- you can help by testing and enabling specific builds by sending a PR to this file. https://github.com/armbian/build/blob/master/config/targets.conf It will help to get things up faster.

We don't have maintainer for this board anymore - he moved to another hardware. We also never received a cent from anyone for trying to keep this HW usable. We only got one free sample from vendor and one (sadly the same revision) from their lead developer. Since this product was never more then 1/4 baken we wasted insane a lot of time for little gain. But our OS was probably the only usable ...
 
Changing board status to EOS is all I can do. If someone has a desire to take over and keep information on that page relevant (Community supported status), send me a private message.

Yes unfortunately nand-sata-install does not work the other way around, I'm looking at it currently since there was another use case related to install on OS rootfs on HDD that wasn't also supported.
 
The step for you case should be :
 
1. First boot the system on a microSD card with a fresh install of Armbian.
 
2. Copy rootfs from old destination (HDD) to new destination (eMMC)
 
mkdir /mnt/rfs_new /mnt/rfs_old mount /dev/mmcblk2p1 /mnt/rfs_new/ mount /dev/sdX1 /mnt/rfs_old/ rsync -avrlt --delete --exclude-from=/usr/lib/nand-sata-install/exclude.txt /mnt/rfs_old/ /mnt/rfs_new/  
3. use command blkid to know the UUID of /dev/mmcblk2p1
 
4. Modify /mnt/rfs_new/boot/armbianEnv.txt to modify rootdev line with the UUID of /dev/mmcblk2p1
 
verbosity=1 bootlogo=false overlay_prefix=rockchip rootdev=UUID=075c8660-77ca-4048-a04b-be3364c60a40 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u  
5. Modify /mnt/rfs_new/etc/fstab 
 
- Remove /media/mmcboot and /boot mount point lines
- Edit / mount point to use the UUID of /dev/mmcblk2p1
 
# <file system> <mount point> <type> <options> <dump> <pass> tmpfs /tmp tmpfs defaults,nosuid 0 0 UUID=075c8660-77ca-4048-a04b-be3364c60a40 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 0 1  
6. Sync and Poweroff
 
7. Remove microSD and Poweron (maybe cross your finger also)
 
 
 

I added a link to this topic to the build options.

I'd like to buy one or more NanoPi NEO2 or NanoPi NEO2 BLACK. Preferably 1GB model.
 
The manufacturer stopped selling these boards and none of the currrent models fit in their CNC OLED case (which I would also be interested in but will otherwise buy from them).
 
(Actually, anything with 64-bit CPU that fits in that case, or similarly nano-size with display and buttons, is of interest)
 
Will pay shipping to Asia from wherever you are.

You all know the problem: You have a spare SBC (with USB3) laying around catching dust, a spare SSD or other hard drive and for whatever reason some (terabyte?) space in whatever cloud on the planet and have no idea what to do with it.
 
Well here is what I came up with to solve this struggle
 
https://zuckerbude.org/cloud-nas-with-local-cache/

I suggest to ask here: https://twisteros.com/index.html

You all know the problem: You have a spare SBC (with USB3) laying around catching dust, a spare SSD or other hard drive and for whatever reason some (terabyte?) space in whatever cloud on the planet and have no idea what to do with it.
 
Well here is what I came up with to solve this struggle
 
https://zuckerbude.org/cloud-nas-with-local-cache/

I'll add your use case (sd + nvme) to install, but you  have to check it yourself. 

So, started playing around a bit. Mostly just mocking up ideas.
 
https://github.com/tparys/armbian-reconfig
 
The script currently is recursively driven by a directory system. When it hits a script, it simply executes it. Should be pretty easy to extend. Just drop a script in place and it should use it.
 
I mulled over how to "name" the various scripts and directories, and eventually settled on using gettext, which also provides internationalization support as well. Basically takes the relative menu location like "/system/firmware" and "translates" into the appropriate language. In the case that only partial translations exist, it falls back to English, which i figured wasn't a horrible default.
 
And for testing, I added some translations of the top level menu to Spanish. I did use Google Translate, as my bash-fu is strong and my Spanish is quite rusty.

This log is not from HC4. Not sure if this a problem of pastebin service or you made some mistake. Check it and do it again.

@i5Js you can download these packages and install them with apt/dpkg: https://users.armbian.com/piter75/nanopim4v2-stability-fix/
You need both of them for the fix.
 
When they are correctly installed and the board is rebooted you should see this message in your dmesg:
piter@nanopim4v2-4:~$ dmesg | grep rk808-regulator.*buck [ 2.840331] rk808-regulator rk808-regulator: max buck steps per change: 4 The last "4" means you have the fix. No message or "8" means you don't have a fix.

It seems that NanoPi K1 Plus is using rtl8189 WiFi ... Right ?
Driver is broken in 5.11, I'm working on it with other guys, I'm using OPiPC+/OPiLite/OPiPlus2E.
In the mean time, if you don't need WiFi, disable the module :
mv /lib/modules/5.11.1-sunxi/kernel/drivers/net/wireless/rtl8189fs/8189fs.ko /lib/modules/5.11.1-sunxi/kernel/drivers/net/wireless/rtl8189fs/8189fs.ko-disabled  

As a test I updated on a secondary Pihole-Server (buster on NanoPi K1 Plus) the kernel to 5.11.1-dev and at startup Pihole did seem to make some trouble
The server isnt getting to the login prompt and on the serial console the last info is "Starting kernel..."
 
I updated some of my SMB-Servers with kernel 5.11.1-deb without problems.
 
Will later try a new resinstall with buster and 5.11.1 and see if Pihole will run on a complete new installation.
 

Yes, and No ... it prevent all networking if WiFi is present, such as running "ifconfig" will hang forever.
Simply move or delete the 8189fs.ko module will prevent that.

@balbes150I'll check the new image tonight. 
I finally have filmed everything I need for the video. I had a lot of issue's with capture devices not working properly and always had to redo it. 
So I installed it 4 times. And every time it didn't boot from NVMe, but instead from sd-card. Changing extlinux with the correct uuid from NVMe works. 
I did choose the correct way, you'll see it in the video. Tomorrow I should have it finished. It'll be a long one. Review and installation all in one...

Moved to proper location.
armhf is 32bit
arm64 is 64bit.
 
There are a few other variants of arm in 32bit which you can lookup via Wikipedia for example

Moved to proper location.
armhf is 32bit
arm64 is 64bit.
 
There are a few other variants of arm in 32bit which you can lookup via Wikipedia for example

The subscriptions behaves weird sometimes. As for myself who was on the intermediate level a few month too I ended up simply canceling everything within forums and paypal, waiting to expire and then do the whole subscription from scratch.

It works. OMG I'm so happy. You did an amazing work. 
 
Graphics Feature Status Canvas: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Force enabled Out-of-process Rasterization: Disabled OpenGL: Enabled Hardware Protected Video Decode: Hardware accelerated Rasterization: Software only. Hardware acceleration disabled Skia Renderer: Enabled Video Decode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated And ... 
/dev/nvme0n1p1 ext4 458G 70M 435G 1% /media/nicod/3acb3cd1-680c-455f-ab36-36f424ce5302  
I'm stoked. I've got a bad habit of staying at a project until it's done. I should have done other things the last month, but every day I kept trying with the P1.
I'll finally be able to finish it and start with another board. And I'll be able to use the P1 as my main machine. And my M4V2 for gaming. Thank you.
 
I'll wait for that. I don't mind waiting a bit longer.

We have a realtime status page for primary Armbian web resources available here:
 
https://status.armbian.com