maemo.org - Talk - Chrooting Nemo Mobile

maemo.org - Talk (https://talk.maemo.org/index.php)

- Nemo Mobile (https://talk.maemo.org/forumdisplay.php?f=53)

- - Chrooting Nemo Mobile (https://talk.maemo.org/showthread.php?t=89491)

Chrooting Nemo Mobile

Hi,

I downloaded the Nemo Mobile raw image. I tried mounting it, but ext* doesn't work for mount. Is there any way to mount (and then chroot) the Nemo raw image?

Thanks

Re: Chrooting Nemo Mobile

With kpartx its very easy.

Re: Chrooting Nemo Mobile

Quote:

Originally Posted by elros34 (Post 1329403)

With kpartx its very easy.

Hmmm... After mounting gnome-disk-utility shows that there are no partitions.
Is there any way to convert the nemo mobile image to something that qchroot would handle?

Re: Chrooting Nemo Mobile

I don't know but to mount raw ubuntu or old meego image I use:
kpartx -av ubuntu/meego.raw
mount /dev/mapper/loop0p1-3
and copy /usr/bin/qemu-arm-static

Re: Chrooting Nemo Mobile

Don't now exact what you want but can create your own custom nemo images using this guide:

https://wiki.merproject.org/wiki/Image_Creation

https://wiki.merproject.org/wiki/Nemo/Creating_Releases

Its a good way to learn more about Mer stuff IMHO :)

I am trying learn more that way.

This can be done inside MerPlatformSDK or SailfishSDK

(SailfishSDK == PlatformSDK + sailfish components etc..)

Re: Chrooting Nemo Mobile

Quote:

Originally Posted by mikecomputing (Post 1329504)

I used the first way, but I'm getting:

Code:

marcin@marcin:~/nemo$ sudo mic-image-creator --config=../Downloads/nemo-handset-armv7hl-n900.ks --format=rootfs --cache=/var/cache/meego-bootstrap --arch=armv7hl



mic-image-creator: error: no such option: --copy-kernel

Re: Chrooting Nemo Mobile

Quote:

Originally Posted by marmistrz (Post 1329392)

Hi,

I downloaded the Nemo Mobile raw image. I tried mounting it, but ext* doesn't work for mount. Is there any way to mount (and then chroot) the Nemo raw image?

Thanks

Check if the Nemo image has an extra /SOMEDIR at a beginning of the actual system files.

http://wiki.meego.com/ARM/N900/Install/chroot

or try This topic

http://213.128.137.28/showthread.php?p=1149489

or you can configure Nemo image and use mic-chroot Like

https://wiki.mozilla.org/Building_Fe...ot_environment

Re: Chrooting Nemo Mobile

Quote:

Originally Posted by elros34 (Post 1329422)

I don't know but to mount raw ubuntu or old meego image I use:
kpartx -av ubuntu/meego.raw
mount /dev/mapper/loop0p1-3
and copy /usr/bin/qemu-arm-static

Well, it was a good idea. I dd-ed the data partition (ext4), but now, when I try to mount & chroot it (let's say at /home/nemo), and do

Code:

chroot /home/nemo

I get

Code:

FATAL: kernel too old

Do I need to copy anything from the other partitions (the boot one?) I've seen uImage and vmlinuz there, so this might be the thing...

Thanks

Re: Chrooting Nemo Mobile

I'm chrooting it on-device, are there some special requirements for it?

Re: Chrooting Nemo Mobile

Quote:

Originally Posted by marmistrz (Post 1333433)

I'm chrooting it on-device, are there some special requirements for it?

I'm tried do this long time ago but without succes. I guess we can't chrooting nemo images due to mismatch between the versions of glibc in nemo and maemo. You should ask qole for better info.
http://qole.blogspot.com/2010/11/run...chroot_06.html

Re: Chrooting Nemo Mobile

Quote:

Originally Posted by elros34 (Post 1333441)

you can use the deb file It is based on qole script

http://www.mediafire.com/?cx23ficm83lgfcu

Then renamed Nemo image to meego and run it. If it does not work You must conformation Nemo image Such as Next

http://qole.blogspot.com/2010/11/run...00-chroot.html

Re: Chrooting Nemo Mobile

Quote:

Originally Posted by amr.fayz (Post 1333470)

I'm using the old version of MeeGo Miro (still with tar.gz) and doesn't work.

When doing everything manually,

Code:

mount -t ext4 /path/to/img.ext4 /.nemo

chroot /home/nemo

The last command fails. qchroot does some nice tweaking, but it's essential to chroot the system alone...

Re: Chrooting Nemo Mobile

What is the size of the img ؟ Possible be needy Sizing like backtrack 5

http://www.opendebug.com/article/466922

http://talk.maemo.org/showthread.php?t=72933

Re: Chrooting Nemo Mobile

amr.fayz, there is no problem with mount or scripts (details) but with chroot.

Re: Chrooting Nemo Mobile

Quote:

Originally Posted by elros34 (Post 1333520)

amr.fayz, there is no problem with mount or scripts (details) but with chroot.

What about extension ext4 the img Working the extension is ext3 & ext2 Is it possible to be the reason that ؟

http://www.robertocolistete.net/MaemoMeeGo/EasyDebian/

Re: Chrooting Nemo Mobile

Quote:

Originally Posted by amr.fayz (Post 1333527)

What about extension ext4 the img Working the extension is ext3 & ext2 Is it possible to be the reason that ؟

http://www.robertocolistete.net/MaemoMeeGo/EasyDebian/

The problem is not with the image file, it mounts alright. I just cannot change the root directory (chroot) to the mount directory. Generally if bad suffix (ext*) is used, qchroot fails. it detects the fs type this way.

Re: Chrooting Nemo Mobile

Quote:

Originally Posted by amr.fayz (Post 1333527)

What about extension ext4 the img Working the extension is ext3 & ext2 Is it possible to be the reason that ؟

I have my own debian armhf on ext4 partition so this is not the point, check this.

Re: Chrooting Nemo Mobile

Quote:

Originally Posted by elros34 (Post 1333541)

I have my own debian armhf on ext4 partition so this is not the point, check this.

You are right

HTML Code:

ext3 to ext4 (or anything else)



A word of warning. The version of e2fsprogs in Maemo is ancient, and xfs-tools seems to be non-existent, so if you use ext4 or xfs, you will lose the ability to fsck the image on the device itself. This is fine if you have (and are happy to use) a Linux PC; if not then you may want to stick to ext2/ext3.



Migrating from ext3 to ext4 has no impact on existing files that were written under ext3, only on newly written files. Therefore, to achieve the expected benefit from a migration to ext4, you'll need to create a fresh image of the desired size, format it and copy the contents of your old image onto your new one. You'll probably want to do this over USB from a Linux PC rather than from the device itself, both for speed reasons and (probably) for newer versions of the applicable filesystem tools.



First, create a file of the desired size, either with dd or by simply making a copy of the image file that you intend to clone.



cp <image-name>.img.ext3 <image-name>.img.ext4



Now format the new image file with the desired file system. We'll use ext4 here, but this should work for any filesystem that is supported by kernel-power.



mkfs.ext4 /path/to/mounted/n900/<image-name>.img.ext4



You might want to consider the "-T small" option to mkfs, which will yield a smaller block size (1KB) and more inodes, otherwise you'll be limited to 262,144 files in 1,048,575 blocks, also, at your option "-m 0" to set the reserved blocks count to zero (do not keep 5% back for the superuser). Once that's done, we need to mount both images, and clone the old one to the new one:



mkdir /mnt/old

mkdir /mnt/new

mount -t ext3 -o loop /path/to/mounted/n900/<image-name>.img.ext3 /mnt/old

mount -t ext4 -o loop /path/to/mounted/n900/<image-name>.img.ext4 /mnt/new

cp -a /mnt/old/* /mnt/new/

umount /mnt/new

umount /mnt/old



It does no harm at this point to run a filesystem check on the newly created image. You'll also need to make sure that the image is either configured in .chroot or is the first such image in the directory in order for the Easy Debian chroot scripts to pick it up.