berturion

Ok thanks. For now I am on Arch Arm with the mainline kernel. But I am not very satisfied with its stability. My system hangs randomly. I suspect a bad support of the USB stuff. I am thinking of migrating to Armbian, I really liked it on my old Cubieboard2. My rootfs is on a partition of a self powered external disk connected to the USB 3.0 port. I also have another external disk in a 2.0 port (powered by the host) that is mounted when executing cron backup tasks. Do you think Armbian with aayfan kernel is a more stable ? What is the probability for the mainline kernel to have a good support for this board ? (Sorry to be a little out of the subject of this thread)

Hello Igor, when you say "a modern kernel", you mean a kernel near the version of the mainline one ? Is there a corresponding git repo to see the progress of it ?

At least, my thread will teach armbian forum readers about how load average is calculated. Me the first. I am looking forward trying your armbianmonitor-daemon

I might be wrong but I think you are a little upset... Sorry if I am responsible for this. I understand what you mean, and I just try to find a way to display more relevant information. The aim of my previous question was to know if coloring in red when it reaches 1.0 was relevant or not. If the answer of my question was "yes", then it was. If the anwser was no, it wasn't. Now, if I understand, coloring in red after 1.0 is not relevant because number of cpu and cores have an impact (but it is not the only one) so, this number, whatever its value, should stay green or white. I agree that the 2 other numbers should be display in order to have a kind of relevant information. So why not simply display those 3 numbers in white ? Or not display any of them at all ? Or why keep this value and its changing color in login script if it is totally useless ?

If we have 2 systems, same linux OS, same hardware, same running processes, same SD Card. The only difference is that one has one core and the other, two. Is load average will be the same ?

Hello, I have a Cubieboard2 and armbian in a vanilla kernel with jessie flavor. This board has a 2 cores processor. When I am logging in, load average is shown and becomes red when it is greater than 1.0. Since, there are 2 cores, it should be colorized only when it reaches 2.0. Is it possible to have this feature (taking care of each board's number of cores) ? Thank you

According to this page https://forums.linuxmint.com/viewtopic.php?t=162677(linuxmint being based on Ubuntu), the package util-linux in which there is blkid could be outdated and not supporting PARTUUID. My desktop is Linuxmint 17.3 based on Ubuntu 14.04 ant util-linux version is "2.20.1-5.1 ubuntu20.7". Command blkid on my desktop doesn't show "PARTUUID", only "UUID". On my Cubieboard2 with Debian 8 Jessie, This package is in version "2.25.2-6". And PARTUUID is shown with blkid. Maybe this is the reason ? PARTUUID on your Ubuntu version is not supported and you can't mount it from it ? I am not an expert, though.

Hello @lampra, It is a Vanilla Jessie Cubieboard2 image taken from armbian.com website, not self-built. Though, I don't remember the initial version I downloaded. There have been some updates since then. ____ _ _ _ _ / ___| _| |__ (_) ___| |__ ___ __ _ _ __ __| | | | | | | | '_ \| |/ _ \ '_ \ / _ \ / _` | '__/ _` | | |__| |_| | |_) | | __/ |_) | (_) | (_| | | | (_| | \____\__,_|_.__/|_|\___|_.__/ \___/ \__,_|_| \__,_| Welcome to ARMBIAN Debian GNU/Linux 8 (jessie) 4.4.1-sunxi $ uname -a Linux local 4.4.1-sunxi #10 SMP Wed Feb 17 17:57:20 CET 2016 armv7l GNU/Linux

Ok, that works, it was the PARTUUID's fault ! /dev/mmcblk0: PTUUID="0006426d" PTTYPE="dos" /dev/mmcblk0p1: UUID="01bed786-74eb-4262-9f51-1c604e65c951" TYPE="ext4" PARTUUID="0006426d-01" /dev/sda1: UUID="83ce9744-1e54-4191-af69-d7a7fcfeedbe" TYPE="ext4" PARTUUID="000c8dd7-01" /dev/sda2: UUID="20753884-8113-4c2e-a9fe-0e2322f84c16" TYPE="ext4" PARTUUID="000c8dd7-02" I had to use "000c8dd7-01" in my boot env line. My fstab was correct. Thank you

Thanks for this quick reply but I don't know what to do exactly... Install intrd ? Modify boot line ? @zador.blood.stained, I am wrong with my partuuid, you're right. I will try again.

Hello, I just re-tried to boot cubieboard with rootfs on external drive using USB it it works now. Although, I want to use UUID of disk in order to be sure the rootfs is correctly found if I plug other USB devices. My u-boot line is now : setenv bootargs "init=/bin/systemd console=tty1 root=PARTUUID=83ce9744-1e54-4191-af69-d7a7fcfeedbe rootwait rootfstype=ext4 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=7" And my fstab has now this line (I commented the /dev/mmcblk0p1... line, rootfs was on sdcard) : UUID=83ce9744-1e54-4191-af69-d7a7fcfeedbe / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 0 The kernel is launching but not Debian. I re-tried with the "/dev/sda1" notation and it works... Is there a problem using UUID ?

Does anyone know how I could force "cold state" of the device or force downloading the firmware ?

$ sudo systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @37.280s └─multi-user.target @37.273s └─smbd.service @34.013s +3.199s └─nmbd.service @14.457s +19.525s └─basic.target @14.224s └─timers.target @14.187s └─systemd-tmpfiles-clean.timer @14.187s └─sysinit.target @14.185s └─nfs-common.service @13.679s +504ms └─rpcbind.target @13.643s └─rpcbind.service @13.443s +198ms └─network-online.target @13.406s └─network.target @13.406s └─networking.service @5.551s +7.852s └─local-fs.target @5.490s └─proc-fs-nfsd.mount @15.904s └─local-fs-pre.target @2.227s └─systemd-remount-fs.service @2.006s +125ms └─keyboard-setup.service @1.159s +805ms └─systemd-udevd.service @1.093s +25ms └─systemd-tmpfiles-setup-dev.service @853ms +98ms └─kmod-static-nodes.service @725ms +60ms └─system.slice @645ms └─-.slice @641ms $ sudo service --status-all [ + ] ajenti [ - ] alsa-utils [ - ] apache2 [ - ] armhwinfo [ - ] bluetooth [ - ] bootlogs [ - ] bootmisc.sh [ - ] brcm40183-patch [ - ] checkfs.sh [ - ] checkroot-bootclean.sh [ - ] checkroot.sh [ + ] console-setup [ + ] cpufrequtils [ + ] cron [ + ] dbus [ + ] fake-hwclock [ - ] firstrun [ + ] haveged [ + ] hddtemp [ + ] hdparm [ - ] hostapd [ - ] hostname.sh [ - ] hwclock.sh [ + ] inadyn [ + ] kbd [ + ] keyboard-setup [ - ] keymap.sh [ - ] killprocs [ + ] kmod [ + ] lirc [ + ] loadcpufreq [ + ] memcached [ + ] minidlna [ - ] motd [ - ] mountall-bootclean.sh [ - ] mountall.sh [ - ] mountdevsubfs.sh [ - ] mountkernfs.sh [ - ] mountnfs-bootclean.sh [ - ] mountnfs.sh [ + ] mysql [ + ] networking [ + ] nfs-common [ + ] nfs-kernel-server [ + ] nginx [ + ] nmbd [ + ] ntp [ + ] php5-fpm [ + ] procps [ + ] prosody [ + ] rc.local [ - ] resize2fs [ - ] rmnologin [ + ] rpcbind [ - ] rsync [ + ] rsyslog [ + ] samba [ + ] samba-ad-dc [ - ] screen-cleanup [ - ] sendsigs [ + ] smbd [ - ] sudo [ + ] sysfsutils [ ? ] thin [ + ] udev [ + ] udev-finish [ - ] umountfs [ - ] umountnfs.sh [ - ] umountroot [ - ] unattended-upgrades [ + ] urandom [ - ] vdr [ + ] winbind [ - ] x11-common For me, all is good now. Thanks for this update

The url is here: http://sprunge.us/dFBB I will place this new script in /etc/init.d and report back the behavior. EDIT: For now, with new script re-enabled: $ sudo systemctl status armhwinfo â— armhwinfo.service - LSB: Armbian gathering informations about hardware Loaded: loaded (/etc/init.d/armhwinfo) Active: active (exited) since ven. 2016-03-04 09:12:41 RET; 6s ago Process: 2854 ExecStart=/etc/init.d/armhwinfo start (code=exited, status=0/SUCCESS) mars 04 09:12:30 xxxxxxxx armhwinfo[2854]: [ ok ] Setting cfg I/O scheduler for sda mars 04 09:12:30 xxxxxxxx armhwinfo[2854]: [ ok ] Setting noop I/O scheduler for mmcblk0 mars 04 09:12:31 xxxxxxxx armhwinfo[2854]: [ ok ] Starting ARM hardware info: Cubieboard mars 04 09:12:41 xxxxxxxx systemd[1]: Started LSB: Armbian gathering informations about hardware.

It was my first config. But when plugged in a powered USB hub, the stick is detected in "warm" state and the driver is not loaded.