Igor

I made several tests and it's no go in my Opi+ ... unfortunately don't have any other H3 board here to test. Since we need HDMI we can leave out this minor (?) performance change for future. We might need to adjust boot script - is it safe using this script on A20 board? I am out of lab next week so won't be able to test anything. I am putting out new images probably today and then let's collect what needs to be done ... for a week.

We had this solution when there were booting problems because of systemd. Since it's solved this become deprecated. Switch is not operational but we forget to remove it.

Ahaa, make a link to that file, not a copy. For further info regarding battery, check this thread: http://forum.armbian.com/index.php/topic/611-wip-axp209-mainline-sysfs-interface/ Battery charged rate is calculated from voltage so capacity does not matter. How correct are the numbers is hard to say. Good enough to put some things in action when capacity drops below certain percentage. You will need a test or two to make sure.

True, forgot that. But since u-boot selects normal banana by default it should work unless you don't change DTB to the one from Pro. Temporally / partial workaround is by using a DTB from normal Banana.

I think that won't be enough. You will still get some prompt from u-boot. I think he needs to recompile u-boot with disabled tty1 console. Would need to look how to do that.

Three questions: - what's in your - it should be: s -l /etc/update-motd.d/ total 20 -rwxr-xr-x 1 root root 245 Feb 19 15:31 10-header -rwxr-xr-x 1 root root 5474 Feb 19 15:31 30-sysinfo -rwxr-xr-x 1 root root 4348 Feb 19 15:31 40-updates - where is your /etc/motd linked to motd -> /var/run/motd - did you alter your sshd.config ?

I fully understand that people don't need a compiler, headers and selection of certain utilities on product deployment. The basic ideas of Armbian was to have all in one / general purpose CLI OS. We added some customization on the way within customize-image.sh but yes, this process is not optimal and takes some time. Desktop is not where I wanted to be and should be developed further. I also don't like to waste time on providing several desktop options. If one urgently doesn't want the defaults ... it's easy to switch to whatever later and it's also possible in a process customize-image.sh ... I am doing something similar in a separate project. It's little outdated and would need update / rework. https://github.com/igorpecovnik/Debian-micro-home-server(latest commits DEV branch)

Thank you for your input - it's helpful to get feedback and to realize where are the problems. All Orange images are still "prebuild / alfa" and we are working on them intensively. disp.screen0_output_mode=1280x720p60 I think this method does not work with Oranges but you are setting it with the number of video mode. Check Orange pi dev hread. It might change as well.

Check some of those: http://linux.die.net/man/1/speaker-test

If it's restarting it means kernel crashes but it would be nice to find out why it does. To get more information on this you will need to mount this image on some Linux machine, edit /boot/boot.cmd and set loglevel to 8 ... than you need to recompile boot.cmd to boot.scr by using u-boot tools. If you have a serial console, change console to ttyS0,115200 and paste the boot log here. Than we might be able to tell more about the problem. And yes, do some easy parts first: use different SD card, write it in Windows 7, on Linux, ...

Yes, I also noticed on Pi+ but haven't got time to check up what's going on... we are going very fast

You need to use proper fex settings on legacy kernel - you need to make new link to /boot/script.bin. You can find those for Lemaker displays within image in /boot/bin: /boot/bin/bananapiprolcd7.bin I haven't saw a working solution for mainline kernel yet but it's also possible.

Added to current stable and development. https://github.com/igorpecovnik/lib/commit/fab7d136f8a5842edd9b01068ff6223e0773b24e

First change console to serial and loglevel to 8 that we will see something in the bootlog.

Which kernel? linux-cubox-default.config linux-cubox-dev.config linux-cubox-next.config linux-marvell-default.config linux-marvell-dev.config linux-marvell-next.config linux-neo-default.config linux-odroidxu4-default.config linux-odroidxu4-next.config linux-s500-default.config linux-s500-next.config linux-sun4i-default.config linux-sun5i-default.config linux-sun7i-default.config linux-sun8i-default.config linux-sunxi-default.config linux-sunxi-dev.config linux-sunxi-next.config linux-toradex-default.config linux-udoo-default.config linux-udoo-neo-default.config linux-udoo-next.config https://github.com/igorpecovnik/lib/tree/master/config

Actually I haven't try to compile. Was already half sleeping at the time ... will check up. Not working MALI could be related to kernel command line, again We are setting some no_video_memory ... etc by default.

Check if this is enough: https://github.com/igorpecovnik/lib/commit/2cda40d18b4915e8238f377aeee365fa5fe72e57

root@production:~/sources/u-boot/branchless# patch -p1 < /root/lib/patch/u-boot/u-boot-dev/sy8106a.patch patching file board/sunxi/Kconfig patching file board/sunxi/board.c patching file configs/orangepi_pc_defconfig patching file drivers/power/Kconfig patching file drivers/power/Makefile patching file drivers/power/sy8106a.c patching file include/configs/sunxi-common.h patching file include/sy8106a.h If you override TAG that doesn't mean you are in DEV branch so the patch must be in DEFAULT ... and it works. I also made wrong conclusion. Copy patch to default.

All A20 boards share the same kernel so this patch is present. Check your script.bin ... I2S is only disabled in board configuration. [i2s_para] i2s_used = 0 i2s_channel = 2 i2s_mclk = port:PB05<2><1><default><default> i2s_bclk = port:PB06<2><1><default><default> i2s_lrclk = port:PB07<2><1><default><default> i2s_dout0 = port:PB08<2><1><default><default> i2s_dout1 = i2s_dout2 = i2s_dout3 = i2s_din = port:PB12<2><1><default><default> /boot/bin/lime2.bin (file location) bin2fex lime2.bin lime2.fex Check / edit / enable in fex file: change i2s_used = 0 to i2s_used = 1 fex2bin lime2.fex lime2.bin For wiring check Olimex docs.

This might be useful: Making DTS out of DTB (decompile) dtc -I dtb -O dts -o <devicetree name>.dts <devicetree name>.dtb Making DTB out of DTS (compile) dtc -I dts -O dtb -o <devicetree name>.dtb <devicetree name>.dts

@Thomas My bad. I guess it's time to go off for a while Patch is working with DEV branch ... add BOOTBRANCH="" to userpatches/lib.config that it u-boot will compile without TAG and try ... Just different solution. We still have must have two separate kernel bin. BTW: I am meeting Jernej next week. @Zador Let's try. I mean, Thomas should try it out ...

What about reading from script.bin ? It's defined which eth type is used.

OK, then perhaps adjusting / fixing the driver if we got skill set / resources for doing it ... since temporally solutions are bringing new logic to the kernel families naming - kernel sub versions: sun8i, sun8i-gmac ... which somehow doesn't sound or look cool Edit: It's already part of 2016.01

I'll make one extended config now that you will be able to use apple keyboard BTW, Have you try to boot those with internal PHY if patch is present? From first quick look this should be or it was designed to be selected from script.bin?

That patch is already a part of Armbian kernel and reported working on Cubietruck and Banana PRO.