manuti

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.

.RAM is meant to be used. If you have a lot of free ram then you over built your system and wasted money. On windows 10 a fresh boot should consume around 30% of RAM. If you experience more ram usage in task manager this guide can help you to clear up some ram.

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

New version of Armbian 20210311.
Based on the main core 5.10.23.
Now anyone can build their own version of Armbian for Jetson Nano without an external PC, the entire process is completely performed on the Jetson Nano itself.

 

Good news. 
Thanks to the work of many, there is now a real opportunity to run the Armbian system with the main core on Jetson Nano, and more importantly, it is easy to integrate the image build process into the official GIT Armbian. In the near future, I plan to post ready-made images with the latest kernel 5.10.22 on the download site. To run them, you need to update u-boot to Jetson Nano. This is very easy to do, just run the latest official version of Ubuntu for Jetson Nano from the SD card, it will update itself in SPI (?) u-boot to the latest version (2020.04), after that you can run Armbian from any SD card or USB media. The new u-boot supports automatic system startup from both media or over the network. Also, now you can build an Armbian image for Jetson Nano yourself, easily build the latest kernel with the necessary options, etc.  
 
 
https://users.armbian.com/balbes150/
 
https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ
 
https://disk.yandex.ru/d/XBRXnig7F1M4rw?w=1

Lubuntu Focal / Panfrost
Download the latest current version of Focal (Panfrost drivers included) for your device and follow the instructions https://www.armbian.com/download/
After the first login type ... exit (exit from root, login with the new user id entered in step 1)
Download the Panfrost Tester script
git clone https://gist.github.com/8f8b0cd40e95ac18c539cd29ecd4c3d2.git install-panfrost-tester cd install-panfrost-tester Version 21.0.0-rc5 will be installed. If you wish, you can modify the mesa branch using:
nano installPanfrostTester.sh (ex: go to install mesa line and change from 21.0 to master) Install Lubuntu Focal / Panfrost *** It will take at least 30 minutes to compile mesa ***
sudo sh ./installPanfrostTester.sh sudo reboot Login graphically with your user id ...
Open Firefox browser, go to Armbian forum to retrieve the link from this topic and follow the instructions.
Verify Memory being used
Open Htop, in my case with Tinkerboard/S the memory was 260M, with the Odroid-C4 it is 400M
Get information from Mesa (Panfrost driver)
To find out the GPU chip that your computer uses, open QTerminal
glxinfo | grep OpenGL Testing performance and 3D acceleration in the real world
Open VLC and change the default settings - Tools -> Preferences -> Interface
Check: Allow only one instance and Enqueue item into...
Uncheck: Show systray icon and Save
Then, from VLC change video output - Tools -> Preferences -> Video
Output: change from Automatic to OpenGL for Embedded Systems 2 video output and Save
Quit VLC
Download HD/4k/8k/10k Videos playlist from vimeo
git clone https://gist.github.com/682ced111c6b3adc74e70dcedf370852.git Videos In VLC, open video-examples.m3u under Videos folder, and observe the results!
For the desktop GPU performance, you can open screensaver and preview the 3D screensaver demo
Cheers, enjoy ... VinVIn
 
 
 

We have Cluster Server R1 with 11pcs of CPU(RK3399 and also compatible with other CPU too) clustered, Cluster server R2 with 73pcs of CPU(RK3399 and also compatible with other CPU too) clustered.
Cluster Server R1: http://en.t-firefly.com/product/clusterserver
Cluster server R2 : http://en.t-firefly.com/product/cluster/r2.html?theme=pc

Those are totally awesome... The data sheets don't have enough information about the networking.

Does the built in switch support LAG/LACP and VLAN trunking?

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

IT'S FINALLY HERE...

THE OFFICIAL ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION
 
After two years of using a separate script to enable the multimedia features in RK3288/3328 Legacy Kernel, the whole framework has been incorporated to the official Armbian packaging system. The choice distro for this integration is Debian Buster (see FAQ at the end of this post about the reasons).
 
I. Installation
Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method. Install the complete multimedia solution with sudo apt update && sudo apt upgrade sudo apt install media-buster-legacy-tinkerboard --install-recommends ## Or ## sudo apt install media-buster-legacy-rk3328 --install-recommends The switch "--install-recommends" will add the whole Kodi binary addons collection (retro-gaming cores, music visualizations, screensavers, additional media decoders/encoders, vfs, etc.), plus the GLES-to-OpenGL wrapper "gl4es".  
II. Features
Accelerated GLES/EGL X desktop: No action needed. Accelerated Chromium, with WebGL and video display acceleration: No action needed Desktop video player capable of smooth 4K HEVC-HDR: Use the "Rockchip Gst Player" from the Multimedia menu, or choose it with right-click on the media file. Command-line 4K playing is also possible with "gst-play-1.0 --videosink=kmssink". RKMPP-accelerated MPV: Use normally for standard operation (windowed with mouse-operated GUI). For fullscreen, keyboard-operated mode, use the command line switch "--gpu-context=drm" (this will allow you to play smooth 4K).
        - See instructions below, in the next post, for playing Youtube videos up to 4k with this MPV. ISP Camera with real-time h.264/1080p HW encoding (RK3288 only): Using the Gstreamer Plugin. Check this wiki for instructions on how to use it. Most of it applies to Armbian, except for the selection of ov5647/imx219 camera, which must be done using DT overlays. OpenCL 1.2 support (RK3288 only): It will be fully functional, no further action needed. You can download some tests and examples from this link. Kodi 18.9 Leia with full RKMPP+GBM acceleration, 4K-HDR capable: You can start it from Light DM menu as your user account: 
 
Alternatively, you can also run it as a system service with these command lines: sudo systemctl disable lightdm sudo systemctl enable kodi-gbm sudo reboot  
Full collection of Kodi binary add-ons: Includes retrogaming cores, media encoders and decoders, PVR, screensavers, vfs and audio visualizations. They are all installed with the package "kodi-addons-full", but are disabled by default. They need to be enabled individually within the Kodi GUI. OpenGL 2.1 support through the gl4es wrapper: It is installed with the package "gl4es", with no further action needed.  
III. Sources
This is the list of the sources used for the packages:
 
IV. FAQ
¿Why did you use Debian Buster as a base for this implementation?
It was the most appropriate for several reasons. Upstream Rockchip-Linux developers use Debian buster, so the software could be ported with less modifications than if we chose a different distro. Besides, it is a completely stable distro, unlike Bullseye, which is a moving target as of today. It also has Chromium as a package, unlike Focal that uses snap instead. For last, it has a good backports repo, with several libs that would otherwise need to be compiled and maintained if we chose, for example, Focal.
  ¿Why Legacy instead of Mainline?
This is an implementation based on the vendor's BSP kernel. It has been tested and is reliable, which many people will prefer rather than having a bleeding-edge, less stable implementation. In addition to that, Mainline upstream multimedia support is still a WIP, and lacks many features that are only present on Legacy kernels.
  ¿Will you add new features to this implementation?
No, this implementation will only receive bug fixes if necessary. From now on, all multimedia work will be focused on Mainline and recent distros (like Focal or Bullseye). All new features will go there.

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.

New images are available for rk3188 (20210301).  https://disk.yandex.ru/d/bmsU1aueVGLPjA?w=1
Anyone can build their own version, I added build support for rk3188 and rk3288 to my GIT.

Perhaps, but when it will be - it is not known.

On the contrary, not removed, but developed. But not fast enough yet. I hope to add support for building images for rk3188 to my GIT in the future (and if there is a demand, it is possible to send a PR to the official GIT).