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

PamNor | # 571 | 2013-10-06, 20:05 | Report

Oh! forgot the logfile....

Attached Files

peterleinchen | # 572 | 2013-10-07, 07:47 | Report

Would you mind to give also your full ubiboot.conf?
Especially interested in
G_OS4_PARTITION=?

The Following User Says Thank You to peterleinchen For This Useful Post:
PamNor

PamNor | # 573 | 2013-10-07, 08:29 | Report

OK. My current ~/MyDocs/boot/ubiboot.conf

Attached Files

ubiboot.conf.txt (9.8 KB, 123 views)

juiceme | # 574 | 2013-10-07, 09:29 | Report

I am fairly sure your problem lies here:

In the log, when you have made the kernel selection and the kernel image is loaded, you should see something like you have when starting harmattan:

Oct 6 19:34:39 (none) user.notice root: Started animated OS selection menu
Oct 6 19:34:46 (none) user.notice root: Selecting Harmattan OS, running kernel /boot/Harmattan/boot/zImage_2.6.32.54-openmode_l2fix
Oct 6 19:34:47 (none) user.notice root: Loading kernel /boot/Harmattan/boot/zImage_2.6.32.54-openmode_l2fix
Oct 6 19:34:47 (none) user.notice root: kexec_load() successful
Oct 6 19:34:47 (none) user.notice root: Restarting to selected OS

However, you got this:

Oct 6 19:40:14 (none) user.notice root: Started animated OS selection menu
Oct 6 19:40:20 (none) user.notice root: Selecting Firefox OS, running kernel
Oct 6 19:40:21 (none) user.notice root: Cannot load Firefox kernel
Oct 6 19:40:21 (none) user.notice root: Boot OS/kernel selection failed

Now, this looks to me like the kernel name string is undefined here. Either the problem is in the selection script or your config, but as you can boot it when used as the first OS, then it sure points to a menu script problem.

The Following User Says Thank You to juiceme For This Useful Post:
PamNor

juiceme | # 575 | 2013-10-07, 10:25 | Report

Originally Posted by juiceme View Post

Now, this looks to me like the kernel name string is undefined here. Either the problem is in the selection script or your config, but as you can boot it when used as the first OS, then it sure points to a menu script problem.

Yeah it's a menuscript problem after all

I have some variables mixed up in the select_os_animated.sh script. Sorry about that!
I'll fix that and compile new CPIO version as soon as I have time to do it!

The Following 2 Users Say Thank You to juiceme For This Useful Post:
PamNor, peterleinchen

Garp | # 576 | 2013-10-07, 12:03 | Report

Originally Posted by PamNor View Post

I have installed Ubiboot 0.3.4 and its great. I have one problem with Firefox OS. when i configure the OS4 section in ubiboot.conf and try booting i got the green warning message.

Where did you get Firefox OS from?

juiceme | # 577 | 2013-10-08, 09:27 | Report

Originally Posted by juiceme View Post

Yeah it's a menuscript problem after all

I have some variables mixed up in the select_os_animated.sh script. Sorry about that!
I'll fix that and compile new CPIO version as soon as I have time to do it!

Allright, corrected&compiled&tested new CPIO that corrects the problems for booting Firefox, Ubuntu, Sailfish.

Please find the file at http://www.swagman.org/juice/ubiboot..._08102013.cpio
(md5sum=fa80955d84514867f76c1bca3068e217)

No need to reflash. Just copy the archive to your MyDocs/boot (or whereever you have the config and edit ubiboot.conf accordingly.

Last edited by juiceme; 2013-10-08 at 09:29. Reason: added the md5sum

The Following 2 Users Say Thank You to juiceme For This Useful Post:
PamNor, peterleinchen

peterleinchen | # 578 | 2013-10-08, 10:15 | Report

Originally Posted by juiceme View Post

Allright, corrected&compiled&tested new CPIO that corrects the problems for booting Firefox, Ubuntu, Sailfish

Thanks for resolving.
And especially for adding the empty line to ubiboot.log! (makes it way easier to read

)

Another suggestion/question from my side:
you have modified the G_global vars to be named according to the OS slot (and not anymore names). BUT the symlinks in /mnt are still named according to the OS names (e.g. G_OS1_NAME="Nitdroid", but G_OS1_1_FILE="/boot/Nitdroid/boot/zImage.pr13")?
As you compiled all into the kernel and did not put the ubifs.tar online, I cannot see the available symlinks. Or are they created on the fly (according to G_OS1_NAME)? Would you please be so kind and give more info here? Or put sources online?

nicolai | # 579 | 2013-10-08, 10:21 | Report

Hi juiceme,

Thank you ubiboot it is really great.

I tested ubiboot on my n950, took the instructions from the wiki page
http://wiki.maemo.org/Ubiboot
and have some questions.

1. Installing open mode kernel
I can not boot with zImage_2.6.32.54-openmode_l2fix
for the n950 I used open mode kernel from here
http://maemo.cloud-7.de/950/openmode_kernel_PR1.1/
Booting in open mode works now.

2. installing other systems.
Then I installed nemo and android, both are working
but I can not boot harmattan anymore.
It seems none of the custom zImages for harmattan are working on a n950. I then changed the boot menu to explicit include one entry
for open mode kernel from http://maemo.cloud-7.de/950/openmode_kernel_PR1.1/
This kernel worked in the step prior to flashing ubiboot kernel.
But it does not work from within the boot menu.
The display stays black but ubiboot.log says:
kexec_load() successful

If I don't select any boot menu item, which kernel will be booted?

Does the ubiboot.conf file has any use at all? It seems I have
to change the cpio file for any boot menu change?

regards
Nicolai

juiceme | # 580 | 2013-10-08, 10:49 | Report

Originally Posted by peterleinchen View Post

Thanks for resolving.
And especially for adding the empty line to ubiboot.log! (makes it way easier to read

)

Sometimes the small changes&fixes are the neatest

Originally Posted by peterleinchen View Post

Another suggestion/question from my side:
you have modified the G_global vars to be named according to the OS slot (and not anymore names). BUT the symlinks in /mnt are still named according to the OS names (e.g. G_OS1_NAME="Nitdroid", but G_OS1_1_FILE="/boot/Nitdroid/boot/zImage.pr13")?
As you compiled all into the kernel and did not put the ubifs.tar online, I cannot see the available symlinks. Or are they created on the fly (according to G_OS1_NAME)? Would you please be so kind and give more info here? Or put sources online?

This time I anticipated you on this

The symlinks are indeed created in init from the conf variables.
You can download the latest source snapshot tarball from the sources directory on either Swagman swagman or Skeiron. (latest is called animatronics_03102013.tar)

The RAMFS source is under the ubifs/ directory in the tarball, this is the complete seed for the FS that gets created in kernel compile.

I also host the complete source tree on my svn server at https://toosa.swagman.org/svn/animatronics which of course has the up-to-date sources, includeing this latest correction I made this morning. However the bandwidth for that server is not very large so you might not want to clone that... (full checkout will take some minutes)