Originally Posted by caveman

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?

Originally Posted by juiceme

As far as I know you are the first one ever to get ubiboot launch Harmattan on a HW rev.1603 device...

Originally Posted by caveman

not so fast :-) I am one step behind: I installed nemo and was testing the dual boot with moslo. Ubiboot is my next step when I manage to have harmattan stable.

Originally Posted by juiceme

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...

Originally Posted by lpt2007

I am still confused, please tell me where Is the right place to put kernel files if I use default boot.conf file.

thx in advance

Originally Posted by juiceme

Just put them in "/boot/" when you are running Harmattan.

Originally Posted by thedead1440

peterleinchen,
Seems like you forgot to delete the 3 folders as user:

Code:

rm -rf /home/user/.aegis
rm -rf /home/user/.accounts
rm -rf /home/user/.activesync

Try not to change between open mode and stock kernels. Changing between openmode kernels is fine but once you involve stock you are going back to aegis configs which cause the issue

Originally Posted by peterleinchen

That is a real pity, if so.
Because then my second problem strikes again:
2. when I want to add a SIP account, this does not work (connection to SIP not possible)
when I boot stock kernel I can connect and this password is not forgotten. But it only works with stock kernel, not with an open mode. Did I miss something here?
Does SIP not work under open mode kernel?

Originally Posted by juiceme

Now if that's the case then there is some aegis-related dependency that I do not know about. Granted, I am not using SIP.