Igor

I am using this heat sink on R1 and other A20 boards. It's low profile and low performance. I guess a little better than nothing.

Hey, There different levels of customizations. http://linux-sunxi.org/Fex_Guide A FEX file defines various aspects of how the SoC works. It configures the GPIO pins and sets up DRAM, Display, etc parameters. Having a fex file is usually good enough to boot the board - with kernel 3.4.x. For new (4.x) you will probably need to construct your own device tree. If it's close to Cubieboard 2 than you start with it's source. It might just work out of the box. The same states for u-boot. Board customizations among my script are on system level - firmware loading, extra modules loading, custom repository, custom applications, ... Roughly, if you want to add a new board: 1. Add to menu and choose a dedicated name: (Myboard A20) https://github.com/igorpecovnik/lib/blob/next/main.sh#L27 2. Add an entry to configuration - copy paste cubieboard and use a previously chosen board name https://github.com/igorpecovnik/lib/blob/next/configuration.sh 3. Copy your fex file to lib/config/Myboard.fex ------ From this point - if you can't boot - you need to tweak U-boot configuration and add exceptions - if necessary - to: https://github.com/igorpecovnik/lib/blob/next/boards.sh and to board configuration if you need some special module. If you have any questions just post it here.

And which u-boot did you use? This is most important. Network is not essential at first boot. If we have it we run apt-get update and recreate ssh-keys else not.

if you see a device it's o.k. there is no module because it's build in.

Cedarx is build in all, just define memory reservation and it will start working. Wrote on mobile phone

I can't give you exact answer yet since I am not sure what is causing this. The board just hangs for no apparent reason - it become unresponsive and you must do a hard reboot - in one hour or in two weeks. Most likely it's an issue with U-boot loader. At this point I also don't know which is exactly last good build - few months ago for sure. I am having one such board with few months uptime. I think that if you build from current sources it will be o.k. To be sure I am doing long term stress test on several boards. You can find old builds here: http://mirror.igorpecovnik.com I'll rebuild all images and fix the problem when I get back from vacations in cca. 10 days.

Ahaa. https://github.com/igorpecovnik/BananaPI-Debian This page should look like this - only links to proper one: https://github.com/igorpecovnik/Cubox-i-Debian This configuration is (almost) deprecated. I am clearing this those days but I am temporally on super bad internet connection ... But if you don't specify the board you will be prompted to choose. Use this; https://github.com/igorpecovnik/lib I also wrote a manual two days ago.

Not exactly this way ... you need to select Orange Pi in menu to get a proper board configuration and u-boot. Specially if you need a wifi to be operational. If you don't need wifi a bananapi configuration and image works without a problem. But, motd is independent - it reads various hw data and determine the board.

That's defined in the script armhwinfo located in /etc/init.d Source location: scripts/armhwinfo It's possible that it's not working perfectly yet.

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.

This FAT boot partition is solved half way - scripts need to be adjusted manually, the rest works. I thought I left a note in configuration but I didn't Nice job. btrfs should be resizeable but not with resize2fs so this part is solvable. f2fs probably too. On the other hand I manage to write a script manual v1.0 I'll fix this asap. Oh, this is intentionally. Some people want to have fat boot partition to be windows accessible. I'll rather do it configurable then. Not sure out of my head how is this on mainline.

It looks like an (rear) server issue. I'll add some extra security checks here to prevent this happen. modified gmac driver for Bananapi (GMAC_FOR_BANANAPI) This is mandatory to enable for BananaPi, R1 and Orange. The rest leave default / ignore.

You probably only need to define where is root, customizing boot.cmd + recompile will be necessary. from root=/dev/mmcblk0p1 to root=/dev/mmcblk0p2

If you are asking for OrangePi+ ... no idea. For others. No need to rebuild kernel, many camera modules are build as modules at least with kernel 3.4.x I was playing a little with Bananas CSI camera but that's about it. Not my field of interest. http://wiki.lemaker.org/BananaPro/Pi:Camera_Module Results was average.

Sorry, don't know. If Google doesn't know it probably doesn't exists. I am not familiar with FreeBSD to say if it can be implement the same way as Debian/Ubuntu. In any case there is probably quite some work to be done.

in lib/common.sh add some brackets near line 385: NEWSIZE=$(($BLOCKSIZE*$NEWSIZE/1024)) fixed My mistake. A little better solution - It works for me - with different locales on host: BLOCKSIZE=$(LANGUAGE=english resize2fs $LOOP $NEWSIZE"M" | grep "The filesystem on" | awk '{ print $(NF-2)}') Thakns!

If the driver is there you only need to bring up menu kernel configuration and search for it. Run the script with: KERNEL_CONFIGURE="yes" and KERNEL_ONLY="yes" to build kernel only. You don't need to rebuild the image. Than re-compile. Thanks

Than in the script configuration set kernel compile only, force=no is most important in such case, double check your source changes and recompile. Wrote on mobile phone

First check if you are booting into correct kernel - type uname -a If you are not using my image as a base you need to create boot script. Wrote on mobile phone

Kernel 3.4 will work fine but Jessie (current stable) not with default kernel configuration so better use this: https://github.com/igorpecovnik/lib/blob/next/config/linux-sunxi.config

No, we are using alternative 3.4.x kernel which has all what has default sunxi community kernel + lemaker fixes + many 3rd party patches and also one known disadvantage - it's not possible to compile latest MALI drivers with it but eventually this will be fixed. Maybe this doesn't work with default kernel anyway? Haven't got a chance to test. It was developed within Cubieboard community then Daniel and I continue to keep it up to date. https://github.com/dan-and/linux-sunxi

If you are trying to glue kernel, uboot and some generic root-fs you are going few steps back. You need to fix default Debian / Ubuntu that things run smoothly, you won't be able to compile modules and upgrading will probably fail. My work covers this. Get my latest (3.4.108 if you need audio video features + some hw acceleration, otherwise 4.x) kernel with many patches and latest stable u-boot. This is somehow a good start. I am not working much on desktop but I successfully upgraded my distribution toward graphics environment, MATE (on Debian) included. Note that all graphics memory reservation is disabled by default since this is "server image". Check Cubian X1, cubian.org or cubiuntu.com as reference. Unfortunately none of those are not supported any more so it would be better to work from my fairly updated basis.

MOTD is generated within /etc/initd.d/armhwinfo while information bar below is generated within /etc/bash.bashrc.custom

The last build was done quickly so I made just boot test. Since cpufrequency scaling is working on Banana with the same kernel the problem must be elsewhere. DTB? Try boot with altered banana DTB. Yes, it's possible that it's not needed. I think it's already done but not stable yet.

Not sure, I guess manually with kernel, u-boot and board definitions from Allwinner SDK. Uboot and machine definitions (aka script.bin) are packed (new) Allwinner way - different than with what we were used to @A10/A20. More details: http://linux-sunxi.org/H3_Manual_build_howto