Hi, On 1 September 2013 20:33, Phi Debian <phi.deb...@gmail.com> wrote: > Hi All, > > Well I got a solution, I took the rootfs.img, truncate 4G, losetup, > gparted, then instead of expanding part2 as I did in my prev try, I > simply added a partition3, that I formated ext4 > > I can then boot as before and now I got one more dev I can use to > mount my extra data partition. > > mkdir /d > mount /dev/mmcblk0p3 /d > df > > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/mmcblk0p2 963288 652152 244988 73% / > udev 514152 4 514148 1% /dev > tmpfs 103060 176 102884 1% /run > none 4 0 4 0% /sys/fs/cgroup > none 5120 0 5120 0% /run/lock > none 515280 0 515280 0% /run/shm > none 102400 0 102400 0% /run/user > /dev/mmcblk0p3 3030800 4608 2852524 1% /d > root@linaro-developer:~# > > An happy camper :) I got now to start the NW on a bridge should be a breeze :) > Cheers, > Phi > > On Sun, Sep 1, 2013 at 6:53 PM, Phi Debian <phi.deb...@gmail.com> wrote: >> Hi Guru's >> >> I successfully builf my own kernel abd run it for arm64, I try now to >> do the same trick with arm32. >> >> I need to have a root fs bigger enough to do basic dev in c user code. >> >> I choose latest raring-developper for this. DL >> vexpress-raring_developer_20130826-443.img.gz >> >> I can then mount it and extract vmlinuz and initrd then boot it like >> given on some doc pages >> >> qemu-system-arm \ >> -kernel vmlinuz \ >> -sd vexp.img \ >> -M vexpress-a9 \ >> -cpu cortex-a9 \ >> -serial stdio \ >> -m 1024 \ >> -initrd initrd \ >> -append 'root=/dev/mmcblk0p2 rw mem=1024M raid=noautodetect >> console=ttyAMA0,38 >> 400n8 rootwait vmalloc=256MB devtmpfs.mount=0' >> >> From there I got a prompt >> >> root@linaro-developer:~# uname -a >> Linux linaro-developer 3.11.0-1-linaro-vexpress >> #1ubuntu1~ci+130822051821-Ubuntu >> SMP Thu Aug 22 05:54:20 UTC 201 armv7l armv7l armv7l GNU/Linux >> root@linaro-developer:~# df >> Filesystem 1K-blocks Used Available Use% Mounted on >> /dev/mmcblk0p2 963288 652056 245084 73% / >> udev 514152 4 514148 1% /dev >> tmpfs 103060 172 102888 1% /run >> none 4 0 4 0% /sys/fs/cgroup >> none 5120 0 5120 0% /run/lock >> none 515280 0 515280 0% /run/shm >> none 102400 0 102400 0% /run/user >> >> >> I need more disc space for doing dev, so I investigated 2 options
if you take a look to the instructions published in the release or the wiki: http://releases.linaro.org/13.08/ubuntu/vexpress you'll notice the pre-built image is generated using linaro-image-tools. you can create a pre-built image with the following command: linaro-media-create --image-file vexpress-raring_developer_20130826-443.img --image-size 3G --dev vexpress --hwpack hwpack_linaro-vexpress_20130826-443_armhf_supported.tar.gz --binary linaro-raring-developer-20130826-474.tar.gz Adjust --image-size option as you need. >> 1) Make the rootfs bigger >> I truncate 4G the rootfs.img (rootfs.img is a short for >> vexpress-raring_developer_20130826-443.img) then I losetup the >> rootfs.img and use gparted to extend the ext4 partition. >> >> Alas next reboot fail, a bit like if /dev/mmcblk0p2 has an hardcoded size... >> >> 2) have an extern (user data) disc, and have it mounted >> So I trucate phi.img 4G, mkfs it, and try to mount it, but I got no >> idea what /dev to use to mount it, and got no idea what could be given >> in the qemu runstring to ask for one more disc in the HW description. >> >> Later on I would need to boot my own kernel, I tried the build from >> source path, all goes fine and I can get an Image a uImage etc, so I >> guess it will be a matter of providing this the vmlinus I get along >> with the initrd I got from teh rootfs.img, will see how it goes. But >> for now my problem is really to have more disc space either in rootfs >> ot in an additional disc. >> >> Any help appreciated. >> >> Cheers, >> Phi > > _______________________________________________ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
