Igor

Heres my try. Instead of one fixed colorset I chose some different colors too, can be used for alfa-beta-stable, release versions etc.
 

 
Recreation of Tux is under Public Commons.
 
RGB codes for different colors are included. Can be used for branding in general.
 
https://dl.dropboxusercontent.com/u/49778084/armbian.zip

I came up with this. I hope you like it Leave a like if you do, i accept criticism.
 

 
Download a whole .zip with all resolutions: https://drive.google.com/open?id=0B5goNLARJa4fSFdscnkyVDhnRUE
 
I used Blender to make Tux (no, i didnt steal it from anywhere) and Cycles render to render it.

armbian 2017
 
#nologo #nolight #nofuture

Contacted David regarding this thread.
 
Ciao,
Gerhard

C2 Ubuntu 16.04.1 image installed to Hardkernel eMMC 32GB 

  Armbian_5.24.161028_Odroidc2_Ubuntu_xenial_3.14.79_desktArmbian_5.24.161028_Odroidc2_Ubuntu_xenial_3.14.79_desktop
[sudo dd bs=1M if=filename.img of=/dev/sdx sync]
 

 
  Firefox running OK. Chromium installed and running OK. Both play html5 OK.   Very fast responsive desktop.   Very fast boot! ...from power on to desktop in 10 seconds! [no boot messages-is this by design?]   [Radio Tray install required pytho-xdg + python-notify]  
​
Memory usage running Chromium+radio tray;
 

 
playing with mpv...nice!
 

 
  LibreOffice writer ugly interface... was missing libreoffice-gtk and libreoffice-style-tango (eg)  
see also here -> http://askubuntu.com/questions/285089/why-does-my-xubuntu-libreoffice-look-ugly
 
I will EDIT as uptime increases and any issues become apparent...
 
Uptime > 3 hours and nearing the end of testing for today.
Nothing more to report at the moment...all stable and running temp of 42C with light load and crappy temporary heat sink addition....aluminium case en route...
 
Uptime = 4.5 hours test reboot initiated and completed in 20 seconds!
 
Conclusion thus far = the fastest most responsive ARM image I have used to date.  
I have to keep reminding myself I am using such a small form factor as a desktop!
Stunning work Armbian team!
 
Note: peripheral = USB DAC HiFime 9018D
http://hifimediy.com/9018D-dac
working out of the box...no issues observed...great sound!
 
1 default apps request;
  glances   
this baby is gonna cook all night while I get my beauty sleep...update am...
 
EDIT: I did shutdown for the night but all is well after a fresh 10 second boot...
EDIT#2: later in the day...C2 dev image still running stable...no issues to report
 
 
[next target is the xu4 dev image - looking forward to testing and reporting back]

H3 kernel is not ready for daily usage, but if you still want to use it, try some of our older builds or build on your own by changing this to 4.7
https://github.com/igorpecovnik/lib/blob/master/config/sources/sun8i.conf#L21
 
4.8.4 is currently broken for H3.

Yep,
Seen the commit in github a couple of minutes ago, tried it and its succeeding now, its fine.
 
Thanks!

We are not there yet since I don't know yet how we will do it. And It depends -  if we collect data mostly automatically, than we better provide some html, generated based on auto submitting. If no data went trough for certain boards, than either tester(s) failed to test or it does not boot at all.
 
Let's see how far we can come with automated approach. 
 
I need some days off so I won't jump to coding in any case.

Ideally I would like to see no more than something like this:
Boot Network HDMI Install Date Performed by ------------------------------------------------------------------------------------------------------ Lamobo R1 yes yes yes yes x.y.2016 JohnDoe Odroid XU4 no www.link-to-boot-log.com Odroic C1 yes ... ... : 

Hello,
 
I know this will be a controversial subject, but I often like to see what's happening in a devel repository by browsing commits.
 
I start by looking at the commit titles (first commit message line) to approximate the interest that particular entry is to me, then if deemed interesting, I'll read the full commit message to understand what it is about, then if still interested I'll go read the code.
 
I think this is a fairly straightforward approach to digging in a codebase or development stream, avoiding to loose time on things outside of interest scope, and allowing to focus on specific subjects.
 
So, in order for this workflow to be doable, the commit messages content need a minimum level of details, which is what I'm asking the community to act upon.
 
Would it be possible to mandate a bit more work on that front ?
 
I'm not against messages like "Whitespace fix", "Typo fix", "Better comment", anything that explains a bit what the code diff is about.
 
WDYT ?
 
PS: I think armbian is not so bad wrt $SUBJECT, it just needs a little bit more. I've seen far worse projects where I wouldn't even ask for better commitmsgs, so take that as an endorsement of the (already good) quality level of the work done.
 
Thanks

Probably it is, but we are overwhelmed with tasks. You will be faster on your own.

Thanks Joe!
 
The idea is to establish a small team, which would help us test the boards upon request. Within 2-3 weeks before planned update. If we would made more changes, more testing will be required. We want to make sure that upgrade does not break the board's core functionality at first place, than we need to try to find hidden bugs and document them under "known problems" what was found in last moment.
 
Specific details about this process are still adjusting, but roughly this is it. 
 
When I cooked my first image, it was easy and I had a lot of fun trying to find and fix a problem. I like doing that   but I simply can not. Today, this task can be done only together.

Igor said "Today, this task can be done only together"
 
 
Right you are!
 
I wish to help as best as possible.
 
I posted about the need, and am happy to say it was reposted to various communities at least 6 times in this very short time.
 
I cannot think of a more deserving project - thank you!

Thanks Joe!
 
The idea is to establish a small team, which would help us test the boards upon request. Within 2-3 weeks before planned update. If we would made more changes, more testing will be required. We want to make sure that upgrade does not break the board's core functionality at first place, than we need to try to find hidden bugs and document them under "known problems" what was found in last moment.
 
Specific details about this process are still adjusting, but roughly this is it. 
 
When I cooked my first image, it was easy and I had a lot of fun trying to find and fix a problem. I like doing that   but I simply can not. Today, this task can be done only together.

In order to make armbian better, we need your help with testing. 
 
Why?
there are simply too many boards to handle, there are task which can't be automatized, there are bugs which are not seen from our perspective. What kind of tests?
 

booting, user creation, updates, upgrades checking if basic supported functions work: video, audio, network, wireless, AP mode do nasty thing to your board and report. How to test?
Download nightly images from here. 

You want to test image which is not there?
Add those two parameters with desired targets to board's config and create a pull request. and / or
change to our daily build developer repository: deb http://beta.armbian.com $(lsb_release -cs) main utils $(lsb_release -cs)-desktop Note: you are entering developer area and things will sometimes be completely broken. Don't use this repository in production!
 
When bug is found?
 
* Provide logs with armbianmonitor -u or type as much data as you can.
 

Check if it's not already on the list and if not, add it there, [optional] Open a topic in issues support forum if you think we need to discuss it, [optional] Fix it.  
 

I have no idea what it is, I would need to hook up a board but have currently no motivation, a headache because of stress and lack of sleep. 
 
During two major updates, there was few cheer ups & thanks, a bunch of useless questions, support question on a private comm, what I "like" most, and we raise 15 euros. One, one person answered to our plead for help and saves us / you some time.
 
I will repeat this plead once again. We need regulars on testing. On daily basis, otherwise such things will continue to happen. We can't test all boards for everything on every update, nobody of the core crew even have them. If you want top service, we need volunteers and cash. I already work full time / way too much and I need to cut down my involvement within the project. Things can go only worse if tasks wont be patched on the way.
 
This service can sustain top quality level only with proper support from users, makers and us. Otherwise it will drift away from end user back to geeks, which always find a way ...

in fact , it run :-)
my dnsmasq.conf and network/interfaces was wrong
then after all ( may be the apt-get update/upgrade are also important ) with driver=nl80211 it's ok
I have a captiv portal with nginx/php/dokuwiki to share information, data, etc   where i want  for 12$ .. cool
I 'll put documentation for that next week

Hi,
 
I'am the new one. I'am German and bought last month an OrangePi PC+ from AliExpress without a clue what todo with it, but it was cheap ;-) And it was perfect for my new OMV.
 
Just installing OMV on top of Armbian / Jessie was not enough because of missing Quota Kernel Options. When setting up a development Enviroment, I found the excellent Build-Scripts of Armbian and thought, why not making an OMV-Image with the customize-image.sh.
 
And here is it (quick and dirty v0.1) Just copy it with a modified kernel.config under userpatches.
It should work with every supported Armbian Board as long as its working with Debian Jessie, because it installes OMV3.X
I compiled my Image with the legacy Kernel but it should also work with mainline.
 
If wanted I can build some Images for testing.
Please give some feedback or critics, I hope its helpfull for someone.
 
Sorry for attaching this as Code but I can't upload attachments?


#!/bin/bash

#################################################################################################################################
## customize-image.sh - for installing openmediavault 3
##
## installs omv, omv-extras, omv-flashmemory
## and making some changes to the System
## started in chroot from /tmp
##
## arguments: $RELEASE $FAMILY $BOARD $BUILD_DESKTOP
##
## Author : Benny St <Benny_Stark@live.de>
## Version : 0.1
##
## Version 0.1 - first Release
##
#################################################################################################################################
RELEASE=$1
FAMILY=$2
BOARD=$3
BUILD_DESKTOP=$4

#Modified display alert from lib/general.sh
display_alert()
#--------------------------------------------------------------------------------------------------------------------------------
# Let's have unique way of displaying alerts
#--------------------------------------------------------------------------------------------------------------------------------
{
# log function parameters to install.log
#[[ -n $DEST ]] && echo "Displaying message: $@" >> $DEST/debug/output.log

local tmp=""
[[ -n $2 ]] && tmp="[\e[0;33m $2 \x1B[0m]"

case $3 in
err)
echo -e "[\e[0;31m error \x1B[0m] $1 $tmp"
;;

wrn)
echo -e "[\e[0;35m warn \x1B[0m] $1 $tmp"
;;

ext)
echo -e "[\e[0;32m o.k. \x1B[0m] \e[1;32m$1\x1B[0m $tmp"
;;

info)
echo -e "[\e[0;32m o.k. \x1B[0m] $1 $tmp"
;;

*)
echo -e "[\e[0;32m .... \x1B[0m] $1 $tmp"
;;
esac
}


case $RELEASE in
wheezy)
# your code here
;;
jessie)
#change root passs first
#else we get some configure-errors
display_alert "Change Root PW" "custom-image.sh" "info"
echo root:openmediavault|chpasswd

display_alert "Change /etc/hostname" "custom-image.sh" "info"
echo "openmediavault" > /etc/hostname ## works after reboot

#generate locales
#they are not there
display_alert "Generate Locals and set them" "custom-image.sh" "info"
locale-gen "en_US.UTF-8"
locale-gen "C"
export LANG=C
export LC_ALL="en_US.UTF-8"

#Unattended apt-get
export DEBIAN_FRONTEND=noninteractive

#Add OMV source.list and Update System
display_alert "Adding OMV-Repo erasmus and update" "custom-image.sh" "info"
cat > /etc/apt/sources.list.d/openmediavault.list << EOF
deb http://packages.openmediavault.org/public erasmus main
## Uncomment the following line to add software from the proposed repository.
# deb http://packages.openmediavault.org/public erasmus-proposed main

## This software is not part of OpenMediaVault, but is offered by third-party
## developers as a service to OpenMediaVault users.
# deb http://packages.openmediavault.org/public erasmus partner
EOF
apt-get update

# OMV Key
display_alert "Install OMV Keys" "custom-image.sh" "info"
#wget -O - packages.openmediavault.org/public/archive.key | apt-key add -
apt-get --yes --force-yes --allow-unauthenticated install openmediavault-keyring
# OMV Plugin developer Key
apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 7AA630A1EDEE7D73


#install debconf-utils for postfix configuration
display_alert "Install debconf-utils" "custom-image.sh" "info"
apt-get --yes --force-yes --allow-unauthenticated --fix-missing --no-install-recommends -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" install debconf-utils

#install postfix
#Postfix configuration
display_alert "Install postfix and configure it - No configuration" "custom-image.sh" "info"
debconf-set-selections <<< "postfix postfix/main_mailer_type select No configuration"
apt-get --yes --force-yes --allow-unauthenticated --fix-missing --no-install-recommends -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" install postfix

#install OMV
#--allow-unauthenticated because openmediavault-keyring doesn't contain all keys???
display_alert "Install OMV" "custom-image.sh" "info"
apt-get --yes --force-yes --allow-unauthenticated --fix-missing --no-install-recommends -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" install openmediavault

#install OMV extras
display_alert "Download and install OMV Keys" "custom-image.sh" "info"
wget http://omv-extras.org/openmediavault-omvextrasorg_latest_all3.deb -O /tmp/omvextras3.deb
dpkg -i /tmp/omvextras3.deb
rm -f /tmp/omvextras3.deb
/usr/sbin/omv-update

#install openmediavault-flashmemory
display_alert "Install openmediavault-flashmemory" "custom-image.sh" "info"
apt-get --yes --force-yes --fix-missing --no-install-recommends install openmediavault-flashmemory
sed -i '/<flashmemory>/,/<\/flashmemory>/ s/<enable>0/<enable>1/' /etc/openmediavault/config.xml
/usr/sbin/omv-mkconf flashmemory

# Tidy up
display_alert "apt-get autoremove / autoclean" "custom-image.sh" "info"
apt-get autoremove
apt-get autoclean

#remove first-login Script
display_alert "Remove first-login Script" "custom-image.sh" "info"
rm /root/.not_logged_in_yet

#remove some services
#ändern auf systemctl enable dienstname.service
# /etc/systemd/system, /run/systemd/system, /usr/local/lib/systemd/system, and /usr/lib/systemd/system are four of those directories.
display_alert "Disable Services - tftpd-hpa, proftpd, nfs-common, smbd, snmpd, ssh"
#tftpd-hpa.service
systemctl disable tftpd-hpa
#proftpd.service
systemctl disable proftpd
#nfs-kernel-server.service
#nfs-common.service
systemctl disable nfs-kernel-server
systemctl disable nfs-common
#snmpd.service
systemctl disable snmpd
#samba.service
systemctl disable nmbd
systemctl disable samba-ad-dc
systemctl disable smbd
#ssh.service
#systemctl disable ssh
display_alert "SSH enable" "custom-image.sh" "info"
systemctl enable ssh
sed -i '/<ssh>/,/<\/ssh>/ s/<enable>0/<enable>1/' /etc/openmediavault/config.xml

#FIX TFTPD ipv4?
display_alert "tftpd-hpa ipv4 startup fix" "custom-image.sh" "info"
sed -i 's/--secure/--secure --ipv4/' /etc/default/tftpd-hpa

#adding omv-initsystem to firststart
display_alert "adding omv-initsystem to firstrun" "custom-image.sh" "info"
echo "/usr/sbin/omv-initsystem" >> /etc/init.d/firstrun


#debug shell
#/bin/bash
;;
trusty)
# your code here
;;
xenial)
# your code here
;;
esac

I see the patches are in the new release. Thanks, updated my Cubietruck.
 

Greetings all.
 
Today I tried updating my Odroid C2 to image 5.22 posted on Oct 22, 2016. And I got the following error during apt-get upgrade:
 
Setting up linux-u-boot-odroidc2-default (5.22) ... /var/lib/dpkg/info/linux-u-boot-odroidc2-default.postinst: line 5: conditional binary operator expected /var/lib/dpkg/info/linux-u-boot-odroidc2-default.postinst: line 5: syntax error near `function' /var/lib/dpkg/info/linux-u-boot-odroidc2-default.postinst: line 5: `[[  == function ]] && setup_write_uboot_platform' I peaked at the code in /var/lib/dpkg/info/linux-u-boot-odroidc2-default.postinst contains
#!/bin/bash source /usr/lib/u-boot/platform_install.sh [[ $DEVICE == /dev/null ]] && exit 0 [[ -z $DEVICE ]] && DEVICE="/dev/mmcblk0" [[ == function ]] && setup_write_uboot_platform write_uboot_platform $DIR $DEVICE exit 0 Which appears broken, so I updated it to:
 
#!/bin/bash source /usr/lib/u-boot/platform_install.sh [[ $DEVICE == /dev/null ]] && exit 0 [[ -z $DEVICE ]] && DEVICE="/dev/mmcblk0" [[ $(type -t setup_write_uboot_platform) == function ]] && setup_write_uboot_platform write_uboot_platform $DIR $DEVICE exit 0  
And the upgrade succeeded. Dunno where else to post this information. Hope it helps someone
 

Wow! It works! Thanks! And instruction is good, so it worked on the first try.

Remove driver from auto loading and start manually. 
modprobe fbtft_device name=adafruit22a rotate=90 speed=48000000 fps=50 gpios=reset:67,led:72,dc:195 busnum=1 and proceed with image loading.
 
Edit: 
 
For auto loading, try this: add only fbtft_device to /etc/modules and create conf file for parameters.
echo 'options fbtft_device name=adafruit22a rotate=90 speed=48000000 fps=50 gpios=reset:67,led:72,dc:195 busnum=1' >/etc/modprobe.d/fbtft_device.conf

OK. I finally got to boot up the image. Got the following:
U-Boot 2012.07 (Oct 20 2016 - 10:51:36) for Exynos5422 CPU: Exynos5422 Rev0.1 [Samsung SOC on SMP Platform Base on ARM CortexA7] APLL = 800MHz, KPLL = 800MHz MPLL = 532MHz, BPLL = 825MHz Board: HardKernel ODROID DRAM: 2 GiB WARNING: Caches not enabled TrustZone Enabled BSP BL1 version: / VDD_KFC: 0x44 LDO19: 0xf2 Checking Boot Mode ... SDMMC MMC: S5P_MSHC2: 0, S5P_MSHC0: 1 MMC Device 0: 7.4 GiB MMC Device 1: 29.1 GiB MMC Device 2: MMC Device 2 not found there are pending interrupts 0x00000001 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press quickly 'Enter' twice to stop autoboot: 0 ** Unable to use mmc 0:1 for fatload ** Unknown command 'ext4load' - try 'help' Unknown command 'ext4load' - try 'help' >>> Load Boot Script from mmc 0:1 <<< ** Unable to use mmc 0:1 for fatload ** >>> Load Boot Script from mmc 0:2 <<< ** Partition 2 not valid on device 0 ** ** Unable to use mmc 0:2 for fatload ** >>> Run Default Bootcmd <<< reading kernel..device 0 Start 1263, Count 16384 MMC read: dev # 0, block # 1263, count 16384 ... 16384 blocks read: OK completed reading RFS..device 0 Start 17647, Count 2048 MMC read: dev # 0, block # 17647, count 2048 ... 2048 blocks read: OK completed Bad Linux ARM zImage magic! Exynos5422 # Going to look into it a bit further...

I can confirm this fixes the issue, using my own Debian image that uses Sven's kernel by default. The file that was being modified remains the same after running the exploit. Good job!
 
-Olgierd

Hello,

I attempted to port the dirty COW fix (https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=19be0eaffa3ac7d8eb6784ad9bdbc7d67ed8e619) for 3.4.112, and came up with this: https://github.com/SvenKayser/Sambooca-Kernel-H3/commit/543472582a6adcef12fae4ad11da72a62f29fb74.patch

Apparently it solves the issue, but to be sure maybe some of you guys can give it a test. If it checks out please do commit it in the right places for Armbian - which I wouldn't know (Armbian has so many kernel patch folders, I don't wanna mess things up)

Regards

Sven