Search the Community

Hi Igor! Thanks for your answer: Enclosed you'll find my network configuration from /etc/network/interfaces: #Loopback device auto lo iface lo inet loopback #LAN Device eth0 auto eth0 iface eth0 inet static address 192.168.175.25 netmask 255.255.255.0 broadcast 192.168.175.255 network 192.168.175.0/24 gateway 192.168.175.1 nameserver 192.168.175.1 #WLAN Device 1 (USB Adapter ALFA AWUS036AC) auto wlx00c0ca8184e0 allow-hotplug wlx00c0ca8184e0 iface wlx00c0ca8184e0 inet manual address 0.0.0.0 ##Bridge br0 fuer Interfaces ETH0 und wlx00c0ca8184e0 auto br0 iface br0 inet static address 192.168.175.191 netmask 255.255.255.0 network 192.168.175.0/24 broadcast 192.168.175.255 gateway 192.168.175.1 nameserver 192.168.175.1 bridge_ports eth0 wlx00c0ca8184e0 bridge_fd 0 bridge_stp n At this time I even can not access the net! Enclosed you'll find a screenshot from my router! strange, that br0 and cubie5 share the same IP address! ifconfig: br0 Link encap:Ethernet HWaddr 00:c0:ca:81:84:e0 inet addr:192.168.175.191 Bcast:192.168.175.255 Mask:255.255.255.0 inet6 addr: fe80::2c0:caff:fe81:84e0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1968 errors:0 dropped:0 overruns:0 frame:0 TX packets:1428 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:155003 (151.3 KiB) TX bytes:244568 (238.8 KiB) eth0 Link encap:Ethernet HWaddr 02:05:06:c0:f8:68 inet addr:192.168.175.25 Bcast:192.168.175.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2391 errors:0 dropped:0 overruns:0 frame:0 TX packets:1577 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:273843 (267.4 KiB) TX bytes:270930 (264.5 KiB) Interrupt:117 Base address:0xc000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:105 errors:0 dropped:0 overruns:0 frame:0 TX packets:105 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:10200 (9.9 KiB) TX bytes:10200 (9.9 KiB) wlx00c0ca8184e0 Link encap:Ethernet HWaddr 00:c0:ca:81:84:e0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:44 errors:0 dropped:34 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 TX bytes:6320 (6.1 KiB) regards, Ireng Cubie5 is the system in trouble! :-)

Hi Josef, u want to do both? so charge the LiPo and powering the board at the same time? It wont be possible without some additional electronics, so NO its charge or Power the board. Sinc P.

hi testing somebody sata power if is using backup li-poly battery?

I know now what's the essential problem and it will be fixed. NAND/SATA/USB install part is as is. If you follow the install it works, It fails in custom situations - It's not designed for that yet. I am glad everything went o.k. and thanks, testing is always helpful and saves a lot of time. Mine and all users if we discover and fix thigns propmtly.

You will loose your time only, when you are trying onboard wifi get running. I tested with all available drivers/kernels/systems and result is the same - nearly unusable. Buy quality USB wifi, and you will have zero problems.

I might be better off buying another USB Wifi adapter but somehow I feel the urge to get the onboard wifi running. If I blacklist the driver as follows, I can see no wlan adapter at all when checking "ifconfig -a" nano blacklist.conf blacklist rtl8192cu Anything I am missing?

Thanks for supporting I'm not sure, last four boots hard drive spin ok. I think now using last uboot. "U-Boot 2015.04-dirty (May 25 2015 - 08:34:10) Allwinner Technology" I think dts file not good for power sata. But included target-supply work well. Maybe at your next build, can you include this? Your work is very nice. https://github.com/Lamobo/Lamobo-R1-OpenWrt/blob/master/target/linux/sunxi/files/arch/arm/boot/dts/sun7i-a20-lamobo-r1.dts#L63 https://github.com/igorpecovnik/lib/blob/next/patch/sun7i-a20-lamobo-r1.dts#L100 Thanks

2) Lime A10 image with kernel 3.4.108 and HW accelerated MATE desktop It starts boot, but it hangs. Output from serial console is below: U-Boot SPL 2015.04-dirty (Jul 14 2015 - 19:32:48) DRAM: 512 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 U-Boot 2015.04-dirty (Jul 14 2015 - 19:32:48) Allwinner Technology CPU: Allwinner A10 (SUN4I) I2C: ready DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment HDMI connected: EDID: invalid EDID data Setting up a 1024x768 dvi console Error: no valid bmp image at 66000000 In: serial Out: vga Err: vga SCSI: SUNXI SCSI INIT 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: emac starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... cannot reset port 1!? 1 USB Device(s) found USB1: USB EHCI 1.00 scanning bus 1 for devices... cannot reset port 1!? 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 6944 bytes read in 192 ms (35.2 KiB/s) switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 1548 bytes read in 181 ms (7.8 KiB/s) ## Executing script at 43100000 ** File not found /boot/.next ** 43508 bytes read in 458 ms (91.8 KiB/s) 5605360 bytes read in 657 ms (8.1 MiB/s) Kernel image @ 0x48000000 [ 0x000000 - 0x5587f0 ] Starting kernel ... <6>Booting Linux on physical CPU 0 <6>Initializing cgroup subsys cpuset <6>Initializing cgroup subsys cpu <5>Linux version 3.4.108-lime (root@kitchen) (gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-16ubuntu4) ) #14 SMP PREEMPT Sun Jul 12 16:43:47 CEST 2015 CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Machine: sun4i <6>Memory Reserved: <6> SYS : 0x43000000 - 0x4300ffff ( 64 kB) <6> LCD : 0x44000000 - 0x44ffffff ( 16 MB) Memory policy: ECC disabled, Data cache writeback <6>sunxi: Allwinner A10 revision C (AW1623/sun4i) detected. <7>On node 0 totalpages: 131072 <7>free_area_init_node: node 0, pgdat c0a7bb40, node_mem_map d0000000 <7> DMA zone: 512 pages used for memmap <7> DMA zone: 0 pages reserved <7> DMA zone: 65024 pages, LIFO batch:15 <7> Normal zone: 512 pages used for memmap <7> Normal zone: 65024 pages, LIFO batch:15 <6>PERCPU: Embedded 8 pages/cpu @d0405000 s8256 r8192 d16320 u32768 <7>pcpu-alloc: s8256 r8192 d16320 u32768 alloc=8*4096<c> <7>pcpu-alloc: <c>[0] <c>0 <c> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 <5>Kernel command line: console=tty1 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=1 <6>PID hash table entries: 2048 (order: 1, 8192 bytes) <6>Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) <6>Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) <6>allocated 1048576 bytes of page_cgroup <6>please try 'cgroup_disable=memory' option if you don't want memory cgroups <6>Memory: 512MB = 512MB total <5>Memory: 489616k/489616k available, 34672k reserved, 0K highmem <5>Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) vmalloc : 0xe0800000 - 0xff000000 ( 488 MB) lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) modules : 0xbf000000 - 0xbfe00000 ( 14 MB) .text : 0xc0008000 - 0xc09d1b00 (10023 kB) .init : 0xc09d2000 - 0xc0a0b040 ( 229 kB) .data : 0xc0a0c000 - 0xc0a842b8 ( 481 kB) .bss : 0xc0a842dc - 0xc0c596b8 (1877 kB) <6>SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 <6>Preemptible hierarchical RCU implementation. <6> RCU dyntick-idle grace-period acceleration is enabled. <6> Additional per-CPU info printed with stalls. <6>NR_IRQS:192 <6>sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms <6>Console: colour dummy device 80x30 <6>console [tty1] enabled <6>Calibrating delay loop... And A10 CPU was very hot. And to you previous question: no, I don't check kernel 3.4.x before.

USB sharing is temporally not compiling on kernel 4.x ... on kernel 3.4.x it's working normally. I notified the author. If there is no driver on the image it means I forgot (it happens) to enable it during compilation and you need to compile yourself. It's easy. Our kernel is (rock) stable. There were some stability issues in some 3.4.107 builds but that was single event and actually linked to U-boot (i think). Latest 3.4.108 (and 4.x) kernel are stable. I just finished two weeks burn in stress test and all three boards (Lime, Cubietruck and Banana) were stable. I don't have any info about bugs or memory leak among USB EHCI controller. BTW. Thanks. When you come to Slovenia next time, give me a visit

This is the DT that I use: https://github.com/igorpecovnik/lib/blob/next/patch/sun7i-a20-lamobo-r1.dts According to the configuration it should work. I was not checking the last R1 build for sata power. Yes, that's the proper way to install u-boot.

This is my first post, sorry for my English. I bought one r1 bpi, I think it similar or the same lamobo-r1. I download from blog this image Lamobo-r1_Debian_3.2_jessie_4.1.2.zip and tried use, but the same was not providing power to the SATA. After hours trying to understand the workings got the following solution: sun7i-a20-lamobo-r1.dtb --- /dev/fd/63 2015-07-14 05:24:00.879114523 +0200 +++ /dev/fd/62 2015-07-14 05:24:00.889113763 +0200 @@ -11,6 +11,7 @@ compatible = "regulator-fixed"; enable-active-high; gpio = <0x1b 0x1 0x3 0x0>; + linux,phandle = <0x3a>; pinctrl-0 = <0x34>; pinctrl-names = "default"; regulator-boot-on; @@ -820,7 +821,7 @@ ir0@0 { allwinner,drive = <0x0>; allwinner,function = "ir0"; - allwinner,pins = "PB3", "PB4"; + allwinner,pins = "PB4"; allwinner,pull = <0x0>; linux,phandle = <0x27>; phandle = <0x27>; @@ -1067,6 +1068,7 @@ interrupts = <0x0 0x38 0x4>; reg = <0x1c18000 0x1000>; status = "okay"; + target-supply = <0x3a>; }; serial@01c28000 { However not find source of dts, then used the DTC tool. Could you help me change the correct file? Another thing, uboot is not leaving the PB3 value high. Is there any solution? I try install linux-u-boot-3.4.107-lamobo-r1_3.0_armhf.deb using only dpkg -i linux-u-boot-3.4.107-lamobo-r1_3.0_armhf.deb, need some else? Thanks.

This is part LT-1318 from https://www.led-tech.de/de/High-Power-Zubehoer/Kuehlkoerper-c_106_114.html

A little to add to this, Dont forget Tkaiser and i use a hdd, and does some cooling 2 Maybe add a lay around laptop hdd, the hdd houseing sits ontop of the Broadcom and far away from the A20. It could only get better this way. If your going to use the hdd read the instructions on Tkaisers wiki because u have to power it another way. P.

Well, in my case I chose the wrong color since the customer now wants to put the device somewhere where it's exposed to sunlight from noon till five. I will include 2 DS18B20 temperature sensors to get a clue how hot it gets inside regardless of internal chip temperatures. The next time I'll build such a device (main part is the 24V PSU in the left and an 8-port Pover over Ethernet injector to provide a couple of Raspberry Pis with network and power) I'll replace the 5V/12 PSU for board and display with 2 step-down converters and use a Banana Pi together with a small 8-port-switch.

Thx, great job. I hope the URL remains since I will link often to it Regarding the filesystems. In my opinion btrfs is only interesting for disk storage (SATA, USB) and for people who know what they do (creating snapshots, transferring these snapshots incrementally using 'btrfs send/receive' to other disks/machines and so on -- all this has drawbacks, for example getting a clue how much space is really available on the disk in question). So regarding btfrs this is more a candidate for nand-sata-install: Allowing to use btrfs for sda1 and recommending to partition the disk prior to that and to use a separate partition for / and for other/media data (since using snapshots this makes backing up everything way more easy). Regarding F2FS: It should be superiour compared to ext4 when used on NAND/SD Cards or other flash based media. But I'm still not convinced whether it's worth the efforts since the resizing problem remains. Would be great to be able to choose it optionally but I doubt that it's ready for your normal OS images. Regarding cpufreq stuff: This remains the same in mainline: You can adjust the sysfs values as you want but all values will be rounded down in 48 MHz steps. BTW: I will try to add a few additional operating points in arch/arm/boot/dts/sun7i-a20.dtsi to slightly 'overclock' some A20 boards: operating-points = < /* kHz uV */ 1200000 1600000 1152000 1550000 1104000 1500000 1056000 1450000 1008000 1450000 960000 1400000 912000 1400000 864000 1300000 720000 1200000 528000 1100000 312000 1000000 144000 900000 >; I'll report back if I find anything interesting (A20 specs say that 1.4V is max.)

USB redirector fails to compile within kernel 4.x ... I already notified the author and got response that they are aware and working on. Thanks for bringing up.

Hello, i want to compile an new Kernel for my BananaPi and used the great script from Igor. (Thanks for your support). Everything works perfect, but there are one error by the development of the Kernelmodul tusbd.ko. Do you know them? [ ok ] Installing external applications --2015-07-03 21:56:33-- http://www.incentivespro.com/usb-redirector-linux-arm-eabi.tar.gz Auflösen des Hostnamen »www.incentivespro.com (www.incentivespro.com)«... 74.52.236.44 Verbindungsaufbau zu www.incentivespro.com (www.incentivespro.com)|74.52.236.44|:80... verbunden. HTTP-Anforderung gesendet, warte auf Antwort... 200 OK Länge: 1851845 (1,8M) [application/x-gzip] In »»usb-redirector-linux-arm-eabi.tar.gz«« speichern. 100%[===========================================================================================>] 1.851.845 4,27KB/s in 16s 2015-07-03 21:56:50 (114 KB/s) - »»usb-redirector-linux-arm-eabi.tar.gz«« gespeichert [1851845/1851845] make -C /home/pit/BananaPi_debian/output/linux-mainline/ M=/home/pit/BananaPi_debian/output/usb-redirector-linux-arm-eabi/files/modules/src/tusbd modules make[1]: Verzeichnis »/home/pit/BananaPi_debian/output/linux-mainline« wird betreten make[1]: Warnung: Kein Jobserver verfügbar: -j1 wird gesetzt. »+« zur Ursprungsregel hinzufügen. CC [M] /home/pit/BananaPi_debian/output/usb-redirector-linux-arm-eabi/files/modules/src/tusbd/usbdcdev.o CC [M] /home/pit/BananaPi_debian/output/usb-redirector-linux-arm-eabi/files/modules/src/tusbd/minor_control.o /home/pit/BananaPi_debian/output/usb-redirector-linux-arm-eabi/files/modules/src/tusbd/minor_control.c: In function ‘IIIlIllll’: /home/pit/BananaPi_debian/output/usb-redirector-linux-arm-eabi/files/modules/src/tusbd/minor_control.c:54:1: error: implicit declaration of function ‘strnicmp’ [-Werror=implicit-function-declaration] if(strnicmp(IllIll,"\x73\x68\x61\x72\x65",(0x1448+2821-0x1f48))== ^ cc1: some warnings being treated as errors make[2]: *** [/home/pit/BananaPi_debian/output/usb-redirector-linux-arm-eabi/files/modules/src/tusbd/minor_control.o] Fehler 1 make[1]: *** [_module_/home/pit/BananaPi_debian/output/usb-redirector-linux-arm-eabi/files/modules/src/tusbd] Fehler 2 make[1]: Verzeichnis »/home/pit/BananaPi_debian/output/linux-mainline« wird verlassen make: *** [default] Fehler 2 cp: der Aufruf von stat für »/home/pit/BananaPi_debian/output/usb-redirector-linux-arm-eabi/files/modules/src/tusbd/tusbd.ko“ ist nicht möglich: Datei oder Verzeichnis nicht gefunden make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -C /home/pit/BananaPi_debian/output/linux-mainline/ M=/home/pit/BananaPi_debian/output/rt8192cu modules make[1]: Verzeichnis »/home/pit/BananaPi_debian/output/linux-mainline« wird betreten Regards, Pit

Hello, I'm using a BananaPi and just tried the latest version (10.6.2015, Linux 4.0.5) of your great distribution. Unfortunately, support for ath9k_htc based USB Wifi adapters seems to be missing, which is crucial for me. (ath9k_htc works great using free and open source firmware.) Could you please add support for this kind of hardware for future releases or give me a hint how I could add support to your existing images? Thank you and kind regards, LINMOB

Some final words. I have R1 powered by two power supplies, microUSB current is 329mA and battery connector 658mA. SATA disk works with new kernel now. But I am still unhappy with wifi. When I use wifi only for my laptop and printer, everything works fine. But when I enable wifi to my neighbours, they are walking around with phones, tablets etc., wifi starts to be very, very slow, unusable. Everything works fine with external wifi from TP-LINK (WN722N), but the onboard wifi has this issue.

GOT IT !!! It was the f***ed-up rtc indeed! Let me explain: I simplified my experiment from above: - installed debian-3.8-wheezy-3.4.107 --> ok (eth0 is ok, ping heise.de works) - survives reboot / halt and power-on / halt and dis-/reconnect power --> everything ok Then upgrade to kernel 4.0.5 as described in your faq and then: - reboot --> System boots till login screen (!!!) but eth0 isn't set up! No ping possible! dmesg | grep rtc 2085-06-25 (NOT ok) date Fr 20. Mai 13:37:52 CET 1949 (NOT ok) hwclock --show hwclock: The Hardware Clock registers contain values that are either invalid (e.g. 50th day of month) or beyond the range we can handle (e.g. Year 2095). So, all date/time and clocks are wrong! Now I've set the correct date manually: date -s "25 JUN 2015 21:00:10" date ok! But hwclock / rtc is still going wrong: hwclock --show (NOT ok) So, I've now set hwclock to system date via: hwclock --systohc --localtime And voilà : hwclock --show --> ok (!) reboot --> eth0 comes up !!!! ping ok! date --> ok hwclock --show --> ok halt and power on date : ok ping ok halt power dis-reconmnect --> ok Then I removed sdcard, copied debian-4.0-wheezy-4.1 on it, put it back in and reset And.................. Tatataaaaaaa, it doesn't complain about rtc, it recognizes eth0 and boots normally! Repeated that with new installation of debian 3.9-jessie-4.0.5, also works like a charm! I'm happy! Hope, that this is helpful for you other guys, too!!!

@cibomato: As I wrote earlier Ubuntu-3.9-4.0.5 and Debian-3.9-jessie-4.0.5 doesn't boot on my Cubietruck. I also tested Debian-4.0-wheezy-4.1.0 which also does not boot. I tried also by cutting the power but no results.

Yes, already understand this. I'm thought that when run "nand-sata-install" from SD-card and choice install rootfs to HDD, bootloader will be installed to NAND. It's not true, bootloader will be on SD-card. Please add to FAQ: If you want boot from NAND (not from SD card) you must run "nand-sata-install" twice: 1 - install from SD-card to NAND 2 - then remove SD-card, boot from NAND and run "nand-sata-install" second time. Only if you connect USB <-> serial converter (3.3v ONLY!) to UART0 then press any key when see "Hit any key to stop autoboot". Not working if you will be using keyboard and monitor.

Cubietruck_Debian_3.8_wheezy_3.4.107 working fine for me but can't boot from SSD. After nand-sata-install rootfs on SSD but booting only from SD-card. Disconnect battery and AC power adaptor but 4.1 still not booting...

U-boot. If u-boot doesn't properly bring up the Ethernet it won't work. I made one boot test with fresh SD card. In first try it failed to initialize but than I cut power (reset might not be enough) and boot again without a problem. Wheezy with kernel 4.1 from the post above. It's working for me. If you won't be able to boot this image we need to figure out why.

Thx, now I power one R1 this way. Works like a charm. I added description/picture to the sunxi wiki: http://linux-sunxi.org/Lamobo_R1