manuti

thanks for the post nico! well, with rk3399 across all.my team we will.make some severe changes on this armbian build. we will move to xfce abd rebrand the build as TwisterOS armbian. the idea would be to start with RK3399, then S922x, not only N2 bc they are competitors arising and also bc you know I don't like N2. cheers! 

If you are running Armbian desktop and you like to use Visual Studio Code,  open a terminal and run:
 
sudo apt update sudo apt install code  

NanoPi Neo3 could now ordered - but not with a metalic case. Dont know how it will heat up in there
https://www.friendlyarm.com/index.php?route=product/product&product_id=279&search=neo3&description=true&category_id=0&sub_category=true
 
And with this cas you couldnt use the 2 additional 2 USB 2.0 ports or fan-support.... which is available on the pin headers...

Update, for whatever reason this is broken in Armbian focal, and the issue appears to be due to an Armbian shell script that xrdp doesn't like, so after doing the install, you also need to then do:
sudo mv /etc/profile.d/armbian-check-first-login.sh /etc/profile.d/armbian-check-first-login.old And volia, you'll actually get a desktop when you RDP from windows.

hey,
after updating my nanopct4 and rockpi-4b to from 20.05 to 20.08 RDP stopped working for me, only black screen.
After reading all the messy logs, fresh install etc, I found a simple working solution online:
 
In /etc/xrdp/startwm.sh change 
#!/bin/sh  to 
#!/bin/bash  
Sources:
https://github.com/neutrinolabs/xrdp/issues/1630
https://askubuntu.com/questions/1166568/remote-desktop-blue-screen-after-login
 
Maybe others are affected too, don't know about Ubuntu.

It's not a case of arm64 not being as well-supported. In general most modern software has way better support on arm64 than armf. If you're on a 64-bit processor, you can choose. HC2 will simply not do arm64 since it's a 32-bit processor.
 
You can use either distro. I'd personally vouch for buster, or even bullseye. debian's testing is generally relatively stable in this phase of the lifecycle, and buster has old versions with known issues of some packages by now.

Hi @manuti
How did you do that? I mean what kind of tool and command that you used to force next boot using uSD card from android? many thanks

My big test rig:
 
32 devices IN
https://dl.armbian.com/_test-reports/2020-08-04_21.44.52.html
 
31 devices OUT
Only Orange Pi Zero Plus 2 failed to respond after extreme testings ...

We have nightly images built available for the boards below.   Please help us test and report your experience via This Google Form.
 
Images are available via our normal Armbian download page.  Just scroll to the bottom to the "nightly build" section.
 
 
Bananapi Bananapim2plus Bananapim2zero Bananapipro Clearfogbase Clearfogpro Cubietruck Espressobin Helios4 Lepotato Lime-a64 Nanopct4 Nanopiair Nanopim4 Nanopim4v2 Nanopi-r1 Nanopi-r2s Odroidc2 Odroidc4 Odroidn2 Odroidxu4 Orangepi3 Orangepi4 Orangepione Orangepipc Orangepipc2 Orangepipcplus Orangepizero Orangepizeroplus2-h3 Orangepizeroplus2-h5 Pine64 Pinebook-a64 Pineh64 Pineh64-b Rock64 Rockpi-4a Rockpi-4b Rockpi-e Teres-a64 Tinkerboard Tritium-h3 Tritium-h5

Who did say that I wanted that?  I know thats a problem on all SBCs when getting a new OS.
It was only as information!
Its really cool to get a newer Kernel greater than 3.0x AND armbian-style  Many Thanks!

@DaviMesquita
For those boxes is really a jungle !!
Those Chinese tend to grab the first avaible cheap chip and put inside so a big variety of possibilities.
@Jock contacted me and maybe now is the moment to " put hands " in this sluttish driver.
 
@Ztrawberry the driver for ssv6051 doesn't suit sv 6x5x this is the problem and that project for a universal image is a nice idea but me and jock and other clever programmers  ( the same man  that bring libreelec to life on those boards @knaerzche ) own so many different boards that  has been reached great maturity  on rk 322x . Mostly bugs are well known ( ssv6x5x among others) and still working on them
Of course support , ideas and suggestions are highly appreciated

I've built fresh image for Beelink X2 on 2020-07-18. Focal with Xorg only. It looks even wifi works out of box.
 
Download image at https://mega.nz/file/z0IlgKiQ#UNdKk68q4XmZ8hb7zrYoGkdh_NtcbiuI-5XEZPvMPQ8

Well, kernel modification is needed for better decoding (less glitches). Probably new *-ctrl.h files contain new fields (not 100% sure) which also need to be filled.
 
There is no any post processing implemented here like scaling. It would be possible to do that via SoC specific peripherals but that wouldn't be universal and thus it's out of scope of this library.
 
Anyway, I'm glad you succeeded.

Is there a set of instructions available on how to update from an early version to a recent version?
 
I got a H96 Max rk3328 running a very early release of the Armbian rk3328 builds, i want to update to a recent version now and after 2 days of searching and trying still no luck...

Test image for rk3188
Download, unpack and burn the ArmbianTV image to your SD card.
Connect to the TV box and turn on the power. The system will start automatically.
 
https://yadi.sk/d/YXA09tNfyRhDIw

you are right , visual inspection:

sudo modinfo lima filename: /lib/modules/5.4.45-sunxi/kernel/drivers/gpu/drm/lima/lima.ko license: GPL v2 description: Lima DRM Driver author: Lima Project Developers alias: of:N*T*Carm,mali-450C* alias: of:N*T*Carm,mali-450 alias: of:N*T*Carm,mali-400C* alias: of:N*T*Carm,mali-400 depends: gpu-sched intree: Y name: lima vermagic: 5.4.45-sunxi SMP mod_unload ARMv7 thumb2 p2v8 sig_id: PKCS#7 as i understand, lima is already installed in my system. 
how can i use it and install OpenGL ES lib?

Are you kidding? Again: 
 
There's no problem with the RK3328, this is just another boring Quad-Core A53 in 28nm (just like the H6). So the question remains what's wrong with NanoPi R2S and not the RK SoCs.
 
And I really don't understand why so many blindly trust in numbers. There's a thermal sensor inside the SoC, there's a reference voltage, there's some calibration needed, there's driver code. The idea that the numbers this driver spits out are somewhat or even closely related to the actual temperature of the SoC in question is just a hope!
 
Care to remember what you yourself already reported?
 

Checked the transition from Bionic to Focal with the command (do-release-upgrade). The system was updated from the beginning to Eoan and then upgraded to Focal. Please note that this is a potentially dangerous procedure and you must first save all your valuable data.

Thanks for confirming that it works. Focal images are also fixed and uploaded by now.

Well, its good that it works ... at all. I don't have this board so I can't test, but I am soon getting one. And it will be added to the autotest rig.

Did you miss the big banner on the download page saying that Focal images are broken? Or is the other one also broken?

If you know the movie "Wargames" then you may know the computer of "David Lightman" a IMSAI 8080
 
Udo Munk did create the software z80pack (last version from 2017 v1.36 at https://www.autometer.de/unix4fun/z80pack/ )
which does include
- IMSAI 8080
- Altair
- Cromemco Z1
and 
- cpmsim
Emulation.
 
Against the text based cpmsim emulation the other features a graphical frontpanel with "blinken lights"
 
Yesterday I did try to compile/start my favourite IMSAI 8080.
I did follow the instructions - which I collect and wrote for me - see attached to this message.
 
But yesterdy I only got limited success (after many "bad" compiles with missing dependencies) in starting the IMSAI 8080 emulation.
I did get the graphical frontend *yeah* - but after POWERON/RUN the computer I didnt get any terminal-output
 
After MANY retries I did give up  
Today I did the same compile-session on a PC with Ubuntu MATE 20.04LTS and it did work in the first try  
 
At first I got no idea what wasnt working....but then I discovered that - when moving the graphical frontpanel - the terminal-output was written VERY SLOWLY to the terminal-screen *Aha*
 
Because the garphical frontpanel seem to work perfectly (and did also compile very well) I searched inside the directorys of imsaisim and found in the "conf"-directory the file system.conf
 
There in system.conf is a line where the FPS-rate of the frontpanel as default is configured to 60 FPS (Frames per second).
While taking a look at htop the NanoPi A64 (where my armbian buster Desktop does run) the cpu-utilization is near 90%
 
So my gut instinct did tell me thats to much and the NanoPi has to much work with the frontpanel than writing to the terminal.
 
I changed the framerate in
- for the IMSAI 8080: ~/z80pack-1.36/imsaisim/conf/systemconf
- for the Altair: ~/z80pack-1.36/altairsim/conf/systemconf
- for the Cromemco Z1: ~/z80pack-1.36/cromemcosim/conf/systemconf
to
# front panel framerate fp_fps 10 After that change all 3 emulators with graphical frontend did startup and give output on the terminal
 
I contacted Udo Munk via email about this topic and he already knew it
He wrote that he had implemented the FPS option, because some lower-spec systems had problems to achieve the power for producing a framerate of 60 FPS for the frontpanel.
 
 
Here my write-up / documentation how I did compile /  successfully start the IMSAI 8080 emulation:
(many thanks to John Kennedy from the FB-Group Altair 8800 for double-checking my instructions!)
====================================================================== My normal evironment for compiling source: ====================================================================== apt install gcc libncurses5-dev liblua5.3-dev git make zip unzip -y ====================================================================== Getting z80pack-source: ====================================================================== cd ~ wget https://www.autometer.de/unix4fun/z80pack/ftp/z80pack-1.36.tgz tar -xvf z80pack-1.36.tgz cd ~/z80pack-1.36/ ====================================================================== Dependencies named by z80pack: ====================================================================== libjpeg X11 OpenGL c++ compiler (g++) libpthread ====================================================================== Packages for the z80pack-dpendencies: ------------------------------------- apt install libjpeg-dev x11-common libpthread-stubs0-dev libxmu-dev apt install mesa-common-dev z80asm libglu1-mesa-dev freeglut3-dev ====================================================================== ==> <== ==> I built all packages of z80pack in the following order: <== ==> <== ==> ATTENTION: for some commands you may have to use sudo <== ====================================================================== 1.) FRONTPANEL ====================================================================== cd ~/z80pack-1.36/frontpanel/ make -f Makefile.linux NOTE: Be sure to copy libfrontpanel.so to a shared library path! NOTE: cp ~/z80pack-1.36/frontpanel/libfrontpanel.so /usr/lib make -f Makefile.linux clean ====================================================================== 2.) CPMSIM ====================================================================== cd ~/z80pack-1.36/cpmsim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean ====================================================================== 3.) CPMSIM-TOOLS ====================================================================== if you are user root: mkdir /root/bin if you are user pi: mkdir /home/pi/bin cd ~/z80pack-1.36/cpmsim/srctools make make install NOTE: (does install in /root/bin/) NOTE: Tools installed in /root/bin, make sure it is NOTE: included in the systems search PATH NOTE: export PATH=$PATH:/root/bin NOTE: or NOTE: export PATH=$PATH:/home/pi/bin make clean ====================================================================== 4.) ALTAIRSIM ====================================================================== cd ~/z80pack-1.36/altairsim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean NOTE: change framerate to "fp_fps 10" in NOTE: ~/z80pack-1.36/altairsim/conf/system.conf ====================================================================== 5.) CROMEMCOSIM ====================================================================== cd ~/z80pack-1.36/cromemcosim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean NOTE: change framerate to "fp_fps 10" in NOTE: ~/z80pack-1.36/cromemcosim/conf/system.conf ====================================================================== 6.) IMSAISIM ====================================================================== cd ~/z80pack-1.36/imsaisim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean NOTE: change framerate to "fp_fps 10" in NOTE: ~/z80pack-1.36/imsaisim/conf/system.conf ====================================================================== PREPARE 1st start of imsaisim; ====================================================================== cp ~/z80pack-1.36/frontpanel/libfrontpanel.so /usr/lib cd ~/z80pack-1.36/imsaisim rm conf ln -s conf_2d conf export PATH=$PATH:/root/bin NOTE: maybe add the export-command to your ~/.bashrc ====================================================================== START of IMSAI 8080 CPM v2.2 from the x-terminal on the desktop (needs to be a "x-terminal) for connecting to the X-Server for creating the graphical frontpanel: ====================================================================== ./cpm22 NOTE: maybe root has to give access-rights: NOTE: chmod -R 666 ~/z80pack-1.36/imsaisim/disks NOTE: on the x-terminal root and the to the desktop logged in user can NOTE :start the application and connect to the X-server on a NOTE: SSH-terminal ONLY the to the desktop logged in user can start the NOTE: application and connect to the X-server to give root access to NOTE: the X-server from a SSH-terminal the he to the desktop logged NOTE: in user has to give root access via the xhost command: NOTE: xhost SI:localuser:root ====================================================================== POWER-UP the IMSAI 8080 in the graphical frontpanel ====================================================================== Press "POWER ON " upper part on the first switch on the right side (POWER ON / POWER OFF) Press "RUN" upper part of the third (red) switch (RUN/STOP) ====================================================================== Exit the IMSAI 8080 ====================================================================== Enter "bye" on the CP/M-commandline OR press "POWER OFF " lower part on the first switch on the right side (POWER ON / POWER OFF) OR close the graphical frontpanel with the close button X (Window-Manager-close)  
Pictures (screenshots are done with Mirage as you can see) of my "success"

To upgrade from the old core, you need to restore the original firmware and go through all the steps for a clean installation. Or perform all the steps manually (do not wait for a detailed step-by-step guide for the manual option, you will have to solve everything yourself on the spot).
 
 

I guess it is more a new installation than an update what you want..because I have just p281 devices with s905w chip I can only write how I proceed on these devices, but as s905x and s905w are quite similar, that should work for you too: Burn image on card, configure that dtb is working for your hardware in uenv.txt"Complete copy OS to eMMC "
If new system runs good from sd card, just boot from it, open a terminal and type:
 
sudo /root/install-aml.sh after few minutes the script should have copied(/usr/ takes a while..) the stuff to eMMC and prompt:"Complete copy OS to eMMC "
 
If that fails to reboot 20.05.5 image from internal after that, maybe try in terminal on boot from card to copy (again):
sudo /root/install-aml-s905-emmc.sh ..but for me on 5+ amlogic p281/p212 devices install-aml.sh works perfect..
 
 

Version 20200529.
Added 4K support for rk3399 and rk3328.