Search the Community

Hi there, I am trying to download the lime2 legacy image : https://www.armbian.com/olimex-lime-2/#kernels-archive But the link is dead (error 404). Any chance to get this back up? Or can I use another legacy image and just change the script.bin or is there other things to modify? Thanks Edit : I just found the image on olimex website : ftp://staging.olimex.com/Allwinner_Images/A20-OLinuXino/2.legacy_images_kernel_3.4.x/

Hello, I configured 2 armbian on sd card and the configuration of the i2c is the same in armbianEnv.txt. Plattform Olimex-Lime2 A20 verbosity=1 logo=disabled console=both disp_mode=1280x1024p50 overlay_prefix=sun7i-a20 rootdev=UUID=194e9f9a-826b-4644-9f2f-4ef388277816 rootfstype=ext4 overlays=i2c1 i2c2 uart3 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u as you see, I confiugred the overlays. But on one image I get: #image with desktop sudo i2cdetect -l i2c-3 i2c mv64xxx_i2c adapter I2C adapter i2c-1 i2c mv64xxx_i2c adapter I2C adapter i2c-2 i2c mv64xxx_i2c adapter I2C adapter and booting the other image I get # headless image sudo i2cdetect -l i2c-3 i2c mv64xxx_i2c adapter I2C adapter i2c-1 i2c mv64xxx_i2c adapter I2C adapter i2c-2 i2c mv64xxx_i2c adapter I2C adapter i2c-0 i2c sun4i_hdmi_i2c adapter I2C adapter so I get an aditional device for i2c-0. I don't understand what's happening. What could cause this effect? Or better: What must happen, that the i2c-0 does not appear in the list. One more info: The first image has a runing desktop and the second one in headless. Maybe this has something to do with the issue? Can someone give me a pointer to understand this. Btw. both versions work perfekt: i2cdetect -y 2 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: 20 21 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- i2cdetect -y 3 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: 20 21 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- The 0x68 is a RTC which is configured. So everything is OK, but I drives me crazy not to understand what I've done "wrong". Can someone give me a pointer? Thanks for all help.

Hi all! I have an Olimex Olinuxino-Lime2-4GB A10 cpu based dev board and I have installed Armbian on an SD card. Everything works fine, except when trying to compile some drivers for the wifi dongle that I want to use. The dongle has an RTL8188CUS chip, and I also have another dongle with an RTL8192CU chip, and when following the instructions found here the compilation fails, because of the kernel headers missing. The instructions work fine on other distributions. Could someone help me figure out how to successfully compile the drivers? Where can I get the kernel headers? I really need these drivers for my project.

Hi! I've been using Armbian on my a20 olinuxino lime2 board without issues for over a year now. Yesterday i decided to reflash the installation image onto the SD board. I've tried to flash it to different SD cards using the same method (SD card formatter + etcher), all of them booted but the SSH server always refuses the connection. Are there any workarounds to this?

Hi, I'm testing the new Rev.K board and facing troubles with uplink performance. Downlink is ok. I already asked on Olymex forum but no response so far. $ iperf3 -c 192.168.0.110 Connecting to host 192.168.0.110, port 5201 [ 4] local 192.168.0.104 port 45700 connected to 192.168.0.110 port 5201 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.00 sec 3.59 MBytes 30.1 Mbits/sec 708 4.24 KBytes [ 4] 1.00-2.00 sec 4.14 MBytes 34.8 Mbits/sec 964 2.83 KBytes [ 4] 2.00-3.00 sec 4.19 MBytes 35.1 Mbits/sec 956 2.83 KBytes [ 4] 3.00-4.00 sec 4.16 MBytes 34.9 Mbits/sec 944 2.83 KBytes [ 4] 4.00-5.00 sec 4.02 MBytes 33.7 Mbits/sec 925 5.66 KBytes [ 4] 5.00-6.00 sec 3.03 MBytes 25.4 Mbits/sec 605 2.83 KBytes [ 4] 6.00-7.00 sec 4.02 MBytes 33.7 Mbits/sec 904 2.83 KBytes [ 4] 7.00-8.00 sec 3.87 MBytes 32.4 Mbits/sec 859 2.83 KBytes [ 4] 8.00-9.00 sec 4.08 MBytes 34.2 Mbits/sec 928 2.83 KBytes [ 4] 9.00-10.00 sec 4.14 MBytes 34.7 Mbits/sec 955 2.83 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 39.2 MBytes 32.9 Mbits/sec 8748 sender [ 4] 0.00-10.00 sec 39.2 MBytes 32.9 Mbits/sec receiver Downlink: $ iperf3 -c 192.168.0.110 -R Connecting to host 192.168.0.110, port 5201 Reverse mode, remote host 192.168.0.110 is sending [ 4] local 192.168.0.104 port 45704 connected to 192.168.0.110 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 106 MBytes 890 Mbits/sec [ 4] 1.00-2.00 sec 109 MBytes 915 Mbits/sec [ 4] 2.00-3.00 sec 111 MBytes 934 Mbits/sec [ 4] 3.00-4.00 sec 111 MBytes 935 Mbits/sec [ 4] 4.00-5.00 sec 111 MBytes 934 Mbits/sec [ 4] 5.00-6.00 sec 111 MBytes 935 Mbits/sec [ 4] 6.00-7.00 sec 111 MBytes 934 Mbits/sec [ 4] 7.00-8.00 sec 111 MBytes 934 Mbits/sec [ 4] 8.00-9.00 sec 111 MBytes 935 Mbits/sec [ 4] 9.00-10.00 sec 111 MBytes 934 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 1.08 GBytes 931 Mbits/sec 37 sender [ 4] 0.00-10.00 sec 1.08 GBytes 928 Mbits/sec The same behavior is repeatable with the official Olimex firmware release #115, with Armbian Stretch and with Buildroot (fixed u-boot 2018.09, CONFIG_GMAC_TX_DELAY=4). Did anyone face the same issue?

Hello, I have an image based on Armbian 5.37 and I have noticed that after upgrading linux-jessie-root-lime2 from 5.37 to 5.60, the Lime2 was not able to get an IP for eth0. The only way is to execute dhclient eth0 I have noticed that a lot of file was added in linux-jessie-root-lime2_5.60_armhf/data/usr/lib/armbian and I think that one of them are responsible of this issue. Do you have any idea on how to fix that ? Thanks

Good day, I use prebuild Armbian Stretch mainline kernel 4.14.y. And I want to connect pcf8563 rtc through i2c protocol on TWI1_SCK/PB18, TWI1_SDA/PB19 hw A20 pins. pcf8563 slave address is 0x51. If by default, no i2c are enabled through overlays= in armbianEnv.txt, I still get i2c-1 device with addresses 0x51-0x57 occupied: root@lime2:~# ls /dev | grep i2c i2c-0 i2c-1 root@lime2:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- root@lime2:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 50: UU UU UU UU UU UU UU UU -- -- -- -- -- -- -- -- If I enable i2c1 through overlays=i2c1 in armbianEnv.txt, i2c-0 disappears from /dev/ and axp209 is now mapped on i2c-2: root@lime2:~# ls /dev | grep i2c i2c-1 i2c-2 root@lime2:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 50: UU UU UU UU UU UU UU UU -- -- -- -- -- -- -- -- root@lime2:~# i2cdetect -y 2 0 1 2 3 4 5 6 7 8 9 a b c d e f 30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- Please advice, how to free up slave address 0x51 on i2c1? Additional info with i2c1 enabled: root@lime2:/# ls /sys/bus/i2c/devices/ 1-0050 1-0051 1-0052 1-0053 1-0054 1-0055 1-0056 1-0057 2-0034 i2c-1 i2c-2 root@lime2:/# cat /sys/bus/i2c/devices/1-0051/modalias i2c:dummy root@lime2:/# grep dummy /lib/modules/4.14.65-sunxi/modules.alias alias rtnl-link-dummy dummy root@lime2:/# rmmod rtnl-link-dummy rmmod: ERROR: Module rtnl_link_dummy is not currently loaded root@lime2:/# dmesg | grep dummy [ 1.063542] ldo1: supplied by regulator-dummy [ 1.063827] ldo2: supplied by regulator-dummy [ 1.064960] ldo3: supplied by regulator-dummy [ 1.065662] ldo4: supplied by regulator-dummy [ 1.065854] ldo5: supplied by regulator-dummy [ 1.066504] dcdc2: supplied by regulator-dummy [ 1.067189] dcdc3: supplied by regulator-dummy [ 1.398296] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found, using dummy regulator

I recently ordered 3 A20-OLinuXino-LIME2-e16GB devices (with 16GB eMMC) and received rev. K boards. Unfortunately, I have troubles with both "official" Olimex eMMC rel 16 image and latest (as of last week) Armbian Stretch images. Both images booted fine from SD card (also tried multiple SD cards, one of them bought from Olimex ) and I was able to run the emmc.sh / nand-sata-install scripts fine. Now the troubles started as I turned off the device, removed the sd-card and tried to boot from eMMC. All 3 boards had entered FEL mode. From fel mode I was able to use the `sunxi-fel` utility and push the uboot fine... Initially I was able to get Olimex's images to work by removing the power by yanking the cord instead of doing proper shutdown, but this only allowed me to boot the board from eMMC single time after install. I have tried different power supplies and SD cards. Any ideas what else to try?

Hi guys! I have some trouble with my Lime 2. My original setup: Armbian 5.38 +4.14.18-sunxi software installed: Pihole V3.0 with dnsmasq dhcp enabled. SD : a fresh Samsung Micro SDHC 32GB EVO power-supply : a 5V power-supply adaptor Current behaviour: After [1~4] days the my board disapear of my network. With dnsmasq dhcp server disabled, there are no problème. My guess: their are some troubles between the dhcp and Armbian. Indeed in tried to setup a isc-dhcp-server to remplace the Pihole dhcp without success. (Same behaviour) You could see my search on Pihole forum here After my vacation, i will test the olimex's image with pihole. However this return to Jessi and a 3.4 sunxi kernel, doesn't enjoy me.

I have device named "atol hub-19" with A20, runs on old 3.4 kernel (fex based system configuration) ... there is a way to do convert .fex to dt ? I used Armbian_5.59_Lime2_Ubuntu_xenial_default_3.4.113_desktop.img and change script.bin... and the device works fine

Hi all, as in title, gpio not work on latest Lime2 5.59 built from source using mainline 4.14.70 kernel and debian stretch. I can export correctly the gpios in sysfs but i cant get the right value. They always remain the same value. I've tried both pulled up and internal pulled up (active low) gpios with the same result. Also gpio buttons defined in dtc do not work. Any idea?

Hello, First of all, please understand that I am a beginner level. My project is to make a NextcloudPlus on a Lime2 NAND version because of the following reasons : - Lime2 is Open source board, so no third party code into it - NAND version because I don't want to rely on a micro SD card, as it can be unstable for too many read/write (NextcloudPlus indexes a lot with sync). - SATA version because I would like to store data through a SATA HDD (I feel it is more stable than USB). So, I have tried to make : nand-sata-install ...but after shutting down and removing the micro SD cart, it was impossible to boot from NAND (the board doesn't even boot). I have tried to understand why on the doc/forum/etc., but it is difficult due to my beginner skills. My question is simple : can somebody please summarize a step-by-step guide to install armbian and be able to boot from NAND ? Which version to download (to boot on NAND and have SATA support), and what to do ? Thank you very much for your help.

Hi Guys, I wanted a debian stretch based OS, and I followed Olimex consideration on Armbian. The I visited the Page of Lime2( not nand or emmc): https://www.armbian.com/olimex-lime-2/ The stretch Image that is there...is configured to boot from emmc :( I want a debian stretch based version. I checked sha256 checksums OK. Serial Debug Output: U-Boot SPL 2017.11-armbian (Jan 25 2018 - 01:01:01) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 mmc_init: -110, time 37 spl: mmc init failed with error: -110 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### How can I solve this situation? can I write a new uboot version? how to do it on Armbian_5.38_Lime2_Debian_stretch_next_4.14.14.img image? thanks in advance. Best Regards tux

Hi all, I've been using the A20-Lime2 together with Armbian for about two years now and I love the effort that the developers and the community have put into this amazing product. Until not too long ago I was on Debian 8 (jessie) on the legacy kernel for webcam compatibility reasons (after having tried switching to mainline from time to time). With the release of Debian 9 I finally had everything that I was looking for in the mainline kernel so I decided to upgrade to Debian 9 and then switch to the mainline kernel. I'm currently on ARMBIAN 5.38 stable with 4.14.15-sunxi and just had to force a reboot. The server I'm running is mainly a webserver, emailserver and home monitoring server (webcam). It also sends me things worth looking into periodically to email using logcheck. I'm no expert by any stretch of the imagination and consider myself more of a linux enthusiast with some basic knowledge and a lot of patience to research and experiment. Since my upgrade to stretch and mainline kernel I've noticed sporadic freezes (which brings back memories of years ago with power supply, before changing my setup). I believe it may have something to do with mysql and/or php-fpm consuming a lot of memory. Logcheck warns me of a kernel panic from time to time and forces a restart of mysql. I actually have a daily restart of services script to avoid those services from clogging up too much memory. The freezes are unrecoverable (after waiting several days). While the kernel LED is still indicating activity, as is the LAN light, nothing is responding otherwise (not through debug UART, not through SSH or web or any other port, not through HDMI output [no signal]). Prior to my upgrade, so while I was on legacy kernel and jessie, I had uptimes for about 6 months until I rebooted for a security update, and then another uptime of again 6 months before I decided to upgrade to stretch. It's why I don't believe it's related to my SD card, or power setup (USB OTG), or USB peripherals. As I'm writing this I am going to disable mysql and php services for a while to see if I still get the freeze or if my initial suspicion about memory hogs/kernel panics may be correct. I've had these freezes occur several times, and after it occurred the last time I decided to do a system check-up, fix some minor things and run some diagnostics (based on a topic on providing debug output from tkaiser). You can see that initial debug output here: http://ix.io/F9A from 2/2/2018. After freezing up again when I was reading RSS feeds (through tt-rss) on my own hosted webserver, I waited a couple of days and forced a reboot today. That debug output can be found here: http://ix.io/Fmj from 2/6/2018. I noticed that both outputs have the same shutdown log (from 1/28 when I was on 4.13.16-sunxi), I'm not sure why that is, or if that will help or prevent troubleshooting assistance. Hopefully with this background and details someone will be able to spot something that looks off, or some explanation as I'm hopeful to identify and resolve the issue. Update on 2/6 at 8:10 PM: after reading this post on (under)powering an SBC through Micro USB, I wanted to clarify that because of some mistakes that I had made about 2 years ago, my A20 LIME2 cannot be powered on through it's PWR jack. I somehow must have messed that up and as such I have been using USB OTG to power my board. Again, I don't think that this is the cause as I have a good power supply (had issues with that 2 years ago and bought a good one) and haven't had issues on the legacy kernel in the past 2 years, but it's always possible that the mainline kernel responds differently to power fluctuations (or causes them more so). I'm running the armbian monitor submodule (since 9 AM this morning) that reports loads and DC-IN every 5 seconds to see what the latest reported data is upon crashing (if it crashes again now that I have turned off php/mysql/dovecot/postfix services). So far, in the past 11 hours, I'm seeing (of 7337 measures): * CPU min: 528Mhz, max: 960Mhz, average: 915Mhz * Load min: 0.06, max: 2.7, average: 0.49 * CPU load min: 2%, max: 100%, average: 18% * CPU temp min: 41.4°C, max: 50.4°C, average: 43.8°C * DC-IN min: 4.86V, max: 5V, average: 4.96V

Hi all, I have Lime2/legacy kernel 3.4, within 2-3 min after boot the network connection are dropped and up again. The problem for my automation, I can fix it? Regards,

Hello ! In my project I need use 2 spi bus : /dev/spidev1.0 and /dev/spi2.0 /dev/spidev1.0 for 3.5inch rpi display and /dev/spidev2.0 for 8x8 led matrices, such as MAX7219-8x32-MCU-Drive-LED If I am use legacy kernel (3.4.113-sun7i) both spi buses work well But if use mainline kernel (4.14.18-sunxi), I can use only 1 spi bus This is my armbianEnv.txt: overlays=spi-spidev spi1 spi2 param_spidev_spi_bus=1 In this case I can use /dev/spidev1.0 If I set param_spidev_spi_bus=2 I can use /dev/spidev2.0 How to enable 2 spi buses at the same time ?

I have encoutered some difficulties on carrier detection with network-manager on ethernet port, on lime2, on default kernel, 5.38. On mii-tools and ethtools, carrier is correctly reported. The result, network-manager try to activate connection at boot even cable is not plugged. It's report drivers (sunxi_gmac) does not support carrier detection, as i found in syslog When unplugged, the connection is still active. Apr 11 11:39:03 localhost NetworkManager[491]: <info> [1523439543.5279] NetworkManager (version 1.2.6) is starting... Apr 11 11:39:03 localhost NetworkManager[491]: <info> [1523439543.5321] Read config: /etc/NetworkManager/NetworkManager.conf (lib: zz-override-wifi-powersave-off.conf) (etc: default-wifi-powersave-on.con f) Apr 11 11:39:03 localhost NetworkManager[491]: <info> [1523439543.5894] manager[0x1d650f8]: monitoring kernel firmware directory '/lib/firmware'. Apr 11 11:39:03 localhost NetworkManager[491]: <info> [1523439543.5920] monitoring ifupdown state file '/run/network/ifstate'. Apr 11 11:39:03 localhost NetworkManager[491]: <info> [1523439543.6314] dns-mgr[0x1d56520]: init: dns=default, rc-manager=resolvconf Apr 11 11:39:04 localhost NetworkManager[491]: <info> [1523439544.3421] init! Apr 11 11:39:04 localhost NetworkManager[491]: <info> [1523439544.3439] management mode: managed Apr 11 11:39:04 localhost NetworkManager[491]: <info> [1523439544.3508] devices added (path: /sys/devices/platform/sunxi_gmac/net/eth0, iface: eth0) Apr 11 11:39:04 localhost NetworkManager[491]: <info> [1523439544.3510] device added (path: /sys/devices/platform/sunxi_gmac/net/eth0, iface: eth0): no ifupdown configuration found. Apr 11 11:39:04 localhost NetworkManager[491]: <info> [1523439544.3512] devices added (path: /sys/devices/virtual/net/bond0, iface: bond0) Apr 11 11:39:04 localhost NetworkManager[491]: <info> [1523439544.3513] device added (path: /sys/devices/virtual/net/bond0, iface: bond0): no ifupdown configuration found. Apr 11 11:39:04 localhost NetworkManager[491]: <info> [1523439544.3515] devices added (path: /sys/devices/virtual/net/lo, iface: lo) Apr 11 11:39:04 localhost NetworkManager[491]: <info> [1523439544.3516] device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found. Apr 11 11:39:04 localhost NetworkManager[491]: <info> [1523439544.3517] end _init. Apr 11 11:39:04 localhost NetworkManager[491]: <info> [1523439544.3519] settings: loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. (/usr/lib/arm-linux-gnueabihf/NetworkManager/libnm-settings-plugin-ifupdown.so) Apr 11 11:39:04 localhost NetworkManager[491]: <info> [1523439544.3525] settings: loaded plugin keyfile: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Apr 11 11:39:04 localhost NetworkManager[491]: <info> [1523439544.3527] (30909152) ... get_connections. Apr 11 11:39:04 localhost NetworkManager[491]: <info> [1523439544.3528] (30909152) connections count: 0 Apr 11 11:39:04 localhost NetworkManager[491]: <info> [1523439544.5797] keyfile: new connection /etc/NetworkManager/system-connections/ethernet-eth0 (c6b12eb9-c6cd-4937-b8cf-59efab1b6f35,"ethernet-eth0") Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.0603] keyfile: new connection /etc/NetworkManager/system-connections/GSMCon (5ab76ce5-300a-42c7-9d77-cd1488fa7e3a,"GSMCon") Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4002] settings: hostname: using hostnamed Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4006] settings: hostname changed from (none) to "lime2" Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4021] Using DHCP client 'dhclient' Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4023] manager: WiFi enabled by radio killswitch; enabled by state file Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4026] manager: WWAN enabled by radio killswitch; enabled by state file Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4028] manager: Networking is enabled by state file Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4033] Loaded device plugin: NMVxlanFactory (internal) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4035] Loaded device plugin: NMVlanFactory (internal) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4037] Loaded device plugin: NMVethFactory (internal) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4040] Loaded device plugin: NMTunFactory (internal) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4042] Loaded device plugin: NMMacvlanFactory (internal) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4044] Loaded device plugin: NMIPTunnelFactory (internal) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4046] Loaded device plugin: NMInfinibandFactory (internal) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4048] Loaded device plugin: NMEthernetFactory (internal) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4050] Loaded device plugin: NMBridgeFactory (internal) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.4052] Loaded device plugin: NMBondFactory (internal) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.5134] Loaded device plugin: NMWwanFactory (/usr/lib/arm-linux-gnueabihf/NetworkManager/libnm-device-plugin-wwan.so) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.6734] Loaded device plugin: NMAtmManager (/usr/lib/arm-linux-gnueabihf/NetworkManager/libnm-device-plugin-adsl.so) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.7438] Loaded device plugin: NMWifiFactory (/usr/lib/arm-linux-gnueabihf/NetworkManager/libnm-device-plugin-wifi.so) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.8610] Loaded device plugin: NMBluezManager (/usr/lib/arm-linux-gnueabihf/NetworkManager/libnm-device-plugin-bluetooth.so) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.8713] device (eth0): driver '(null)' does not support carrier detection. Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.8763] device (eth0): driver 'sunxi_gmac' does not support carrier detection. Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.8906] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/0) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.9090] device (eth0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Apr 11 11:39:05 localhost NetworkManager[491]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.9616] device (lo): link connected Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.9688] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1) Apr 11 11:39:05 localhost NetworkManager[491]: <info> [1523439545.9803] manager: (bond0): new Bond device (/org/freedesktop/NetworkManager/Devices/2) Apr 11 11:39:06 localhost NetworkManager[491]: <info> [1523439546.0033] manager: startup complete Apr 11 11:39:06 localhost NetworkManager[491]: <info> [1523439546.0933] urfkill disappeared from the bus Apr 11 11:39:06 localhost NetworkManager[491]: <info> [1523439546.1036] device (eth0): state change: unavailable -> disconnected (reason 'none') [20 30 0] Apr 11 11:39:06 localhost NetworkManager[491]: <info> [1523439546.1117] policy: auto-activating connection 'ethernet-eth0' Apr 11 11:39:06 localhost NetworkManager[491]: <info> [1523439546.1316] device (eth0): Activation: starting connection 'ethernet-eth0' (c6b12eb9-c6cd-4937-b8cf-59efab1b6f35) Apr 11 11:39:06 localhost NetworkManager[491]: <info> [1523439546.1345] ofono is now available Apr 11 11:39:06 localhost NetworkManager[491]: <info> [1523439546.1414] ModemManager available in the bus Apr 11 11:39:06 localhost NetworkManager[491]: <warn> [1523439546.1418] failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 11 11:39:06 localhost NetworkManager[491]: <info> [1523439546.1463] device (eth0): state change: disconnected -> prepare (reason 'none') [30 40 0] Apr 11 11:39:06 localhost NetworkManager[491]: <info> [1523439546.1483] manager: NetworkManager state is now CONNECTING Apr 11 11:39:06 localhost NetworkManager[491]: <info> [1523439546.1575] device (eth0): state change: prepare -> config (reason 'none') [40 50 0] Apr 11 11:39:06 localhost NetworkManager[491]: <info> [1523439546.1632] device (eth0): state change: config -> ip-config (reason 'none') [50 70 0] Apr 11 11:39:06 localhost NetworkManager[491]: <info> [1523439546.1749] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Apr 11 11:39:07 localhost NetworkManager[491]: <info> [1523439547.5063] dhcp4 (eth0): dhclient started with pid 605 Apr 11 11:39:13 localhost NetworkManager[491]: <info> [1523439553.8929] manager: WiFi hardware radio set enabled Apr 11 11:39:13 localhost NetworkManager[491]: <info> [1523439553.8932] manager: WWAN hardware radio set enabled Apr 11 11:39:41 localhost NetworkManager[491]: <info> [1523439581.2941] manager: (ttyUSB0): new Broadband device (/org/freedesktop/NetworkManager/Devices/3) Apr 11 11:39:41 localhost NetworkManager[491]: <info> [1523439581.2990] device (ttyUSB0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Apr 11 11:39:41 localhost NetworkManager[491]: <info> [1523439581.3115] device (ttyUSB0): modem state 'enabling' Apr 11 11:39:42 localhost NetworkManager[491]: <info> [1523439582.2504] device (ttyUSB0): state change: unavailable -> disconnected (reason 'modem-available') [20 30 58] Apr 11 11:39:42 localhost NetworkManager[491]: <info> [1523439582.2629] policy: auto-activating connection 'GSMCon' Apr 11 11:39:42 localhost NetworkManager[491]: <info> [1523439582.2785] device (ttyUSB0): Activation: starting connection 'GSMCon' (5ab76ce5-300a-42c7-9d77-cd1488fa7e3a) Apr 11 11:39:42 localhost NetworkManager[491]: <info> [1523439582.2828] device (ttyUSB0): state change: disconnected -> prepare (reason 'none') [30 40 0] Apr 11 11:39:42 localhost NetworkManager[491]: <warn> [1523439582.8901] device (ttyUSB0): failed to look up interface index Apr 11 11:39:42 localhost NetworkManager[491]: <info> [1523439582.8919] device (ttyUSB0): state change: prepare -> config (reason 'none') [40 50 0] Apr 11 11:39:42 localhost NetworkManager[491]: <info> [1523439582.8953] device (ttyUSB0): state change: config -> ip-config (reason 'none') [50 70 0] Apr 11 11:39:42 localhost NetworkManager[491]: <warn> [1523439582.9008] device (ttyUSB0): interface ttyUSB1 not up for IP configuration Apr 11 11:39:42 localhost NetworkManager[491]: <info> [1523439582.9033] (ttyUSB0): using modem-specified IP timeout: 20 seconds Apr 11 11:39:42 localhost NetworkManager[491]: <info> [1523439582.9100] ppp-manager: starting PPP connection Apr 11 11:39:42 localhost NetworkManager[491]: <info> [1523439582.9189] ppp-manager: pppd started with pid 846 Apr 11 11:39:42 localhost NetworkManager[491]: Plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so loaded. Apr 11 11:39:42 localhost NetworkManager[491]: nm-pppd-plugin-Message: nm-ppp-plugin: (plugin_init): initializing Apr 11 11:39:43 localhost NetworkManager[491]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection' Apr 11 11:39:43 localhost NetworkManager[491]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Apr 11 11:39:43 localhost NetworkManager[491]: <info> [1523439583.0409] manager: (ppp0): new Generic device (/org/freedesktop/NetworkManager/Devices/4) Apr 11 11:39:43 localhost NetworkManager[491]: Using interface ppp0 Apr 11 11:39:43 localhost NetworkManager[491]: Connect: ppp0 <--> /dev/ttyUSB1 Apr 11 11:39:43 localhost NetworkManager[491]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' Apr 11 11:39:43 localhost NetworkManager[491]: <info> [1523439583.1848] devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Apr 11 11:39:43 localhost NetworkManager[491]: <info> [1523439583.1850] device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Apr 11 11:39:43 localhost NetworkManager[491]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 6 / phase 'authenticate' Apr 11 11:39:43 localhost NetworkManager[491]: nm-pppd-plugin-Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials... Apr 11 11:39:43 localhost NetworkManager[491]: nm-pppd-plugin-Message: nm-ppp-plugin: (get_credentials): got credentials from NetworkManager Apr 11 11:39:43 localhost NetworkManager[491]: CHAP authentication succeeded: Welcome!! Apr 11 11:39:43 localhost NetworkManager[491]: CHAP authentication succeeded Apr 11 11:39:43 localhost NetworkManager[491]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase 'network' Apr 11 11:39:43 localhost NetworkManager[491]: Could not determine remote IP address: defaulting to 10.64.64.64 Apr 11 11:39:43 localhost NetworkManager[491]: local IP address 10.228.59.95 Apr 11 11:39:43 localhost NetworkManager[491]: remote IP address 10.64.64.64 Apr 11 11:39:43 localhost NetworkManager[491]: primary DNS address 172.20.2.39 Apr 11 11:39:43 localhost NetworkManager[491]: secondary DNS address 172.20.2.10 Apr 11 11:39:43 localhost NetworkManager[491]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 9 / phase 'running' Apr 11 11:39:43 localhost NetworkManager[491]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip_up): ip-up event Apr 11 11:39:43 localhost NetworkManager[491]: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_ip_up): sending IPv4 config to NetworkManager... Apr 11 11:39:43 localhost NetworkManager[491]: <info> [1523439583.5462] ppp-manager: (IPv4 Config Get) reply received. Apr 11 11:39:43 localhost NetworkManager[491]: <error> [1523439583.5820] platform-linux: do-add-ip4-address[6: 10.228.59.95/32,0.0.0.0]: failure 17 (File exists) Apr 11 11:39:43 localhost NetworkManager[491]: <info> [1523439583.5847] device (ttyUSB0): state change: ip-config -> ip-check (reason 'none') [70 80 0] Apr 11 11:39:43 localhost NetworkManager[491]: <info> [1523439583.5946] device (ttyUSB0): state change: ip-check -> secondaries (reason 'none') [80 90 0] Apr 11 11:39:43 localhost NetworkManager[491]: <info> [1523439583.6034] device (ttyUSB0): state change: secondaries -> activated (reason 'none') [90 100 0] Apr 11 11:39:43 localhost NetworkManager[491]: <info> [1523439583.6243] policy: set 'GSMCon' (ppp0) as default for IPv4 routing and DNS Apr 11 11:39:43 localhost NetworkManager[491]: <info> [1523439583.6252] dns-mgr: Writing DNS information to /sbin/resolvconf Apr 11 11:39:43 localhost NetworkManager[491]: <info> [1523439583.7840] device (ttyUSB0): Activation: successful, device activated. Apr 11 11:39:52 localhost NetworkManager[491]: <warn> [1523439592.8910] dhcp4 (eth0): request timed out Apr 11 11:39:52 localhost NetworkManager[491]: <info> [1523439592.8913] dhcp4 (eth0): state changed unknown -> timeout Apr 11 11:39:52 localhost NetworkManager[491]: <info> [1523439592.9105] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 605 Apr 11 11:39:52 localhost NetworkManager[491]: <info> [1523439592.9107] dhcp4 (eth0): state changed timeout -> done Apr 11 11:39:52 localhost NetworkManager[491]: <info> [1523439592.9152] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] Apr 11 11:39:52 localhost NetworkManager[491]: <info> [1523439592.9180] manager: NetworkManager state is now CONNECTED_GLOBAL Apr 11 11:39:52 localhost NetworkManager[491]: <info> [1523439592.9201] manager: NetworkManager state is now CONNECTED_SITE Apr 11 11:39:52 localhost NetworkManager[491]: <info> [1523439592.9204] manager: NetworkManager state is now CONNECTED_GLOBAL Apr 11 11:39:52 localhost NetworkManager[491]: <warn> [1523439592.9258] device (eth0): Activation: failed for connection 'ethernet-eth0' Apr 11 11:39:52 localhost NetworkManager[491]: <info> [1523439592.9436] device (eth0): state change: failed -> disconnected (reason 'none') [120 30 0] Apr 11 11:39:52 localhost NetworkManager[491]: <info> [1523439592.9759] policy: auto-activating connection 'ethernet-eth0' Apr 11 11:39:52 localhost NetworkManager[491]: <info> [1523439592.9865] device (eth0): Activation: starting connection 'ethernet-eth0' (c6b12eb9-c6cd-4937-b8cf-59efab1b6f35) Apr 11 11:39:52 localhost NetworkManager[491]: <info> [1523439592.9884] device (eth0): state change: disconnected -> prepare (reason 'none') [30 40 0] Apr 11 11:39:52 localhost NetworkManager[491]: <info> [1523439592.9950] device (eth0): state change: prepare -> config (reason 'none') [40 50 0] Apr 11 11:39:53 localhost NetworkManager[491]: <info> [1523439593.0488] device (eth0): state change: config -> ip-config (reason 'none') [50 70 0] Apr 11 11:39:53 localhost NetworkManager[491]: <info> [1523439593.0546] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Apr 11 11:39:53 localhost NetworkManager[491]: <info> [1523439593.0637] dhcp4 (eth0): dhclient started with pid 965 Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.6136] address 192.168.1.95 Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.6139] plen 24 (255.255.255.0) Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.6140] gateway 192.168.1.1 Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.6141] server identifier 192.168.1.1 Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.6142] lease time 86400 Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.6144] nameserver '192.168.1.1' Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.6145] domain name 'home' Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.6146] dhcp4 (eth0): state changed unknown -> bound Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.6320] device (eth0): state change: ip-config -> ip-check (reason 'none') [70 80 0] Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.6440] device (eth0): state change: ip-check -> secondaries (reason 'none') [80 90 0] Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.6517] device (eth0): state change: secondaries -> activated (reason 'none') [90 100 0] Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.6670] manager: NetworkManager state is now CONNECTED_LOCAL Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.6691] manager: NetworkManager state is now CONNECTED_GLOBAL Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.6712] policy: set 'ethernet-eth0' (eth0) as default for IPv4 routing and DNS Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.6800] dns-mgr: Writing DNS information to /sbin/resolvconf Apr 11 11:39:56 localhost NetworkManager[491]: <info> [1523439596.8263] device (eth0): Activation: successful, device activated.

Hi, System: A20Lime2-4gb with latest legacy image Linux lime2 3.4.113-sun7i #23 SMP PREEMPT Wed Jun 14 23:57:45 CEST 2017 armv7l armv7i armv7l GNU/Linux When I shutdown or restart, it throws me back to login screen and again loads desktop even if I don't enter id and password and then shutdown automatically within 10 secs . I want it to shutdown/restart without this login screen. I tried shutdown from terminal ' sudo shutdown -h now' , 'sudo poweroff' still giving login screen. How can solve this issue ? Thank you in advance

I'm using Armbian 5.38 stable Debian stretch 4.14.14-sunxi on A20 Lime2. I try to use PGxx pins (connector GPIO-1 on board), without any luck. I know i must use formula (position of letter in alphabet - 1) * 32 + pin number, so i have tried (for PG11): echo 203 > /sys/class/gpio/export echo out > /sys/class/gpio/gpio203/direction echo 1 > /sys/class/gpio/203/value but nothing happened. I tried from 192 to 203 (PG00 to PG11), but nothing happened. On the same connector (GPIO-1), PC23, PC18 and PB23 work perfectly. What am i doing wrong?

Hi everyone, i have a strange problem with my a20 lime2 board as described in the topic. Please help The i2s0 pins should be MCLK-PB5 BCLK-PB6 LRCK-PB7 DO0-PB8. But I got data signal from PB7, and the LRCK was missing. a 24 bit 44.1khz file was played by aplay.

Hello. this is my first post. I was looking through the forum but I did not find a similar problem. About power supply - until now I did not have any problems, I use a computer power supply. After a few months of non-use of my device, I downloaded an updated, latest version (Armbian_5.38_Lime2_Ubuntu_xenial_default_3.4.113_desktop) to an old, previously functioning card. When I connected the device, it did not turn on. I tried to turn it on manually, but nothing happened except the short flash on the connected mouse. A while ago, I uploaded an older desktop version to NAND. I used the sd card to start up. Is it possible that this older version loaded on NAND causes problems? On the other card, I uploaded the latest debian server version but it did not succeed. Any suggestions? Best regards and thank you in advance, Damijan

I am currently trying to upgrade my kernel from 3.4 to 4.14 and it is working quite well for my needs. But i have a problem i have not found a solution for, i can not set the PE00-11 pins as gpios. Acutally i cant set or configure them at all. I am using the /sys/class... export and writing via echo direction and value. For all other GPIOs it works perfectly fine exept for those 12 (and the IR0-pins PB3 and PB4, those are also not accessible). I tried really a lot already: stripping down the kernel to only the most essential modules, deactivating almost everything in the dts file, using different images... but in essence, as soon as i change from 3.4 to mainline, the PE-pins stop working. Has anyone any clue how i can dig deeper into this or maybe even a solution?

Hello, Upgrading uboot 5.25 to 5.35 on Armbian_5.25_Lime2_Ubuntu_xenial_default_3.4.113 fail to boot at next reboot. It's a lime2 Nand with SD card system, last rev hardware I don't find any solutions for the moment, because serial output doesn't output very much ... here is the 5.35 boot U-Boot SPL 2017.09-armbian (Nov 22 2017 - 15:21:35) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2017.09-armbian (Nov 22 2017 - 15:21:35 +0100) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Olimex A20-OLinuXino-LIME2-eMMC I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial SCSI: SATA link 0 timeout. 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 6944 bytes read in 154 ms (43.9 KiB/s) ### ERROR ### Please RESET the board ### on the original image the boot is fine : U-Boot SPL 2017.01-armbian (Feb 02 2017 - 02:40:37) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2017.01-armbian (Feb 02 2017 - 02:40:37 +0100) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Olimex A20-OLinuXino-LIME2 I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial SCSI: SATA link 0 timeout. 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 159 ms (42 KiB/s) switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2652 bytes read in 179 ms (13.7 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 114 bytes read in 124 ms (0 Bytes/s) 5072050 bytes read in 535 ms (9 MiB/s) 5607392 bytes read in 582 ms (9.2 MiB/s) ** File not found /boot/.next ** ** File not found .next ** 53488 bytes read in 370 ms (140.6 KiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5071986 Bytes = 4.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Starting kernel ... So i have just downloaded le last prebuilt legacy image with 5.35 already in it and it boot. I will continue devlopment on this image and maybe make a userbuilt image later. Hope it help, here is the boot log of this one : U-Boot SPL 2017.09-armbian (Nov 22 2017 - 15:21:35) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2017.09-armbian (Nov 22 2017 - 15:21:35 +0100) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Olimex A20-OLinuXino-LIME2-eMMC I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial SCSI: SATA link 0 timeout. 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 230454 bytes read in 193 ms (1.1 MiB/s) Error: 24 bits/pixel bitmap incompatible with current video mode starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 198 ms (17.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 192 bytes read in 150 ms (1000 Bytes/s) 5073641 bytes read in 545 ms (8.9 MiB/s) 5594808 bytes read in 591 ms (9 MiB/s) Found legacy kernel configuration 53488 bytes read in 372 ms (139.6 KiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5073577 Bytes = 4.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK EHCI failed to shut down host controller. Loading Ramdisk to 49b29000, end 49fffaa9 ... OK Starting kernel ...

Hi all! After success image building I have problem at boot [Armbian_5.37_Lime2_Debian_jessie_default_3.4.113] Boot stoped after line '<6>axp20_ldo2: 1800 <--> 3300 mV at 3000 mV' PSU and board work fine, what is the problem? Regards, boot log ========HV Inital =================== <3>tkey_fetch_sysconfig_para: tkey_unused. hv_keypad_init: after fetch_sysconfig_para: normal_i2c: 0x0. normal_i2c[1]: 0x0 <3>sunxi-rtc sunxi-rtc: Warning: RTC time is wrong! <6>sunxi-rtc sunxi-rtc: rtc core: registered rtc as rtc0 <6>i2c /dev entries driver config i2c gpio with gpio_config api <6>axp_mfd 0-0034: AXP (CHIP ID: 0x41) detected <6>axp_mfd 0-0034: AXP internal temperature monitoring enabled <4>i2c i2c-0: Invalid probe address 0x00 <6>I2C: i2c-0: AW16XX I2C adapter config i2c gpio with gpio_config api <4>i2c i2c-1: Invalid probe address 0x00 <6>I2C: i2c-1: AW16XX I2C adapter config i2c gpio with gpio_config api <4>i2c i2c-2: Invalid probe address 0x00 <6>I2C: i2c-2: AW16XX I2C adapter <5>cedar: failed to allocate memory buffer [tt]----- avs_dev driver load... ---- [tt]----- register iomem ---- Cannot reserve region for ccmu [tt]--- avs_dev driver load ok!! ----- [ace_drv] start!!! [ace_drv] init end!!! [pa_drv] start!!! [pa_drv] init end!!! <6>axp20_ldo1: 1300 mV <6>axp20_ldo2: 1800 <--> 3300 mV at 3000 mV

Hi everybody, At first I would like to thank you all cause of all your comments in previous posts that helped to make my Lime2 working great. But since the 5.35 upgrade it doesn't want to start anymore. I was on a A20-OLinuXino-LIME2 without eMMC and the Armbian_5.31_Lime2_Ubuntu_xenial_default_3.4.113_desktop image which I upgraded to the 5.35. On the 5.31 I modified before the update the /boot/bin/lime2.bin file into a lime2lcd10.bin file in order to make the lime2 work with the LCD-OLinuXino-10TS of Olimex. After the update, I needed to make the link again with the /boot/script.bin file. But even with a new Armbian image freshly downloaded, it doesn't start also. When I plug the HDMI I see : U-Boot 2017.09-armbian (nov 22 2017 -15:21:35 +0100) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Olimex A20-OlinuXino-Lime2-eMMC I2C: ready DRAM: 1GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environnment HDMI connected: Setting up a 1920x1000 hdmi console(overscan 0x0) Error: no valid bmp image at 66000000 In: serial Out: vga Err: vga SCSI: SATA link 0 timeout. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slun part ccc apst Net: eth0: ethernet@01c50000 38518 bytes read in 146 ms (256.0 KiB/s) starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.src 3565 bytes read in 194 ms (176 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 192 bytes read in 156 ms (1000 Bytes/s) 5076840 bytes read in 559 ms (8.7 MiB/s) 5594800 bytes read in 549 ms (9.7 MiB/s) Found legacy kernel configuration 53532 bytes read in 576 ms (89.8 KiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Minux RAMDisk Image (gzip compressed) Data Size: 5076776 Bytes = 4.8 MiB Load Addresses: 00000000 Entry Point: 00000000 Verifying Checksum ... OK EHCI failed to shut down host controller. Loading Ramdisk to 49b28000, end 49fff728 ... OK Starting kernel ... And then nothing... For the Warning at the beginning I stopped the Autoboot and wrote the code : saveenv reset No more warning but still doesn't start. Any idea how to fix it? Thanks