Igor

remove linux-u-boot-cubietruck linux-image-4.1.2-cubietruck linux-image-next-cubietruck and install linux-u-boot-cubietruck-next reboot and you'll be fine.

https://wiki.debian.org/Bonding If you mean this, than the answer is yes. In all images since some time.

What power supply are you using? If you are running system from nand, than uEnv.txt is taking control. boot.scr and boot.cmd should not be there. Is your /boot (/dev/nand1)? nand1 is boot partition with kernel uImage and uEnv.txt and some other files but not boot.scr and boot.cmd And you have to remove SD card if you want to boot from NAND .. if it's not booting than check BUG/Limitations and proceed with the hint.

Can you attach the error or simply recompile the driver.

DD is direct copy and you can use it almost anywhere. If you want to speed up the process - shrink data partition on the drive, save only partitions (separate) and expand back. But in this case you are not saving the boot loader. You need to save it separate.

Thanks. I added this to the default config. Better to have stable than unstable with a little better performance.

Check bugs and limitation section on the board description / download page. Legacy kernel.

This is normal boot procedure.

You will need to decompile DTB (hummingboard) add UART2 definitions and recompile. This is theory ... but. I don't know what are correct numbers - for this you will need to check technical manuals or contact SolidRun. https://github.com/linux4kix/linux-linaro-stable-mx6/blob/linux-linaro-lsk-v3.14-mx6/arch/arm/boot/dts/imx6qdl-microsom.dtsi Look how it is done for UART1 and 4

Check this: https://github.com/igorpecovnik/lib/blob/second/common.sh#L240 Input is RAW image, output minimal RAW image with 15% free space. Works with one or two partition.

Because there was a bug in upgrade script. You need to upgrade boot loader to the "next". Remove the one without "next" just in case. dpkg -r linux-u-boot-lime2 or ... Lime 1 with A20 and 512Mb RAM apt-get install linux-u-boot-lime-next or Lime 2 with A20 and 1024Mb RAM apt-get install linux-u-boot-lime2-next Micro apt-get install linux-u-boot-micro-next Reboot.

Yes, you need to enable it in FEX but I am afraid it might not be wired to connector or elsewhere.

Check bonding interfaces. There is an example in /etc/interfaces

... and I merged this config with default + added firmware. https://github.com/igorpecovnik/lib/commits/second Next build should work out of the box with this hardware and the rest what has been enabled.

I guess VPN server must be the problem since I was testing without, but installing Transmission and TVheadend. Thanks for this info. It will save time for others and I'll fix this somehow. Maybe it's time that we do some updates to the script.

The smartest / perfect backup is if you backup only what's needed - your work on the top of the system. I have a script to install all services that I need and a backup where are only configuration files + my data. Both data and configuration files are saving periodically. Restore can be done easy from scratch or only from older data. This way of course requires deeper knowledge of the operating system. Average way would be to save directories with your data and system configuration (/etc /boot). For this, some basic knowledge will be enough. Saving the whole file-system periodically is possible but not recommended but if you insist - you can do it this way: tar czpf backup.tgz --directory=/ --exclude=dev/* --exclude=proc/* --exclude=run/* --exclude=tmp/* --exclude=mnt/* . Note that this backup is not boot-able image but the content of it - it's all but the u-boot.

Now this part is fixed + I found and fix some other case bug. (booting from NAND) I run an upgrade over one of my production server today & upgrade succeeded.

I am not familiar with this Tronsmart device but you can try to boot Cubieboard 4 Debian. This is closest you can get at the moment. http://docs.cubieboard.org/tutorials/cc-a80/start#linux_distrabutions

Yes, I already plan to prepare emergency recovery. I'll try to add this during a day to Manual.

OK, I'll try this image and also to build 3.19.x, also tomorrow, today already EOL

Just to compare to: - sources downloading (@10Mbit) - u-boot and kernel compiling (VM on 4Core 4G Xeon) - system downloading (Debian Wheezy) cca. 40 minutes When everything is in cache: 2 minutes

This might be a problem due too a bug in script. Perhaps you only need to updated scripts because it should be fixed. Error is in the line before, it should be: BLOCKSIZE=$(LANGUAGE=english resize2fs $LOOP $NEWSIZE"M" | grep "The filesystem on" | awk '{ print $(7)}') There are many reasons why it does not boot. First enable more verbose output in boot.cmd loglevel=7 recompile scripts and boot again.

Only I admin and a moderator can. Speaking about - an extra hand for keeping forum clean is welcomed. Any volunteers?

This ttyS0 or nework adapter timeout is a bug which is not fixed yet. Power cycle usually helps.

I prepared script that is functional if we have more than one SD card partition. If you have some 3rd party installation. That's the reason of this functions. But the usage might be false. I'll look into it and fix. Thanks for detailed report. It helps!