Search the Community

Hello, First I would like to thank Igor for his amazing work on Armbian! I know that the Lamobo/BPI R1 is very problematic with power and SATA, but when I installed Armbian 5.1 jessie with the legacy kernel, it seems that the SATA is working fine. But when I tried the same Armbian 5.1 with vanilla kernel it wasn't able to boot and the hard drive made knocking noises. Just to make sure, I disconnected the HD and it booted fine. I think that this is a software problem (maybe uboot?) because as I mentioned it works with the older kernel. I tried installing the uboot package bananapro-next as Igor adviced someone with a banana pro but it didn't help. I'm using a good 2A power adapter and a quality cable so I guess that solves the hardware side of the problem. I would really like to have the newer kernel with Docker support because I want to be able to run Docker containers. Any ideas about the software side? Thank in advance.

Hi! Using Jessie, I made the mistake of running apt-get upgrade => and on the next reboot by R1 did not boot anymore. I can chroot into the image (using qemu-arm-static) but have absolutely no clue what went wrong: Checking my dpkg.log, I found that the kernel seems not have been updated? root@asterix:/var/log# grep 05-10.*linux dpkg.log 2016-05-10 18:22:02 upgrade linux-libc-dev:armhf 3.16.7-ckt20-1+deb8u3 3.16.7-ckt25-2 2016-05-10 18:22:02 status half-configured linux-libc-dev:armhf 3.16.7-ckt20-1+deb8u3 2016-05-10 18:22:02 status unpacked linux-libc-dev:armhf 3.16.7-ckt20-1+deb8u3 2016-05-10 18:22:02 status half-installed linux-libc-dev:armhf 3.16.7-ckt20-1+deb8u3 2016-05-10 18:22:10 status half-installed linux-libc-dev:armhf 3.16.7-ckt20-1+deb8u3 2016-05-10 18:22:10 status unpacked linux-libc-dev:armhf 3.16.7-ckt25-2 2016-05-10 18:22:10 status unpacked linux-libc-dev:armhf 3.16.7-ckt25-2 2016-05-10 18:25:55 upgrade linux-dtb-next-sunxi:armhf 4.70 5.10 2016-05-10 18:25:55 status half-configured linux-dtb-next-sunxi:armhf 4.70 2016-05-10 18:25:56 status unpacked linux-dtb-next-sunxi:armhf 4.70 2016-05-10 18:25:56 status half-installed linux-dtb-next-sunxi:armhf 4.70 2016-05-10 18:25:56 status half-installed linux-dtb-next-sunxi:armhf 4.70 2016-05-10 18:25:57 status unpacked linux-dtb-next-sunxi:armhf 5.10 2016-05-10 18:25:57 status unpacked linux-dtb-next-sunxi:armhf 5.10 2016-05-10 18:25:57 upgrade linux-firmware-image-next-sunxi:armhf 4.70 5.10 2016-05-10 18:25:57 status half-configured linux-firmware-image-next-sunxi:armhf 4.70 2016-05-10 18:25:57 status unpacked linux-firmware-image-next-sunxi:armhf 4.70 2016-05-10 18:25:57 status half-installed linux-firmware-image-next-sunxi:armhf 4.70 2016-05-10 18:25:57 status half-installed linux-firmware-image-next-sunxi:armhf 4.70 2016-05-10 18:25:58 status unpacked linux-firmware-image-next-sunxi:armhf 5.10 2016-05-10 18:25:58 status unpacked linux-firmware-image-next-sunxi:armhf 5.10 2016-05-10 18:25:58 upgrade linux-headers-next-sunxi:armhf 4.70 5.10 2016-05-10 18:25:58 status half-configured linux-headers-next-sunxi:armhf 4.70 2016-05-10 18:25:58 status unpacked linux-headers-next-sunxi:armhf 4.70 2016-05-10 18:25:58 status half-installed linux-headers-next-sunxi:armhf 4.70 2016-05-10 18:27:34 status half-installed linux-headers-next-sunxi:armhf 4.70 2016-05-10 18:29:24 status unpacked linux-headers-next-sunxi:armhf 5.10 2016-05-10 18:29:24 status unpacked linux-headers-next-sunxi:armhf 5.10 2016-05-10 18:29:25 upgrade linux-image-next-sunxi:armhf 4.70 5.10 2016-05-10 18:29:25 status half-configured linux-image-next-sunxi:armhf 4.70 2016-05-10 18:29:25 status unpacked linux-image-next-sunxi:armhf 4.70 2016-05-10 18:29:25 status half-installed linux-image-next-sunxi:armhf 4.70 2016-05-10 18:29:44 status half-installed linux-image-next-sunxi:armhf 4.70 2016-05-10 18:29:46 status unpacked linux-image-next-sunxi:armhf 5.10 2016-05-10 18:29:46 status unpacked linux-image-next-sunxi:armhf 5.10 2016-05-10 18:29:46 upgrade linux-jessie-root-next-bananapi:armhf 4.70 5.00 2016-05-10 18:29:46 status half-configured linux-jessie-root-next-bananapi:armhf 4.70 2016-05-10 18:29:46 status unpacked linux-jessie-root-next-bananapi:armhf 4.70 2016-05-10 18:29:46 status half-installed linux-jessie-root-next-bananapi:armhf 4.70 2016-05-10 18:29:48 status half-installed linux-jessie-root-next-bananapi:armhf 4.70 2016-05-10 18:29:48 status unpacked linux-jessie-root-next-bananapi:armhf 5.00 2016-05-10 18:29:48 status unpacked linux-jessie-root-next-bananapi:armhf 5.00 2016-05-10 18:30:21 configure linux-libc-dev:armhf 3.16.7-ckt25-2 <none> 2016-05-10 18:30:21 status unpacked linux-libc-dev:armhf 3.16.7-ckt25-2 2016-05-10 18:30:21 status half-configured linux-libc-dev:armhf 3.16.7-ckt25-2 2016-05-10 18:30:21 status installed linux-libc-dev:armhf 3.16.7-ckt25-2 2016-05-10 18:31:49 configure linux-dtb-next-sunxi:armhf 5.10 <none> 2016-05-10 18:31:49 status unpacked linux-dtb-next-sunxi:armhf 5.10 2016-05-10 18:31:49 status half-configured linux-dtb-next-sunxi:armhf 5.10 2016-05-10 18:31:49 status installed linux-dtb-next-sunxi:armhf 5.10 2016-05-10 18:31:49 configure linux-firmware-image-next-sunxi:armhf 5.10 <none> 2016-05-10 18:31:49 status unpacked linux-firmware-image-next-sunxi:armhf 5.10 2016-05-10 18:31:49 status half-configured linux-firmware-image-next-sunxi:armhf 5.10 2016-05-10 18:31:49 status installed linux-firmware-image-next-sunxi:armhf 5.10 2016-05-10 18:31:49 configure linux-headers-next-sunxi:armhf 5.10 <none> 2016-05-10 18:31:49 status unpacked linux-headers-next-sunxi:armhf 5.10 2016-05-10 18:31:49 status half-configured linux-headers-next-sunxi:armhf 5.10 2016-05-10 18:33:18 status installed linux-headers-next-sunxi:armhf 5.10 2016-05-10 18:33:19 configure linux-image-next-sunxi:armhf 5.10 <none> 2016-05-10 18:33:19 status unpacked linux-image-next-sunxi:armhf 5.10 2016-05-10 18:33:19 status half-configured linux-image-next-sunxi:armhf 5.10 2016-05-10 18:33:19 status installed linux-image-next-sunxi:armhf 5.10 2016-05-10 18:33:19 configure linux-jessie-root-next-bananapi:armhf 5.00 <none> 2016-05-10 18:33:19 status unpacked linux-jessie-root-next-bananapi:armhf 5.00 2016-05-10 18:33:19 status half-configured linux-jessie-root-next-bananapi:armhf 5.00 2016-05-10 18:33:20 status installed linux-jessie-root-next-bananapi:armhf 5.00

Hello. I'm having trouble with infrared receiver. Whether the sunxi_cir driver installed in kernel or not, there is nothing in /dev/input except "event0", which is the power controller. Dmesg doesn't show anything neither. Version: Armbian 4.5 Lamobo-r1 Debian jessie next (unofficial), kernel 4.2.3. IR support was declared on download web page, so I decided to get vanilla kernel. That's because I had already tried Bananian with 3.18 kernel, and there were huge problems with kernel ppp (up to freezes of whole device). Has anybody encountered this problem?

LED link on WAN port ON when disconnect cable link ( not change to OFF, always ON). Help me how to fix the problem

hi there, just created the account to report what i experienced with my r1. unfortunately i had a bunch of changes w/o reboot so i only can estimate what caused the gap but im pretty sure it was at least the fact that i changed to the /etc/network/interfaces.r1router cfg before i rebooted from do-release-upgrade to xenial (install image has been the recent trusty of today). that was when i couldnt even ping my banana from any other box in my home net. have to say im with the german telekom which provides ipv6 in a dual stack manor. i saw on the pi console that it got the exspected ipv4, but also ipv6 addresses by telekom speedport dhcp. nevertheless from my other box it looked like that there has not been another ipv4 computer on that address while i could see on the pi cli it had been assigned ... i connected from the other box by using an ipv6 i read on tty of the banana which succeeded. after all my quick'n dirty solution was to follow this guide to simply disable ipv6, after reboot ipv4 ssh from other boxes was working again. this brought me to the conclusion i indeed have to deal with ipv6 conversion of my personality - but have mercy - not today but i thought this information could be usefull for you since i appreciate your work. cheers ...

Hello I have a BPi-R1 with Igor's 3.2 image (http://www.igorpecovnik.com/2014/09/07/banana-pi-debian-sd-image/) that runs as a router (with pppoe) and nginx/php5/mysql config for my wife's blog and also with ez-ipupdate for dynamic dns I have a nasty issue... once every 2 or 3 days, my board freezes for no aparent reason It does this even if root is on SD card (only sd card connected) or HDD (I have a modified mSATA adapter to get power from 3,3V SATA power connector... I removed the 3,3V regulator and added a thick wire from the 3,3V provided by the board through the SATA connector) Also I moved from this configuration: to this fan gpio controlled (witch was very noisy): ending up with this one (no fan control): So the system is cooled by the 12v fan powered at 5v, with soctemp reporting 34,7 degrees, and pmutemp reporting 41 degrees Also the power source is stable (I had a script that monitored the voltage before it freezed... it never dropped below 5,09V) I already tested with wireless power management disabled by command (added in rc.local too) echo 0 > /sys/module/8192cu/parameters/rtw_power_mgnt since adding this line to a file named /etc/modprobe.d/8192cu.conf doesn't work options 8192cu rtw_power_mgnt=0 rtw_enusbss=0 Even with the power management for the wireless disabled it happened once again. Also, looking at the ethernet leds on the BPi-R1, every time the freeze happenes these leds are flashing like there is activity. I took a look at the logs and I found something that could be the cause for this: In cron i have a line set for php [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean I found for the last few freeze times that in syslog this was the last event. Earlier events had DHCP event on last lines before freeze I read about some Out Of Memory issues with this script. Could it be that this is what is actually happening to my system? For now I removed the comment for swap in /etc/fstab /var/swap none swap sw 0 0 and I added in /etc/sysctl.conf vm.swappiness=0 (this was the last line in the file) vm.overcommit_memory = 2 vm.overcommit_ratio = 100 I'm stabbing things in the dark here so if anybody could help please do...

Hi, Was anyone able to use the watchdog in the Lamobo/banana pi r1? If not is anyone using some hardware that resets it/an hardware watchdog?

Hi All, I have R1 issue again. After lot of experiments and tuning, I decided try to use R1 for real routing :-) It means dual WAN, lot of VLANs, thousands connections, traffic shaping etc. Everything worked well, until yesterday. As whole Europe has real summer these days, working temperature of my R1 is around 30 celsius. I experienced strange issues when traffic is very high. This happen approx. twice a day. System was not restarted, but PPPOE goes down, kernel reinitialize some hardware and everything continues well. Outage is several seconds only. I have to say, that I'm using OpenWrt for this application, but the system is well patched and worked without problems up to now. So I have suspect that a hardware is overheated. Which part it can be? CPU or switch? Has somebody similar experience? I'm trying another board with CPU aluminium cooler, I will post results here. Any idea is welcome. Petr

Good day all. Anyone having issues of not able to see anything after "Uncompressing Linux... done, booting the kernel." via serial console on Lamobo R1 ? Tried to experiment a bit, it seems that U-Boot works correctly, but in Linux kernel, sent data from USB-serial to ttyS0 arriving correctly, but anything written to ttyS0 is not visible on connected USB-serial adapter.

Hello, I just upgraded my system from 3.4.110 to the kernel 4.4.1 (Debian7) by Igor's script (Thanks Igor). But I have noticed that in this version of the kernel is no longer possible to set the green light to the disk activity. Is there a way, patch or other to fix it? Thanks Fred

Hi, to resume the problem I encounter please let me introduce the network I use. 1) a main modem/router called BBox2 which is a Sagem F@st 3464 connected in LAN-WAN to a 2) a secondary router called Lamobo R1 (also named Banana Pi R1 = BPi R1) 3) a laptop connected to the BPi-R1 4) I think to connect IP camera to the BBox2 then need to stay in the same network range (so I presume I need to change the conneciton used in 1) from LAN-WAN to LAN-LAN isn't it ?) Here is the connections and IP Addresses : BBox2 is connected in LAN-WAN to the BPi-R1 ISP -> BBox2 (LAN) -> (WAN) BPi-R1 (LAN) -> (LAN) Laptop 192.168.1.1 (DHCP->) 192.168.1.2 .............. 192.168.1.3 (manually set because BPi-R1 did give a dynamic IP) All HW use the subnet mask 255.255.255.0 ---------------------------------------------------------------------------------- BBox2 gave an IP to the BPi-R1 because it has DHCP activated. BPi-R1 did not gave a dynamic IP to the laptop then Laptop got a manual static IP address Laptop can ping BPi-R1 at 192.168.1.2 but can not pint the BBox2 at 192.168.1.1 even if it has the IP 192.168.1.1 BPi-R1 can ping both BBox2 and Laptop It seems then that the laptop can not passthrough the BPi-R1. ---------------------------------------------------------------------------------- Questions : 1) by considering the fact I will need to connect the IP camera connected to the BBox2 (at 192.168.1.1) thanks to confirm I will need to use LAN-LAN connection in place of LAN-WAN connection between the BBox2 and BPi-R1 2) how could I set the BPi-R1 to tell it it must give a dynamic IP address (coming from it or coming from BBox2) ? 3) how to be sure it will passthrough the BPi-R1 to go through BBox2 to internet ? Sincerely thanks and have a nice day. Miguipda ;-)

Please, help me how to config Lamobo-R1 with Lan USB QF9700. I need eth0, eth1 with command ifconfig. a) Plug USB QF9700 and reboot : ifconfig show only eth0 with mac address as Lan USB QF9700 Remove USB QF9700 and reboot : ifconfig show only eth0 with mac address as WAN I need two interface eth0 and eth1 for ( WAN and USB QF9700 ) work in command ifconfig. Best regards, CVH

Hi, I just saw ARMBian has been upgraded to 5.00 version. Then I though to check if my initial problem (for my first ARMBian test with the previous 4.5 version) could be solved with this new version : http://forum.armbian.com/index.php/topic/616-lamobo-bpi-r1-network-issue-sudden-reboot-quick-usb-uart-how-to/?hl=miguipda What I encounter now with the 5.0 is a Lamobo R1 seems stable because no blinking green led. Just keep the red led switched on and wan with lan usable (I may contact website like you now ;-) ). Even with the connected harddrive. But... As my modem has the IP 192.168.1.1 and says that two IP are distributed with DHCP I saw the 192.168.1.4 is my computer IP but when I try to ping the 192.168.1.2 (that could only be the Lamobo R1) I got an IP unreachable error. Then why the router seems to get an IP (192.168.1.2) and can contact the modem and allow a computer to access internet if it could not be reachable by a simple ping then access it with a SSH ? How could I get the real received (Lamobo R1) IP address (if a simple ping 192.168.1.2 could not answer) ? Sincerely thanks.

Hi, after unsuccessful experiences with bananian I found armbian - due to the active forum and answers to questions it looks like the better choice. I try to install fhem on bpr-r1. Combine a access point with homeautomation server (the router ifunction is handled by another device). After some work with Debian Jessie (lot´s of issues with hostapd and gpio) - Ubuntu with 4.4.1 kernel works stable. Only issue which keeps me from going into operation is following problem: all directories /sys/devices/platform/gpio-sunxi/gpio/gpio* are recreated everytime fhem server starts. The trick from Raspbian with chown -R root:gpio ys/devices/platform/gpio-sunxi/gpio/gpio* is not working, due to recreation. The effect is, that attributes like "active_low" are not working, behaus fhem cannot modify them because of missing access rights. Running fhem as root is not an option. I know for sure, this is not a fhem problem. Some device definition is working fine on 2 RaspberryPis. Where is the place I can tell the system do recreate gpio-subdirectories with user:group = root:gpio as well as 775 as access rights? Greetings Harald

How can view kernel version?

Hi all, i got the problem, that my Banana Pi doesn't boot. I receive the error Unknown command 'U-Boot' - try 'help' This is similar while try use openwrt, bananaian or ip-fire. Did i brick my PI? Can i do something? Thanks BigChris

First of all: my compliments to the staff of armbian for the important work done. I bought some lamobo r1 boards to use in a production environment such as (open)vpn router to realize a tele-service with PLC. I installed bananian (the first distro that I found on internet) but after a week I switched to armbian trying to create my own image from scratch. Very well, I like to have control over things. The question is: I should connect a lipo battery to the board so that when the main power goes off a daemon script syncs sd and then shutdown, but when the main power is reconnected the board must do a reboot automatically. It is possible to do this? Where should my daemon script look under /sys ? I already tried to connect a lipo battery but I burned a board (maybe it was already broken, or maybe I wrong the polarity). With my tester on a new board I found that the battery connector has + inward and - to the outside, but I would like to know, before burning another board, if anyone has actually tried to connect a lipo battery. My battery is minimal, 3.7V 600mAh. greetings Giorgio

Hi, Finally SinoVoip /Foxconn released the schematic for the Lamobo R1 (R1-V3_SD July 18, 2014). First page a blockdiagramm and 13 pages of schematics as PDF. May be because the next Version of the R1 is soon ready?? Cheers Tido

Hi, as I need to use an OS allowing me to have Cozy and Gladys (both node.js) on my router (using them it as server) I tried to use armbian for the first time. I sucessfully installed armbian on a SD Card and boot it. My BPi-R1 is not connected to a display or other periherals (keyboard / mouse). Because I do not have those materials I sold them. It is just connected with RJ45 and has a HDD connected on the SATA port. I then connected my modem RJ45 connector to my BPi-R1 on the WAN port. I connected my computer on the first port (near the WAN one). I saw my laptop do not get an IP certainly due to the fact that LAN port seems to be manually activated. Because I just now read your text telling that : "BCM53125 switch configured as follows – looking at front of ports: |2|1|0|4|(LAN=manual) |3|(WAN=dhcp and bridged to enabled wireless adapter in (theoretical) high throughput mode with SSID lamobo and password 12345678" Then if I do not get automatically an IP on my computer how could I manually configure it ? It has no sense to activate it manually if I can at least not access the router through my LAN ports. Ecxept if I must I do it by using wifi ? Sincerely thanks and have a nice day. Miguipda ;-) P.S. : I used the Legacy version

Hello and thanks for the good work and support with these images. First, excuse my bad english, it's not my native. And i am a little rookie and a little noob, so sorry if i write crap and don't understand basics some time. Recently i've try to install desktop on this board and hardware accelerated driver with partial result. I had Armbian_4.5_Lamobo-r1_Debian_wheezy_3.4.109 with installed Gnome. I install Gnome following this site: https://www.namhuy.net/1085/install-gui-on-debian-7-wheezy.html Then i started to install and configure stuff based on sunxi site. First libUMP tnen this: http://linux-sunxi.org/Mali_binary_driver "make test" didn't do anything - can't create a test or something. Then i do this: http://linux-sunxi.org/Xorg#fbturbo_driver in log i had the same: but i also notice the following in Xorg.0.log: Aaaand my odyssey begin. I notice the second parameter is defined in boot.scr file. There where other parameters too, preventing 2Dand 3D acceleration - "sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16". I notice the following lines are not present in version - Armbian_4.5_Lamobo-r1_Ubuntu_trusty_3.4.109_desktop (why i am not using this version - long story), so i follow this description: http://linux-sunxi.org/Display#boot.scr edit boot.cmd file and create new boot.scr without these lines and reboot then try to install Gnome (i do this on fresh installation). The problem is - i don't know if i am cursed or this @#%^&%* board is cursed, but from the site maintenance yesterday i am unable to install Gnome anymore, no mater content of boot.scr file. At first i thought this is the problem but it appears to be something with apt-get because once i received the following error - apt-get error (100) or something similar. Tasksel freeze at around 55%, i try "apt-get install gnome" it freeze at some point too. I don't know what log to loot at, i couldn't find anything related to apt-get or aptitude in /var/log/ . I even try older images where i used to install the same desktop before and the result is the same. This is my major problem right now, because instead of going forward i am way beyond the start line at the moment. About the first thing about FBTURBO(0) in Xorg0.log i understand this parameter is in script.bin which is not so easy to edit, but i am defiant... I install libusb-1.0-0-dev and use this guide to modify the file: http://docs.cubieboard.org/tutorials/common/edit_the_system_configuration But i notice script.bin in this board is a simlink to /bin/lamobo-r1.bin so i edited this file and change parameter - fb0_framebuffer_num, from 2 to 3. And by the way i am using nano instead of vi because me and vi are old enemies and every time i risk and using it result in disastrous results - in this case - boot loop or various problems before boot. The problem is, after i change parameter from 2 to 3 (with nano) and reboot system is unable to load desktop anymore if i do this after i installed one. If i try to install desktop with this parameter enabled i can't startx later (and it can't autoload too). I have to make fresh install again. Sorry for the long post. What am i doing wrong so i can't install desktop environment? And why setting framebuffer to 3 causing troubles when it's recommended value in sunxi site: http://linux-sunxi.org/Display#boot.scr

As tkaiser would say, Lamobo-r1 has terrible design but the concept is good (multiple usage possible: network, misc services) But let's be honest, perfection is when you are dead. Like sleeping & coffee some weeks ago, I was wondering (right or wrong) if a DMA config for the lamobo-r1 GMAC would help the bandwidth issues. One CPU core is 100% with all the gazillions of interruptions to handle. Now the DMA for A20 is in the mainline kernel but I am missing some tech glue. I have read an example in the kernel 4.3 doc with DMA config (DTS) for DWMAC (*if* applicable, not only for STMMAC, but also for A20-GMAC ???) links: I have tried the recipe provided by the lamobo-r1 openwrt support crew, fifo buffer is not enough, also the code between 4.1 - 4.3 has changed for the STMMAC, patch is not portable, I have tried the coe/roe fix with no luck. links: At least, I was able to set the clock @1GHz, the cpu handling all the interruption, some small BW gain work (CPU is able to handle more interruptions). if I could get a hand on the possible DTS (uboot?kernel?) DWMAC DMA glue as in the kernel example (no link @ hand for now, see later) http://lxr.free-electrons.com/source/Documentation/devicetree/bindings/net/stmmac.txt patchs to look at:

Hello, I am using for the first time a cable Neuftech PL2303HX I was looking @ lamobo-r1.fex file and cannot figure out which pins are the default uart for boot-up (not skilled enough yet) both links mention P13 as default, but I cannot get any messages from USB-uart cable (double checked UART RX & TX + ground) http://linux-sunxi.org/Lamobo_R1 http://www.bananapi.com/index.php/component/content/article?layout=edit&id=59 Thanks!

Hello, with 3.4. kernel I could use my csi-cam on my R1: #5.0 Mega Pixel Banana PI Camera Module for Android #and Linux. OV5640 chipset, CSI connector #Price: US $24.00 / piece from aliexpress sudo modprobe ov5640 sudo modprobe sun4i_csi0 #video stream #mplayer tv:// #snapshot mplayer tv:// -vo png -frames 1 Now I switched to armbian 4.7 with 4.2.6 to use new wifi-usb-drivers but I saw that those modules are not supported in the new kernel. :-( Source of drivers: https://github.com/LeMaker/linux-sunxi/tree/lemaker-3.4/drivers/media/video/sun4i_csi https://github.com/LeMaker/linux-sunxi/blob/lemaker-3.4/drivers/media/video/sun4i_csi/device/ov5640.c Did anyone got this to work with 4.x-kernel? Is there a chance that it will/could be integrated in mainline-based Armbian? regards

Hello, I have been looking for days without finding an answer, so here goes. I want to know if there is a way of turning on the banana pi, without using the onboard switch. Because the Banana pi r1 doesn't power on automatically when powered by the battery connector. And i don't want to solder wires on the pwr button, but i would also like to avoid using the usb connections because of the lower power throughput. Thank you in advance for the information.

Hello, I just received a replacement unit of my Lamobo-R1 board and I'd like to test it with an SD card I've currently running on a BananaPro with the latest Armbian release. Is there a way to use it on the Lamobo-R1 without having to reinstall & reconfigure everything? Thanks, V.