Igor

There is a problem with (simple) frame buffer initialization if your monitor is too large in matter of pixels. I figured out this just recently when I hooked a board to UHD HDMI monitor. Need to look into u-boot code and check how can this be solved. Second issues is that u-boot sometimes breaks booting if you have an USB keyboard inserted or some other strange device. Boot script breaks "on any key pressed", so board doesn't boot. I can only say it's a general bug, not just Armbian's

yes. Update will be soon since I produced some bugs in latest release. But you need to enable / map certain led to "disc-activity" in script.bin or your startup script, but that you probably already have. Just a not for others who wants to use this.

Now I am a bit consed. I just build a new image for A10 from clean sources and install it to NAND with root on SATA drive. Zero problems. What's clean image different from upgrade? I'll upload a complete pack later and try that first. There is one common issues .. sometimes, when NANDs boot part gets corrupted it's necessary to install stock Android / Ubuntu to NAND with factory tools (Phoenix suite) and do the install part again. It doean't look that you need to do this but it's an option to try.

I thought changing init system is not that hard ... if this is not trivial, than I'll leave as is. I really don't want to mess with this if not absolutely necessary.

HDMI / VGA is auto detected in current U-boot while HDMI is default for kernel. Are you perhaps using UHD or some weird non-standard monitor? Do you have anything connected to USB port? Thanks

Added (back) to this kernel. https://github.com/igorpecovnik/lib/commit/3da8d0b92e608696bbdf314c95d625198a8d6a1c Add: tested, working o.k.

1. git clone https://github.com/igorpecovnik/lib cd lib/scripts/nand-sata-install/usr/lib/nand-sata-install/a10/bootloader rsync -aqc * /XXXXXXXXXXXXXXXXXX # directory where is your /dev/nand1 mounted or file by file, this way: 2. RAW github dl wget https://github.com/igorpecovnik/lib/raw/second/scripts/nand-sata-install/usr/lib/nand-sata-install/a10/bootloader/boot.axf

There is something wrong with a file - they are wrong size. Check if you download files properly (RAW). I had the same error and I only copy those files over and it's booting fine.

Perhaps the best would be to use sysvinit in Trusty and it would work out of the box plus it's less demanding to support?

Yes, it's a bug. It will be gone in next update ... if you overwrite files on nand boot with this: https://github.com/igorpecovnik/lib/tree/second/scripts/nand-sata-install/usr/lib/nand-sata-install/a10/bootloader it should boot. Please try.

Let's check first if your upgrade was successful ? The script is new, old one should be removed on upgrade since it's deprecated and probably won't work. What do you get: which nand-sata-install and ls -l /boot

OK, will check later today. I must have done something ... It's not possible to compile video acceleration within mainline kernel. There is nothing you can do.

How to do you power your Cubietruck? Via power connector?

I noticed few days ago ... no clue at the moment but you can try with alternative kernel: https://github.com/igorpecovnik/lib/blob/def90eb1997a267627882c186cb603bbc1dde92c/configuration.sh Comment line: 67,68 and 70

Yes, that's correct. When you will have / find a working script.bin simply add (with some obvious name) it's source (fex) to lib/config or attach it here and I'll add this to build by default.

Perhaps it's some weird FAT type ... I made a test build, 64M boot partition and root for the rest. Here is my fdisk print: Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 2048 133119 131072 64M e W95 FAT16 (LBA) /dev/mmcblk0p2 133120 15677439 15544320 7.4G 83 Linux I can normally install DTB on this but if there is already installed I got an error: dpkg -i linux-dtb-next-sunxi_4.6_armhf.deb (Reading database ... 48751 files and directories currently installed.) Preparing to unpack linux-dtb-next-sunxi_4.6_armhf.deb ... Unpacking linux-dtb-next-sunxi (4.6) over (4.6) ... dpkg: error processing archive linux-dtb-next-sunxi_4.6_armhf.deb (--install): unable to make backup link of `./boot/dtb/sun7i-a20-cubieboard2.dtb' before installing new version: Operation not permitted Errors were encountered while processing: linux-dtb-next-sunxi_4.6_armhf.deb

Generally: new kernel is not populated with all features from stock. This particular part is done but it's not function properly so it's disabled. Sooner or later it will be fixed. Maybe already is ... I need to check.

OK. I'll check if it's a problem made by me ..

No, it should be possible to install on FAT drive. Remove previously installed packet if exists. Do you have enough free space on boot partition? What's now on it?

http://linux-sunxi.org/LeMaker_Banana_Pi There is no special M1+ config, so you need to alter script.bin ... and you will get a sound.

Strange. Today's fresh install: [ 12.764268] EXT4-fs (nand2): mounted filesystem without journal. Opts: (null) [ 18.399862] EXT4-fs (nand2): Remounting file system with no journal so ignoring journalled data option [ 18.408673] EXT4-fs (nand2): re-mounted. Opts: data=writeback,commit=600,errors=remount-ro Installer script or image is not yet available for download ... rebuilding updates now.

Just a quick add: Some / one error(s) are normal during build and also ureadahead is useless so exclude it. Is image produced?

Uboot detect and set correct output while kernel not. You need to alter settings in /boot/script.bin and set output to VGA. By default is HDMI. Here are the steps: cd /boot bin2fex script.bin script.fex edit and alter this number to 4 screen0_output_type = 3 fex2bin script.fex script.bin reboot

OK, Thanks for update.

Hmm, this should already be fixed ... it was working correctly in previous version of U-boot. Downgrade uboot package or wait for update.