Le 08/06/2015 12:40, Guillaume Gardet a écrit :
Le 08/06/2015 12:24, Guillaume Gardet a écrit :
Le 08/06/2015 12:06, Marcus Schäfer a écrit :
Hi,
Le 28/05/2015 16:32, Guillaume Gardet a écrit :
Hi,
after testing some factory images, it appears that boot.scr/boot.script are not
updated, so board is unbootable after first boot.
Anything changed in config or kiwi?
Marcus, it seems that kiwi does not run our u-boot hook (setupUBoot.sh) which
is in /kiwi-hooks/ because test if file exists fails whereas it is there. :(
boot.kiwi log:
**********************************************************************
++ local 'IFS=
'
++ '[' '!' -z '' ']'
++ export eval KIWI_ALLOW_HOOK_CMD_setupUBoot=0
++ KIWI_ALLOW_HOOK_CMD_setupUBoot=0
++ HOOK=/kiwi-hooks/setupUBoot.sh
++ '[' '!' -e /kiwi-hooks/setupUBoot.sh ']'
++ HOOK=/lib/kiwi/hooks/setupUBoot.sh
++ '[' -e /lib/kiwi/hooks/setupUBoot.sh ']'
++ '[' '!' -z '' ']'
++ eval local 'call_cmd=$KIWI_ALLOW_HOOK_CMD_setupUBoot'
+++ local call_cmd=0
**********************************************************************
How could we debug this?
Check the initrd if the script is really included
gzip -cd <initrd> | cpio -it | grep setupUBoot.sh
It is in uImage format, so we need to remove headers before extract it with:
sudo tail -c+65 < initrd.uboot | gunzip > /tmp/out
gzip -cd /tmp/out | cpio -it | grep setupUBoot.sh
which returns:
kiwi-hooks/setupUBoot.sh
265320 blocs
So, it is here...
Moreover, second script installUBoot.sh is executed (but it is a bit later).
Full boot.kiwi log is there: http://paste.opensuse.org/90335031
I just rechecked and it seems that there is no /kiwi-hooks/ at all in initrd
(seems I had a look at a previous initrd extraction, sorry)
BUT installUBoot.sh is called. So, I guess this is from /kiwi-hooks/ from SD
card.
Guillaume
Guillaume
If it does not exist at all check if the tarball providing the
script(s) is bootincluded
<archive name="foo.tgz" bootinclude="true"/>
Yes :
<archive name="uboot-setup-beaglebone.tgz" bootinclude="true"/>
Next check if the archive bundled the scripts correctly, should
look like this:
tar -tf foo.tgz
kiwi-hooks/
kiwi-hooks/setupUBoot.sh
tar -tf uboot-setup-beaglebone.tgz
kiwi-hooks/
kiwi-hooks/installUBoot.sh
kiwi-hooks/setupUBoot.sh
If all that matches check the kiwi build log if you can see the
"Installing archives" log information
Build log is here:
https://build.opensuse.org/build/openSUSE:Factory:ARM/factory/armv7l/JeOS-beaglebone/_log
I can see:
[ 253s] Jun-07 19:57:50 <1> : Installing raw archives in:
/usr/src/packages/KIWIROOT-oem...
[ 253s] Jun-07 19:57:50 <1> : EXEC [chmod 755
/usr/src/packages/KIWIROOT-oem/screenrc.smart]
[ 254s] + export PBL_SKIP_BOOT_TEST=1
[ 254s] + PBL_SKIP_BOOT_TEST=1
[ 254s] + trap clean INT TERM
[ 254s] + for i in uboot-setup-beaglebone.tgz
[ 254s] + grep -v '/$'
[ 254s] + tar -tf /usr/src/packages/SOURCES/uboot-setup-beaglebone.tgz
[ 254s] + for i in uboot-setup-beaglebone.tgz
[ 254s] + tar -C /usr/src/packages/KIWIROOT-oem -xvf
/usr/src/packages/SOURCES/uboot-setup-beaglebone.tgz
[ 254s] kiwi-hooks/
[ 254s] kiwi-hooks/installUBoot.sh
[ 254s] kiwi-hooks/setupUBoot.sh
[ 254s] + echo 0
[ 254s] + exit 0
And:
[ 285s] Jun-07 19:58:22 <1> : Reading contents of bootincluded
packages/archives
[ 285s] Jun-07 19:58:22 <1> : EXEC [rpm --root /usr/src/packages/KIWIROOT-oem -ql
"dtb-am335x" 2>&1]
[ 285s] Jun-07 19:58:22 <1> : --> got list from dtb-am335x
[ 285s] Jun-07 19:58:22 <1> : EXEC [rpm --root /usr/src/packages/KIWIROOT-oem -ql
"kernel-default" 2>&1]
[ 286s] Jun-07 19:58:22 <1> : --> got list from kernel-default
[ 286s] Jun-07 19:58:22 <1> : EXEC [rpm --root /usr/src/packages/KIWIROOT-oem -ql
"u-boot-am335xevm" 2>&1]
[ 286s] Jun-07 19:58:23 <1> : --> got list from u-boot-am335xevm
[ 286s] Jun-07 19:58:23 <1> : --> got list from bootincluded_archives.filelist
[ 286s] Jun-07 19:58:23 <1> : Checking for tools in bootincluded contents to
keep
[ 286s] Jun-07 19:58:23 <1> : --> no tools to keep
Does it help you to find the problem?
Guillaume
Regards,
Marcus
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
