Re: Introducing ubiboot N9 (multiboot OS loader)
 

When you look at the device filesystem when running harmattan, then the correct place is /boot/ as your mmcblk0p2 is mounted as /

When you look at the device filesystem when running ubiboot, the same location becomes /boot/Harmattan/boot/ because your / is now a RAMFS instance, and your mmcblk0p2 is mounted at /mnt/2/, which is symlinked to /boot/Harmattan/ :D


What happens when your boot does not succeed, will the device just remain with black screen, does it reboot back to menu, or does it start loading Harmattan and then stop?

What is your device's HW revision?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

1- Boot the device press the MeeGo button the device Shutdown
2- Boot the device again choose the MeeGo button device Shutdown
3- Boot the device choose the MeeGo button the Nokia annimation apears and phone

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Okay, now as you have Meego Harmattan running, can you check the ubiboot log which is created on your device as; "MyDocs/boot/ubiboot.log"

For each time you start device with ubiboot you will find an entry in the log, can you post that log somewhere?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Possibly an OTA upgrade ?

So do a:
and good luck.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Here it is :
https://www.dropbox.com/s/7ccb859q0zsi0ex/ubiboot.log

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks.

According to the log, each time you boot Harmattan, it should start normally as far as ubiboot is concerned:

Jan 2 11:13:42 (none) user.notice root: Loading kernel /boot/Harmattan/boot/zImage_2.6.32.54-openmode_l2fix
Jan 2 11:13:42 (none) user.notice root: kexec_load() successful
Jan 2 11:13:42 (none) user.notice root: Restarting to selected OS

If there was a problem that ubiboot could detect, you would see something else than "kexec_load() successful" in the logfile.
Now, the problem is then something that happens after kexec() which starts the 2nd stage kernel.

Now, I presume your harmattan has to be PR1.3 level, as else you propably could not start the zImage_2.6.32.54-openmode_l2fix kernel at all. (it would require an older PR kernel to match the OS)

So, most propably it is an aegis-related problem in startup. Can you check in your /var/log/syslog (and possibly /var/log/syslog.old) if there is something defilite that occurred when you tried starting harmattan and failed?

One thing that comes to mind, in which way have you entered Open Mode? Unless it is by back-to-back-closedmode-openmode flashing, it can leave your aegis in a state that causes all kinds of funny business, includeing but not limited to boot problems. :mad:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I flashed nitdroid kernel to enter openmode .. Didnt flash the openmode_fix

Re: Introducing ubiboot N9 (multiboot OS loader)
 

That is also OK, it forks with any openmode kernel, but the important thing to do is to first flash it fully Closed Mode and then flash to Open Mode, without letting the device boot between the flashings.

If you do it that way, your device aegis keys will be created for Open Mode and everything will work much better.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Nice service, but not available from N9:
;)