Re: Introducing ubiboot N9 (multiboot OS loader)
 

One of the advantages of Open mode and ubiboot should be: 'You will not need to flash the device to install and test a new kernel; just copying the kernel and modules to the device is enough.'

I have earlier used this procedure for Open mode: http://forum.nitdroid.com/index.php?topic=241.0
meaning zImage.pr13 but without sillyboot and NITDroid.

Instead I have multiboot from here:
http://talk.maemo.org/showthread.php?t=86957

I have flashed to Open mode in Windows7 therefore /boot is empty (e.g. no zImage here)

Checking my N9 in terminal shows:
~ # export LANGUAGE=C
~ # accli -I
Current mode: open
IMEI: 357923045945013
Credentials:
UID::root
GID::root
GRP::root
GRP::adm
GRP::dialout
GRP:: pulse-access
~ # uname -r
2.6.32.54-dfl61-20121301

Want to change kernel to:
zImage_2.6.32.54-ubiboot-02_040613
Using this procedures:
http://wiki.maemo.org/Ubiboot#Moving...g_Filebox_Root

Download file:
zImage
ubiboot-02_040613.tar

Copy to /home/user/MyDocs/boot:
ubiboot.conf
ubiboot-02.menus.cpio

Copy to /boot (which is empty!):
zImage (changed to zImage_e-yes_nitdroid+12fix)
zImage_2.6.32.54-ubiboot-02_040613

Correct and if then further what to do?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

So I assume you now have it working, all the kernels in /boot/ etc...?
If still you have problems, please post the ubiboot logs /var/log/ubiboot.dmesg and /var/log/ubiboot.log

Re: Introducing ubiboot N9 (multiboot OS loader)
 

This is how it is, when you have it working after that you need never again use flasher to update your kernels. :D

Correct up to now, however you do not need to put zImage_2.6.32.54-ubiboot-02_040613 into /boot/

Every other kernel you need goes to /boot/, and possinbly if you have different modules then they go to /lib/modules/<kernelname>/

However, the zImage_2.6.32.54-ubiboot-02_040613 is the ubiboot kernel, the 1st stage kernel that you need to flash to the device.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Does it mean that even if I have Open mode right now I need to flash to get the ubiboot-2 kernel?

Or even if I have the old stuff: "zImage.pr13: (not recommended) before Ubiboot was published, this was the latest zImage being used for dual-booting or multi-booting NITDroid."
It's not enough to avoid flash to get new kernel?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yes, I can boot Harmattan ;), Android and Nemo 2.6.32. :D
Thank you !

Is it normal I cannot boot (black screen) "Unstable 3.5.3 SabreTSq" ?:confused:
I read that it could take some time, so I have plugged it and I am waiting... :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yes, ubiboot is a loader kernel.
It is not a "user-kernel", in a way that it is meant to be a boot loader 1st stage, which then launches your "real" kernels which run your OS.
Think of it like Grub or LiLo, or Uboot.

Under ubiboot, you then select/load the 2nd stage kernel, this can be plain open mode kernel, old-style nitdroid kernel, enhanced kernel+NAT, enhanced Nitdroid kernel, whatever.

Ubiboot is just the method to select between all these kernels (and of course the OS that the kernel runs, as default it can be Harmattan, Nitdroid or Nemo. Later maybe something else too... FFOS, SailfisOS, Tizen,...)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well you would need to supply the kernel first :)

See, the menu entries are configured in your ubiboot.conf. For each OS/Kernel combination you find a configuration section there.

The lines are just examples, you need to copy the kernels and modules to the device or edit the ubiboot.conf to your own desire.

And yes, the SabreToothSquirrel is my take on porting the 3.5.3 linux kernel to Nemo... nowhere near usable and needs LOTS of work :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

i'm stuck at 'Re-partitioning failed!' (installing nemo) and i cannot telnet to my N9
edit : i can telnet succesfully but i cannot repartition
edit 2 : succesfully repartitioned

for future reference MyDocs should have at least 6GB free ( i had 5.5)
edit 3 : i cannot start any os

http://pastebin.com/pQUzTN5d ubiboot.dmesg

Re: Introducing ubiboot N9 (multiboot OS loader)
 

bump added log file

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well, ubiboot.dmesg looks okay, can you paste the ubiboot.log also?
Can you show what is on your /boot/ directory? (ls -la /boot)
Did you extract the preinits correctly? (ls -la /sbin/preinit*)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I got it it working . It was the preinits . Thanks anyway for the hard work in ubiboot :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks for a very good explanation!:)

PC:
C:/Programmer/Nokia/Flasher:
DFL61_HARMATTAN_40.2012.21-3.340.04.1_PR_LEGACY_340_ARM_RM-696_PRD_signed.bin
flasher.exe ( from Winflasher_3.12.1.exe)
zImage_2.6.32.54-ubiboot-02_040613

N9:
/home/user/MyDocs/boot:
ubiboot.conf
ubiboot-02.menus.cpio (unpacked or *.tar?)

/boot:
zImage_2.6.32.54-dfl61-20121301
(alternative kernel-plus 2.6.32.59 for Harmattan)

Now I have ubiboot in the bottom so to speak and on top Harmattan “default” open mode kernel.
Later I can add NITDroid, Nemo etc if I want to!

Two questions:
What about the slow boot issue mentioned in the README file 4.), is that a problem if I don’t use openmode+L2fix kernel? http://www.swagman.org/juice/ubiboot/README

The Backup menu: http://talk.maemo.org/showthread.php?t=86957 can’t be used with ubiboot as I see it?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

The unpacked config file and the cpio is what you want there.
The cpio is an archive format, just like tar is. It contains the part of the ubiboot FS that has the menus and the launching system.

If you want to use the kernel-plus you also need to unpack the related modules to /lib/modules/2.6.32.54-dfl61-20121301
If you want to use the kernel-plus_NAT you also need to unpack the related modules to /lib/modules/2.6.32.59-plus_nat-20121301 directory.

Also, do not forget to edit the kernel locations and names in ubiboot.conf.

For example, if you have a kernel named "/boot/zImage_foobar" and you want to have a menu entry "My foobar kernel" as the first line in the ubiboot menu, you could put something like this in ubiboot.conf:
G_HARMATTAN_1_LABEL="My foobar kernel"
G_HARMATTAN_1_FILE="/boot/Harmattan/boot/zImage_foobar"

If you want it as the second entry, put the lines in G_HARMATTAN_2_LABEL and G_HARMATTAN_2_FILE and so on...

You need to have the so called "l2fix" in the kernel to make it boot up faster.
There are lots of kernels that have this, for example the latest Nitdroid kernel from e-yes, and the harmattan-plus kernel from Hurrian have this.

Well it could easily be implemented. I made a test cpio for Farfry which has a menu entry for backup tools, but it needs some work before being useful. As I recall there were 2 requests by Farfry for features not implemented in ubiboot yet to make it possible to do it, bmestat and sshd. those are still under construction.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks again for your detailed answer and help!:)

Yes know cpio is an archive, question is shall it stay as so or be extracted to .../MyDocs/boot/ ?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

as it is.
it will be extracted to RAM rootFS when device boots.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I just want to share a guide I revised/compiled for windows users. Hope It can help others. It is based from what I experienced.

http://www.ziddu.com/download/228114...uide.docx.html

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Could you please upload it to some place it's possile to access?

When I try following your link, it ends up to some download site which offers a windows execuatble to download.
Presumably this EXE then will download the actual document, but there are at least 2 problems with this:

1.) Will only work with Windows machines. Even as I don't have windows, I'd like to review the guide...
2.) Nobody wants to download some random EXE files, whoknows what malware they contain...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

before clicking the download,just unclick the box saying Download with ziddu accelerator and get recommended offers.

feel free to review it coz Im sleepy when Im doing it haha

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks for the tip, and thanks also to peterleinchen who already sent me the file by mail :D

I looked over the document, and it seems to be pretty detailed.
Only small comments:

1.) in the chapter "7. Extract preinits.tar and the NITDroid files" you tell as the last thing to do is to turn off the device, to flash to open mode. I think most logical thing to do is to go to open mode before this, so put the chapter "Flash the Device with Open-Mode Kernel" before chapter 7.

2.) the last steps in the last chapter, where you copy the Noemo kernel from /boot/ of mmcblk0p4 to the /boot/ of mmcblk0p2 (to Harmattan root) is not necessary, as ubiboot can find the Nemo kernel from the Nemo partition (and with default setup it looks for it from there already...)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I see, Thanks. That are the things that are already existing in the guide :D That's the guide that mostly are in Linux and it just made my NEMO screen black lol coz there are drivers I think missing in Windows so I just added the things you taught me to make it work :D Well you can just revised it again and post it to help Windows Users,Thanks again :D

well kudos again to juiceme and topet2k12001

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Can I have ubiboot for dualboot without Nemo? Can it be done just with skipping moslo stuf in installation process?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yes.

You can have ubiboot also for use with just one OS, just if you want to switch kernels easy with that OS for example.
(and it can be any OS you want to...)

If you just want Harmattan & Nitdroid, skip the Nemo parts.
You will of course still have the Nemo icon in the top menu, unless you remove it from the scripts.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I get the green text on nemo and it won't stop. I formatted it via Windows as a prompt came up, was that a bad idea? Also, as I am in Windows "Alt_Os" doesn't come up.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

If I remember correctly you do not need to format it, the repartitioning script in Moslo already does it.
if it needs to be formatted it cannot be done in Windows anyway as it needs to be ext4.
For the same reason your Windows does not see the ALT_OS partition...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hi, I finally managed to install ubiboot,great stuff! Thanks for it :)
Only one thing, I don't understand how to add a new kernel. For, example, I got the stock harmattan kernel from http://www.swagman.org/juice/zImage_...13_nokiasigned and placed to /boot, then? Sorry for my noobiness :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

To get the kernel seen in the menu list, now you need to edit your ubiboot.conf (which in default is in your /home/user/MyDocs/boot/ directory...)

1.) find the place where it says # Harmattan kernels
for example, in my device it looks like this:

# Harmattan kernels
G_HARMATTAN_NUM=5
G_HARMATTAN_AUTOBOOT=0
G_HARMATTAN_1_LABEL="2.6.32.54 + fbconsole"
G_HARMATTAN_1_FILE="/boot/Harmattan/boot/Image-2.6.32.54-fbconsole"
G_HARMATTAN_2_LABEL="2.6.32.54 Nemo backport"
G_HARMATTAN_2_FILE="/boot/Harmattan/boot/zImage-2.6.32.54-juice_backport"
G_HARMATTAN_3_LABEL="Nitdroid pr13 kernel"
G_HARMATTAN_3_FILE="/boot/Harmattan/boot/zImage.pr13"
G_HARMATTAN_4_LABEL="Openmode + L2fix"
G_HARMATTAN_4_FILE="/boot/Harmattan/boot/zImage_2.6.32.54-openmode_l2fix"
G_HARMATTAN_5_LABEL="2.6.32.59 kernel+xxx"
G_HARMATTAN_5_FILE="/boot/Harmattan/boot/zImage_2.6.32.59-plus_nat_extfat-20121301"
G_HARMATTAN_6_LABEL=""
G_HARMATTAN_6FILE=""

2.) The tag G_HARMATTAN_NUM=5 means that the kernel menu holds 5 entries. (5 kernel name lines are shown)
You need to put here a number from 1 to 6, depending on how many kernels you have.

3.) The tag G_HARMATTAN_AUTOBOOT=0 means that there is no autoboot active now. If you change that to number 1...6, then when you press the Harmattan icon, that kernel number will boot automatically, it will not ask for which kernel to boot.
This is useful, for example if you have just one kernel under an OS, for example Nitdroid and always want to boot it.

4.) Each of the tag pairs, G_HARMATTAN_x_LABEL and G_HARMATTAN_x_FILE signify one kernel menu line.
For example, I have G_HARMATTAN_1_LABEL="2.6.32.54 + fbconsole" which means that this text is shown in the menu as the first kernel line.
When I press that line, ubiboot will search for the file specified by the corresponding tag G_HARMATTAN_1_FILE="/boot/Harmattan/boot/Image-2.6.32.54-fbconsole"

So, now you know how this is constructed. If you want to have this kernel you downloaded as the first line, you will need to set the tag G_HARMATTAN_1_LABEL to some name for it (anything is OK, it's yours to decide) and the tag G_HARMATTAN_1_FILE as your kernel path, "/boot/Harmattan/boot/zImage_original_PR13_nokiasigned" for example.

(note here that the file path is /boot/zImage_original_PR13_nokiasigned when you are looking at it in Harmattan, but when you are running ubiboot the device has very different root file system, and then the file appears as /boot/Harmattan/boot/zImage_original_PR13_nokiasigned. This can be confusing for some people...)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@juiceme thank you very much for your reply :)
I'm trying right now :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Ok it worked :)
but the device is still in open mode, I thought that loading the stock kernel would make the device run in normal mode... Btw is this possible at all? :confused:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Unfortunately the way it works, is once you ever run any non-nokia-signed kernel, even just boot it and then immediately reboot with signed kernel, the device goes to open mode and it cannot be put back to normal mode except by flashing it.

I guess this is Nokia's way of ensuring device security/protection, you cannot go to open mode to make some tweak and then return to normal mode :(

There's just one thing that is available in normal mode and not in open mode, and that's device locking. Everything else works OK, so I always run my devices in open mode.
If you absolutely need device lock, then I'm afraid custom kernels and other advanced tweaks are not possible for you, but I assure you everything else works in open mode correctly.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

My problem is not with device lock, but with installations: everytime (almost) I install a package, when it finishes installing all apps shut down and this is quite annoying... This is also a problem while installing for example unrestricted system ui or using n9qtweak :(

Re: Introducing ubiboot N9 (multiboot OS loader)
 

This is indeed strange, I have heard some people complain that they have this kind of problem but I have not ever seen it myself.

I find it is possible this has nothing to do with open mode itself, but rather the way you have entered open mode. Maybe there's something leftover from aegis that's causing this for you?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I tried installing Ubiboot, but the green text for repartioning nemo would not go away. i let it sit for an hour.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

That part is not specifically related to ubiboot, but to Nemo installation. (which people often do want to install along with ubiboot, though).

Normally it should not take more than couple of minutes so clearly something went wrong. Did you try it a second time, just in case it was an one-time glitch?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I don't know, I installed ubiboot using the guide on http://wiki.maemo.org/Ubiboot The only problem i encountered is the devicelock on error on the flasher but of course I've turned off the lock code and track and protect app before. It used to appear even after flash (both firmware and emmc) and the only way to get rid of this was using --erase-user-data=secure. After that everything went flawlessy. I remember that the app used to close after installation also when in open mode with sillyboot some months ago,,, :confused:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yup, tried it 3 times. And yeah, I knew it was Nemo but I didn't want to make a new thread.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Once partitioning is done, it does not reboot on its own... What is the green text saying ?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

The stuff it should say as it says on the Wiki. It just doesn't change.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

juiceme, as I digged the mtd3, I found some occurrences of kernel clashing. And I just had the night before to struggle with charging device in a powered off state. I.e. N9 is shut down, then I attachwall charger, device boots up, selects default kernel (your L2 fix) and crashes/reboots. Then I believe it does it again and on third time it starts with console, Then I unplug, replug and most often it boots/charges correctly then.
I have attached one occurrence. If you like some more, let me know. I hope you can read what is going south...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

At least according to this log, what happens is it is booting Nitdroid, not Harmattan. AFAIK you should autoboot Harmattan if you want to use the ACT_DEAD-type charging scheme.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

omg
copy/paste...

Here is the correct attachment, sorry.