sooperior

Hi I have a suggestion to modify update-mot.d script 30-sysinfo. It reports battery chargin or not depending on percentage (if <100% then is charging): # Battery info for Allwinner # kernel 4.4+ axp_dir="/sys/power/axp_pmu" if [[ -e "$axp_dir" ]]; then status_battery_connected=$(cat $axp_dir/battery/connected) if [[ "$status_battery_connected" == "1" ]]; then status_battery_charging=$(cat $axp_dir/charger/charging) status_ac_connect=$(cat $axp_dir/ac/connected) battery_percent=$(cat $axp_dir/battery/capacity) # dispay charging / percentage if [[ "$status_ac_connect" == "1" && "$battery_percent" -lt "100" ]]; then status_battery_text=" charging" elif [[ "$status_ac_connect" == "1" && "$battery_percent" -eq "100" ]]; then status_battery_text=" charged" else status_battery_text=" discharging" fi fi fi However, at least on banana pi M1 (A20) it can be below 100% and not charging, Seems that the PMU doesn't charge just for 1-2%. So we can just use driver info to check if it is really charging, like this: # Battery info for Allwinner kernel 4.4+ axp_dir="/sys/power/axp_pmu" if [[ -e "$axp_dir" ]]; then status_battery_connected=$(cat $axp_dir/battery/connected) if [[ "$status_battery_connected" == "1" ]]; then status_battery_charging=$(cat $axp_dir/charger/charging) status_ac_connect=$(cat $axp_dir/ac/connected) battery_percent=$(cat $axp_dir/battery/capacity) # dispay charging / percentage if [[ "$status_ac_connect" == "1" && "$status_battery_charging" == "1" ]]; then status_battery_text=" charging" elif [[ "$status_ac_connect" == "1" && "$status_battery_charging" == "0" ]]; then status_battery_text=" charged" else status_battery_text=" discharging" fi fi fi Hope someone else finds it useful

Just +1 for armbian. I used bananian for over a year and it had very few releases with very few characteristics. And if you have a look at their bug tracker right now it looks like dead. On the other hand the guys at armbian are doing a huge job, frequent releases with bugfixes (this is of paramount importance to me) and new features. My hardware is also banana pi M1 and decission for armbian is absolutely clear.

I'm using a Banana Pi (first generation) + battery + updated vanilla kernel and it can run for months, just restart for installing new kernels or similar. I use it mainly for storage and media: Encrypted backups (ecryptfs), minidlna, samba, ssh, etc. I try to install or keep running as few things as possible and I have a script to detect "power cut" or "power back" which stops/starts all critical services, dismounts disks, etc (with this trick I can resist 1h power outage, until battery is very low and then I run a script for safe power off). Also my sdcard is one of the recommended models on this forum (samsung evo+ 32gb) From time to time I get sata errors on high writing operations (I guess is rather due to journalling+disk firmware than to the kernel itself) but never a critical error or lost data.

Are you root? you can do a backup with dd which is a tool usually included in all linuxes. But you need root or sudo to remove permissions problems, both for the filesystem on the card and for being able to read-write a boot sector

First guess... you must be member of group... I can't remember, I guess it will be netdev or similar. Just google for that, make your user part of that group and then maybe the issue is solved

Hi, My results: http://sprunge.us/KLWN Using the image provided for this test, no modifications Hardware: Banana pi M1 Card Samsung EVO+ 32 gb U1 Quick comment: could it be possible to make a script (e.g. testsd) with the command? I think I did it the right way but there is a risk of inputting the wrong parameters Hope it helps!

You were exactly looking for a compromised system?

I'm not quite sure about LXDE but some others desktop environment allow "auto login" but normally not for root. I don't know if autologin as root is possible... because I have never tried that. That is given the keys from your home to anyone, I strontly recommend never do that. Even on embebded at-home not-network systems

Boot as root to... hdmi screen? ssh?

Hi, I'm afraid this might not be the best place. Armbian, or rather the devices it runs on, requires some technical knowledge/linux background. If I were you I recommend using something like Debian, Ubuntu or Linux Mint (Mint is easy and similar to windows 7/Vista) in a standard PC. You can find plenty of tutorials on how to install / use them and most of the time you'll be working with a graphical interface. You are more than welcome to use armbian (after you have learned a bit of linux) but as a starting point... Honestly, I don't recommend it. Armbian is based on debian (also Ubuntu and Mint), so you can start by learning Debian or its derivatives and then give armbian a try. PS: You know that armbian can only run on soc devices, not in a standard PC, don't you?

Sure, try this link: www.google.com

Ecryptfs has been enabled by default. It was not compiled in previous versions I hope that together with sunxi_ss will do a great team

Do you have...? Alsa installed Analog jack selected as output device (by default can be hdmi) Device unmuted in alsa (some time it is muted by default) Kindly note that if you ask for something totally different than the title, you should open a new post. That will be useful for other users with the same problem

Maybe not very useful but banana pi M1 (I guess also other variants) is able to run on ac/battery. You just have to find the specs of the board you are interested in and check if it has a power charger chip and connections for battery. Or you can make a micro-usb connector for your battery and most of the boards will work. Power consumption will depend on the board and -what- is installed. So less services running = more battery

There is nothing wrong, Banana Pi and Pro share the same image (even if they have different hardware). If you are very pissed you can edit /etc(update-mot.d/10-header and look for a line toilet -f standard -F metal $(cat /var/run/machine.id) and change it to toilet -f standard -F metal "Banana" or, as I did, comment out the line and save space #toilet -f standard -F metal $(cat /var/run/machine.id)

Sorry if these pictures are misleading, let me explain: - First rework was removing the cover and placing at 90º - Second is adding alluminium heatsinks I'm missing a picture of 90º+heatsinks, that's why you see that the A20 is no heatsinked. But it really is (today)

Sorry, I forgot attachments

Hi, As a quick comment I'm also doing my best to keep my banana pi m1 cool. My tricks: - Buy a kit of heatsinks, I found kit with exact size for processor memory and pmu - Cut the full bottom of the acrilic case. Not just holes or lines, remove all of it (0 problems for heatsinks not fitting in between) - Instead of laying on the bottom, turn 90º and build "legs" (with foam). This will allow more are to be move by convection. And of course I had no other option: Sata and hdmi are on that side - Grooves on the heatsinks are aligned up-to-down to ease air flow I can't really tell the effect of the heatsinks (cheap stuff bought in china) but removing the bottom and turning to the side gave 10ºC less in hot days

I have armbian with kernel 4.4 and it works out of the box... 50%. If I use a Y connector (power from another USB and data from otg port) it works correctly. It is not a problem because I have USB power nearby and a stock Y cable, but it is not they way it is expected to work (In fact I was going crazy until I read in another post from Igor that port is not powered)

Hi, I had the same problem, tryed everything but the disk "keeps forgetting" apm params. The only solution (=patch) I could find is setting a cron job to re-record params every 10 minutes #!/bin/bash #hdparm -S starts disk, send only if already spinned up if /sbin/hdparm -C /dev/diskX | grep "active" > /dev/null; then /sbin/hdparm -S120 /dev/diskX touch /tmp/disksaving fi if /sbin/hdparm -C /dev/diskX | grep "standby" > /dev/null; then touch /tmp/disksaving fi /sbin/hdparm -B255 /dev/diskX touch /tmp/disksaving is a quick&dirty way to check last run

Thank you! I was driving crazy looking for that. Totally agree with blacklisting SS, specially when the maintainer is still looking for the cause behind data corruption

Hi All, My first topic here, I own a Banana Pi M1 and I have just switched from bananian. Everything looks great in armbian and most of the things are just working, I just miss zsh from bananian but that was easy to fix. However I use my server for backups using ecryptfs (so I can encrypt/decrypt folders on demand) and I'm unable to mount any ecryptfs directory. My configuration: Banana PI M1 running Debian Wheezy mainline kernel 4.4.3 (just installed) Things I've done: Install ecryptfs-utils (installs ok and tools are available) Try to mount a ecryptfs directory: I get the message "unknown filesystem type ecryptfs" Try to load as a module (just in case): modprobe ecryptfs = FATAL, module ecryptfs not found cat /boot/config-4.4.3-sunxi I can't find anything related to ecryptfs Also had a look at /proc/filesystems and ecryptfs is not there (should be automatically supported by kernel) lsmod reports sun4i_ss and fuse loaded (I thought it could be a problem related to sun4i_ss -security system cryptographic accelerator- I've read in the forums that ss is buggy) Any ideas? Anybody using ecryptfs?