Igor

I am using general /etc/bash.bashrc which only include the actual script: /etc/bash.bashrc.custom The other part, what you find "not so cool" is here: /etc/init.d/armhwinfo

OK

If Ubuntu fails try also Debian. There are some issues with Ubuntu debootstrap which are out of my power but sometime occur.

apt-get update & upgrade will solve everything. It takes some time that all servers are populated so files might not yet be available in next minutes

nope, wrong. read documentation regarding kernel upgrade, you have older image so you need to add repository first. More info: http://www.armbian.com/kernel/

https://github.com/igorpecovnik/lib/commit/0b4f6424b60b00cf088810e7f8387552ad9ae61d Sources are fixed, kernel recompilation and repository update will follow asap.

No, running out of space is not a good idea. Logs are archiving / compressing so should not happen so soon.

Never saw such error. It must be related to some sort of corruption withing base system. If you run the script and rerun again some process could hang so sometimes reboot is needed. It's recommended that you run this script within virtual machine and update script libraries /lib too. All of your changes should be inside compile.sh call script - for general / basic work. If you haven't touched them, they are auto updated.

There is / must be a link to headers / sources on all images for at least a year. If you did an kernel upgrade, than you need to upgrade headers too. I checked some of my running configurations and all have a valid link. Ahaa, I see. Naming is wrong. BTW. Latest image works as expected. I compiled some driver without a problem.

This is something odd. I built new image set two days ago and had zero problems. Jessie was under heavy testing since we had some boot problems. None of image has and signs of corruption.

BTW. There is a temporal solution by switching to alternative A20 kernel. apt-get install linux-image-banana ... but that kernel will not update anymore in the future so you will need later to come back to linux-image-sun7i

No, there is no script for that ... if you already set the system than do a rysnc copy from current root which is on /dev/sda1 to /dev/mmcblk01 ... this will take some time. Than edit boot scripts /boot/boot.cmd and change root to /dev/mmcblk0p1 And do a backup of your data before starting this. If your modifications are minor, rather start over.

I haven't update to latest yet if you are asking me that. This requires reboot which I don't wont to do yet. Update is usually safe. I do some tests but some minor issues might occur. It happened before and it will in the future. BTW. Package names are always the same but their version is changing.

Yes, it's a bug ... I'll fix it asap.

I updated all Jessie images with kernel 4.x ... they are working as expected. At first boot you get an error / eth0 failed to bring up ... ignore it ... than my scripts fix RTC and reloads the Ethernet. This is possible if there is no systemd so it's disabled by default. You can turn systemd back if you like. Howto is inside /boot/boot.cmd

The problem persist only on Jessie images. On others there is an fix build into startup script. There are many ways how to do it but none is ideal. Disabling sytemd is the best out of this since it covers new install and upgrade. Disabling it at least for first boot and problem would go away. Since I haven't put no info about new releases, I would rather rebuild all Jessie images with kernel 4.x and disable systemd. That was origina idea but I lost focus on other things. I'll write on first page within release info @www.armbian.com when it's done.

Yes, It should be populated on all servers by now.

Yes. Further. If you are copying root from SD card check and adjust /etc/fstab if needed.

What No kernel is working for you? 3.4.109 and 4.2.3. Are you doing power cycle? Have you try to set clock as described here? Once this is solved you should be able to boot normally.

We are using boot scripts (on all images) for several reasons ... The procedure is similar except, boot.cmd need to be translated / compiled to boot.scr (u-boot script format). Maybe it looks like a bit more complicated but you are changing the same thing. root=/dev/mmcblk0p1 to root=/dev/sda1 (for example) Then recompile with: mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr Check boot.cmd source: # 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/${fdtfile} || 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 https://forum.htpcguides.com/thread-Problem-pointing-boot-to-hdd BTW: Bananian also have boot.scr now.

https://github.com/igorpecovnik/lib/issues/111

It's part of the board support package. It's on apt.armbian.com linux-DISTRO-root-DEVICE_NAME

Thanks! This variable should do the work: AFTERINSTALL is a variable with command executed in a process of building just before closing image to insert some of your custom applications or fixes.

Best chances are with Wheezy if you seek stability. Kernel 4.x is also not completely o.k., I fixed some bugs in latest build. Try this image: http://mirror.igorpecovnik.com/Armbian_4.5_Lime2_Debian_jessie_4.2.3.zip (wait until is fully uploaded. can take some time, up to 1h) Or better: http://mirror.igorpecovnik.com/test/linux-image-next-sunxi_4.5_armhf.deb Just update kernel and reboot.

I am just finishing new build, probably tomorrow there will be a legacy (3.4.109) build from another source and 4.2.3 Both my Olimex's are still online, one has 4.2.2, other 3.4.108. If no system is stable on your board (bare, without any plugs to USB or else) and if you try different power supplies it could be a defect board. It happens.