-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Paul,
in attachment the patch to modify the pwrmgmnt script for lava in order
to take into account the new pm-qa scripts.
Let me know if everything is ok or not.
Thanks for your help !
-- Daniel
- --
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOSvJQAAoJEAKBbMCpUGYA85sH/3IlfWWunRuLtOcLenOosM73
EkNSFPY5+HN1txtL0rIY//P4TRFiVoKciV6+Muzp6KIhqytRLNNkh0tpz6rfOM7A
G5mv6O2qQGwTpWN7GyqWUMkewxtTUCXmzy+ITkgK0RIDeUXiLftDtW5KZyW2W0GT
cnYe8mUv5/d5zxucCoMScOcpxLfTRIVh5+1EvkcRtD5TSoTX5eqzV29bb+EchTun
ZCg25fDTFCa5+kaqdfaygdgNGsn4Q7wgIunduN/hEs4mQAftU2BQJ7JtM7XGje90
2MaBDcX/GMpjV2FQ8DWcXg9U/9IVLHfRWcM6+PAY6cesPAtpsreVHL7loqgZENY=
=8Fkx
-----END PGP SIGNATURE-----
Using linaro-media-create (version
linaro-image-tools_0.4.8-0ubuntu1~lucid1_all) to create an image the
default image size seems to be 2GB if no --image_size is given.
Creating an image (--image_file) with the recent
linaro-n-ubuntu-desktop-tar-20110817-0.tar.gz fails with tons of "No
space left on device" [1] while the hard disk space is still fine
(tested on different PCs).
It seems that the 2GB image file is loop mounted to
/tmp/xxx/root-disc/ and that 2GB is too small for recent Ubuntu
desktop images. The recent linaro-n-ubuntu-desktop
tar-20110817-0.tar.gz is compressed ~490MB while an older one (e.g.
linaro-n-ubuntu desktop-tar-20110628-1.tar.gz) was only ~430MB. With
this creating an image worked fine with the default 2GB image size.
Adding '--image-size 3G' fixes the issue.
What's about increasing the default image size of l-m-c if it's too
small for creating recent images?
Best regards
Dirk
[1]
...
mv: cannot create regular file
`/tmp/tmpT4h0vR/root-disc/var/lib/dpkg/info/vim-tiny.md5sums': No
space left on device
mv: cannot create regular file
`/tmp/tmpT4h0vR/root-disc/var/lib/dpkg/info/libnss3.postinst': No
space left on device
mv: cannot create regular file
`/tmp/tmpT4h0vR/root-disc/var/lib/dpkg/info/ibus-table.md5sums': No
space left on device
mv: cannot create regular file
`/tmp/tmpT4h0vR/root-disc/var/lib/dpkg/info/apmd.list': No space left
on device
mv: cannot create regular file
`/tmp/tmpT4h0vR/root-disc/var/lib/dpkg/info/eog.list': No space left
on device
...
Key Points for wider discussion
=======================
Move to Android 2.3.5 is done and being tested.
Toolchain with OpenMP, loop parallelization support is done and being tested.
ffmpeg with support for H.264 and WebM runs on Linaro Android.
Team Highlights
=======================
Snowball runs Android 2.3.5.
-O3 for gcc 4.6 works.
Linaro Android image for Samsung Origen board can boot to console.
Gerrit is in daily use.
Miscellaneous
=======================
Zach on vacation from 21st-24th
Code complete on the 18:th.
> We have several people here in the support office trying to build an
> sdcard using the latest hwpack and root filesystem files as found
> here:
>
> http://releases.linaro.org/platform/linaro-n/ubuntu/leb-panda/latest/
>
> We are running into a segfualt in /usr/bin/dpkg during what seems to
> be the hwpack installation.
Hi Frederik,
Please use the linaro-dev mailing list (copied here) for future
issue reports. I looked at the log and it's indeed odd that this is
happening. Can you reproduce the problem on any of your hosts, and if
so, what OS version is installed on them?
--
Christian Robottom Reis, Engineering VP
Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935
Linaro.org: Open Source Software for ARM SoCs
On 17 August 2011 06:05, Bernhard Rosenkranzer
<bernhard.rosenkranzer(a)linaro.org> wrote:
> On 17/08/2011, Chao Yang <chao.yang(a)linaro.org> wrote:
>> Hi Bernhard,
>>
>> Well, I personally think so. Are we supposed to stop supporting 2.3.4 after
>> we release 2.3.5 and move all the activities to 2.3.5? Thanks.
>
> I think so - I think the idea is to always stay on current things.
> (Possibly with an exception for when things really change, like
> keeping 2.3.5 around once we can move to 3.x)
> But it's not my call - Zach?
Yup, once 2.3.5 is here (it is now) we'll move on to that.
> ttyl
> bero
>
Hi,
Linaro Android has now moved up to 2.3.5.
The daily builds (https://android-build.linaro.org/index) are now
based on the linaro_android_2.3.5 branch of the manifest.
Please rebase any dev_branches you have to 2.3.5. The
linaro_android_2.3.4 branch will no longer be supported.
Regards
Patrik