Re: Introducing ubiboot N9 (multiboot OS loader)
 

yes thats right :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Awesome. I wish I had the skills to get my phone set up like the one in your video.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Instead of using cp and tar you can only use tar:
Nice work! I Just bricked my device. It shows Nokia logo and then i blackouts. I don't want to reflash my device.
I just need normal zImage for kernel and then it will go to normal mode.

EDIT1 : used http://downloads.nitdroid.com/e-yes/n9/zImage.pr13 and reflashed kernel. Atleast, phone is now booting.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Bricking the phone for good is not easy, but getting into reboot loop or unbootable state is. Fortunately it is almost always really easy to fix it. Just use rescue mode boot, and mount your ubifs into some directory, and check/correct what went wrong.

During development, I have not even counted how many times it has happened to me, kernel development is like that :D:D:D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

This is awsome, I'm going to try right now and will report back later.
Thanks JuiceMe !

Re: Introducing ubiboot N9 (multiboot OS loader)
 

juiceme, I noticed that on boot, the device is initially sluggish. (fixed by locking and unlocking the phone)

I'm using the Patched Openmode PR1.3 kernel - by any chance, does it need to be patched to explicitly enable L2 cache?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yes, you are correct!

The boot to the Harmattan takes longer than necessary as the stock harmattan kernel (or openmode kernel) do not enable L2 cache in the kexec boot phase. I myself am using a patched "arch/arm/mm/proc-v7.S" which turns the cache back on after kexec().

I guess I should provide the patch for making it boot quicker.
This is the patch from Nemo: https://github.com/nemomobile/kernel...b38e5fe2639e73

BTW, the same also goes with Nitdroid boot, the kernel should also be patched similarily for quicker boot.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I am running this with the open mode Harmatten and Nitdroid. I experience that I have to reboot two of three times before the open mode kernel is loaded and started. When I select the OS from the ubiboot menu, it returns to the ubiboot without starting the selected OS. That happens two or three times and then the OS is loaded.

So if I boot to Nitdroid, and want to switch OS, it takes me two or three reboots. And everytime Harmatten is started, it looks like it initializes again like it is started the first time. I see a very long loading icon before I can use the phone.

I installed ubiboot on a clear nokia N9 with open mode enabled. So I did not had other OS-es installed. Now I am installing the separate OS-es afterwards. I am trying to get the MER os also running, but takes a bit more time....

Are the reboots known issues? Is there some debug options to figure this out?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Anyone uses it on n950 as well

would an installer app be useful ?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I have not encountered that kind of behaviour myself. Either the 2nd level kernel boots correctly or fails, and if it fails then it fails every time until the problem that causes it is corrected.

When the OS&kernel slection has been done, and the icons in the top menu fade away, if there is some problem loading the 2nd level kernel then the device will show an error message in green letters. If that does not happen, then the kernel selection has succeeded and device will boot the 2nd level kernel.

Now, it sounds to me there is some initialization problem in the 2nd level kernel.
Do you have the correct modules in "/lib/modules/<kernel_name>" of your harmattan root partition? Have you checked the module dependencies?
Did you try starting Harmattan with some other kernel, Nitdroid for example?
When you finally get to boot up Harmattan, can you check that the command line parameters for the kernel are correct, do "cat /proc/cmdline". Check also from dmesg if there are some strange errors.