Search the Community

So I've gone ahead and got an Orange Pi PC. I've already been using a few Raspberry Pi boards, as well as the Odroid C2. I wanted to see what the Orange looks like in comparison. It fails to boot properly. I've read a few things around the web, tried the official as well as a few of the Loboris images, including the Raspbian, Jessie and Slackware ones; used the newer script.bin and uImages, etc. But still no go. The board isn't dead, the power LED and the other 2 LEDs near the ethernet port light up. I get activity through the debug serial port, but that's about it. No image through the HDMI, no DHCP request to my router (I connected it through a wired connection, so I eliminate any wifi variables). Here's what I get through the serial port: HELLO! BOOT0 is starting! boot0 version : 4.0.0 fel_flag = 0x00000000 rtc[0] value = 0x00000000 rtc[1] value = 0x00000000 rtc[2] value = 0x00000000 rtc[3] value = 0x00000000 rtc[4] value = 0x00000000 rtc[5] value = 0x00000000 rtc[6] value = 0x00000000 rtc[7] value = 0x00000000 DRAM DRIVE INFO: V0.8 DRAM Type = 3 (2:DDR2,3:DDR3,6:LPDDR2,7:LPDDR3) DRAM CLK = 672 MHz DRAM zq value: 003b3bfb READ DQS LCDL = 001e1e1e DRAM SIZE =1024 M odt delay dram size =1024 card boot number = 0 card no is 0 sdcard 0 line count 4 [mmc]: mmc driver ver 2014-12-10 21:20:39 [mmc]: ***Try SD card 0*** [mmc]: SD/MMC Card: 4bit, capacity: 15193MB [mmc]: vendor: Man 00035344 Snr 53a94a68 [mmc]: product: SL16G [mmc]: revision: 8.0 [mmc]: ***SD/MMC 0 init OK!!!*** sdcard 0 init ok The size of uboot is 000dc000. sum=ede66ee7 src_sum=ede66ee7 Succeed in loading uboot from sdmmc flash. Ready to disable icache. Jump to secend Boot. SUNXI_NORMAL_MODE [ 0.358]e mode U-Boot 2011.09-rc1 (Jun 21 2015 - 19:33:17) Allwinner Technology [ 0.366]version: 1.1.0 normal mode [ 0.373]pmbus: ready not set main pmu id axp_probe error [ 0.388]PMU: pll1 1200 Mhz,PLL6=600 Mhz AXI=400 Mhz,AHB=200 Mhz, APB1=100 Mhz sid read already fel key new mode run key detect no key found no key input dram_para_set start dram_para_set end normal mode [ 0.418]DRAM: 1 GiB relocation Offset is: 35af9000 [box standby] read rtc = 0x0 [box_start_os] mag be start_type no use user_gpio config user_gpio ok gic: normal or no secure os mode workmode = 0 MMC: 0 [ 0.493][mmc]: mmc driver ver 2014-12-10 9:23:00 [ 0.498][mmc]: get sdc_phy_wipe fail. [ 0.502][mmc]: get sdc0 sdc_erase fail. [ 0.506][mmc]: get sdc_f_max fail,use default 50000000Hz [ 0.511][mmc]: get sdc_ex_dly_used fail,use default dly [ 0.517][mmc]: SUNXI SD/MMC: 0 [ 0.530][mmc]: *Try SD card 0* [ 0.574][mmc]: CID 0x3534453 0x4c313647 0x8053a94a 0x6800fbe1 [ 0.579][mmc]: mmc clk 50000000 [ 0.583][mmc]: SD/MMC Card: 4bit, capacity: 15193MB [ 0.588][mmc]: boot0 capacity: 0KB,boot1 capacity: 0KB [ 0.593][mmc]: ***SD/MMC 0 init OK!!!*** [ 0.602][mmc]: erase_grp_size:0x1WrBlk * 0x200 = 0x200 Byte [ 0.607][mmc]: secure_feature 0x0 [ 0.611][mmc]: secure_removal_type 0x0 [ 0.615]sunxi flash init ok script config pll_de to 864 Mhz Not Found clk pll_video1 in script script config pll_video to 297 Mhz [boot]disp_init_tv [DISP_TV] disp_init_tv enter g_tv_used screen 0 do not support TV TYPE! [BOOOT_DISP_TV] disp tv device_registered unable to find regulator vcc-hdmi-18 from [pmu1_regu] or [pmu2_regu] enable power vcc-hdmi-18, ret=-1 DRV_DISP_Init end boot_disp.auto_hpd=1 auto hpd check has 100 times! auto check no any connected, the output_type is 4 [disk_read_fs] no the partition error: open disp_rsl.fex, maybe it is not exist not support this mode[4], use inline mode[4] attched ok, mgr0<-->device0, type=4, mode=4---- ready to set mode [ 1.998]finally, output_type=0x4, output_mode=0x4, screen_id=0x0, disp_para=0x0 fail to find part named env Using default environment In: serial Out: serial Err: serial --------fastboot partitions-------- mbr not exist base bootcmd=run setargs_mmc boot_normal bootcmd set setargs_mmc key 0 cant find rcvy value cant find fstbt value no misc partition is found to be run cmd=run setargs_mmc boot_normal [ 2.035][mmc]: MMC Device 2 not found [ 2.039][mmc]: Can not find mmc dev [ 2.042][mmc]: read first backup failed in fun sdmmc_secure_storage_read line 1849 sunxi_secstorage_read fail get secure storage map err the private part isn't exist WORK_MODE_BOOT adver not need show sunxi_bmp_logo_display [disk_read_fs] no the partition error: open bootlogo.bmp, maybe it is not exist sunxi bmp info error : unable to open logo file bootlogo.bmp [ 2.075]Hit any key to stop autoboot: 0 ## Booting kernel from Legacy Image at 40007800 ... Image Name: Linux-3.4.39 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 10915552 Bytes = 10.4 MiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK [ 5.983][mmc]: MMC Device 2 not found [ 5.987][mmc]: mmc not find,so not exit [ 5.991] Starting kernel ... [sun8i_fixup]: From boot, get meminfo: Start: 0x40000000 Size: 1024MB ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1 ion_reserve_common: ion reserve: [0x70000000, 0x80000000]! [ 0.000000] Booting Linux on physical CPU 0 [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.4.39 (boris@UbuntuMate) (gcc version 4.6.3 20120201 (prerelease) (crosstool-NG linaro-1.13.1-2012.02-20120222 - Linaro GCC 2012.02) ) #1 SMP PREEMPT Mon Oct 12 12:02:29 CEST 2015 [ 0.000000] Ignoring tag cmdline (using the default kernel command line) [ 0.000000] bootconsole [earlycon0] enabled [ 0.000000] cma: CMA: reserved 256 MiB at 70000000 [ 0.000000] Memory policy: ECC disabled, Data cache writealloc [ 0.000000] On node 0 totalpages: 262144 Then nothing. That BTW is with the Loboris Raspbian image and new uImage and script.bin; the OPi is attached to a router, but from the router side I see no DHCP request. The microSD card is a class-10 16GB G.Skill brand, and it was used before with both R.Pi and Odroid C2 with no problems. Just to be sure before writing the image I formatted it fresh, then did a thorough check with h2testw and no problems were found. For writing the image I used first w32diskimager in win7, then dd in Linux, but in either case the result is the same. Any ideas about what to do next?

Try to use the words you read when calling a failing command for feeding search engines. It's a missing kernel thingie. And regarding '3.4 repo of Armbian' you should be aware that this doesn't exist. We use the software from Debian/Ubuntu repositories and just a few Armbian specific packages are provided by apt.armbian.com. Next step: Build an own kernel providing the necessary features to play with fat rat (for whatever reasons -- you noticed that ARM is not Intel and that you can avoid the whole issue by choosing wisely where to put the rootfs on?).

martinayotte I have Ethernet, USB and SPI working, see attached patches. I've not communicated with an SPI slave yet, but the clock line is pulsing at 50kHz (set by the dts file) according to my scope. Thanks for the most part to your patches. Hope this helps you. I'm off to figure out GPIO in DTS now woop Edit: There was no DTS GPIO problem, rather a user is an idiot problem. I was using old code that was trying to export GPIO pins that don't physically exist eth-usb-spi-opi-pc-patches.zip

BTW: What about including the f3 package to the list of default packages and introducing 'armbianmonitor -c' (check card)? Would be a bit tricky since we can not allow f3write filling the whole card [1] (might require patching f3write/f3read to be able to specify the size of the test files and adjust this to 100MB instead) and we're not able to test the whole card in this mode but it will rule out 99% of the 'Armbian is unreliable' complaints that are in fact related to faulty SD cards. Seeing the reported sequential write speeds from f3write can also be interesting/frustrating/enlightening (since there exist many cards that show good performance on 75% of the capacity and transfer speeds drop down to a few KB/s on the rest of the capacity) and if we add/install also the iozone3 package and fire up the random I/O tests mentioned here we could provide a simple tool to nail many of the problems related to 'bad storage' down. BTW: 'please provide full boot log' can be translated to recommend 'sudo armbianmonitor -b', reboot, 'sudo armbianmonitor -u' now [1] f3 manual page:

I tried compile the kernel, but i have this issue: "ccache: FATAL: Could not find compiler "arm-linux-gnueabihf-gcc" in PATH" I see diferent post about this, but i can fix it. i use Vbox and use the ubuntu 14.04 of the download that are in the official tutto of ArmBian y tried too on a Debian Jessie and have same problems. Any helps? Armbian building script, http://www.armbian.com | Author: Igor Pecovnik ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── ┌──────────────────────────────────────────────────────────────────────────────┠│ Installing 27 host dependencies... │ │──────────────────────────────────────────────────────────────────────────────│ │ build-essential cpp-4.7-arm-linux-gnueabi cpp-arm-linux-gnueabi │ │ cpp-arm-linux-gnueabihf debian-archive-keyring debian-keyring debootstrap │ │ device-tree-compiler dpkg-dev f2fs-tools g++ g++-4.8 │ │ gcc-4.7-arm-linux-gnueabi gcc-4.7-arm-linux-gnueabi-base │ │ gcc-arm-linux-gnueabi gcc-arm-linux-gnueabihf keyutils libcloog-ppl1 │ │ libdpkg-perl libfile-fcntllock-perl libgcc-4.7-dev-armel-cross │ │ libgcc1-armel-cross libgmpxx4ldbl libgomp1-armel-cross libgssglue1 liblzo2 │ │ libncurses5-dev libnfsidmap2 libppl-c4 libppl13 libssl-dev libstdc++-4.8-d │ │ libtinfo-dev libtirpc1 libusb-1.0-0-dev lzop nfs-common nfs-kernel-server │ │ pigz pkg-config pv qemu-user-static rpcbind u-boot-tools unzip uuid-dev zi │ │ zlib1g-dev │ │ 0 upgraded, 53 newly installed, 0 to remove and 0 not upgraded. │ │ Need to get 98.8 MB of archives. │ │ After this operation, 253 MB of additional disk space will be used. │ │ WARNING: The following packages cannot be authenticated! │ │ aptly E: There are problems and -y was used without --force-yeshe following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9E3E53F19C7DE460 /home/test/lib/general.sh: line 362: update-binfmts: command not found [ o.k. ] Starting Armbian build script [ @host ] [ o.k. ] Building [ Armbian 5.05 Bananapim2 Debian jessie dev ] [ o.k. ] Syncing clock [ host ] [ o.k. ] source downloading [ @host ] [ o.k. ] ... updating [ u-boot ] [ o.k. ] ... updating [ linux-vanilla ] [ o.k. ] ... updating [ sunxi-tools ] [ o.k. ] ... updating [ rt8192cu ] [ o.k. ] ... updating [ sunxi-display-changer ] [ o.k. ] ... updating [ mt7601 ] [ o.k. ] Compiling sunxi tools [ @host & target ] cp: cannot stat ‘fex2bin’: No such file or directory cp: cannot stat ‘bin2fex’: No such file or directory [ o.k. ] Cleaning [ /home/test/sources/u-boot/branchless ] [ o.k. ] Cleaning [ /home/test/sources/linux-vanilla/branchless ] [ o.k. ] Cleaning /home/test/output/debs for [ bananapim2 dev ] [ o.k. ] Started patching process for [ kernel sunxi-dev 4.5.0 ] [ o.k. ] Looking for user patches in [ userpatches/kernel/sunxi-dev ] [ o.k. ] ... 0012-bananapi_r1_dts.patch [ succeeded ] [ o.k. ] ... a20-gmac-txfifo.patch [ succeeded ] [ o.k. ] ... axp20x-sysfs-interface.patch [ succeeded ] [ o.k. ] ... bananapi-codec.patch [ succeeded ] [ o.k. ] ... headers-packing.patch [ succeeded ] [ o.k. ] ... orangepi-mini-codec.patch [ succeeded ] [ o.k. ] ... packaging-dev.patch [ succeeded ] [ o.k. ] ... pcDuino3-nano-codec.patch [ succeeded ] [ o.k. ] ... stmmac-coe-and-bugged-jumbo.patch [ succeeded ] [ o.k. ] Started patching process for [ u-boot u-boot-dev 2016.03 ] [ o.k. ] Looking for user patches in [ userpatches/u-boot/u-boot-dev ] [ o.k. ] ... add-awsom-uboot.patch [ succeeded ] [ o.k. ] ... add-cubieboard4.patch [ succeeded ] [ o.k. ] ... u-boot-02-support-cheap-mmc.patch [ succeeded ] [ o.k. ] Compiling uboot. Please wait. [ 2016.03 ] Armbian building script, http://www.armbian.com | Author: Igor Pecovnik ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── ┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┠│ Compiling u-boot... │ │──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────│ │ ccache: FATAL: Could not find compiler "arm-linux-gnueabihf-gcc" in PATH │ │ ccache: FATAL: Could not find compiler "arm-linux-gnueabihf-gcc" in PATH │ │ dirname: missing operand │ │ Try 'dirname --help' for more information. │ │ scripts/kconfig/conf --silentoldconfig Kconfig │ │ CHK include/config.h │ │ GEN include/autoconf.mk │ │ ccache: FATAL: Could not find compiler "arm-linux-gnueabihf-gcc" in PATH │ │ make[1]: *** [include/autoconf.mk] Error 1 │ │ make: *** No rule to make target `include/config/auto.conf', needed by `include/config/uboot.release'. Stop. │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘ [ o.k. ] Target directory [ /home/test/output/debs/ ] [ o.k. ] Building deb [ linux-u-boot-dev-bananapim2_5.05_armhf.deb ] [ error ] ERROR in function compile_uboot [ common.sh:143 ] [ error ] Building u-boot failed, check configuration [ o.k. ] Process terminated root@ubuntu:/home/test# find / -name 'arm-linux-gnueabihf*' /usr/share/man/man1/arm-linux-gnueabihf-cpp-4.8.1.gz /usr/share/man/man1/arm-linux-gnueabihf-gcc-nm-4.8.1.gz /usr/share/man/man1/arm-linux-gnueabihf-gcov-4.8.1.gz /usr/share/man/man1/arm-linux-gnueabihf-gfortran-4.8.1.gz /usr/share/man/man1/arm-linux-gnueabihf-g++-4.8.1.gz /usr/share/man/man1/arm-linux-gnueabihf-gcc-ranlib-4.8.1.gz /usr/share/man/man1/arm-linux-gnueabihf-gcc-4.8.1.gz /usr/share/man/man1/arm-linux-gnueabihf-gcc-ar-4.8.1.gz /usr/lib/gcc-cross/arm-linux-gnueabihf /usr/arm-linux-gnueabihf /usr/arm-linux-gnueabihf/include/c++/4.8.2/arm-linux-gnueabihf /usr/x86_64-linux-gnu/arm-linux-gnueabihf /usr/bin/arm-linux-gnueabihf-g++-4.8 /usr/bin/arm-linux-gnueabihf-elfedit /usr/bin/arm-linux-gnueabihf-c++filt /usr/bin/arm-linux-gnueabihf-strip /usr/bin/arm-linux-gnueabihf-ld.bfd /usr/bin/arm-linux-gnueabihf-gprof /usr/bin/arm-linux-gnueabihf-gcov-4.8 /usr/bin/arm-linux-gnueabihf-ld /usr/bin/arm-linux-gnueabihf-strings /usr/bin/arm-linux-gnueabihf-gcc-4.8 /usr/bin/arm-linux-gnueabihf-ranlib /usr/bin/arm-linux-gnueabihf-ar /usr/bin/arm-linux-gnueabihf-nm /usr/bin/arm-linux-gnueabihf-addr2line /usr/bin/arm-linux-gnueabihf-objcopy /usr/bin/arm-linux-gnueabihf-ld.gold /usr/bin/arm-linux-gnueabihf-dwp /usr/bin/arm-linux-gnueabihf-gcc-nm-4.8 /usr/bin/arm-linux-gnueabihf-as /usr/bin/arm-linux-gnueabihf-cpp-4.8 /usr/bin/arm-linux-gnueabihf-size /usr/bin/arm-linux-gnueabihf-gcc-ar-4.8 /usr/bin/arm-linux-gnueabihf-gcc-ranlib-4.8 /usr/bin/arm-linux-gnueabihf-readelf /usr/bin/arm-linux-gnueabihf-gfortran-4.8 /usr/bin/arm-linux-gnueabihf-objdump

Commit logs exist This is still work in progress, please do not publish pre-release images since user feedback at this stage isn't helpful (maybe Zador corrects me but I would believe we should first test everything internally and wait for Xenial to be released)

I have armbian jessy desktop, there it is saying WICD NETWORK MANAGER. Is this an old Ubuntu ? I called it pathetic coz it was not responding to whatever tweaks I did to wifi adapter, my phone to connect to an internet. It even showed that I have no connection when Im actually downloading online.,There is this wifi radar gui, even it is not detecting anything .Take one more example of this REMOVABLE DRIVES AND MEDIA GUI, it is so dead. So ,if one has to use this armbian, One has to use the TERMINAL which lacks GUI.I have trouble playing a video 640x342 with the inbuilt mv player.I haven't tried the other players tricks. I also know that this is just in developing stage, so bugs are bound to exist. But at this early stage, its is so awfull.Not that I criticise this development. I KNOW there is a lot of hard working by countless no of people. But all my views pertain to this buggy rom and not armbian itself.If possible plz add the bugs list in this release especially for orange pi pc.Had I known the bugs I must have never tried it.

New line 37 and 138. [[0;32m o.k. [0m] Compiling uboot. Please wait. [[0;33m 2016.01 [0m] HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf # # configuration written to .config # scripts/kconfig/conf --silentoldconfig Kconfig CHK include/config.h GEN include/autoconf.mk GEN spl/include/autoconf.mk GEN include/autoconf.mk.dep CHK include/config/uboot.release CHK include/generated/timestamp_autogenerated.h UPD include/generated/timestamp_autogenerated.h CFG u-boot.cfg CHK include/generated/version_autogenerated.h CC lib/asm-offsets.s CC arch/arm/lib/asm-offsets.s CHK include/generated/asm-offsets.h CHK include/generated/generic-asm-offsets.h HOSTCC tools/gen_eth_addr HOSTCC tools/bmp_logo HOSTCC tools/img2srec HOSTCC tools/mkenvimage.o HOSTCC tools/os_support.o WRAP tools/lib/crc32.c HOSTCC tools/aisimage.o LDS u-boot.lds HOSTCC tools/atmelimage.o WRAP tools/common/bootm.c HOSTCC tools/default_image.o WRAP tools/lib/fdtdec_common.c WRAP tools/lib/fdtdec.c HOSTCC tools/fit_common.o HOSTCC tools/fit_image.o HOSTCC tools/gpimage.o HOSTCC tools/gpimage-common.o WRAP tools/common/image-fit.c HOSTCC tools/image-host.o WRAP tools/common/image.c HOSTCC tools/imagetool.o HOSTCC tools/imximage.o HOSTCC tools/kwbimage.o WRAP tools/lib/md5.c HOSTCC tools/lpc32xximage.o HOSTCC tools/mxsimage.o HOSTCC tools/omapimage.o HOSTCC tools/pblimage.o HOSTCC tools/pbl_crc32.o WRAP tools/lib/rc4.c HOSTCC tools/rkcommon.o HOSTCC tools/rkimage.o HOSTCC tools/rksd.o HOSTCC tools/rkspi.o HOSTCC tools/socfpgaimage.o WRAP tools/lib/sha1.c WRAP tools/lib/sha256.c WRAP tools/common/hash.c HOSTCC tools/ublimage.o HOSTCC tools/zynqimage.o WRAP tools/lib/libfdt/fdt.c WRAP tools/lib/libfdt/fdt_ro.c WRAP tools/lib/libfdt/fdt_rw.c WRAP tools/lib/libfdt/fdt_strerror.c WRAP tools/lib/libfdt/fdt_wip.c WRAP tools/lib/libfdt/fdt_region.c HOSTCC tools/dumpimage.o HOSTCC tools/mkimage.o HOSTCC tools/mksunxiboot HOSTCC tools/proftool HOSTCC tools/fdtgrep.o tools/bmp_logo --gen-info ./tools/logos/denx.bmp > include/bmp_logo.h tools/bmp_logo --gen-data ./tools/logos/denx.bmp > include/bmp_logo_data.h HOSTCC tools/lib/crc32.o HOSTCC tools/common/bootm.o HOSTCC tools/lib/fdtdec_common.o HOSTCC tools/lib/fdtdec.o HOSTCC tools/common/image-fit.o HOSTCC tools/common/image.o HOSTCC tools/lib/md5.o HOSTCC tools/lib/rc4.o HOSTCC tools/lib/sha1.o HOSTCC tools/lib/sha256.o HOSTCC tools/common/hash.o HOSTCC tools/lib/libfdt/fdt.o HOSTCC tools/lib/libfdt/fdt_ro.o HOSTCC tools/lib/libfdt/fdt_rw.o HOSTCC tools/lib/libfdt/fdt_strerror.o HOSTCC tools/lib/libfdt/fdt_wip.o HOSTCC tools/lib/libfdt/fdt_region.o HOSTLD tools/mkenvimage HOSTLD tools/dumpimage HOSTLD tools/mkimage HOSTLD tools/fdtgrep LD arch/arm/cpu/built-in.o CC arch/arm/cpu/armv7/cache_v7.o CC board/sunxi/board.o AS arch/arm/lib/vectors.o CC board/sunxi/gmac.o CC arch/arm/cpu/armv7/cpu.o LD board/sunxi/built-in.o CC arch/arm/cpu/armv7/cp15.o AS arch/arm/lib/crt0.o CC arch/arm/cpu/armv7/syslib.o AS arch/arm/cpu/armv7/lowlevel_init.o AS arch/arm/lib/relocate.o AS arch/arm/cpu/armv7/nonsec_virt.o CC arch/arm/lib/bootm-fdt.o CC arch/arm/lib/bootm.o CC arch/arm/cpu/armv7/virt-v7.o CC arch/arm/lib/sections.o CC arch/arm/cpu/armv7/virt-dt.o CC arch/arm/lib/stack.o CC arch/arm/lib/interrupts.o AS arch/arm/cpu/armv7/psci.o CC common/init/board_init.o CC arch/arm/lib/reset.o LD common/init/built-in.o CC arch/arm/lib/cache.o CC common/main.o CC arch/arm/cpu/armv7/sunxi/timer.o CC arch/arm/lib/cache-cp15.o CC arch/arm/cpu/armv7/sunxi/board.o AR arch/arm/lib/lib.a CC common/exports.o CC arch/arm/cpu/armv7/sunxi/clock.o CC arch/arm/lib/eabi_compat.o LD arch/arm/lib/built-in.o CC common/hash.o CC arch/arm/cpu/armv7/sunxi/cpu_info.o CC arch/arm/cpu/armv7/sunxi/dram_helpers.o CC common/cli_hush.o CC arch/arm/cpu/armv7/sunxi/pinmux.o CC arch/arm/cpu/armv7/sunxi/usb_phy.o CC common/autoboot.o CC arch/arm/cpu/armv7/sunxi/prcm.o CC arch/arm/cpu/armv7/sunxi/p2wi.o CC arch/arm/cpu/armv7/sunxi/clock_sun6i.o CC common/board_f.o CC common/board_r.o CC arch/arm/cpu/armv7/sunxi/tzpc.o CC common/cmd_boot.o CC arch/arm/cpu/armv7/sunxi/pmic_bus.o CC common/cmd_bootm.o CC common/bootm.o AS arch/arm/cpu/armv7/sunxi/psci_sun6i.o CC common/bootm_os.o CC common/cmd_help.o LD arch/arm/cpu/armv7/sunxi/built-in.o CC common/cmd_version.o AS arch/arm/cpu/armv7/start.o CC common/env_attr.o CC common/env_callback.o CC common/env_flags.o LD arch/arm/cpu/armv7/built-in.o CC common/env_mmc.o CC common/cmd_source.o CC disk/part.o CC common/cmd_bdinfo.o CC disk/part_dos.o CC common/cmd_console.o CC common/cmd_echo.o CC disk/part_efi.o CC common/cmd_elf.o CC common/cmd_exit.o CC common/cmd_ext4.o LD disk/built-in.o CC common/cmd_ext2.o CC common/cmd_fat.o CC common/cmd_fdt.o CC common/fdt_support.o LD drivers/dma/built-in.o LD drivers/adc/built-in.o CC common/cmd_fs.o CC drivers/gpio/gpio-uclass.o LD drivers/block/built-in.o CC common/cmd_gpio.o CC drivers/gpio/sunxi_gpio.o CC common/cmd_itest.o CC drivers/core/device.o LD drivers/gpio/built-in.o CC common/cmd_load.o CC drivers/core/lists.o CC drivers/core/root.o CC drivers/core/uclass.o CC drivers/core/util.o CC common/cmd_mem.o CC drivers/core/device-remove.o CC common/miiphyutil.o CC drivers/crypto/fsl/sec.o CC drivers/core/simple-bus.o CC common/cmd_mii.o LD drivers/crypto/fsl/built-in.o CC drivers/core/dump.o LD drivers/crypto/rsa_mod_exp/built-in.o CC common/cmd_mdio.o LD drivers/core/built-in.o LD drivers/crypto/built-in.o LD drivers/dfu/built-in.o CC common/cmd_misc.o LD drivers/hwmon/built-in.o CC drivers/input/keyboard-uclass.o LD drivers/memory/built-in.o CC common/cmd_mmc.o LD drivers/misc/built-in.o CC drivers/input/input.o CC common/cmd_net.o CC drivers/pcmcia/tqm8xx_pcmcia.o CC drivers/input/key_matrix.o CC common/cmd_part.o LD drivers/pcmcia/built-in.o LD drivers/input/built-in.o CC common/cmd_pcmcia.o CC common/cmd_pxe.o LD drivers/pwm/built-in.o CC common/cmd_setexpr.o CC common/cmd_test.o CC common/cmd_usb.o CC drivers/rtc/date.o CC common/usb.o LD drivers/rtc/built-in.o CC common/usb_hub.o LD drivers/soc/built-in.o LD drivers/sound/built-in.o LD drivers/thermal/built-in.o CC common/usb_storage.o LD drivers/timer/built-in.o LD drivers/tpm/built-in.o LD drivers/twserial/built-in.o CC common/cmd_ximg.o CC drivers/video/cfb_console.o LD drivers/watchdog/built-in.o CC common/iomux.o CC common/flash.o CC common/edid.o CC common/splash.o CC common/menu.o CC drivers/video/sunxi_display.o CC drivers/video/videomodes.o CC common/usb_kbd.o LD drivers/video/bridge/built-in.o LD drivers/video/built-in.o CC common/cmd_nvedit.o LD drivers/built-in.o LD drivers/i2c/built-in.o CC common/env_common.o CC drivers/mmc/mmc.o LD drivers/mtd/built-in.o CC drivers/mmc/sunxi_mmc.o CC common/console.o CC drivers/mmc/mmc_write.o CC common/dlmalloc.o LD drivers/mtd/onenand/built-in.o LD drivers/mmc/built-in.o CC common/malloc_simple.o CC common/image.o LD drivers/mtd/spi/built-in.o CC common/image-fdt.o CC common/memsize.o CC drivers/net/designware.o CC common/stdio.o CC common/cli_simple.o LD drivers/net/built-in.o CC common/cli.o CC common/cli_readline.o CC drivers/net/phy/phy.o CC common/command.o CC common/s_record.o LD drivers/net/phy/built-in.o CC common/xyzModem.o CC common/cmd_disk.o LD drivers/pci/built-in.o LD common/built-in.o LD drivers/power/battery/built-in.o CC drivers/power/axp221.o LD drivers/power/built-in.o LD drivers/power/fuel_gauge/built-in.o LD drivers/power/mfd/built-in.o LD drivers/power/pmic/built-in.o LD drivers/power/regulator/built-in.o CC drivers/serial/serial-uclass.o CC drivers/spi/spi.o LD drivers/usb/dwc3/built-in.o CC drivers/serial/ns16550.o LD drivers/spi/built-in.o LD drivers/serial/built-in.o LD drivers/usb/emul/built-in.o LD drivers/usb/eth/built-in.o LD drivers/usb/gadget/built-in.o LD drivers/usb/gadget/udc/built-in.o CC drivers/usb/host/usb-uclass.o LD drivers/usb/musb/built-in.o CC drivers/usb/host/ohci-hcd.o LD drivers/usb/phy/built-in.o LD drivers/usb/ulpi/built-in.o CC drivers/usb/host/ohci-sunxi.o CC drivers/usb/host/ehci-hcd.o CC drivers/usb/host/ehci-sunxi.o LD drivers/usb/host/built-in.o CC fs/fs.o LD drivers/usb/musb-new/built-in.o CC fs/ext4/ext4fs.o CC fs/ext4/ext4_common.o CC net/checksum.o CC fs/ext4/dev.o CC net/arp.o CC lib/libfdt/fdt.o LD fs/ext4/built-in.o CC net/bootp.o CC lib/libfdt/fdt_ro.o CC lib/libfdt/fdt_rw.o CC fs/fat/fat_write.o CC net/eth.o CC lib/libfdt/fdt_strerror.o CC fs/fat/file.o CC lib/libfdt/fdt_sw.o CC net/net.o CC lib/libfdt/fdt_wip.o LD fs/fat/built-in.o CC net/nfs.o LD fs/built-in.o CC lib/libfdt/fdt_empty_tree.o CC net/ping.o CC lib/libfdt/fdt_addresses.o LD test/built-in.o CC lib/libfdt/fdt_region.o CC net/tftp.o CC test/dm/cmd_dm.o LD lib/libfdt/built-in.o LD net/built-in.o CC lib/crc7.o LD test/dm/built-in.o CC lib/zlib/zlib.o CC lib/crc8.o CC lib/crc16.o CC lib/fdtdec.o CC lib/fdtdec_common.o LD lib/zlib/built-in.o CC lib/gunzip.o CC lib/initcall.o CC lib/lmb.o CC lib/ldiv.o CC lib/net_utils.o CC lib/qsort.o CC lib/rc4.o CC lib/list_sort.o CC lib/strmhz.o CC lib/hashtable.o CC lib/errno.o CC lib/display_options.o CC lib/crc32.o CC lib/ctype.o CC lib/div64.o CC lib/hang.o CC lib/linux_compat.o CC lib/linux_string.o CC lib/membuff.o CC lib/slre.o CC lib/string.o CC lib/time.o CC lib/uuid.o CC lib/vsprintf.o CC lib/panic.o CC lib/strto.o LD lib/built-in.o CC examples/standalone/stubs.o CC examples/standalone/hello_world.o LD examples/standalone/libstubs.o LD examples/standalone/hello_world OBJCOPY examples/standalone/hello_world.srec OBJCOPY examples/standalone/hello_world.bin LD u-boot OBJCOPY u-boot.bin DTC arch/arm/dts/sun6i-a31-app4-evb1.dtb OBJCOPY u-boot.srec DTC arch/arm/dts/sun6i-a31-colombus.dtb DTC arch/arm/dts/sun6i-a31-hummingbird.dtb DTC arch/arm/dts/sun6i-a31-i7.dtb DTC arch/arm/dts/sun6i-a31-m9.dtb DTC arch/arm/dts/sun6i-a31-mele-a1000g-quad.dtb DTC arch/arm/dts/sun6i-a31-mixtile-loftq.dtb DTC arch/arm/dts/sun6i-a31s-cs908.dtb DTC arch/arm/dts/sun6i-a31s-primo81.dtb DTC arch/arm/dts/sun6i-a31s-sinovoip-bpi-m2.dtb MKIMAGE u-boot.img SHIPPED dts/dt.dtb CAT u-boot-dtb.bin COPY u-boot.dtb MKIMAGE u-boot-dtb.img LD spl/arch/arm/cpu/built-in.o CC spl/board/sunxi/board.o AS spl/arch/arm/lib/vectors.o CC spl/arch/arm/cpu/armv7/cache_v7.o CC spl/board/sunxi/gmac.o CC spl/arch/arm/cpu/armv7/cpu.o LD spl/board/sunxi/built-in.o AS spl/arch/arm/lib/crt0.o CC spl/arch/arm/cpu/armv7/cp15.o CC spl/common/spl/spl.o CC spl/arch/arm/lib/spl.o CC spl/arch/arm/cpu/armv7/syslib.o CC spl/arch/arm/lib/sections.o AS spl/arch/arm/cpu/armv7/lowlevel_init.o CC spl/arch/arm/lib/stack.o CC spl/arch/arm/lib/interrupts.o AS spl/arch/arm/cpu/armv7/nonsec_virt.o CC spl/arch/arm/lib/reset.o CC spl/arch/arm/lib/cache.o CC spl/arch/arm/cpu/armv7/virt-v7.o CC spl/arch/arm/lib/cache-cp15.o CC spl/arch/arm/cpu/armv7/virt-dt.o CC spl/common/spl/spl_mmc.o AR spl/arch/arm/lib/lib.a AS spl/arch/arm/cpu/armv7/psci.o CC spl/arch/arm/lib/eabi_compat.o LD spl/common/spl/built-in.o LD spl/arch/arm/lib/built-in.o CC spl/common/init/board_init.o LD spl/common/init/built-in.o CC spl/arch/arm/cpu/armv7/sunxi/timer.o CC spl/disk/part.o CC spl/common/cmd_nvedit.o LD spl/disk/built-in.o CC spl/arch/arm/cpu/armv7/sunxi/board.o CC spl/common/env_common.o CC spl/common/console.o CC spl/arch/arm/cpu/armv7/sunxi/clock.o CC spl/common/dlmalloc.o CC spl/common/malloc_simple.o CC spl/arch/arm/cpu/armv7/sunxi/cpu_info.o CC spl/common/image.o CC spl/common/memsize.o CC spl/arch/arm/cpu/armv7/sunxi/dram_helpers.o CC spl/common/stdio.o CC spl/common/cli_simple.o CC spl/arch/arm/cpu/armv7/sunxi/pinmux.o CC spl/common/cli.o CC spl/arch/arm/cpu/armv7/sunxi/usb_phy.o CC spl/common/cli_readline.o CC spl/common/command.o CC spl/arch/arm/cpu/armv7/sunxi/prcm.o CC spl/common/s_record.o CC spl/common/xyzModem.o CC spl/arch/arm/cpu/armv7/sunxi/p2wi.o CC spl/common/cmd_disk.o AS spl/arch/arm/cpu/armv7/start.o LD spl/common/built-in.o CC spl/arch/arm/cpu/armv7/sunxi/clock_sun6i.o CC spl/arch/arm/cpu/armv7/sunxi/tzpc.o CC spl/arch/arm/cpu/armv7/sunxi/pmic_bus.o CC spl/arch/arm/cpu/armv7/sunxi/dram_sun6i.o AS spl/arch/arm/cpu/armv7/sunxi/fel_utils.o CC spl/drivers/gpio/sunxi_gpio.o CC spl/drivers/mmc/mmc.o LD spl/arch/arm/cpu/armv7/sunxi/built-in.o LD spl/drivers/gpio/built-in.o LD spl/arch/arm/cpu/armv7/built-in.o CC spl/drivers/mmc/sunxi_mmc.o LD spl/drivers/mmc/built-in.o CC spl/drivers/power/axp221.o LD spl/drivers/power/pmic/built-in.o LD spl/drivers/power/regulator/built-in.o LD spl/drivers/power/built-in.o CC spl/drivers/serial/serial.o CC spl/drivers/serial/serial_ns16550.o LD spl/dts/built-in.o CC spl/drivers/serial/ns16550.o LD spl/fs/built-in.o LD spl/drivers/serial/built-in.o LD spl/drivers/built-in.o CC spl/lib/hashtable.o CC spl/lib/errno.o CC spl/lib/display_options.o LDS spl/u-boot-spl.lds CC spl/lib/crc32.o CC spl/lib/ctype.o CC spl/lib/div64.o CC spl/lib/hang.o CC spl/lib/linux_compat.o CC spl/lib/linux_string.o CC spl/lib/membuff.o CFG spl/u-boot-spl.cfg CC spl/lib/slre.o CC spl/lib/time.o CC spl/lib/string.o CC spl/lib/vsprintf.o CC spl/lib/panic.o CC spl/lib/strto.o LD spl/lib/built-in.o LD spl/u-boot-spl OBJCOPY spl/u-boot-spl.bin MKSUNXI spl/sunxi-spl.bin CAT u-boot-sunxi-with-spl.bin [[0;32m o.k. [0m] Target directory [[0;33m /home/pibuilder/m2-armbian/output/debs/ [0m] [[0;32m o.k. [0m] Building deb [[0;33m linux-u-boot-next-bananapim2_5.05_armhf.deb [0m] dpkg-deb: error: control directory has bad permissions 2755 (must be >=0755 and <=0775) wc: /home/pibuilder/m2-armbian/output/debs/linux-u-boot-next-bananapim2_5.05_armhf.deb: No such file or directory rm: cannot remove '/home/pibuilder/m2-armbian/output/debs/linux-u-boot-next-bananapim2_5.05_armhf.deb': No such file or directory [[0;31m error [0m] ERROR in function compile_uboot [[0;33m common.sh:146 [0m] [[0;31m error [0m] Building u-boot failed, check configuration [[0;32m o.k. [0m] Process terminated The error is the same as here. http://forum.armbian.com/index.php/topic/693-sunxi-a31s-banana-pi-m2-syntax-error-in-configurationsh/#entry5070

Some of the explanation might be found here ... "NAND is not supported yet." ... however, shouldn't /dev/nand be at least visible as a device ? I tried installing jessie/legacy on a microSD card, but when I boot from it, I can only log in as root, and all I can do is change the password from 1234 to whatever I desire, then I'm logged out. This repeats as often as I log in. -So I've decided to go for jessie/vanilla and hope for nand support. -This is the only real problem I've had. I've had great success with moving Armbian to the SATA harddisk using the nand-sata-install script (note: if you have more than 4 devices, they *are* listed in the box; just scroll using the down-arrow key). I've also moved /var and /home to their own partitions (along with a few others). I'm also using UUID= in fstab instead of /dev/sd??*

No, you are'nt too naive, it's just linux which takes too dinosauric approaches with monolithic kernel (and overall model, the model of lacking any model) that turns all this situation into such a mess. You asked a reasonable question, I am an NT guy not linux one, and I was always wondering why the hell the situation around these sbc's, mostly powered by linux, why it is so abysmal, with all those bunches of variants of bunches of distros (images, bsp's) every of which is made for the only board, and not working anyway easily there, not to mention being compatible to some other even very related board (often even with the same SoC on the board). Supposed to be compatible it is turned out to be as incompatible as possible and so for example some image for cubieboard with no chance would run on some banana or whatever. It's the most reasonable thinking - why the situation isn't as it is with desktop Windows, when you have the same set of kernel images and then, after installing them, you do add all needed drivers from the vendor. And that's all. It works. Without any freaking recompiling, patching and actually redisigning. But how many different motherboard vendors, models, variants exist? There is even more diversity over there, because there is no single SoC chip on the board which encapsulates a plenty of peripheral controllers on it, helping with unification. There, we see discrete CPU, chip set, GPU, and other controllers which all vary. Even though, we see, there is no such a problem as is here, in the arm sbc landscape, where you inevitably will face with awful and numerous incompatibility issues. And mostly they are due to linux poorly thought designed crossplatforminess. it just isn't a good constructor for a vendor to play with. The only thing it has is its open sourceness. But at the level of architecture, internal API's, driver models... what driver model? It is very chaotic and as a consequense mediocre both at the dimension of easiness of porting, bringing to a new device, and at the dimension of quality. never mind what are saying its fans. you just see it by the reality and the fact such questions as yours appear, only proves this. Anyway I'm definitely have begun wrong way on the linux lovers site with linux bushing. Sorry for this, I won't do it anymore xD it's just the TS question, it was so close to me! I couldn't resist myself to add my own 5 cents. I am ineterested in arm (particularly) sbc's and in system development on them. I has come here to read mostly. there is useful information on the topic for me here, since the guys do a great deal of work and I definitely have something to learn from their working communication. Even if my work isn't related to linux. I'm going to be a non-visible reader, so, sorry for kind of flame again.

You don't need to edit anything in lib/ directly. In fact it's better that you reset or remove lib directory so your changes don't prevent pulling future updates. You shoud use "customize-image.sh" conviniently (auto) copied to "userpatches/". Because it is copied only if it doesn't exist already, your changes in lib/scripts didn't have any effect. Yes, git should be installed at this point.

This is not entirely true since there exist some very nice examples of cross site scripting attacks that work very well in such 'behind NAT in secured private LAN' (a malicious website modifies router settings from within the internal net for example). Best practice therefore should be to separate access by using different browsers for different purposes. Only using a browser to access such internal insecure web apps that has no access to the outside will prevent XSS attacks (yeah, very unlikely that anyone attacks your Cubieboard but at least for routers and other stuff that have a web interface like switches, NAS and so on, this should be a requirement). Apart from that thx for the nice tutorial! It should be noted that the whole thing works not only on A10/A20 but with any board after the GPIO pin mappings have been defined.

Ok, this is useful from a 'user experience' point of view. As soon as you get the green led working please drop us a note, we will switch the behaviour of both leds (I also believe it would make some sense if our projects coordinate a bit regarding user experiences) Great! If you want to go the extra mile think about submitting it upstream. You will learn a lot but it might also cause a 'bit' of frustration And another problem might be that you would have to rebase your patch since AFAIK there exist currently a few different WiP branches for H3 upstream.

after changing the check_first_login.sh it works somehow. Here the terminal output: root@192.168.178.30's password: -bash: /var/log/user-creation.log: Read-only file system Thank you for choosing Armbian! Support: www.armbian.com Creating new account. Please provide a username (eg. your forename): achilles Adding user `achilles' ... Adding new group `achilles' (1000) ... groupadd: cannot lock /etc/group; try again later. adduser: `/usr/sbin/groupadd -g 1000 achilles' returned error code 10. Exiting. usermod: user 'achilles' does not exist usermod: user 'achilles' does not exist usermod: user 'achilles' does not exist usermod: user 'achilles' does not exist usermod: user 'achilles' does not exist usermod: user 'achilles' does not exist rm: cannot remove ‘/root/.not_logged_in_yet’: Read-only file system Dear , your account achilles has been created and is sudo enabled. Please use this account for your daily work from now on. root@bananapipro:~# It looks like that system booted in RO mode: root@bananapipro:/boot# mount /dev/mmcblk0p1 on / type ext4 (ro,relatime,data=ordered) devtmpfs on /dev type devtmpfs (rw,relatime,size=505360k,nr_inodes=126340,mode=755) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=23,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) mqueue on /dev/mqueue type mqueue (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime,size=262144k) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=102744k,mode=700) and dmesg: [ 8.282663] systemd-udevd[160]: starting version 215 [ 8.299699] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Apr 22 2013 14:50:00 version 5.90.195.89.6 FWID 01-b30a427d [ 8.315395] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 8.964878] sun4i-ss 1c15000.crypto-engine: no reset control found [ 8.966448] sun4i-ss 1c15000.crypto-engine: Die ID 0 [ 9.218466] sun7i-dwmac 1c50000.ethernet: no reset control found [ 9.218493] Ring mode enabled [ 9.218503] No HW DMA feature register supported [ 9.218510] Normal descriptors [ 9.218516] TX Checksum insertion supported [ 9.263874] libphy: stmmac: probed [ 9.263907] eth0: PHY ID 001cc915 at 0 IRQ POLL (stmmac-0:00) active [ 9.263917] eth0: PHY ID 001cc915 at 1 IRQ POLL (stmmac-0:01) [ 9.267169] sun4i-codec 1c22c00.codec: Codec <-> 1c22c00.codec mapping ok [ 14.729415] EXT4-fs (mmcblk0p1): Cannot change data mode on remount [ 15.095964] systemd-journald[161]: Received request to flush runtime journal from PID 1 [ 15.550204] RX IPC Checksum Offload disabled [ 15.550236] No MAC Management Counters available [ 21.537749] sun7i-dwmac 1c50000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx root@bananapipro:/boot# because RO filesystem, not possible to create logfile.

Hm.. I'll write to you what I have done. Please tell me what's wrong. I have a cubietruck, and I downloaded this one, Legacy Jessie(http://mirror.igorpecovnik.com/Armbian_5.00_Cubietruck_Debian_jessie_3.4.110.zip), and installed it. Install was successful, and worked good. I tried to use nand and SD, and SD only. There were no differences. The result that I want to tell you below, is the same on both cases. ......................... After OS install, I followed this instruction, and I installed several packages. Instruction : wget -q -O - http://upgrade.armbian.com | bash Packages : NFS server Samba server Deluge Daemon(server) I have a 3TB sata disk with External Sata Interface Case, so I connected it. The external case has it's own power. By the way, I've been using Volumio 1.5 (https://volumio.org/) for CubieTruck for a long time, and it has worked very good. When I connect the 3TB disk to Cubietruck, it was usually mounted with read only. However I did not mean to do that. I used this on /etc/fstab, UUID=xxxx-xxx-xxxx-xxx /mnt/Big_Storage ext4 defaults 0 2 or /dev/sda1 /mnt/Big_Storage ext4 defaults 0 2 The results are same, sometimes mounted read only, few times mounted ok, and everytime file system cracks. I have to manully fix the system with fsck.ext4 -y -v -C 0 /dev/sda1. fsck could fix the problem, but I lost some of my data. The report is like this. 3TB_Drive: ***** FILE SYSTEM WAS MODIFIED ***** 234152 inodes used (0.13%, out of 183148544) 11690 non-contiguous files (5.0%) 36 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 13/13/14 Extent depth histogram: 232917/1204 463810814 blocks used (63.31%, out of 732566272) 0 bad blocks 145 large files 210620 regular files 23498 directories 2 character device files 9 block device files 3 fifos 30049 links 7 symbolic links (3 fast symbolic links) 4 sockets ------------ 264191 files I think that Volumio(1.5) is based on Jessie too, but it did not happen everytime. Volumio also sometimes made the file system broken, but not always. I'm trying to install Trusty Legary version.... Can you find out what was the problem? Please help me. Thanks in advance! PS. 1. I tried Ubuntu Trusty version, and it works fine, at least for 2 hours, with several reboots and power off/on. 2. I've got this message when it boots. : *** Warning - bad CRC, using default environment. But it seems to be working fine. Can I ignore this?

Thanks. Recently I reviewed your fex files for One. Could you please not remove extra USB settings from OPiOne/Lite fex files? Those USBs exist on the PCB and I plan in the future to solder mini WiFi dongle directly to data lines (because I don't want to wait for Lite release). I have a question - how to read from the system current CPU voltage? Is it available anywhere in /sys/class*?

There's the wrong u-boot running (U-Boot 2011.09-rc1 (Jun 21 2015 - 19:46:23) Allwinner Technology) therefore boot.src will never be read? AFAIK this u-boot will tell the kernel to search on /dev/mmcblk0p2 for the rootfs (default with all Xunlong and loboris images) and that does not even exist in our default images.

hello, Exist a way to install armbian on my A13-OLinuXino-WIFI ? Best Regards

Ok, so you're not talking about chip temperatures but readouts from a thermal sensor somewhere inside a chip that are interpreted by a driver and that might be somewhat off directly after booting? Good luck trying to solve software/calibration issues with a heatsink To stop this useless discussion: Use cpuburn-a7 for several minutes, check the temperature readout (and keep in mind that it's still uncalibrated since no one did the work to do calibration for A20) and check the real temperature on the chip's surface. As I already tried to point out: the A20 is from a different SoC generation, the contained thermal sensor is part of a touch screen controller and more included by accident than by design. That's different on more recent SoCs like the H3: They contain a thermal sensor by design to prevent overheating and to be used for cooling strategies (throttling, disabling CPU cores). And even with these sensors that are way more reliable than the one in A20 we have calibration problems. Don't trust in numbers generated by software! Regarding toys you started with the RPi Zero. Always out of stock, if not you have to order an expensive bundle containing a bunch of crap and you're limited to one piece per order: https://shop.pimoroni.com/products/pi-zero-complete-starter-kit And if you're not a tinkerer/maker you can't do anything with a 'Zero' except of using it as a very slow desktop without connections to the outside. I'm talking about IoT/controller stuff where I need connectivity (Ethernet, USB), a few sensors (SPI, I2C, maybe 1-Wire) and sometimes also performance. And I need to get this up and running quickly and reliably. The board in question doesn't matter that much if it has the necessary features and is supported by my distro of choice: Armbian. Now we can also use cheap Orange Pis too (hardware quality is good, software/support from the vendor sucks -- but the latter doesn't matter at all fortunately) And BTW: You should really open your eyes and realise that there exist more than 3-5 SBC manufacturers in this world

Ethernet works with kernel 3.4.x. Mainline driver for Ethernet in H3 (same as in A64 and A83T -- Allwinner chose a new IP block compared to the older SoCs) will be ready in a few weeks. And USB-to-Ethernet adapters do exist if you want to use mainline kernel right now with the One or PC or any other H3 device. The heatsinks are mine, if you get an Orange Pi One where voltage switching works as expected no heatsink is necessary -- compare with our latest findings: http://forum.armbian.com/index.php/topic/617-wip-orange-pi-one-support-for-the-upcoming-orange-pi-one/?p=5420 But thx for mentioning heatsinks: I normally use one for A20 (20x20 mm). These fit on the PC but won't fit on the Orange Pi One due to placement of other components. You need heatsinks that do not exceed 16x16 mm in size. But as already said: They're not necessary if you've a board that is not defective (mine is obviously). Regarding RPi Zero: comparing real products with virtual products is not that fair http://whereismypizero.com And it's simply a matter of the use case. For the project we're currently developing the One can always be used instead of the PC when only one USB port is needed (printing/scanning workflow with RFID authentication). You should keep in mind that the Orange Pi One is many times faster than the 'Zero' (important since we're using the device as software RIP converting PDF to primitive PDLs), there Ethernet and USB do not have to share bandwidth and it's also cheaper (when you add shipping costs to the virtual product that no one can buy). Most importantly: Would you use an SBC that is not capable of running Armbian?!

Ok, i'm concerned about the situation that different OS images use different pin definitions (if unfortunate users try a tutorial for RPi and fail on OPi that's one thing but if they follow one for OPi just to realise that they've to check which OS image they use... you get the idea?) I always thought there would a 'common' definition (most probably made by loboris) exist. Already containing of strange exceptions (1-Wire on GPIO connector 37 instead of 7 for example). But I thought it would be a good idea to stay with this since there exist other projects like WiringOP too. Until now I never dig deep into this, I just wanted to avoid reinventing the wheel with Armbian and being incompatible to 'pseudo standards'. And now I'm even more confused I think still we should try to define as much pins as possible like on RPi and maintain compatibility somewhat. But have no idea how... Will try your modifications out next week anyway. In the end it would be nice to have a coloured picture of all 40 pins on the GPIO header with function names that match reality. Unfortunately there's not that much to see (no change the last 10 minutes):

Hello, first I want to thank for the Armbian distribution and the developer tools. "sudo ./compile.sh" complains about a syntax error in configuration.sh. Already up-to-date. Already on 'master' Your branch is up-to-date with 'origin/master'. [ o.k. ] Preparing [ host ] /home/toor/armbian/lib/configuration.sh: line 236: syntax error near unexpected token `)' /home/toor/armbian/lib/configuration.sh: line 236: ` orangepipc)#enabled' [ o.k. ] Starting Armbian build script [ @host ] [ o.k. ] Building [ Armbian 5.00 Bananapim2 Debian jessie next ] [ o.k. ] Syncing clock [ host ] [ o.k. ] source downloading [ @host ] [ o.k. ] ... creating a shallow clone fatal: repository '/home/toor/armbian/sources//branchless' does not exist /home/toor/armbian/lib/general.sh: line 91: cd: /home/toor/armbian/sources//branchless: No such file or directory [ o.k. ] ... creating a shallow clone Seems some ";;" are missing. Greetings, Steve

root@bananapi:~# apt-get install linux-image-next-sunxi Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: linux-image-next-sunxi 1 upgraded, 0 newly installed, 0 to remove and 76 not upgraded. Need to get 13.0 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Get:1 http://apt.armbian.com/ jessie/main linux-image-next-sunxi armhf 5.00 [13. 0 MB] Fetched 13.0 MB in 15s (831 kB/s) (Reading database ... 49566 files and directories currently installed.) Preparing to unpack .../linux-image-next-sunxi_5.00_armhf.deb ... Unpacking linux-image-next-sunxi (5.00) over (4.5) ... Setting up linux-image-next-sunxi (5.00) ... root@bananapi:~# apt-get install linux-dtb-next-sunxi Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: linux-dtb-next-sunxi 1 upgraded, 0 newly installed, 0 to remove and 75 not upgraded. Need to get 63.3 kB of archives. After this operation, 494 kB of additional disk space will be used. Get:1 http://apt.armbian.com/ jessie/main linux-dtb-next-sunxi armhf 5.00 [63.3 kB] Fetched 63.3 kB in 0s (107 kB/s) (Reading database ... 50291 files and directories currently installed.) Preparing to unpack .../linux-dtb-next-sunxi_5.00_armhf.deb ... Unpacking linux-dtb-next-sunxi (5.00) over (4.5) ... Setting up linux-dtb-next-sunxi (5.00) ... root@bananapi:~# blkid /dev/mmcblk0: PTUUID="000380a6" PTTYPE="dos" /dev/mmcblk0p1: UUID="b5d952cd-46ba-4d79-b669-ba961ec9559f" TYPE="ext4" PARTUUID="000380a6-01" /dev/sda1: UUID="38f93141-1d36-434f-9f53-ca0d6916fb0e" TYPE="ext4" PARTUUID="1bd8dd3e-01" root@bananapi:~# reboot Broadcast message from root@bananapi (pts/0) (Sun Feb 14 20:30:48 2016): The system is going down for reboot NOW! root@bananapi:~# login as: root root@192.168.0.8's password: ____ | __ ) __ _ _ __ __ _ _ __ __ _ | _ \ / _` | '_ \ / _` | '_ \ / _` | | |_) | (_| | | | | (_| | | | | (_| | |____/ \__,_|_| |_|\__,_|_| |_|\__,_| Last login: Sun Feb 14 20:26:07 2016 from 192.168.0.100 Load: 0.57, 0.20, 0.07 - Board: 38.9°C - Memory: 966Mb root@bananapi:~# blkid /dev/mmcblk0: PTUUID="000380a6" PTTYPE="dos" /dev/mmcblk0p1: UUID="b5d952cd-46ba-4d79-b669-ba961ec9559f" TYPE="ext4" PARTUUID="000380a6-01" root@bananapi:~# That broke SATA!!

Updated boot.cmd # if you want to boot jessie with systemd: setenv bootargs init=/bin/systemd console=tty1 ... # remember to disable ramlog prior switching to systemd setenv bootargs "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" #-------------------------------------------------------------------------------------------------------------------------------- # Boot loader script to boot with different boot methods for old and new kernel #-------------------------------------------------------------------------------------------------------------------------------- if ext4load mmc 0 0x00000000 /boot/.next || fatload mmc 0 0x00000000 .next then # sunxi mainline kernel #-------------------------------------------------------------------------------------------------------------------------------- ext4load mmc 0 0x49000000 /boot/dtb/sun7i-a20-bananapro.dtb || fatload mmc 0 0x49000000 /dtb/${fdtfile} ext4load mmc 0 0x46000000 /boot/zImage || fatload mmc 0 0x46000000 zImage env set fdt_high ffffffff bootz 0x46000000 - 0x49000000 #-------------------------------------------------------------------------------------------------------------------------------- else # sunxi android kernel #-------------------------------------------------------------------------------------------------------------------------------- ext4load mmc 0 0x43000000 /boot/script.bin || fatload mmc 0 0x43000000 script.bin ext4load mmc 0 0x48000000 /boot/zImage || fatload mmc 0 0x48000000 zImage bootz 0x48000000 #-------------------------------------------------------------------------------------------------------------------------------- fi # Recompile with: # mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr Recompiled root@bananapi:~# mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr Image Name: Created: Sat Feb 13 20:12:46 2016 Image Type: ARM Linux Script (uncompressed) Data Size: 1922 Bytes = 1.88 kB = 0.00 MB Load Address: 00000000 Entry Point: 00000000 Contents: Image 0: 1914 Bytes = 1.87 kB = 0.00 MB root@bananapi:~# root@bananapi:~# root@bananapi:~# reboot Broadcast message from root@bananapi (pts/1) (Sat Feb 13 20:12:49 2016): The system is going down for reboot NOW! root@bananapi:~# login as: root root@192.168.0.8's password: ____ | __ ) __ _ _ __ __ _ _ __ __ _ | _ \ / _` | '_ \ / _` | '_ \ / _` | | |_) | (_| | | | | (_| | | | | (_| | |____/ \__,_|_| |_|\__,_|_| |_|\__,_| Welcome to ARMBIAN Debian GNU/Linux 8 (jessie) 4.4.1-sunxi System load: 1.02 Up time: 50 sec Memory usage: 3 % of 1005Mb IP: 192.168.0.8 CPU temp: 32°C Usage of /: 16% of 7.3G Last login: Sat Feb 13 19:59:37 2016 from 192.168.0.3 root@bananapi:~# blkid /dev/mmcblk0: PTUUID="000380a6" PTTYPE="dos" /dev/mmcblk0p1: UUID="b5d952cd-46ba-4d79-b669-ba961ec9559f" TYPE="ext4" PARTUUID="000380a6-01" Still nothing showing up.

OMG. The requirement to backup databases exists since the day databases have been invented. That's what mysqldump is for (similar solutions/tools exist for every other database daemon in this world). And if you're smart then you use mainline kernel, btfs, snapshots and 'btrfs send/receive' to send consistent backups to another machine with minimal efforts.