guidol

Yes. I've got a big heatsink on the way for my Rock Pi4B. That one has 4GB ram vs 2GB of my M4. So with that I can do 4K or higher renders during a week/month of all of them.
I've added all the original .png renders + all the blender files as attachment file. Everyone can do a higher resolution render (8K, 16K, 32K???) if they want. Or play with it a bit.

Here are all of them. These are 1440p but converted to jpg.
Armbian transport

Snowy Armbian

Old school Armbian

Armbian in space

Empire of Armbian

Armbian @ the beach

Armbian__Backgrounds.7z

Armbian as transportation company (of 1's and 0's)...

This will be my last submission. I've got too many other things to do. Otherwise I would never stop. Cheers.

@Igor Understood, thanks for your answer … it seems to be complicated. Another idea in my head … Is there a csv file somewhere that contains which board has which feature?
@Tido Thanks for your input … I'll consider that if I'm going to buy a new board
@guidol Thanks for the links … and pointing out that sata search won't work for it

Devuan on ARM is up!
 
Ok, so all I had was an RPI3, but yeah it's a base system.  Classic root/toor .  You do the rest.  Noted that /etc/fstab might need some Armbian love to save your sd card.  Crusty old 1.22 ver of busybox included as a catastrophe fallback.  Yeah, replace that if you like with an up to date version pronto.
 
Beginners who cut n paste docs might get frustrated by not seeing an mmcblk0 device from some other box when dd'ing the image, and using /dev/sdx initially.
 
So there you go.  Kernel 4.9.16, classic init style.  Whaddya know?  It works!  Rock systemd if you want, but nice to know Devuan is more about choice than the init drama itself. (other than luser fanboy stuff...).
 
DIAGNOSTICS:
Interestingly enough, my usb mouse kept on disconnecting and reconnecting at random intervals spewing itself on the console while doing so.  Makes me wonder if something like that could be *hidden* by systemd constantly babysitting it and only a binary log review would reveal it?  Dunno - too many variables - luser talk.  Might be interesting to bring up the same systems with different inits to see who's talking and who's not.
 

Man..... i kinds wish gopher would make a come back for my terminal lifestyle dreams 

let's try this url for wheezy security updates?:
http://security.debian.org/debian-security/dists/wheezy/updates/
http://security-cdn.debian.org/debian-security/dists/wheezy/updates/
 
and here main contrib and non-free?
 

I 
 
Sorry! you're right! the buildroot for opi 2G is that:
https://github.com/txurtxil/broot2g
I Leave the config-OpiIoT2G file preconfigured for our card, the procedure is this:
  git clone https://github.com/txurtxil/broot2g
  cd broot2g /
  mv config-OpiIoT2G .config
  make menuconfig -> if you want to see or modify buildroot parameters
   make ---> to build buildroot
Note1: you can modify or view kernel parameters by running make linux-menuconfig
Note2: I  use to develop and compile a cheap tv box (x96) with armbian, I am very comfortable and I do not use the PC, I access it by SSH, tmux, etc ...:
 
Processor       : AArch64 Processor rev 4 (aarch64)
processor       : 0
processor       : 1
processor       : 2
processor       : 3
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: AArch64
CPU variant     : 0x0
CPU part        : 0xd03
CPU revision    : 4
Hardware        : Amlogic

 

Hi Guys,
I'm new to the forum here but have been using [only] Armbian on my various OPi boards for some time.
I'm now waiting for an OPi3 board to arrive from Aliexpress and so I've been following this thread with interest.
I've now successfully built Stretch images from the dev sources but with no hardware yet to test I'm restricted to keeping up with the posts on here.
Many thanks to everyone who has already contributed to what I reckon is going to be a pretty awesome board for the price.
George
Somerset, UK

In a Opi Iot 2G I have used 64gb usb flash disk mounted from a armbian that i installed at 512mb flash rom. 
The kernel is 3.10.62, I have modified it so that it does not rotate the MAC, I do not see a larger version of the kernel necessary although it seems that it has been incorporated into version 5 in development:
https://github.com/torvalds/linux/tree/master/arch/arm/mach-rda
 
Actually I have created several images with buildroot, it is simple, I have shared the code ready to make the image in my github:
https://github.com/txurtxil/broot2g
The merit is from a 4pda user (Yoshee) has done an in-depth job to program tft screens from the kernel. I have never seen it work so well at the same time oled screen + sensor dht22 and switches and with the image that has left yoshee all the good and very fine, I leave it here (root / 1)
https://mega.nz/#!oB0mmSBD!XhslDKikwAyvt-6frhpsnX5Tj5SIrKKK7KrHqVE7hms
In /etc/iot.conf we can configure bot telegram, mqtt, etc ... it's a great job.

which problems did you have? I do ask, because I did setup today my NanoPi K1 Plus for setiathome with a fresh build dev-image:
 
Welcome to ARMBIAN 5.77 user-built Debian GNU/Linux 9 (stretch) 5.0.4-sunxi64 package bsp-kernel[5.77] u-boot[5.77] dtb[5.77] firmware[5.77] config[5.77] BOINC_Manager connected from PC to NanoPi K1 Plus:

I have recovered my IoT-2G board because, basically I think it can be fun to program it, I also expect an i96, I love its small size (and its price to learn basic things about kernel programming). Armbian has discarded this board, but we have alternative: buildroot, which is great and can be installed in the 512mb flash memory.
You can do things as interesting as this: DHT22+Qt5+Old SD1301
 
 

Yes ! I was blind, because I've only search in my stuff, the glitch was elsewhere :
@megous , Megous 5.0.y branch has USB0-IDDET wrongly on PC6, one of the eMMC data pin, I've fixed it by assigning it to the good PC15 pin.

Initial commit is done !

I would like to announce that I am getting started on an armbian-derived project, Armbian-NG. This is not a fork of Armbian, nor a rewrite, it's a derived project that piggyback's on the excellent work by Igor and the entire armbian development team. I think of Armbian-NG as armbian's little clumsy brother, who is just learning to walk but has great potential. 
In as few words as possible, Armbian-NG will be a Python (set of) script(s) that runs natively on Aarch64 (64-bit ARM) hardware (running Ubuntu 18.04 or later) to build Armbian images. More details  can be found here: https://github.com/AndrewBCN/Armbian-NG
 
As with armbian, anybody is welcome to contribute with code and ideas to Armbian-NG. And since no project is worth its storage space without a logo, Armbian-NG already has one. 

To anyone who needs a Linux 4.20/5.0 8189es driver, I successfully compiled one from here https://github.com/jwrdegoede/rtl8189ES_linux/  
 
I installed the headers .deb but needed some files from source kernel,  so cloned the https://github.com/150balbes/Amlogic_s905-kernel/ and copied the scripts/mod folder to the /lib/modules/<kernel version>/build/
 
Then, on the rtl8189es_linux folder
 
make ARCH=arm64  KSRC=/lib/modules/<kernel version>/build/ CONFIG_POWER_SAVING=n
 
To install, for some reason sudo make install not worked, so I typed:
 
sudo install -p -m 644 8189es.ko  /lib/modules/<kernel version>/kernel/drivers/net/wireless/
sudo /sbin/depmod -a
sudo modprobe 8189es
 
And voilà, wifi working

Thank you very much, you save my 10 days work  .... perfectly work 

check with nmtui your ip address - there should be a /24 at the end of the ip of your OPi Zero..... like 192.168.7.8/24
but only for the ip of your zero and not at the gateway or dns-ip
 
I got tge same like problem, because if you enter only the ip for your zero in nmtui then nmtui will add a /32 when you do save the connection and then your zero is very "lonely"...

Did create a more compact version for me (and you?)
 
nano /etc/update-motd.d/10-armbian-header ARMBIAN_bsp=$(more /etc/armbian-release|grep VERSION|cut -f 2 -d '=') ARMBIAN_kernel=$(dpkg -s linux-image-$BRANCH-$LINUXFAMILY|grep Version|cut -f 2 -d ' ') ARMBIAN_uboot=$(dpkg -s linux-u-boot-$BOARD-$BRANCH|grep Version|cut -f 2 -d ' ') ARMBIAN_dtb=$(dpkg -s linux-dtb-$BRANCH-$LINUXFAMILY|grep Version|cut -f 2 -d ' ') ARMBIAN_firmware=$(dpkg -s armbian-firmware|grep Version|cut -f 2 -d ' ') ARMBIAN_config=$(dpkg -s armbian-config|grep Version|cut -f 2 -d ' ') printf '\n' printf 'pkg-version kernel[\e[0;91m%s\x1B[0m] u-boot[\e[0;91m%s\x1B[0m] dtb[\e[0;91m%s\x1B[0m] firmware[\e[0;91m%s\x1B[0m] config[\e[0;91m%s\x1B[0m]\n' "$ARMBIAN_kernel" "$ARMBIAN_uboot" "$ARMBIAN_dtb" "$ARMBIAN_firmware" "$ARMBIAN_config" printf '\n'  

Hi @guidol Thank you
I just did some more searching and found your very useful forum posts about audio issues you had with orange pi zero
I did try making /etc/asound.conf as per examples on the orange pi forums, which didn't help.

I'm going to see if I've got all the modules loaded.
I've edited my first post with more commands and outputs.
 
I added
sun4i_codec sun8i_codec_analog to /etc/modules
 
YES, progress!!!
 
$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 YES!!! IT WORKS. IT WORKS!!!

It's ALIVE!!!!! (demented laughter)
Muahahahah
 

 
Wow! I'm impressed with the sound quality!!!

Actually, you can natively build an Aarch64 Rockchip kernel very easily.
 
Instructions to do so can be found here:  http://wiki.loverpi.com/faq:sbc:libre-aml-s805x-howto-native-compile-kernel
 
You'll have to modify a couple of steps slightly if you are building for Rockchip SoC's but basically it's a 10 minutes process to get started on compilation, and depending on your hardware your kernel will compile in 15 to 45 minutes. Another 5 minutes to spend on installing and voilà! You can run your own self-compiled mainline Linux kernel on your SBC, if it manages to boot properly but note that this is not guaranteed on Rockchip SoC's.

That was an excellent tip, thank you very much! 

for more information about the versions of your armbian-system-packages you could add the following to your
/etc/update-motd.d/10-armbian-header
ARMBIAN_bsp=$(more /etc/armbian-release|grep VERSION|cut -f 2 -d '=') ARMBIAN_kernel=$(dpkg -s linux-image-$BRANCH-$LINUXFAMILY|grep Version|cut -f 2 -d ' ') ARMBIAN_uboot=$(dpkg -s linux-u-boot-$BOARD-$BRANCH|grep Version|cut -f 2 -d ' ') ARMBIAN_dtb=$(dpkg -s linux-dtb-$BRANCH-$LINUXFAMILY|grep Version|cut -f 2 -d ' ') ARMBIAN_firmware=$(dpkg -s armbian-firmware|grep Version|cut -f 2 -d ' ') ARMBIAN_config=$(dpkg -s armbian-config|grep Version|cut -f 2 -d ' ') printf 'ARMBIAN bsp : \e[0;91m%s\x1B[0m\n' "$ARMBIAN_bsp" printf 'ARMBIAN kernel : \e[0;91m%s\x1B[0m\n' "$ARMBIAN_kernel" printf 'ARMBIAN u-boot : \e[0;91m%s\x1B[0m\n' "$ARMBIAN_uboot" printf 'ARMBIAN dtb : \e[0;91m%s\x1B[0m\n' "$ARMBIAN_dtb" printf 'ARMBIAN firmware : \e[0;91m%s\x1B[0m\n' "$ARMBIAN_firmware" printf 'ARMBIAN config : \e[0;91m%s\x1B[0m\n' "$ARMBIAN_config" printf '\n' printf 'ARMBIAN kernel : \e[0;91m%s\x1B[0m u-boot : \e[0;91m%s\x1B[0m dtb : \e[0;91m%s\x1B[0m firmware : \e[0;91m%s\x1B[0m config : \e[0;91m%s\x1B[0m\n' "$ARMBIAN_kernel" "$ARMBIAN_uboot" "$ARMBIAN_dtb" "$ARMBIAN_firmware" "$ARMBIAN_config" printf '\n' this will give you the armbian-system-package-informations in different lines or
at the end in one line like in the attached image
 
 

Worked like a charm. Thanks !

https://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html
 
These features are new in 0.71 (released 2019-03-16):
 
Download at
https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
Windows Binary 32Bit: https://the.earth.li/~sgtatham/putty/latest/w32/putty.zip
Windows Binary 64Bit https://the.earth.li/~sgtatham/putty/latest/w64/putty.zip

if you got a Box with S912 and armbian 5.76 - then you could "update" like I did.
Download the packages from  https://yadi.sk/d/pHxaRAs-tZiei/5.77/deb and
dpkg -i armbian-config_5.77_all.deb dpkg -i linux-image-aml-s912_5.77_arm64.deb dpkg -i linux-headers-aml-s912_5.77_arm64.deb dpkg -i firmware-armbian-full_5.77_all.deb reboot (firmware and headers could be optional from your sight of view)
Before this firmware-package I only got a Broadcom (brcm) package installed for the WiFi Firmware
Headers are for compiling Sourcecode
 
This should leave you apps/config intact.