hook

I was actually starting to wonder if it’s the battery. Will look into it, thanks How do I figure out if it is faulty, BTW? If I `cat` the files in `\/sys/power/axp_pmu/battery/*` I get: capacity = 99 charge = 3827848 voltage = 4208600 ts_voltage = 2400

Oddly enough, after I managed to connect it via UART/serial, it just stopped rebooting itself. (the reboot in the log below was triggered by me with `shutdown`) The only noticeable issue I found so far is the CRC warning at the beginning, but I’m fairly sure I’m running it all from the external 2.5" HDD. Any ideas? U-Boot SPL 2017.05-armbian (Jun 15 2017 - 02:55:35) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC2 U-Boot 2017.05-armbian (Jun 15 2017 - 02:55:35 +0200) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Olimex A20-OLinuXino-LIME2-eMMC I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 1, SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial SCSI: Target spinup took 0 ms. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: eth0: ethernet@01c50000 Hit any key to stop autoboot: 0 6944 bytes read in 168 ms (40 KiB/s) switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2092 bytes read in 184 ms (10.7 KiB/s) ## Executing script at 43100000 Booting from eMMC or secondary SD 146 bytes read in 80 ms (1000 Bytes/s) 6328370 bytes read in 687 ms (8.8 MiB/s) 7497384 bytes read in 768 ms (9.3 MiB/s) 0 bytes read in 142 ms (0 Bytes/s) 40538 bytes read in 538 ms (73.2 KiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 6328306 Bytes = 6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 499f7000, end 49fffff2 ... OK Loading Device Tree to 499ea000, end 499f6e59 ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Loading, please wait... Starting version 241 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Warning: fsck not present, so skipping root file system done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Debian GNU/Linux 10 (buster)! [ OK ] Set up automount Arbitrary…s File System Automount Point. [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Reached target Remote File Systems. [ OK ] Listening on initctl Compatibility Named Pipe. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Created slice system-getty.slice. [ OK ] Listening on Journal Socket. Starting Restore / save the current clock... Starting Load Kernel Modules... Mounting Kernel Debug File System... Starting Remount Root and Kernel File Systems... Starting Create list of re…odes for the current kernel... [ OK ] Started Dispatch Password …ts to Console Directory Watch. [ OK ] Listening on Journal Audit Socket. [ OK ] Listening on udev Kernel Socket. Starting Set the console keyboard layout... [ OK ] Reached target System Time Synchronized. [ OK ] Started Forward Password R…uests to Wall Directory Watch. [ OK ] Reached target Local Encrypted Volumes. [ OK ] Listening on fsck to fsckd communication Socket. [ OK ] Listening on udev Control Socket. [ OK ] Listening on Syslog Socket. [ OK ] Created slice system-systemd\x2dfsck.slice. Starting Journal Service... [ OK ] Created slice User and Session Slice. [ OK ] Reached target Slices. [ OK ] Created slice system-postgresql.slice. Mounting POSIX Message Queue File System... Starting udev Coldplug all Devices... [ OK ] Started Restore / save the current clock. [ OK ] Started Load Kernel Modules. [ OK ] Mounted Kernel Debug File System. [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Started Create list of req… nodes for the current kernel. [ OK ] Mounted POSIX Message Queue File System. Starting Load/Save Random Seed... Starting Create System Users... Mounting Kernel Configuration File System... Starting Apply Kernel Variables... [ OK ] Mounted Kernel Configuration File System. [ OK ] Started Load/Save Random Seed. [ OK ] Started Apply Kernel Variables. [ OK ] Started Create System Users. Starting Create Static Device Nodes in /dev... [ OK ] Started Journal Service. Starting Flush Journal to Persistent Storage... [ OK ] Started Set the console keyboard layout. [ OK ] Started Create Static Device Nodes in /dev. Starting udev Kernel Device Manager... [ OK ] Reached target Local File Systems (Pre). [ OK ] Started Flush Journal to Persistent Storage. [ OK ] Started udev Coldplug all Devices. Starting Helper to synchronize boot up for ifupdown... [ OK ] Started udev Kernel Device Manager. [ OK ] Started Helper to synchronize boot up for ifupdown. [ OK ] Found device /dev/ttyS0. [ OK ] Found device /dev/disk/by-…1-7f59-4dd5-8991-8f6c2f2157af. [ OK ] Found device WDC_WD10JFCX-68N6GN0 1. [ OK ] Found device WDC_WD10JFCX-68N6GN0 2. Mounting /srv... Mounting /home... Activating swap /dev/sda1... [ OK ] Listening on Load/Save RF …itch Status /dev/rfkill Watch. Starting File System Check…7f59-4dd5-8991-8f6c2f2157af... [ OK ] Mounted /srv. [ OK ] Mounted /home. [ OK ] Activated swap /dev/sda1. [ OK ] Started File System Check Daemon to report status. [ OK ] Reached target Swap. Mounting /tmp... [ OK ] Mounted /tmp. [ OK ] Started File System Check …1-7f59-4dd5-8991-8f6c2f2157af. Mounting /media/mmcboot... [ OK ] Mounted /media/mmcboot. Mounting /boot... [ OK ] Mounted /boot. [ OK ] Reached target Local File Systems. Starting Create Volatile Files and Directories... Starting Set console font and keymap... Starting Raise network interfaces... [ OK ] Started ifup for eth0. [ OK ] Started Set console font and keymap. [ OK ] Started Create Volatile Files and Directories. Starting Update UTMP about System Boot/Shutdown... [ OK ] Started Entropy daemon using the HAVEGE algorithm. [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Reached target System Initialization. [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Started watches the cert bundle. [ OK ] Started Daily man-db regeneration. [ OK ] Started watch blog for changes. [ OK ] Reached target Paths. [ OK ] Started Clean PHP session files every 30 mins. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Basic System. Starting Deferred execution scheduler... [ OK ] Started Self Monitoring an…ing Technology (SMART) Daemon. Starting LSB: Armbian gathering hardware information... Starting Resets System Activity Data Collector... [ OK ] Started Regular background program processing daemon. Starting LSB: Load kernel …d to enable cpufreq scaling... Starting System Logging Service... [ OK ] Started Handle events from…R remotes decoded by lircd(8). [ OK ] Started D-Bus System Message Bus. Starting WPA supplicant... Starting Network Manager... [ OK ] Started Daily apt download activities. [ OK ] Started Daily apt upgrade and clean activities. [ OK ] Started Run certbot twice daily. [ OK ] Started Daily rotation of log files. [ OK ] Reached target Timers. Starting Login Service... [ OK ] Started Deferred execution scheduler. [ OK ] Started Resets System Activity Data Collector. [ OK ] Started System Logging Service. [ OK ] Started LSB: Load kernel m…ded to enable cpufreq scaling. [ OK ] Started Login Service. [ OK ] Started Raise network interfaces. [ OK ] Started LSB: Armbian gathering hardware information. [ OK ] Started WPA supplicant. Starting LSB: set CPUFreq kernel parameters... [ OK ] Started LSB: set CPUFreq kernel parameters. Starting LSB: Set sysfs variables from /etc/sysfs.conf... [ OK ] Started Network Manager. [ OK ] Started LSB: Set sysfs variables from /etc/sysfs.conf. Starting Hostname Service... Starting Network Manager Wait Online... [ OK ] Reached target Network. Starting A high performanc… and a reverse proxy server... Starting OpenBSD Secure Shell server... Starting PostgreSQL Cluster 11-main... Starting Advanced key-value store... Starting The PHP 7.0 FastCGI Process Manager... Starting The PHP 7.3 FastCGI Process Manager... Starting Network Time Service... Starting PostgreSQL Cluster 9.6-main... Starting Permit User Sessions... [ OK ] Started Unattended Upgrades Shutdown. [ OK ] Started Permit User Sessions. [ OK ] Started OpenBSD Secure Shell server. [ OK ] Started Hostname Service. [ OK ] Started Network Time Service. Starting Network Manager Script Dispatcher Service... [ OK ] Started Network Manager Script Dispatcher Service. [ OK ] Started Advanced key-value store. Starting Authorization Manager... [ OK ] Started Network Manager Wait Online. [ OK ] Reached target Network is Online. Starting /etc/rc.local Compatibility... Starting LSB: disk temperature monitoring daemon... Starting LSB: Advanced IEEE 802.11 management daemon... [ OK ] Started /etc/rc.local Compatibility. [ OK ] Started LSB: Advanced IEEE 802.11 management daemon. [ OK ] Started Serial Getty on ttyS0. [ OK ] Started Getty on tty1. [ OK ] Reached target Login Prompts. [ OK ] Started LSB: disk temperature monitoring daemon. [ OK ] Started Authorization Manager. [FAILED] Failed to start PostgreSQL Cluster 9.6-main. See 'systemctl status postgresql@9.6-main.service' for details. [ OK ] Started The PHP 7.0 FastCGI Process Manager. [ OK ] Started A high performance…er and a reverse proxy server. [ OK ] Started The PHP 7.3 FastCGI Process Manager. Debian GNU/Linux 10 juno ttyS0 juno login:

I’ve recently ran into this where whenever I power up my Olimex Lime 2 eMMC with Armbian, it powers down before it propretly starts. Here’s what I managed to observe so far. Armbian version …em, latest at this stage, I guess, it’s a bit hard to check exactly right now press power on button, it powers on via HDMI I see the Armbian boot logo some early boot messages pop up and ends with “Starting kernel ....” (Loading init Ramdisk seems OK, loading of device tree also OK) it goes back to black screen with Armbian logo and the _ blinking for a very short time I see an error with a long number and saying something about ”rebooting again” it powers down by itself I tried to reboot with and without the external SATA disk attached as well as other with the battery plugged in or not, and everything leads to the same result.

Same situation here on a Lime2(eMMC) on latest stable using the 4.11.6-sunxi kernel. What I did was add the following the Armbian docs on Allwinner DT overlays to /boot/armbianEnv.txt: overlay_prefix=sun7i-a20 overlays=pwm and reboot. But that didn’t fix it either. So I then tried to load the module (unsure which one it would be): modprobe pwm-sun4i modprobe pwm-fan But that didn’t fix it either. If you have any suggestion, do let me know.

Yay! Works now Thanks Igor, again I owe you a cuppa tea.

OK, just found it odd. But I can see the logic behind it, as a fail-safe if the HDD fails, right?

On it, thanks Oddly enough, the eMMC seems to include a full 1.5 GiB system and not just the /boot/ dir ls /media/mmcboot/ bin/ dev/ home/ lost+found/ mnt/ proc/ run/ selinux/ sys/ usr/ boot/ etc/ lib/ media/ opt/ root/ sbin/ srv/ tmp/ var/

Both are possible, as the board with the 4.8 kernel, is the one used to test the Lime 2 eMMC installer/images for. That’s odd though. On both boards it should be eMMC as /boot/ and the HDD for the rest. The other board has it that way. Is there an official way how to fix this or should I just copy the /etc/fstab entries for /boot and /media/mmcboot and from the other board and simply change the UUID accordingly? Good thing that it seems that the 5.31 installer seems to have worked fine on the other board

http://sprunge.us/ibXh

Odd, I now cancelled the hold/freeze (if it was on before at all), did `apt update; apt upgrade`, rebooted. Then repeated this procedure, just in case. And the results are: uname -a Linux juno 4.8.14-sunxi #1 SMP Sun Dec 11 15:20:01 CET 2016 armv7l GNU/Linux but on the other hand: ls /boot/ bin.old/ dtb@ dtb.old@ script.bin@ uInitrd@ vmlinuz-4.11.6-sunxi* config-4.11.6-sunxi dtb-4.11.6-sunxi/ initrd.img-4.11.6-sunxi System.map-4.11.6-sunxi uInitrd-4.11.6-sunxi zImage@ Colour me confused …

Yeah, sorry, wrong copy-paste. Fixed now with more info. Got it. I *might* have done that without realising what it does

Hm, you are right. Server A is on 4.11.6-sunxi; while Server B is on 4.8.14-sunxi Although in both cases `apt search` shows the 4.11.6 kernel as installed: linux-image-next-sunxi/jessie,now 5.32 armhf [installed] Linux kernel, version 4.11.6-sunxi Where would I have to check if the package is indeed frozen (and how to unfreeze it)? I honestly don’t remember doing it myself.

I just did and unfortunately this didn’t help.

I have two Olimex Lime 2 eMMC boards, both set up the same way – same HDDs, same batteries, same power supplies, etc. Both run: - Armbian 5.31 (although one was updated to it, and the other was freshly installed with that version) - Debian 9 “stretch“ (same issue when they were both on Debian 8 “wheezy” though) - Linux kernel 4.8.14-sunxi Yet, one shows the CPU temperature, and the other doesn’t. A (the fresh-installed one): cat /sys/class/thermal/thermal_zone0/temp 41800 B (the one updated to 5.31 from a previous 5.x version): cat /sys/class/thermal/thermal_zone0/temp cat: /sys/class/thermal/thermal_zone0/temp: Invalid argument Any idea how that came to be and how to fix it? My plan is to use the GPIO pins to regulate the power of an 5V fan to provide cooling only when needed. If there is interest, I’m happy to share a HowTo, if I succeed

So I went ahead and sacrificed one of my Olimex Lime2 eMMC and am happy to report that switching to stretch, as described in the original post, seems to work OK. What I noticed though is that there is also /etc/apt/sources.list.d/armbian.list, which in my case states: deb http://apt.armbian.com jessie main utils jessie-desktop Looking at http://apt.armbian.com currently only jessie and xenial are present, which means that at least Armbian-specific packages are not yet based on stretch. The packages in them do seem to be mainly kernel, u-boot, firmware etc. though.