borsti67

I see. So user scripts should be included to customize-image.sh (only)? The problem there is that it's executed within chroot while I make use of e.g. fetch-from-github to have a local cache. Probably I can solve this issue for the moment by splitting prerequisites (caching etc) from execution (configure/build). Or is it also wrong? What is your recommendation to handle such cases?

unfortunately I noticed now that my QT installation script now fails. This error follows the one above, I assume the building order was changed? QT depends on headers which are installed as a part of the sunxi display driver, which now comes after "extra drivers and applications"... Was there a special reason to change that or could it be reverted easily?

Hi, on a lime2 the firstrun script hangs as it doesn't seem to have a red or blue LED. So I'd like to propose the following change which shouldn't break anything but add the green one. Unless some vendor adds even more colors. Not sure if the trailing "|| true" is the best solution to make sure the script will never fail? diff --git a/scripts/firstrun b/scripts/firstrun index 760cf0d..2f2b222 100644 --- a/scripts/firstrun +++ b/scripts/firstrun @@ -119,8 +119,8 @@ adjust_sunxi_settings() { sed -i "s/^MAC_ADDR=.*/MAC_ADDR=${MACADDR}/" /etc/default/brcm40183 \ echo -e "\n### [firstrun] Use MAC address ${MACADDR} for Bluetooth from now" >>${Log}) - # trigger red or blue LED as user feedback - echo heartbeat >/sys/class/leds/*red*/trigger 2>/dev/null || echo heartbeat >/sys/class/leds/*blue*/trigger 2>/dev/null + # trigger red, blue or green LED as user feedback + echo heartbeat >/sys/class/leds/*red*/trigger 2>/dev/null || echo heartbeat >/sys/class/leds/*blue*/trigger 2>/dev/null || echo heartbeat >/sys/class/leds/*green*/trigger 2>/dev/null || true [ -f /etc/wicd/wired-settings.conf ] && \ read HOSTNAME </etc/hostname sed -i "s/^dhcphostname =.*/dhcphostname = ${HOSTNAME}/" /etc/wicd/wired-settings.conf && \

Your commit works, thanks a lot!

Will check it out immediately, thanks! You're absolutely right. My proposal would indeed suppress any output to screen, so it should be done with "tee", shouldn't it? At least I saw this in other parts of the script.

Hi Zador, these are my settings: BRANCH="default" RELEASE="jessie" BUILD_DESKTOP="yes" PROGRESS_DISPLAY="plain" PROGRESS_LOG_TO_FILE="yes" FORCE_USE_RAMDISK="no" FIXED_IMAGE_SIZE=12000 KERNEL_ONLY="no" KERNEL_CONFIGURE="no" CLEAN_LEVEL="debs" KERNEL_KEEP_CONFIG="no" EXTERNAL="yes" FORCE_CHECKOUT="yes" BUILD_ALL="no" I haven't changed these for quite a long time, didn't have this issue before. I don't think so for 2 reasons:there is a lot of stuff rolling by, depending on processor power a build can take several hours where I don't believe anyone is staring at the monitor all of the time at least if I have set the log file option I expect to see EVERYTHING there, especially things which went wrong If an error occurs which does not break the script (like this one) the build will finish nicely but by chance the image will not work. You will not be able to see why, even if you turn on logging!I haven't checked what "output.log" is used for otherwise (or if it is overwritten halfways), it was always very small in my case. So I recommend redirecting error output into the log file as it won't hurt but can be helpful. Not sure what exactly these 2 debs are required for but some error handling (at least logging a warning) sounds reasonable to me?

Hi, after some days with other projects I have updated to newest master and now see this message during installation: [ o.k. ] Installing extra applications and drivers [ o.k. ] Installing linux firmware [ 5.14 ] dpkg: error processing archive /tmp/armbian-firmware_5.14_all.deb (--install): cannot access archive: No such file or directory Errors were encountered while processing: /tmp/armbian-firmware_5.14_all.deb [ o.k. ] Installing [ armbian-hostapd-jessie_5.14_armhf.deb ] invoke-rc.d: policy-rc.d denied execution of stop. dpkg: error processing archive /tmp/armbian-hostapd-jessie_5.14_armhf.deb (--install): cannot access archive: No such file or directory Errors were encountered while processing: /tmp/armbian-hostapd-jessie_5.14_armhf.deb These errors are NOT mentioned in install.log or output.log! It looks like these lines are coming from extras/firmware.sh. May be the last line should be appended with "2>&1" to catch such issues? But I was unable to find out yet why the .deb cannot be found. It is created and has the correct name in output/debs. Have there been changes to the order of processing? It looks like the "mount --bind" to /tmp is no longer (or not yet?) active...

Hi, I noticed that "install.log" was missing the beginning of the process, it starts at building the .deb for u-boot. There is one ">" missing in common.sh: diff --git a/common.sh b/common.sh index 503a3ab..920ba38 100644 --- a/common.sh +++ b/common.sh @@ -90,7 +90,7 @@ compile_uboot (){ cd $DEST/debs display_alert "Target directory" "$DEST/debs/" "info" display_alert "Building deb" "$uboot_name.deb" "info" - dpkg -b $uboot_name > $DEST/debug/install.log 2>&1 + dpkg -b $uboot_name >> $DEST/debug/install.log 2>&1 rm -rf $uboot_name FILESIZE=$(wc -c $DEST/debs/$uboot_name.deb | cut -f 1 -d ' ')

Hello Zador, In fact this already happened. hm, this is a rather complex one. I did a lot of changes to lib.config and customize_image.sh as well as an additional "external" script. Do you know the Paparazzi project? http://wiki.paparazziuav.org/wiki/Main_Page I was able to install dependencies, create and install the .debs for ivy and install modules with OPAM (this also is obviously not using all processor power ). The final step would be to call "make" in the paparazzi folder. I have manually mounted the image and fired chroot: /opt/paparazzi# make qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault (core dumped) qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault (core dumped) ------------------------------------------------------------ Building Paparazzi version v5.8.1_stable-none-g < ... > The script continues for a while but either errors out somewhen or just does nothing anymore so I have to kill it with ^C. Unfortuantely there is no more output, and a google search wasn't helpful. I think I can paste the necessary changes here but be aware that a compilation (with cached data!) takes over an hour here.

Hi, it seems my VM got corrupted somehow... I have created a new one, since then the compilation succeeds. I have no clue what happened there. In the meantime I have managed to update most of my stuff to Jessie, looks quite good but the processor load using h.264 is still much higher compared to an "original" Olimex image. For the moment I have 3 more annotations/questions: formerly I have set the host name in lib.config. Now I noticed after the 1st login the machine is called "lime2" again? Looks like there is a bootscript now which changes it (but the other code seems still to be included?)... I would prefer if any automated change to the hostname would be done ONLY when it's not set manually. I need to install a lot of packages with apt-get. As I understand, repositories are cached (at least partially?) on the host machine. How do I make use of this, add mine to $PACKAGE_LIST? when I try to compile a project using c++ and OCAML in chroot, I see fails with a core dump. Seemingly qemu has some serious problems as this doesn't happen when running "live". Does anybody know how to circumvent this? Compiling on the A20 is no fun.

hmm, is it possible that caching leads to some of these issues? At work I was unable to create an image (neither wheezy nor jessie) regardless of removing the caches. At home - where I formerly created working images - I only switched from wheezy to jessie but forgot to remove the caches and the same errors came. Then I deleted all caches and now it compiled again... Will check it tomorrow @work again and supply logs. Thanks for your patience!

Hi Igor and Zador, I have removed the sources and set the mirror as Zador proposed but still no luck... The script seemingly runs fine, rolling back the screen and checking the logs shows no errors until here: Free space: tmpfs 2.5G 342M 2.2G 14% /home/qt/armb2/output/cache/sdcard [ o.k. ] Ending debootstrap process and preparing cache [ wheezy ] wheezy-ng-armhf.538...610.tgz: 218MB [ 176MB/s] [=====================================================================================================] 103% [ o.k. ] Applying distribution specific tweaks for [ wheezy ] sed: can't read /home/qt/armb2/output/cache/sdcard/etc/default/ramlog: No such file or directory sed: can't read /home/qt/armb2/output/cache/sdcard/etc/default/console-setup: No such file or directory [ o.k. ] Installing packages [ linux-image-sun7i ] [ o.k. ] Installing u-boot [ linux-u-boot-lime2 ] [ o.k. ] Installing headers [ linux-headers-sun7i ] [ o.k. ] Installing firmware [ linux-firmware-image-sun7i ] sed: can't read /home/qt/armb2/output/cache/sdcard/etc/lirc/hardware.conf: No such file or directory sed: can't read /home/qt/armb2/output/cache/sdcard/etc/lirc/hardware.conf: No such file or directory sed: can't read /home/qt/armb2/output/cache/sdcard/etc/lirc/hardware.conf: No such file or directory sed: can't read /home/qt/armb2/output/cache/sdcard/etc/lirc/hardware.conf: No such file or directory sed: can't read /home/qt/armb2/output/cache/sdcard/etc/lirc/hardware.conf: No such file or directory cp: cannot create regular file ‘/home/qt/armb2/output/cache/sdcard/etc/lirc/lircd.conf’: No such file or directory ...followed by the same errors as mentioned in my 1st post, finally failing at the Mali acceleration.

I have added the following line into customize-image.sh: # set German keyboard layout sed -i 's/XKBLAYOUT=".*"/XKBLAYOUT="de"/' /etc/default/keyboard ...may be you want to do it alike? Just check the value to be inserted instead of "de"...

yes, I already found that switch after I tried to include another driver into the kernel (it didn't compile but anyway only "install.log" was in the debug folder - a compilation log was only saved when it was not needed: successfully compiled ). But I left in since then. Thanks for the hint regarding the mirror, I will try that. It would explain why it sometimes works! For my project I need full graphics support (eventually I will also have to switch to another kernel branch as mentioned here http://linux-sunxi.org/Optimizing_system_performance#Advanced_topic:_Using_more_recent_Mali_drivers - as far as I can see currently R3P0 is used while R3P2 could get more out of it). Some of the toolchains I will have to install are only maintained within Wheezy - I don't know if everything will work with Jessie. For compiling Armbian I also need the (former) LTS Ubuntu instead of Xenial, I fear many things will break here if that's going to be changed... But probably I'll give it a try after having everything else up and running. Now let's have some quiet holidays, I hope you have 'em, too!

ok, I started from scratch with only "compile.sh" in an empty directory. Unfortunately it still doesn't work, but by chance I saw a message which is not recorded in the logs: Get:595 http://httpredir.debian.org/debian/ wheezy/main wifi-radar all 2.0.s08+dfsg-1.1 [52.4 kB] Failed to fetch http://httpredir.debian.org/debian/pool/main/w/weather-util/weather-util-data_2.0-1_all.deb Hash Sum mismatch Fetched 295 MB in 43s (6787 kB/s) E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? Free space: tmpfs 2.5G 624M 1.9G 25% /home/qt/armb2/output/cache/sdcard ...could this be the reason? How can I possibly fix it? Or is more data cached anywhere outside of the lib, sources and toolchains directories? I have searched for "fail" and "error" in the available logs, but the only logged one is at the end, when Mail fails.

Hi all, some days ago I successfully built the image mentioned above (Build environment is Ubuntu 14.04/64 bit). The only remarkable issue was the ever-repeating "firstrun" script, which was easily solved with the method mentioned here: http://forum.armbian.com/index.php/topic/1100-post-install-scripts-on-every-reboot/#entry8509 (may be ALL of the scripts should be changed this way?) But today, after checking out the actual "master", I see a lot of failed copy and sed commands until the debootstrap-ng script finally fails at Mali-libdri2. The 1st occurrence of an error was during installation of "ramlog". I've inserted a breakpoint and looked into the image. "dpkg.log" reads 2016-05-13 07:45:53 startup archives install 2016-05-13 07:45:53 install ramlog:all <none> 2.0.0 2016-05-13 07:45:53 status half-installed ramlog:all 2.0.0 2016-05-13 07:45:53 status unpacked ramlog:all 2.0.0 2016-05-13 07:45:53 status unpacked ramlog:all 2.0.0 I manually issued the dpkg -i with the following result: dpkg -i /tmp/ramlog_2.0.0_all.deb Selecting previously unselected package ramlog. (Reading database ... 9890 files and directories currently installed.) Unpacking ramlog (from /tmp/ramlog_2.0.0_all.deb) ... dpkg: dependency problems prevent configuration of ramlog: ramlog depends on lsof; however: Package lsof is not installed. ramlog depends on rsync; however: Package rsync is not installed. dpkg: error processing ramlog (--install): dependency problems - leaving unconfigured Errors were encountered while processing: ramlog I have tried to deactivate the apt-cache by inserting the somewhat hidden command "NO_APT_CACHER=yes" in my compile.sh but this didn't help. (There are more errors following this one, e.g. /etc/default/console-setup is missing as well as /etc/lirc/hardware.conf, /etc/lirc/lircd.conf, /etc/wicd/manager-settings.conf, /etc/default/nodm, /etc/X11/xorg.conf) Some strange messages in-between, which I think I also saw earlier but as i haven't faced an issue with the image I ignored them: [ o.k. ] Installing desktop [ XFCE ] /bin/tar: A lone zero block at 70 /bin/tar: A lone zero block at 70 /bin/bash: unzip: command not found At the very end: [ o.k. ] Adding support for Mali - acceleration [ sunxi ] E: Unable to locate package mesa-utils-extra E: Unable to locate package libdri2-1 E: Unable to locate package libdri2-dev dpkg: dependency problems prevent configuration of libdri2-1: libdri2-1 depends on libdrm2 (>= 2.3.1); however: Package libdrm2 is not installed. libdri2-1 depends on libx11-6 (>= 2:1.4.99.1); however: Package libx11-6 is not installed. libdri2-1 depends on libxext6; however: Package libxext6 is not installed. dpkg: error processing libdri2-1 (--install): dependency problems - leaving unconfigured Errors were encountered while processing: libdri2-1 [ error ] Installation failed [ Mali - libdri2-1 ] What should I do now?