Re: Introducing ubiboot N9 (multiboot OS loader)
 

Releasing ubiboot-02 (integrated) version.

This version of ubiboot introduces several niceties;

• It is no longer necessary to install ubiboot on mtd partition
• If installed on mtd partition, less flash eraseblock wear due to ro-mount
• Better handling of exceptional conditions (RTC/USB poweron events)
• Ability to fast-boot to a OS/kernel
• More configurable options
• Persistent logging with correct timestamps

See the full story on http://www.swagman.org/juice/ubiboot/README
Get the newest version from http://www.swagman.org/juice/ubiboot/ubiboot-02

Support on IRC at #ubiboot

Re: Introducing ubiboot N9 (multiboot OS loader)
 

With vers.2 I only get "Failed to load selected OS!", "Please run a maintanance boot".

I had a mtd5 installation before and put content for the kernels from "boot.conf" to "ubiboot.conf" and put ist together with "ubiboot-02.menus.cpio" to MyDocs/boot. I get the menu, but no kernel boots.

will flash back to mtd5-kernel next.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

thanks for your answer,
i want ubiboot only for couriosity and for use n9 at the best possible- i'm not a dev. i know something about unix and terminal but i think isnt enoght. so i appreciate this work and a waitingfor the day (if it come) when we have a step by step instruction or when i learned how to do it!
dont give up with this work!
i think it's awesome
best regards!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

It's possible you have introduced some path problems when you set up your ubiboot.conf based on your previous boot.conf.

There should be a /var/log/ubiboot.log" in your system which might show what is the problem.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

You might want to try the new ubiboot-02 then. It is easier to set up than the original ubiboot.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@juiceme
Astonishing!
Real nice one.

Would have loved the logging ability in first version to save me some time ;)

What about updating from 01 to 02. I think as easy as grab source/ubifs.tar and overwrite? Or do we need to do some more.

Thanks also for the USB/RTC thingy. I hope it works, will see soon.
I had modified the init to only enable the maintenance mode when bootreason was pwr_key and USB attached (so first push power button and then attach USB). But this seems way better.

Another report:
I had a lot of wd32_to bootreasons. Almost always after shutting down device from any other kernel. And then boot up and let menu time out ( so default kernel l2fix was chosen). Then first boot did not succeed and a second boot (also timeout) did work. For this second boot the bootreason was wd32_to. Any ideas?
Did not go completely through sources, but have seen you have command line in logger (which holds also bootreason, right?)

Another report (which you may change maybe):
in new sources: when/if the kexec loading fails we get a log, but this log will not show the error number given back

also the possible number of block devices is limited to 8, so a maximum of 7 partitions is supported for mmcblk. You may forget about p8 and p9. I did so :)
btw: Thanks for the p7 configuration possibility

: Selecting Harmattan OS, running kernel /boot/Harmattan/boot/zImage-2.6.32.54-openmode-l2fix.pr13
Apr 4 16:03:52 (none) user.notice 0: Failed to load selected OS!

whats wrong? The kernel is stored on rootfs in /boot, like before on version 01. Uses the vers. 02 a different mounting?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@mmemorph
Do you have set the G_HARMATTAN_AUTOBOOT=1 ?

Then reset it to '0' and you should be OK. See irclog...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well, updating from 01 -> 02 is really easy, just grab the ubiboot-02_040413.tar, put the ubiboot.conf and ubiboot-02.menus.cpio in the root of your ubifs partition (since you already have prepared that) and check the content of the ubiboot.conf.

The fix should work now. The logic is 2-staged, first it is detected that powerup reason was "usb" and then sysfs is mined for the actual event, whether it is "charger" or "data" connection. Device only enters maintanance mode if it was plugged to a computer.

Just realised that therr is some unclean umounting going on... propably that amounts to the problems coderus has been also having. Just took me 30min to boot back to Harmattan :D

I'll have a look at it when I need to change init code anyways to fix the current issues.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

There are some issues that need fixing, been debugging it now for some time. :mad: