maemo.org - Talk - Introducing ubiboot N9 (multiboot OS loader)

maemo.org - Talk (https://talk.maemo.org/index.php)

- Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)

- - Introducing ubiboot N9 (multiboot OS loader) (https://talk.maemo.org/showthread.php?t=89345)

Re: Introducing ubiboot N9 (multiboot OS loader)

@jmsarriat mtd partitions unused by system and you can not care about them :)

Re: Introducing ubiboot N9 (multiboot OS loader)

Can someone give me more detailed instruction about this part?

Where can I download kernel & os files for Nitdroid,Harmattan,Nemo and where I must put them if I use default boot.conf.

thx in advance

Quote:

4.) Next, you must configure your 2nd level boot kernels, or at leat one OS and kernel.
If you do not do this correctly you will be stuck on the boot selector with nothing
to boot up to.

Bootable OS & kernel configuration is done in the file "/etc/boot.conf" on the ubifs.
There are 6 entries for Nitdroid, 6 entries for Harmattan and 6 entries for Nemo.
You do not need to fill up everything, of course. Just the bits you have on your N9.

The "G_<os>_<n>_LABEL" identifier is the line shown on the menu.
The corresponding "G_<os>_<n>_FILE" is the path to the bootable kernel.
Note the "G_<os>_NUM" variable, this tells the menu how many lines to show, starting
from the line 1.
The filesystem is pre-set to that "/boot/Harmattan" is a link to "/mnt/2" which is
mounted as /dev/mmcblk0p2 and "/boot/Nemo" is a link to "/mnt/4" which is mounted
as /dev/mmcblk0p4.

If, for example your Nemo partition is something else than 4, then you need to update
symlinks in /boot/ to point to correct loactions and make sure that you mount the
partitions before kernel selection is done (kexec_load needs to see the kernels...)

In my own setup Harmattan and Nemo kernels are stored in "/boot/Harmattan/boot/"
and Nemo kernels in "/boot/Nemo/boot/"

You need to copy your kernels to the correct location!

The modules for the kernels are located in each OS's hierarchy, normally in the
"/lib/modules" directory.
Do not forget to have the correct modules there, and remember to do "depmod -a <name>"
if you are copying new modules to the directory!

Re: Help with Step 4.

Quote:

Originally Posted by jmsarriat (Post 1331360)

Hi,

I followed the step by step directions on the README file and everything has worked as it should. But i have a question regarding the step 4. My N9 has Nitdroid installed as described in their own tutorial, it works without a problem, so i assume i have a plain open mode and everything else is stock/default. I didn't quite understand what should be configured in the boot.conf file, where should i copy new modules nor what "depmod -a <name>" would do. My question is, given my actual configuration should i modify this file in any way? or can i just leave the default values and go on?

Thanks for your help,

Me

Hi!

Configuring how your kernels appear in the menu is done in the boot.conf file. The defaults in there are how my own system appeared at that moment, but something like this is very basic configuration:

Code:

# Nitdroid kernels

G_NITDROID_NUM=1

G_NITDROID_1_LABEL="Eyes zImage.pr13 kernel"

G_NITDROID_1_FILE="/boot/Harmattan/boot/zImage.pr13"



# Harmattan kernels

G_HARMATTAN_NUM=3

G_HARMATTAN_1_LABEL="Plain openmode kernel"

G_HARMATTAN_1_FILE="/boot/Harmattan/boot/zImage-2.6.32.54-dfl61-20121301"

G_HARMATTAN_2_LABEL="Openmode + L2fix"

G_HARMATTAN_2_FILE="/boot/Harmattan/boot/zImage_2.6.32.54-openmode_l2fix"

G_HARMATTAN_3_LABEL="Nitdroid pr13 kernel"

G_HARMATTAN_3_FILE="/boot/Harmattan/boot/zImage.pr13"

With this you have just the one kernel for Nitdroid, and three alternate kernels you can use for Harmattan: plain open mode, l2-fixed and Nitdroid-pr13.

Now, in addition to setting up your boot.conf, you need to put these kernels somewhere. A good place (and this is what is shown in the boot.conf file) is to put the kernels in the "/boot" directory on your Harmattan rootfs (mmcblk0p2).
So just copy the kernel files there.

That part about the modules and depmod is only useful to you when you want to compile and test your own kernels (which might have modules that have different dependencies & naming conventions than the default set of modules)

If you are just using the vanilla kernel, vanilla open mode, l2-fixed openmode or Nitdroid-pr13 kernels, then you do not have to do anything to your modules as all of those use the already installed /lib/modules/2.6.32.54-dfl61-20121301 path.

And, like Coderus says, unless you have more OS'es than just Harmattan and Nitdroid, this might not really give you any extra advances, except perhaps the integrated repair mode which I find quite useful myself.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by lpt2007 (Post 1331451)

The Nitdroid kernel you can download from E-yes's repositories, same place where you downloaded your android FS tarfile.

For the vanilla open mode kernel, you can look at this thread for information: http://talk.maemo.org/showthread.php?t=81579

The l2-fixed kernel you can get from the ubiboot home page http://www.swagman.org/juice/ubiboot/

See my previous posting for the items in boot.conf...

Seem there only problem with hw1603 16GB

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by TMavica (Post 1331526)

Seem there only problem with hw1603 16GB

Currently, that is true.
I would need to see what happens in the boot phase of rev.1603 devices that's different from the other revisions to fix it :(

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by coderus (Post 1331420)

@jmsarriat mtd partitions unused by system and you can not care about them :)

That's true. If you have an non-ubiboot aware kernel flashed to your device, it acts like there is no ubi partitions whatsoever.

In fact I find it useful to have it there even if you do not use it for boot selection; the repair mode can be then activated by just booting an ubiboot-aware kernel with the "-l -b" options without flashing anything... :D

I have 2 of my friends in 16GB 1603, same situation, cant boot harmattan, recharge battery something like that

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by peterleinchen (Post 1328949)

Hey juiceme,
OK, got a dead battery. And put it to charger. Checked again and now return value is "0", so everything okay!
This time bootreason=usb. When I got the 255 the bootreason was sw_rst. Maybe this caused the 255? IDK.
- I still have sometimes weird restart behavior, i.e. after decoupling battery (nemo did not start) it needed a few attempts. It seems bootreason=pwr_off? Maybe change the bootreason in command_line also?
- Charging does not take place when connected charger to powered off phone. it goes to ubi console and does not charge.
Maybe wait for 60s and when there was no telnet connection established (do not know how to detect) then boot to Harmattan (bootreason=act_dead) and let it charge?

OK, finally had time to tweak init a bit, checking the powerup reason. I added the following check before the check for existing USB connection:

Code:

# if boot reason is USB or RTC, boot up directly to default Harmattan

bootreason=$(cat /proc/original_cmdline | cut -d' ' -f12 |  cut -d'=' -f2)

if [ "$bootreason" != "pwr_key" ]; then

  if [ -r /boot/menu/select_default_os.sh ]; then

    mount /mnt/2

    /boot/menu/select_default_os.sh

    if [ $? -eq 0 ]; then

      /usr/bin/disable_pm

      # restart to the default Harmattan OS

      kexec -e ; echo $? ; sleep 10

    fi

  fi

fi

Also added a short script "/boot/menu/select_default_os.sh" which basically does the same thing as "/boot/menu/select_os_animated.sh" when booting to default Harmattan OS & kernel.

Now, what this is supposed to do; When the boot reason is not "pwr_key", meaning the device has woken up either from pugging in USB or RTC event (alarm clock triggering) then instead of normal menu the device should boot to Harmattan directly.

For RTC events this works as it should; device boots up to the alarm handling state and then powers off, just as it would do without ubiboot installed.

Unfortunately it still does not do that when USB is plugged in, at least with computer connected USB (did not try it yet with just dummy charger), instead it tries to boot into Harmattan but goes to boot loop instead.

Re: Introducing ubiboot N9 (multiboot OS loader)

Hello guys...
My Ubiboot is working ok.
Harmattan booting with OpenMode / Open Mode L2fix / Nitdroid PR13 kernels
NITDorid booting with PR13 / PR13 USB fixed Kernel

What about Nemo?
Maybe someone can give me a short advice how i should install Nemo on /dev/mmcbll0p4 ?

fdisk -l /mmcblk0 show me:

/home/user # fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 64.1 GB, 64130908160 bytes
4 heads, 16 sectors/track, 1957120 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 17 1760512 56335872 c Win95 FAT32 (LBA)
/dev/mmcblk0p2 1760513 1891584 4194304 83 Linux
/dev/mmcblk0p3 1891585 1957120 2097152 83 Linux

So i think i must create /dev/mmcblk0p4 ?

Can anybody assist me?
In the Nemo installation manual this part isn't well discribed IMHO....

THX