Meego Wiki
Views

ARM/Creating ARM image using MeeGo Image Creator

From MeeGo wiki
< ARM
Revision as of 07:47, 8 November 2010 by Alien (Talk | contribs)
Jump to: navigation, search

Contents

Requirements

 * Fedora 12/13/14, Ubuntu 10.10 or other mic compatible linux distribution.
 * Required tools, e.g., qemu-arm-static and btrfs-progs
 * MeeGo Image Creator tool from MeeGo tools repository

Fedora

Insert the suitable .repo file for you system from http://repo.meego.com/MeeGo/tools/repos/fedora/ to /etc/yum.repos.d/

For fedora 12 and later install the qemu-arm-static from Fedora 11 repository

sudo rpm -Uvh http://repo.meego.com/MeeGo/tools/repos/fedora/11/i386/qemu-arm-static-0.12.3-1.2.i386.rpm

Install the required package:

sudo yum install btrfs-progs mic2

Ubuntu

Add the mic2 PPA repository

sudo add-apt-repository ppa:goelkunal/mic2

Install the packages

 sudo apt-get install mic2 btrfs-tools qemu-arm-static

Run MeeGo Image Creator

Create a working directory and copy your kickstart file there.

Latest kickstart files can be found gitorious (click appropriate branch and then tree).

NOTE: When using the kickstarts from the gitorious repository shown earlier you need to use also --release= option in mic to get @BUILD_ID@ set properly. If you wish to build current daily define --release=daily.

There are also kickstarts available with the weekly build repos which will generate that specific weekly release.

Image will be created in working directory by default.

Packages will be cached in mycachedir to speed up the next image creation.

If you are behind a proxy, you can set it to mic by adding

proxy=http://proxy.yourcompany.com:8080

to /etc/mic2/mic2.conf.

Loop image

sudo mic-image-creator --run-mode=0 --cache=mycachedir --format=loop --arch=armv7l --config=YOUR_KICKSTART 

Raw image (PREFERRED)

Create the image with following command:

sudo mic-image-creator --run-mode=0 --cache=mycachedir --format=raw --arch=armv7l --save-kernel --config=YOUR_KICKSTART

In the end of the mic-image-creator the output files are listed. In this list the file that contains raw in it name is the rootfs image and file with vmlinuz is the kernel. More information on writing the image/flashing the kernel see the pages for the appropriate device, e.g., N900 MMC installation

Troubleshooting

exit status 255 error

warning: %post(libgcc-4.4.2-12.2.armv5tel) scriptlet failed, exit status 255 

This is caused by SELinux, which can be disabled with:

setenforce 0

or

echo "0" > /selinux/enforce

This fix is valid, until you reboot your device.

Personal tools