manuti

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:
====================================================================== 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 mesa-common-dev z80asm libglu1-mesa-dev freeglut3-dev libxmu-dev ====================================================================== ==> <== ==> I built all packages of z80pack in the following order: <== ==> <== ====================================================================== 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 ====================================================================== mkdir /root/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 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 ~/z80pack-1.36/altairsim/conf/systemconf ====================================================================== 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 ~/z80pack-1.36/cromemcosim/conf/systemconf ====================================================================== 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 ~/z80pack-1.36/imsaisim/conf/systemconf ====================================================================== 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: chmod -R 666 ~/z80pack-1.36/imsaisim/disks NOTE: on the x-terminal root and the to the desktop logged in user can start the application and connect to the X-server NOTE: on a SSH-terminal ONLY the to the desktop logged in user can start the application and connect to the X-server NOTE: to give root access to the X-server from a SSH-terminal the he to the desktop logged 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.

I tried to build Armbian images directly on the ARM device (rk3399). Surprisingly, after some refinement of the build system, i'm managed to get the first test images of the universal system RK+AW+AML. At this stage, there is no u-boot in the images. Therefore, you can run on rk3399 either from USB media, or, when writing to an SD card, you need to additionally write u-boot, as provided in the instructions in the first message of the theme for all other platforms. Otherwise, the handling of these images is the same as before (setting up DTB via uEnv.txt, etc).
Please check these images on different hardware to determine their  whether they can be used as images build in the traditional way.
 
https://yadi.sk/d/6ZY-ld9fyUgHxg

Version 20200519.
This version is fully built not mediocre on the ARM platform (rk3399).
I checked how the images work on different models, and no problems were found. The system works identically to the version built using the old scheme via cross-compilation on x86. While these images do not have u-boot and to run from the SD card on RK3399 add u-boot, as described at the beginning of the topic.
Now anyone can build their own version of ArmbianTV not mediocre on their device.

The clean build of the Focal-server on NanoPC T4 with NVMe took 22 minutes.

The new version 20.05.5 (20200522).
All images are build entirely on the ARM platform (rk3399 + NVMe). After fixing bugs, the process of building the first image (including downloading sources, building all packages, building the kernel, u-boot, and so on) took less than 50 minutes. 

Contact the hardware manufacturer to develop and source the correct DTB for the mainline kernel with support for all devices for your models.

additionally to the 2 USB-devices
- WLAN/WiFi Realtek 
Bus 004 Device 002: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter
- USB Stick sda Kingston DataTraveler 3.0
Bus 003 Device 002: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
 
you do use more than 1008Mhz on the OPi PC (H3-CPU):
Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St.
13:43:55: 1368MHz 1.20 44% 18% 12% 0% 13% 0% 72.8°C 0/8
13:43:56: 1368MHz 1.20 75% 27% 31% 1% 12% 2% 71.2°C 0/8 13:43:56:
 
which is often unstable and does heat up the cpu (too much).
 
Try to set the max. Mhz to 1008 in armbian.config -> system -> cpu
(around 500 Mhz for min.) and governor ondemand.
 
Maybe then it will be more stable
 
 

armbianmonitor -u

You dont have a Raspberry Pi 4 with armbian These are Rockchip64 SBCs  
because there is no armbian for the Raspberry Pi

Great job!
Thanks to you I finally have a working image for my MXq-4k ,
PCB silkscreen : MXQ-S-V3.0-20180126 ZN
Hw: Allwinner H3, 1G DDR3, 8G NAND, XR819
XR819 work
All 4 USB enable from armbian-config
cpufreq is working.
Because i have NAND system transfer to eMMC does not work ...
 
 

I'm having the exact same trouble with my two, same AP6181. I've tested both Xenial (3.4) and Stretch (4.19) but neither have Wifi working. The older kernel image is loading dhd drivers but its a repeat of what Andeser is getting. Stretch says dhd module not found. 
using "sudo modprobe brcmfmac" on either kernel adds "registered new interface driver brcmfmac" to dmesg but nothing else. 

Thanks to
 
 
@Neil Armstrong we already have full blown Armbian for C4. Images are ofc only for testing at this stage.
 
K5.4 and K5.6 in Focal and other variants
https://www.armbian.com/odroid-c4/

Looking interesting, indeed. Just noticed in the comments the Armbian boys already got in touch with them

https://wiki.odroid.com/odroid-c4/hardware/hardware

there is then also (no more?) NanoPi Neo2/NeoCore2 in a LTS-version - only the Neo/NeoCore/NeoAir H3 line has LTS-support
So - what will be the "big next thing" as CPU?  H6/H64/H313/H616 on a like Neo2-device?
http://www.allwinnertech.com/index.php?c=product&a=index&pid=6

In some cases, I need the ethernet cable and WiFi :
- first time to set up the WiFi and test it.
In some other cases, I need only the ethernet cable :
- to have a better stable network cnx.
And in some other cases, I need only the WiFi cnx :
- I don't want to link the opi with a very long cable.
- The opi should be mobile and need to be "stored" it in some particulary places. 
 
This time, the main problem is not that I have only a WiFi lost when disconnecting the ethernet cable but I can't have any WiFi cnx if the ethernet cable is not plugged. It means that if I start the device without the ethernet cable plugged, I don't have any WiFi cnx. So I can't use the opi in "WiFi only mode". And I have found after about one week of research that the problem seems to appear with my last WiFi Access Point device (that I'm using every day for about 4-6 months from now).
 
I have found this article that I have tried to follow without any success (probably because I have used the Network Manager and the IfUpDown with WiFi together). This is a workaround to manage only the ethernet plug/unplug (not the "only Wifi" case)

I remember that the maximum frequency was 1296Mhz back with Xenial, with kernel 3.x. It even says here
 
Heat is not a problem since i have a large heatsink and temperature controlled fan, i was just curious about why the max frequency was bumped to 1368Mhz on the newer builds. What's the rationale behind it?

Hi,
 
There's been a few guides around on how to get RDP working with Armbian so you can login from your Windows or other PC. Some solutions mentioned in various threads here were:
 
Install tightvncserver instead + x2go bloat (i.e. use VNC) Only login as root - didn't seem to make any difference for me Change some permissions of a log file in your home directory.  
Well, this is what I did on my Orange PI PC running Buster desktop with Kernel 5.4, as of April 2020.
 
sudo apt install xrdp xorgxrdp sudo systemctl enable xrdp sudo reboot ... and that was it. The missing piece of the puzzel appeared to be the install of xorgxrdp, this isn't installed automatically by 'xrdp' package, and it's useless without it.

Added.

As I have been watching the development of Armbian for TV boxes, there is one area that my needs haven't been addressed yet.  And since this is open source that means I needed to read a lot of posts and get into the code to understand how things are working.  I have been doing that over the last six months or so and wanted to report back on what I am now doing to solve my issue as it may help others.
 
I have a number of TV boxes running as headless servers for a variety of projects.  Once I install Armbian on them I then get OS updates through ubuntu (I am using Ubuntu Bionic on my boxes).  That gives me bug fixes and patches for the software running on these boxes via apt update/upgrade.  However the linux kernel generally stays unpatched at the point in time that I installed one of balbes150's TV box builds.  What I wanted was to be able to build and update kernels so that I can apply new kernel versions to my servers.
 
I am now able to do that successfully across a number of TV boxes ( TX3mini, TX3 X3, H96 Max X2) (Note I only have amlogic based boxes that I test with).  I am building kernels from kernel.org sources, building .deb files and then installing those files across my servers as new kernel versions are released.  My goal was to simply stick with the 5.4 kernel as it is a long term support kernel, but I find that I have moved to 5.6 as I wanted native wireguard support.  Another goal I have is to do all this with as few patches as possible (i.e. running stock base unmodified linux).  And a final goal was to build natively on my arm based boxes.
 
Below are my notes that explain what I have done and hopefully provides others with some of the knowledge I have built up over time to be able to get what I needed working.
 
I hope this is helpful to others who want to get their hands into armbian a little deeper than just installing and running it.
 
 
build-debs.txt