![]() |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
Can you specify which tasks and parts of the process exactly are the difficult ones? Of course it is difficult to me to know, as it is always hard to see mistakes in own work... (which is why we have peer review :p) |
Re: Introducing ubiboot N9 (multiboot OS loader)
I guess the most misleading may be the definition of location where the second-level kernel is stored on device.
Excerpt from my config: Code:
# The first OS is usually Nitdroid. The kernel (second-level, to-be-booted) may be where ever you like. For convenience juiceme created links (named after the definition of G_OS1_NAME) on first-level system under /boot: so /boot/Nitdroid defines /dev/mmcblk0p5 In my case the kernel is on /dev/mmcblk0p5/boot/ see G_OS1_2_FILE="/boot/Nitdroid/boot/zImage_pr13-l2fix" but in former times I had in on partition #2: G_OS2_PARTITION=2 G_OS2_NAME="Harmattan" #G_OS1_2_FILE="/boot/Harmattan/boot/zImage_pr13-l2fix" |
Re: Introducing ubiboot N9 (multiboot OS loader)
Yeah, the paths are confusing should be documented. How is it with preinits? Will it suffice to modify the target system's /sbin/init or more trickery is required? Are there any thing which have to be done? (The preinit is needed due to the watchdog kicking in)
I seem to spend far much time wondering about how to properly set up the boot process. |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
Moreover, the partition definitions correspond to the physical partition layout of the device which is something else as the way the partitions are mounted in various OS'es... Quote:
Reason for that is simple; if I have a potential lockup, I want to see the kernel oops... :p |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
However this might be dependent on the actual HW revision of the device...? |
Re: Introducing ubiboot N9 (multiboot OS loader)
Hi.
I think the 'nand chip'/'omap2-onenand'/'whatever' is showing symptoms of ageing in my backup device (possibly a refurbrished one)..... Code:
[86115.653320] init: xsession/sysuid main process (8139) killed by FPE signal Is it possible to use ubiboot to avoid the use of partitions mtd0 --> mtd6? I think this could help to extend the device's life a bit :). I'm running nandtest command and all six show r/w errors. Maybe only using /dev/mtd0 as bootloader to redirect the process somewhere else would help? Regard. |
Re: Introducing ubiboot N9 (multiboot OS loader)
Not really knowing what I speak of, but:
we all have those errors in kernel log. And as long as the error is correctable -as I understood the discussion (somewhere on TMO)- it is not a problem. So I do not think about it... |
Re: Introducing ubiboot N9 (multiboot OS loader)
I use the latest version of ubiboot with 6 boot options, i'd like to use one with this menu of only 3 OS (meego, android, sailfish) mainly because this looks more clean and i dont use the others anyway.
How do I do it? |
Re: Introducing ubiboot N9 (multiboot OS loader)
1.) get the toolkit from https://toosa.swagman.org/svn/animatronics/
2.) the essentials are described in the README file |
All times are GMT. The time now is 07:13. |
vBulletin® Version 3.8.8