Hi,An alternative (and much simpler) way is to replace offending groups in ks file with its modified contents. So, for example instead of putting @Common Console Tools you can just list packages it contains:
snapper-zypp-plugin tar wget grep gzip openssh rsync parted zip vim unzip less xz nano curl strace diffutils patch findutils wdiff powertop sudo ca-certificates-mozilla iptables tree # intel-gpu-tools
Notice that offending intel-gpu-tools package is commented out. I'm attaching ks file I'm using to create common arm image. By using it you can create image simply by running command without the need to mirror repositories:
sudo mic create loop common-arm.ks --release=latest Best regards, Jacek On 06/06/2014 11:49 AM, Roman Kubiak wrote:
I already opened a bug in JIRA to fix those repository issues and once that is done i think a ready image will appear on download.tizen.org (this is ongoing https://bugs.tizen.org/jira/browse/TC-29)Below is an extract on how to get the image built for M0 _**_ _*To create the image manualy:*_ * Mirror the current Live repository with ARM rpms for Tizen common from http://download.tizen.org/snapshots/tizen/common/common-wayland-arm/latest/repos/common/armv7l/packages/ (you need the entire structure, just mirror that location somewhere on you disk) * Once that's done you need to make sure that the package mic-bootstrap is in the repository (once it was missing from the downloaded repository, i copied some other ARM profile on download.tizen.org)The repository needs to be rebuilt, download two XML files: * The repository metadata needs to be fixed (it is currently broken and MIC will refuse to build an image), you need 2 XML fileshttp://download.tizen.org/snapshots/tizen/common/common-wayland-ia32/latest/repos/common/ia32/packages/repodata/group.xmlhttp://download.tizen.org/snapshots/tizen/common/common-wayland-ia32/latest/repos/common/ia32/packages/repodata/patterns.xml place them in the repodata directory of the downloaded structure. |# cp patterns.xml group.xml repodata/| I had to edit the patterns.xml and remove the <rpm:entry <http://rpmentry> name="intel-gpu-tools"/> tag (it causes a dependency problem for mic later on) To rebuild the repository data, cd into the directory that you downloaded and run (you need the createrepo package |# createrepo -g repodata/groups.xml | |# modifyrepo repodata/patterns.xml| * Download the .ks file for the profile you want to use (there currenly is no ARM kickstart image, but you should use the IA32 kickstart with little modifications) (attached) * Change the repository path in the KS file to whatever location you downloaded in the first step for example (assuming that i downloaded the files to /media/porucznik/live/common/arm-wayland): repo --name=common-wayland_armv7l --baseurl=file:///media/porucznik/live/common/arm-wayland/ --ssl_verify=no * If you are using your own custom KS or you are re-using a KS from a different profile make sure that the below packages are installed (they appear in the %packages section of your KS): |%packages| |usb-server| |usbutils| |sdbd| |security-server| |%end| * Run mic as root or via sudo (replace KICKSTART_FILE with the path to you kickstart and OUTPUT_DIRECTORY to a directory where you want the resulting image to placed) |# mic create loop KICKSTART_FILE -A armv7l -o OUTPUT_DIRECTORY| This will create a .img file (depending on the KS it might have a different name, if you are using the provided KS it will be platform.img, if it's a different file name rename it to platform.img) * Run the below script to create a flashable TAR file: |#! /bin/bash| |for imgfile in *.img; do| | echo -en "$imgfile: "| | echo -en "fsck "| | e2fsck -p -f $imgfile > /dev/null| | size=$(resize2fs -P $imgfile 2>/dev/null | awk '{ print $NF }')| | size=$((size*110/100))| | echo -en "resize2fs ($size)"| | resize2fs $imgfile $size 1>/dev/null 2> /dev/null| | echo| |done| |echo "Tar"| |tar cf image.tar *.img| |echo "Done"| |ls -al image.tar| * This will produce a file image.tar you can lthor to your device |# lthor image.tar| On 06/06/2014 07:54 AM, ??? wrote:Dear Roman Kubiak, My name is Jinmin Chung and I am a Mobile PM in Tizen 2015 project.I am pleased to hear that you got the Tizen 3.0 common ARM binaries running on M0.Actually when I tried the same what you wrote in the below mail, unfortunately, I got some error so that I couldn't get the ARM binary.https://lists.tizen.org/pipermail/dev/2014-May/003008.htmlCould you explain how you can build the binary in detail? Actually it was very hard to make meta data files like group.xml and pattern.xml.If you give a detailed guide, then I'll ask HQ engineers - Tae-Soo Kim and Tae-Soo Kim to reproduce the ARM binary for M0.One more thing is ...Why don't you ask Dominique to create M0 target in OBS and download.tizen.org site so that anyone can download the same binary for M0?I think that It will be very helpful for our Samsung engineers to work for Tizen 3.0.Regards, Jinmin*From:*Dev [mailto:[email protected]] *On Behalf Of *Roman Kubiak*Sent:* Wednesday, June 04, 2014 6:28 PM *To:* [email protected]*Subject:* Re: [Dev] Tizen:Common @ ARM metup at TdcSf14 (exynos, allwinner sunxi, freescale, renesas...)I got odroid x2 running, with software rendering (framebuffer) it runs fine, but once you load up MALI and use the HDMI output the kernel starts to crash. I reported this bug to the guys that are working on odroid support in the kernel and i'll let you know when they come up with something.M0 (the official target) works with framebuffer and MALI, i posted 4 bugs to get some fixes on ARM in the Common repository. Once those get fixed it should be really easy for anyone to build their own images.best regards On 06/04/2014 12:32 AM, Philippe Coval wrote: Hi, Let me recycle this thread to announce that there are many pple who seems to hack to make Tizen:Common supporting their favorite ARM configuration I started to list different works in progress on this page https://wiki.tizen.org/wiki/ARM But it could be nice to met face to face also at TdcSf14 let's met tomorow Wen morning at 8 am at our booth eurogiciel one is the one on left once you enter though the leftest door : https://lh3.googleusercontent.com/-XimbLWrox0w/U43b_ex93aI/AAAAAAAAAF0/ujsi_2NMu40/w299-h530-no/20140602_038.jpg You will recognize the a demo of current Tizen3 Common (wayland) on Olimex A20 ... Btw are there any unofficial exynos image to test or resources (with or without mali blobs) I managed to get odroid board, It would be nice to demo as well ... If you there pass the info around and see you at breakfast :) -- -------------- Roman Kubiak ---------------- -------------- Roman Kubiak -------------- _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
-- Jacek Bukarewicz Samsung R&D Institute Poland Samsung Electronics [email protected]
common-arm.ks
Description: application/java-keystore
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
