Thanks for cpio lesson.

As the N9 does not support SD cards my thinking was there is no need for full partition names (just partition number is unique name). But in general you are right, of course

For NIT it may work directly with my small changes, for Harmattan I do expect some more problems, direct p2 access, whatever. So this would surprise if it would work out of the box

--edit
Please see latest changes.

Neat, the changes make sense and at least the partition number variableizing is going to be included in future releases.

What about the aegis-directory copying hack, can you make SIP calls with your operator work correctly with it?
I would not include that yet in official releases as it depends on your device that you back up the aegis directories before taking that into use...

I would like to see if the method Jonni proposed would work with your SIP accounts (meaning, reflash to open mode without booting to closed mode between)

OK!??

After non-booting and correction of (lot of) typos I switched between stock and openmode kernel.
Still it did not work, so I double-checked and found that I could not delete (rm) the links from stock/closed kernel, even with devel-su and develsh. So I checked those links and I created them as root under openmode. ! ?
OK, nevertheless created a new account for SIP (working under stock kernel).
Then booted to open kernel and expected my accounts to ask for passwords. Guess what?
Right. There was nothing asking me. Everything was right. All my e-mail accounts worked directly. Of course the SIP could not connect.
Then created another mail account under open mode and rebootedL no password was asked, so everything fine.
What should I say?
No need for my little hack (which would need more testing) and no need to reflash (Jonni's proposed method). But maybe I will go for this once again . Maybe (right now no need anymore).

P.S.: I do not understand it and I feel tricked/cheated/verarscht ...

peterleinchen,

You re-created the aegis directories in open mode so they won't ask you for passwords again even if you did the new account creation in normal mode...

But I am pretty sure, that I rm'ed those directories under open kernel. And created a new mail account directly.
Only explanation I have is that I maybe deleted and created the first (SIP) account then under closed stock kernel (so aegis striked again).
But this time I am absolutely sure to have the first account created under open mode!

peterleinchen,

When flashing an open mode kernel, the CAL is converted to read-only and this region becomes writeable only when the rootfs is flashed again. Flashing just the stock kernel wont reverse the read-only state of CAL. Hence the experience you faced

It is (not) totally OT to this thread, but not really related to ubiboot. So I do not want to hijack juicee's thread.
But:
I know about CAL. And I did not flash in between these two experiences. Just removed the dirs again and started all over to create my accounts.
Once it did not work. Second time it worked.

BTW (if we speak OT ):
Is really nobody experiencing the same SIP behaviour with OpenKernel (no connection, but with stock kernel everything works) under ubiboot? Or does nobody use SIP?

E-yes has compiled a new nitdroid kernel image that includes the L2Fix.

Using this new image in ubiboot lets ICS boot up in 33 seconds vs. using the older zimage.pr13 which takes about 65 seconds to boot.
Also, Nitdroid is instantly more responsive to touch after the boot.

You can download the new kernel from http://downloads.nitdroid.com/e-yes/n9/ubiboot/zImage
(md5sum=22114bd3cbaa88ee8c49c022f53080a1)

Hello juiceme, hello guys.
The ubiboot_01 version for the mtd5 Partition working perfect for me, but ubiboot_02 not working at all... I put ubiboot-02.menus.cpio, ubiboot.conf and my kernels inside the MyDocs/boot folder. Also copied the kernel zImages into /boot on my N9 rootfs.
in the ubiboot.cfg I adjusted folders to /boot/.

I see the menus, can choose the kernel (or not choose them)...
Then i got black screen and nothing happen....

Any ideas ?

PS: inside the mtd5 i have a fully working ubifs_01 with all kernels inside /mnt/boot

For sure just typos in config. But without posting content of conf amd ls of kernel directory we all can just guess.