Reply
Thread Tools
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#201
The first time you run MOSLO as described in the installation guide, your mmcblk0 will be repartitioned, so that your partition 1 (MyDocs) is split into two parts, and the upper (4G) part is then assigned to partition 4.

It looks a bit weird but it's a valid partition configuration.

If I remember correctly it works without losing your data but to be sure backup your MyDocs before doing that. (if I remember correctly I had to reformat my partition 1 after that...)

After partitioning it will look something like this:

Code:
~ # /sbin/sfdisk -l

Disk /dev/mmcblk0: 1957120 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/mmcblk0p1         16  1632511  1632496   52239872    c  FAT32
		end: (c,h,s) expected (1023,3,16) found (1023,63,32)
/dev/mmcblk0p2     1760512  1891583  131072    4194304   83  Linux
/dev/mmcblk0p3     1891584  1957119   65536    2097152   83  Linux
/dev/mmcblk0p4     1632512  1760511  128000    4096000   83  Linux
		start: (c,h,s) expected (1023,3,16) found (1023,63,32)
		end: (c,h,s) expected (1023,3,16) found (1023,63,32)
 

The Following User Says Thank You to juiceme For This Useful Post:
explit's Avatar
Posts: 592 | Thanked: 1,603 times | Joined on Apr 2010 @ Berlin / Germany
#202
Originally Posted by juiceme View Post
The first time you run MOSLO as described in the installation guide, your mmcblk0 will be repartitioned, so that your partition 1 (MyDocs) is split into two parts, and the upper (4G) part is then assigned to partition 4.

It looks a bit weird but it's a valid partition configuration.

If I remember correctly it works without losing your data but to be sure backup your MyDocs before doing that. (if I remember correctly I had to reformat my partition 1 after that...)

After partitioning it will look something like this:

Code:
~ # /sbin/sfdisk -l

Disk /dev/mmcblk0: 1957120 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/mmcblk0p1         16  1632511  1632496   52239872    c  FAT32
		end: (c,h,s) expected (1023,3,16) found (1023,63,32)
/dev/mmcblk0p2     1760512  1891583  131072    4194304   83  Linux
/dev/mmcblk0p3     1891584  1957119   65536    2097152   83  Linux
/dev/mmcblk0p4     1632512  1760511  128000    4096000   83  Linux
		start: (c,h,s) expected (1023,3,16) found (1023,63,32)
		end: (c,h,s) expected (1023,3,16) found (1023,63,32)
Thank you juiceme,

So i have to boot to Moslo, connect the N9 with the USB-Cable to PC, check the fdisk -l, if i have the /dev/mmcblk0p4 and than ?

What should i I do with the nemo image.bz2 ?
bzcat to /dev/mmcblk04 ?

Sorry for my dumb questions...

THank You
 
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#203
Originally Posted by explit View Post
Thank you juiceme,

So i have to boot to Moslo, connect the N9 with the USB-Cable to PC, check the fdisk -l, if i have the /dev/mmcblk0p4 and than ?

What should i I do with the nemo image.bz2 ?
bzcat to /dev/mmcblk04 ?

Sorry for my dumb questions...

THank You
Yes, that's basically it.

You should follow the guide https://wiki.merproject.org/wiki/Nemo/Installing using the part "Dual-boot method" which will not flash your bootloader but just starts up the MOSLO installer.

When your mmcblk0 is repartitioned, it will be exported to your linux PC via USB, then you can just untar the NEMO image to the exported partition. Then, unmount, and if you have already installed ubiboot, just boot it to the Nemo installation.
The defaults in boot.conf already contain reference to the Nemo partition and kernel, if you have not changed them.

When in Nemo, set up 3G or WIFI networking, login to shell and do "zypper ref; zypper dup" as root to get the latest updates. It looks quite slick with the new homescreen layout
 

The Following User Says Thank You to juiceme For This Useful Post:
Posts: 9 | Thanked: 0 times | Joined on Mar 2013
#204
Can somebody tell me where is correct location to un-tar file "nitdroid_n9_jellybean_alpha5.tar.bz2" if I am using un-changed boot.conf.
 
coderus's Avatar
Posts: 6,436 | Thanked: 12,699 times | Joined on Nov 2011 @ Ängelholm, Sweden
#205
@lpt2007 same with nitdroid instruction
__________________
Telegram | Openrepos | GitHub | Revolut donations
 
Posts: 9 | Thanked: 0 times | Joined on Mar 2013
#206
@lpt2007 same with nitdroid instruction
Thx for help coderus

And where is correct location for kernel file "zImage.pr13" if I am using unchanged boot.conf?

this: "/boot/Harmattan/boot/"
or this "/mnt/2"

Last edited by lpt2007; 2013-03-27 at 16:28.
 
coderus's Avatar
Posts: 6,436 | Thanked: 12,699 times | Joined on Nov 2011 @ Ängelholm, Sweden
#207
@lpt2007 /boot/zImage.pr13
read instructions lovely!
__________________
Telegram | Openrepos | GitHub | Revolut donations
 
Posts: 9 | Thanked: 0 times | Joined on Mar 2013
#208
Originally Posted by coderus View Post
@lpt2007 /boot/zImage.pr13
read instructions lovely!
And what about this part of instructions:
The filesystem is pre-set to that "/boot/Harmattan" is a link to "/mnt/2" which is
mounted as /dev/mmcblk0p2
This sentence means to me that I must put kernel files in "/mnt/2" or
I got it all wrong.
 
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#209
Originally Posted by lpt2007 View Post
And what about this part of instructions:

The filesystem is pre-set to that "/boot/Harmattan" is a link to "/mnt/2" which is mounted as /dev/mmcblk0p2
This sentence means to me that I must put kernel files in "/mnt/2" or
I got it all wrong.
Well, that just means that on the ubiboot FS you have symlink "/boot/Harmattan --> /mnt/2"
Note that also the target of the link is the "/mnt/2" of the ubiboot FS, not the "/mnt" of your Harmattan root FS.

When (still in ubiboot FS, running the menu...) you do "mount /dev/mmcblk0p2 -t ext4 /mnt/2", what happens is that your Harmattan root FS now appears on the "/mnt/2" of your ubiboot FS.
Now, remember you have the symlink there, the place that your kernels will appear can be resolved to: "/boot/Harmattan/boot/"
This is same as "/boot/" on your Harmattan root FS.

If you are still confused, either just take my word for it or grab a pencil and piece of paper and sketch it out for yourself...
 
Posts: 191 | Thanked: 415 times | Joined on Jan 2012
#210
I have been trying a dual boot configuration with harmattan and nemo on my N9 (1603).

I managed to have both systems booting and working, but could never achieve stability in harmattan. I tried the following kernels: bzImage that came with nemo installation (on boot-orig dir), openmode kernel, openmode kernel + l2fix.

The only kernel that allowed me to boot harmattan was the l2fix. However, the system had stability problems, with several reboots in sequence. On the other hand, nemo was rock-solid.

What kernels are you using for harmattan? Is it running stable?
 

The Following User Says Thank You to caveman For This Useful Post:
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 06:28.