wildcat_paris

@zador.blood.stained I will be testing the "next" tool instead of "dev", keep you in touch. I will extract the *.deb to check the files before applying the packages.

@Igor, no binary tools like swconfig, so yes, confirmed

long story short... So yes, it failed, but the on going modifications of "Armbian tools" are very promising. Kindly, Guillaume

Guys, You have done a tremendeous update for Armbian kernel compiling on current beta "master" branch I have tested BOARD="lamobo-r1" BRANCH="dev" KERNELTAG="v4.4-rc4" PROGRESS_LOG_TO_FILE=yes beta testing :-)

Igor, the real answer for the fan (often up and running) is from kernel 4.2, same frequencies but less heat / temperature... at least what I have noticed. but kernel 4.2 is pretty limited for the devices available EDIT: I guess reading code, kernel 4.2 has PWM management for the fan [to be checked]

Igor, Nope. I did not get the cable to have the serial console, my bad. Considering they send from UK with Fedex... and Fedex has been a PITA for xu4 and cloudshell, I have ordered the eMMC module from Hardkernel directly (UPS which is better at delivering but paid VAT TAX toll from South Korea to France) forgetting to order the cable as well... :-( edit: I mean this "cable" http://www.hardkernel.com/main/products/prdt_info.php?g_code=G134111883934 looking for something compatible, odroid needs 1.8V logic not 3.3V+ I might order this cable for 6€ http://www.amazon.fr/gp/cdp/member-reviews/AF3948B6XWFHI/ref=pdp_new(sorry in French) One comment mentions using it with Odroid + Mac, adding do not connect the VCC red cable, it might break your card By spec, PL2303HX can handle 1.8V depending on the implementation (some only do 3.3v+) => too risky... EDIT ordered hardkernel cable in South Korea (10 USD + 16 USD for shipment + toll fees if any), with odroid.co.uk it's 15€ + 22€ shipment

it is WIP odroid xu3 & xu4 have 4 Cortex-A7 cores max=1400MHz 4 Cortex-A15 cores max=2000MHz in HMP mode (patched kernel 3.10), 4 cores can run @1.4GHz and 4 cores @2GHz Cf. Heterogeneous Multi-Processing (HMP) solution

gr@bpi:~$ docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 4a3bcbd40604 hypriot/rpi-tor-relay "tor -f /etc/tor/torr" 2 minutes ago Up 2 minutes 0.0.0.0:9001->9001/tcp tor-relay 815d0a3de6df hypriot/rpi-busybox-httpd "/bin/busybox httpd -" 43 minutes ago Exited (137) 21 minutes ago grave_ptolemy gr@bpi:~$ ps axf 10476 ? Sl 0:32 /usr/bin/docker -d=true -p /var/run/docker.pid --storage-driver=overlay -D 13711 ? Sl 0:00 \_ docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 9001 -container-ip 172.17.0.2 -container-port 9001 13846 ? Ssl 0:34 \_ tor -f /etc/tor/torrc.bridge

ok see... I add to comment to start docker server: gr@bpi:~$ cat /etc/init.d/docker [...] # see also init_is_upstart in /lib/lsb/init-functions (which isn't available in Ubuntu 12.04, or we'd use it) #if [ -x /sbin/initctl ] && /sbin/initctl version 2>/dev/null | grep -q upstart; then # log_failure_msg "$DOCKER_DESC is managed via upstart, try using service $BASE $1" # exit 1 #fi

FYI switch back a while from a 15.04 hardkernel rootfs, upgraded to Ubuntu 15.10 gr@odroid:~$ cat /proc/version Linux version 3.10.92 (root@xu-b1) (gcc version 4.6.4 (Ubuntu/Linaro 4.6.4-6ubuntu2) ) #1 SMP PREEMPT Tue Nov 17 00:15:24 BRST 2015 Got my 32GB eMMC module, cloudshell (nas) working (cloudshell screen not tested so far) + a separate SD card let me boot to make a backup of the eMMC Stable let's see odroid)#enabled #description Exynos5422 XU3/XU4 octa core #build 3wip LINUXFAMILY="odroid" BOOTSIZE="16" BOOTCONFIG="odroid_config" MODULES="ethernet wlan_8723bs bonding" MODULES_NEXT=""

Zador,blood.stained, Yes great! it is far far simpler and far much better. I wanted a wrapper to avoid Igor changes including "\" as well as to keep learning bash/scripting. dealing with "dialog" non-standard parameters is pretty hard. Thanks!

Hello, When patching or generally compiling, "dialog" is not my friend for reading & testing I would propose adding a wrapper in common.sh (as in branch "second") dialog_wrapper () { ARGS=$(getopt -o b:p: -l "backtitle:,progressbox:" -n "$0" -- "$@"); if [ $? -ne 0 ]; then exit 1; fi eval set -- "$ARGS"; unset cmdl while true; do case "$1" in -b|--backtitle) shift; if [ -n "$1" ]; then cmdl="$cmdl --backtitle '$1'"; shift; fi ;; -p|--progressbox) shift; if [ -n "$1" ]; then cmdl="$cmdl --progressbox '$1'"; shift; fi ;; --) shift; break; ;; esac done for args in "$@" do cmdl="$cmdl $args" done LOGFILE=/dev/null if [[ $DIALOG_LOGFILE != "" ]] ; then LOGFILE=$DIALOG_LOGFILE [ ! -f $DIALOG_LOGFILE ] && touch $LOGFILE lines=$(wc -l <$DIALOG_LOGFILE) if [[ $lines -ge 2000 ]]; then rm -f $DIALOG_LOGFILE.log mv $DIALOG_LOGFILE $DIALOG_LOGFILE.log touch $DIALOG_LOGFILE fi fi if [[ $DIALOG_WRAPPER == "" ]] ; then tee -a $LOGFILE | eval "dialog $cmdl" else tee -a $LOGFILE fi } and replacing the "dialog" with "dialog_wrapper" for compilation in "compile.sh", 2 options: #DIALOG_WRAPPER # use dialog as usual DIALOG_WRAPPER=1 # dialog is not active #DIALOG_LOGFILE # logfile is /dev/null DIALOG_LOGFILE=compile.log

the "userpatches" feature is pretty promising... branch "second" is working fine with fresh install + "--depth 1 --no-single-branch" + BOARD="lamobo-r1" BRANCH="next" KERNELTAG="v4.2.6" BUILD_DESKTOP="No" and RELEASE="trusty" or "wheezy" or "jessie" branch "master" still choke on "arch/arm/boot/dts/Makefile:586: *** commands commence before first target. "

Igor, "--depth 1 --no-single-branch" seems far better than "--depth 20" because the download is faster (>1 MB/s but more files to download vs. 100kB/s) and there is less computation to do (as seen while testing the 2 options) ok, I will retry "-b master" thanks!

Igor, FYI testing a fresh install of "-b master" got a kernel 4.4.0-rc3 to compile (I guess your target is 4.3 4.2.6) and then arch/arm/boot/dts/Makefile:639: *** commands commence before first target. x x make: *** [dtbs] Error 2

"Help yourself and Armbian will help you. ARMen."

sorry, wrong reply, if you intend to compile natively as Igor suggests :-)

quick update (2015/11/27) the Odroid XU4 is running Archlinux ARM as for now with kernel 3.10.92 (ok it is creepy) more ARM generic 4.2/4.3/4.4-rc2 are online, won't test it so far, testing what I can get of the hardware. The XU4 is able to compile thunderbird 38.4.0 with lightning (with ccache) on a SSD, quite powerful.

Igor, the Armbian tools is fine for Wheezy/Jessie but nope for Trusty the process stops with invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found. invoke-rc.d: policy-rc.d denied execution of stop. there is a fix here: https://hub.docker.com/r/calvinpark/arduino-ide-builder-linux32/~/dockerfile/ related to https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325142 Sorry I'm late to the party, but what about this as a workaround? # dpkg-divert --local --add /etc/init.d/systemd-logind # ln -s /bin/true /etc/init.d/systemd-logind In the chroot, obviously. :-) also same issue http://osdir.com/ml/ubuntu-bugs/2015-07/msg05371.html because yes in a real VM there is no issue but docker is not a VM, so we leaked an old bug. :-)

humm. my guess your Armbian tool environment is not setup properly a recent install gives root@d1dfc6648c59:/# file /usr/bin/arm-linux-gnueabihf-ld /usr/bin/arm-linux-gnueabihf-ld: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=481a5f6210c1256f352b9751f669265f81f90885, stripped so /usr/bin/arm-linux-gnueabihf-ld file exists. try to start a fresh install http://www.armbian.com/using-armbian-tools/

Rui, there is probably a workaround as root to get back dkms working to compile make scripts in gr@bpi:/usr/src/linux-headers-4.3.0-sunxi$ sudo make scripts HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/bin2c HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf --silentoldconfig Kconfig HOSTCC scripts/dtc/dtc.o HOSTCC scripts/dtc/flattree.o HOSTCC scripts/dtc/fstree.o HOSTCC scripts/dtc/data.o HOSTCC scripts/dtc/livetree.o HOSTCC scripts/dtc/treesource.o HOSTCC scripts/dtc/srcpos.o HOSTCC scripts/dtc/checks.o HOSTCC scripts/dtc/util.o HOSTCC scripts/dtc/dtc-lexer.lex.o HOSTCC scripts/dtc/dtc-parser.tab.o HOSTLD scripts/dtc/dtc CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/modpost.o CC scripts/mod/devicetable-offsets.s GEN scripts/mod/devicetable-offsets.h HOSTCC scripts/mod/file2alias.o HOSTCC scripts/mod/sumversion.o HOSTLD scripts/mod/modpost HOSTCC scripts/kallsyms HOSTCC scripts/conmakehash HOSTCC scripts/sortextable HOSTCC scripts/asn1_compiler HOSTCC scripts/extract-cert gr@bpi:/usr/src/linux-headers-4.3.0-sunxi$ file scripts/basic/fixdep scripts/basic/fixdep: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=e21986187584d701fa8f4d5d987a9cee808208c8, not stripped Armbian will provide a better solution.

Igor, no it stopped the process (usually working very fine with virtualbox + ubuntu 14.04 server). let's see later, thanks for your support :-)

Apparently, cannot make it work for "trusty" as "image", I cannot figure out the issue (conflict docker guest / host system ?) Setting up xml-core (0.13+nmu2) ... Processing triggers for ureadahead (0.100.0-16) ... Setting up bluez (4.101-0ubuntu13.1) ... initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused * Starting bluetooth Can't open RFCOMM control socket: Address family not supported by protocol ...done. Setting up systemd-services (204-5ubuntu20.15) ... Setting up libpam-systemd:armhf (204-5ubuntu20.15) ... initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found. dpkg: error processing package libpam-systemd:armhf (--configure): subprocess installed post-installation script returned error exit status 100 Processing triggers for libc-bin (2.19-0ubuntu6) ... Processing triggers for sgml-base (1.26+nmu4ubuntu1) ... Processing triggers for ureadahead (0.100.0-16) ... Errors were encountered while processing: libpam-systemd:armhf E: Sub-process /usr/bin/dpkg returned an error code (1)

Hello, Interested in replacing virtualbox as a VM host, "docker" tool seems to be able to run on Debian/Ubuntu/other linux distro/MacOS/Windows (as they claim) My test: 1/ Installing docker on my amd64 4-cores Ubuntu 14.04 (too much tweaking to run "armbian" properly) see doc here also I have been using "Create a Docker group" and don't forget to run "Hello World" test 2/ To create a new container with Ubuntu 14.04 (if you have added docker group to your non-privileged user, if not use "sudo") $ docker run --privileged -i -t ubuntu:14.04 /bin/bash "privileged" is needed for /dev/loop operations, if not the container cannot see the loop device, btw it is less "secure" but not "really" applicable here, I am on my test system. on the host system, the files are stored in "/var/lib/docker", you can move this folder on another HDD/SSD, then you need to (in my example) "cd /var/lib; ln -s /home4/docker docker" 3/ once you have the root shell of the VM # mkdir /root/armbian # cd /root/armbian then feel free to follow the Armbian tool instructions Once all is compiled & package, you can transfer the files with "sftp", "ftp", etc. Or if you want a challenge, grab the files in /var/lib/docker (good luck!) 4/ later to come back to the container, list the containers, get the "Container ID" then start the container $ docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES e12d3a2b9263 ubuntu:14.04 "/bin/bash" About an hour ago Up About an hour grave_ardinghelli d1efa716ad64 hello-world "/hello" 8 hours ago Exited (0) 8 hours ago elegant_meitner $ docker start -i e12d3a2b9263 (to be tested more carefully) edit: you need the "under work" script attached as the ubuntu:14.04 is *not* really a ubuntu server packaged style! edit2: [ o.k. ] Fixing release custom applications. [ jessie ] [ o.k. ] Install board specific applications. [ lamobo-r1 ] [ o.k. ] Fingerprinting. [ Armbian 4.6 Lamobo-r1 Debian jessie next Linux 4.2.6 ] [ o.k. ] Creating boot scripts [ lamobo-r1 ] [ o.k. ] Possible after install. [ o.k. ] Writing boot loader [ /dev/loop1 ] [ o.k. ] Shrink image last partition to [ minimum ] [ o.k. ] Create and sign [ Armbian_4.6_Lamobo-r1_Debian_jessie_4.2.6.zip ] [ o.k. ] Runtime [ 81 min ] et voilà ! more testing needed

Hello, FYI for prospective on Odroid XU4, testing images for XU4 (I also have a Cloushell (mini NAS including LCD display)) desktop image link folder Ubuntu 14.04.1 : ok, upgrade to 14.04.3 ok, upgrade to kernel 3.10.92 ok, upgrade to odroid final kernel 4.2.0 DEAD Ubuntu 15.04 : DEAD after reboot (kernel 4.2.0) It seems the image with kernel 4.2.0 just removed "journal" feature of ext4 on startup, so at next reboot, the ext4 fs is dead. trying to fix the SD card on a amd86 Ubuntu gives error like "/usr/sbin" dead, filesystem is garbage server image link ubuntu server image is not usable, dead after first reboot (kernel 4.2 ?) archlinux image using kernel 4.2 3.10.92 (existing 4.3/4.4-rc1 general kernel - untested) pretty ok after rebooting. Only drawback, everything is to be installed, I don't know much of archlinux tools. edit : Do not install odroid-cloudshell package, it really breaks the filesystem after reboot. edit2: in fact, kernel 3.10.92 make the ethernet interface (USB=>ETH) no longer working. It seems the drivers is "closed" sourced edit3: looking at images maybe edit4: ArchlinuxArm seems stable, kernel is old. but image is fine after reboots over and over. pacman is pretty cool!