manuti

https://docs.armbian.com/Developer-Guide_Adding-Board-Family/

I just bought 3 of these, 2 for me and one for a friend. I should have them by next week and can follow line by line instructions.

Hi,
 
I have not much time either, but I would like to see an Armbian release for the M1S. I have one M1S unit with me I could use for testing, but I will have to share it with other tasks. Maybe I could help accelerate the process somehow, I just don't know where to start. I have been using Linux on embedded systems for some years, but never went very deep.
 
I have tried the linuxfactory bookworm image and it works, even with the Vu8S 8" display which connects to the MIPI connector. It must be installed to the onboard eMMC.
 
Does someone want to guide me on this? Or maybe supply ready to flash images I could test?
 

Hey guys,
 
I just wanted to mention, that I have not forgotten this topic .
 
I just have currently no time to drive this further because of real-life stuff going. Additionally I currently have no hardware in spare which i could perform the tests on. So either you guys wait for a non-specified time or try something on your own.
 
So long... Cheers

https://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card

Two good news :
- Rockpi S is supported again
- There is a bugfix to get gpio values via sysfs and libgpiod
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/drivers/gpio/gpio-rockchip.c?h=linux-5.19.y&id=a11544efbcf5caa1c6e7ccc8e0f3bf1b63c9b500

Kernel must be >= 5.19.17, or wait the next release of armbian rockpi s.

I have two Rockpi S without SDNAND and one refuse to boot on SDcard.
If you have the same problem :
sed -i 's/^IDBLOADER_BLOB/#IDBLOADER_BLOB/' config/sources/families/rockpis.conf touch .ignore_changes sudo rm ./cache/sources/u-boot/v2022.04/idbloader.bin ./compile.sh ...  
@ia64
If you use armbian 22.11, spi2 is disabled, see :
https://github.com/armbian/build/commit/d3a3afe3850861ceaeb44f3631251c764a28cd43
For the moment i don't use spi but this overlay :
overlay-rockpi-s.dts
You can replace "disabled" by "okay", and :
sudo /usr/sbin/armbian-add-overlay overlay-rockpi-s.dts && sudo reboot
In this overlay, gpio-line-names is usefull with libgpiod (sysfs is deprecated
https://www.thegoodpenguin.co.uk/blog/stop-using-sys-class-gpio-its-deprecated/)
to have the standard gpio pin between pin1 to pin24. I have equivalent overlays
for Orange Pi Zero and Nanopi Neo and access pins with their physical pin number.

... and you got it wrong.

Good news!
 
The updated operating points for the RK3308B-S do work.
sysbench confirms a 10% speed improvement.
But, more importantly, idle power consumption is almost halved!!!!
[from 0.39W measured previously to about 0.20W when running the CPUs at 0.85V as opposed to 0.95V]
I need to run this overnight to confirm.
 
I'll look into the other B-S silicon device tree updates soon.
 
Does anyone have ideas on how best to package this?
 
I've read the docs here:
https://docs.armbian.com/User-Guide_Allwinner_overlays/
 
but they refer to Allwinner for 64-bit arm and some of the example dirs seem to be missing.
 
Are device tree overlays supported for Rockchip?
Can anyone point to an example of their use?
 
Do we end up with a magic rk3308bs.dtbo file that one moves into an overlay to optimize performance?
 
Is there a better approach?
Does the older (B) silicon even boot with these updated (BS) operating points?
 
Attached is the latest version of the rk-3308-rock-pi-s.dtb optimized for the BS chips.
rk3308-rock-pi-s.dtb

My strongest ARM-based BOINC crunchers are two Hardkernel Odroid-N2+ boards, one running Android 9 PIE, the other Armbian. While the Rockchip RK3399 has two ARM Cortex-A72's and four ARM Cortex-A53's, the Amlogic S922X of the Odroid-N2+ has four ARM Cortex-A73's (@2.4 GHz) and two ARM Cortex-A53's (@2.0 GHz). So more, faster, and better high-performance cores and less, but faster, efficiency cores. Both N2+ boards have a 80mm fan under the big standard heatsink and this helps to maintain a CPU temperature below 40 degrees centigrade. 

Without fan they run quite a bit hotter. Fan screws double as stand-offs.

Hi, I would like to ask, if you could share it again. I want to reborn one old box, and your image will be very helpful. Thank you.

H6 is newer an has a way better GPU on it, and also a higher clock. Between them, H6 wins 
 
And mine is a T95 Mini (TUREWELL). It didn't arrive yet. Soon I'll be able to give support to it 

The image is quite popular so I compiled a new one for r69. I didn't have time to test it, so be careful This is standard minimal image

Armbian_21.08.0-trunk_Sunvell-r69_buster_current_5.10.37_minimal

https://mega.nz/file/V3QQyBaY#Y332sD2oa36L5BZa0xtANx1O6QrS_903Qj1RHg1vuy8

A test version of the image Armbian for TV boxes on the basis of RK3328. Tested on MVR9
http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/653167-bqeel-mvr9-rk3328-quad-core-64bit-cortex-a53-android-7-2-16gb-2-4ghz-wifi-bt4
 
All basic functions work. For running. Download. Unpack. To record on the SD card. Connect the SD card to TV box, connect a keyboard and mouse. To turn the power on the TV box. The system should start within 2-3 minutes. You must perform the initial configuration of Armbian.

https://yadi.sk/d/DSO6euzB3ahemo
 
https://mega.nz/#F!zoZywCTQ!9sNfXIAB3m_DyLl5I8P94w
 
The system of choosing the correct dtb has changed.
Please note, now it should be done on a different principle (files do not need to be copied).
To select the desired dtb, you need to change the line in the text file "/extlinux/extlinux.conf". In the line "FDT" you need to change the name of the file that the system will use at startup. The list of available files (names to specify in the configuration) can be found in the "dtb"directory. If you do not know exactly what file you need , you can enter all available names in turn and check the operation of the system. In accordance with this, the system installation script in eMMC has been changed. The steps to install the system on the eMMC remain the same.
 
Added a utility to full backup and restore the entire eMMC "ddbr". Checked mode the backup MVR9. Now if you try to check the recovery mode.
 
The order of installation in eMMC.
 
1. Download, unzip and burn the image to SD card.
2. Start Armbian on the TV box and perform the initial setup of the system.
3. If the system works correctly and you are satisfied, run the utility "ddbr" and create a full backup of eMMC (this is a prerequisite).
4. Rename the file "/boot/mvr9-uboot.img" in "/boot/uboot.img".
5. Run as user "root" script "/boot/create-mbr-linux.sh"
6. To run the script "/root/install.sh"
 
Pay attention to the correct operation of the installation procedure need to comply strictly with the order of the steps.

After mounting and unmounting several times both external units it seems to start working. Now the mount point at /sda is consistent across all the commands. The outpus you asked, @lanefu, is:
ls -l /dev/disk/by-uuid total 0 lrwxrwxrwx 1 root root 15 may 11 22:57 d4e4d15d-d587-4f5d-83d7-4cbb1700e7c5 -> ../../mmcblk0p1 lrwxrwxrwx 1 root root 9 may 11 22:57 dcb5a19c-6bd2-4c5a-8fc4-9ed4adec7074 -> ../../sdb lrwxrwxrwx 1 root root 9 may 11 22:57 e6201983-bfd8-4eae-bf54-90575f09835f -> ../../sda  
I also added a new screenshot. Thanks for the help. And I'll keep an eye on this if it happens again.

After mounting and unmounting several times both external units it seems to start working. Now the mount point at /sda is consistent across all the commands. The outpus you asked, @lanefu, is:
ls -l /dev/disk/by-uuid total 0 lrwxrwxrwx 1 root root 15 may 11 22:57 d4e4d15d-d587-4f5d-83d7-4cbb1700e7c5 -> ../../mmcblk0p1 lrwxrwxrwx 1 root root 9 may 11 22:57 dcb5a19c-6bd2-4c5a-8fc4-9ed4adec7074 -> ../../sdb lrwxrwxrwx 1 root root 9 may 11 22:57 e6201983-bfd8-4eae-bf54-90575f09835f -> ../../sda  
I also added a new screenshot. Thanks for the help. And I'll keep an eye on this if it happens again.

okay sorry I didn’t understand the issue exactly.
 
so I believe this is a technicality of using lsblk.   A btrfs subvolume isn’t going to trace back to a block device.   Would be interesting to look at the output of 
 
ls -l /dev/disk/by-uuid
 

I burned a xz compressed image of Armbian Focal onto a good SD card using BalenaEtcher as instructed on the Armbian website.
I placed it into my NanoPC T4 - which currently boots from the eMMC, and held the boot button while powering on. 
It tried to boot - but it kept reporting there was no bootloader file and seemed to be trying to load something from the internet, not the SD card.
 
If I dont press the boot button, it simply ignores the SD card and boots from eMMC.
 
I reburned the SD card several times, and each time it verified fine.  
 
Does anyone know what I did wrong?

You probably didn't do anything wrong.  The only focal I can get to work is the xfce desktop version, the others have an  empty boot folder after burning so won't boot.

I can also report that the "Q+" model works as well ("works" as always means w/o WiFi, Bluetooth).  This is another model worth considering, although in my experience it runs hotter.  All these boxes are best used as a small server as @SteeMan suggests.  But for that purpose and for the reasons he states (price, EMMC flash, case), they are excellent.  I have tried several AMLogic (before they were dropped) and RockChip models in the past, but was never able to get them to work, at least not easily.  So, if you are looking for a small server box that just "works", I would highly recommend that you save yourself considerable grief and get/use one of these H6 models (before buying, confirm that they use EMMC and not NAND! - I had one batch I bought on Amazon that was NAND - all the ones on Alibaba have been EMMC).  The models I have tested are the TX6, T95 Mini (and Max), and Q+.  They are completely interchangeable and use the same images that @Balbes150 posts here.

OK, I compiled new image for Sunvell R69
 
Armbian_20.05.0-trunk_Sunvell-r69_buster_current_5.4.33_minimal

- Installation/flashing to internal emmc via armbian-config works fine
- 2 x USB works
- Analog audio device is detected but I can't get any sound, maybe my unit is broken or I'm doing something wrong (feedback needed)
- Working IR, WiFi and ethernet
- Default password (root/1234)
 
https://mega.nz/file/4ugAhKjb#NIt6KIv2tsPFzVVGwLcykFSdQp0MgCXgdCzxcj0PUxA

@Kusa, thanx a lot for your image. My previous one was 3 year and half old! All that time running 7/7 24/24  PiHole, Domoticz and some script managing Amazon Dash Buttons. IMHO a decent use case for a (16€) useless tv box (according to TK ). Everything fine (eemc boot) , and reboot do not need anymore to unplug!
 
By the way, with my previous image (eemc installed), it was impossible to boot from *any* SD Armbian image. But... I could boot with H3Droid image, install H3Droid on eemc, then I could boot with an Armbian SD.
 

There is a T95 H6 version that works well.

I am running the latest Armbian 21.02.3 on two NanoPCT4s.
Thanks to everyone for this. I didnt think I would see this performance on this device.
But here it is and I see Armbian is getting good notice for this.
I dont know how they did it but these devices are running very well.
I am a little tired this week so I dont have any technical details.
I want to just ramble (opinionate) on how nice this is and what I like about it.
I am running standard Focal Gnome Desktop from Armbian Download.
I just disable the pwm-fan module and run hot.
As long as I dont make -j6 I can avoid meltdowns.
I run Firefox and Microsoft VSCode. I run a complex desktop and my
standard install involves a day of burnin compilation.
I can run Firefox videos and Microsoft Code.
By the way Code can now be downloaded direct from Microsoft.
I run a lot of Python and JavaScript and C++ [avoid Java and C# at the moment
but really I dont have much time considering I do more and more C/C++]
and use Python as scripting language for C. I compile Sage Math 9.2
and that will halt this machine at make -j6 and no fan.
with fan, no problem. but make -j3 works OK with no fan.
After compiling these little ARM devices run SageManifolds doing complex
Jupyter Lab interactions. Pretty slick.
So I think this is a wonderful desktop.
 
I know the Gnome people own GItHub and Microsoft
TypeScript backended on GitHub integrated with the wonderful
Microsoft Code is a great desktop that Armbian is Smart to invest in.
 
more later.
 

A95X Z2
4GB/64GB, RK3318

Armbian_19.11.4_Arm-64_bionic_dev_5.5.0-rc2_desktop_20191228
Doesn't work: Wifi, Bluetooth
Does work: everything else
It is stable and relatively fast, considering low price. It is based on RK3318 chip so it's not really desktop replacement material. Video playback in chromium works very slow and VLC has issues playing higher resolution videos. Desktop environment seems to be GPU accelerated and browsing seems quite smooth. Kodi - LibreElec, plays videos smoothly, even in a bit higher resolution (fullHD). I haven't tried 4k, but I very much doubt it can. 
If I install Kodi in Armbian it can't play even  video resolutions such as 720p.
 
Armbian_19.11.5_Aml-g12_bionic_dev_5.5.0-rc5-next-20200110_desktop is newer, but USB3 stopped working.

did anyone already test to boot this image on the 2gb model of the jetson nano? i just tried it and it does not boot - the nano already has the new u-boot in the spi ... looks like i have to connect a serial console when i find some time