![]() |
Re: Introducing ubiboot N9 (multiboot OS loader)
The first time you run MOSLO as described in the installation guide, your mmcblk0 will be repartitioned, so that your partition 1 (MyDocs) is split into two parts, and the upper (4G) part is then assigned to partition 4.
It looks a bit weird but it's a valid partition configuration. If I remember correctly it works without losing your data but to be sure backup your MyDocs before doing that. (if I remember correctly I had to reformat my partition 1 after that...) After partitioning it will look something like this: Code:
~ # /sbin/sfdisk -l |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
So i have to boot to Moslo, connect the N9 with the USB-Cable to PC, check the fdisk -l, if i have the /dev/mmcblk0p4 and than ? What should i I do with the nemo image.bz2 ? bzcat to /dev/mmcblk04 ? Sorry for my dumb questions... THank You |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
You should follow the guide https://wiki.merproject.org/wiki/Nemo/Installing using the part "Dual-boot method" which will not flash your bootloader but just starts up the MOSLO installer. When your mmcblk0 is repartitioned, it will be exported to your linux PC via USB, then you can just untar the NEMO image to the exported partition. Then, unmount, and if you have already installed ubiboot, just boot it to the Nemo installation. The defaults in boot.conf already contain reference to the Nemo partition and kernel, if you have not changed them. When in Nemo, set up 3G or WIFI networking, login to shell and do "zypper ref; zypper dup" as root to get the latest updates. It looks quite slick with the new homescreen layout :) |
Re: Introducing ubiboot N9 (multiboot OS loader)
Can somebody tell me where is correct location to un-tar file "nitdroid_n9_jellybean_alpha5.tar.bz2" if I am using un-changed boot.conf.
|
Re: Introducing ubiboot N9 (multiboot OS loader)
@lpt2007 same with nitdroid instruction ;)
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
And where is correct location for kernel file "zImage.pr13" if I am using unchanged boot.conf? this: "/boot/Harmattan/boot/" or this "/mnt/2" |
Re: Introducing ubiboot N9 (multiboot OS loader)
@lpt2007 /boot/zImage.pr13
read instructions lovely! |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
Quote:
I got it all wrong. |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
Note that also the target of the link is the "/mnt/2" of the ubiboot FS, not the "/mnt" of your Harmattan root FS. When (still in ubiboot FS, running the menu...) you do "mount /dev/mmcblk0p2 -t ext4 /mnt/2", what happens is that your Harmattan root FS now appears on the "/mnt/2" of your ubiboot FS. Now, remember you have the symlink there, the place that your kernels will appear can be resolved to: "/boot/Harmattan/boot/" This is same as "/boot/" on your Harmattan root FS. If you are still confused, either just take my word for it or grab a pencil and piece of paper and sketch it out for yourself... :D |
Re: Introducing ubiboot N9 (multiboot OS loader)
I have been trying a dual boot configuration with harmattan and nemo on my N9 (1603).
I managed to have both systems booting and working, but could never achieve stability in harmattan. I tried the following kernels: bzImage that came with nemo installation (on boot-orig dir), openmode kernel, openmode kernel + l2fix. The only kernel that allowed me to boot harmattan was the l2fix. However, the system had stability problems, with several reboots in sequence. On the other hand, nemo was rock-solid. What kernels are you using for harmattan? Is it running stable? |
Re: Introducing ubiboot N9 (multiboot OS loader)
@juiceme (also thedead1440)
I have two "severe" problems now. Maybe more related to open kernel instead of ubiboot, but as I read from TMO I did everything right: flashed full eMMC stock image. flashed open kernel, repartitioned, prepared ubifs, flashed ubi kernel, booted open mode l2 fix kernel BUT when I now try to 1. enter a mail password it is forgotten with next reboot even when I boot into stock omap kernel and/or recreate the account I have to reenter on next boot This is the same with all kernels (stock, open mode, l2 fix, ...) 2. when I want to add a SIP account, this does not work (connection to SIP not possible) when I boot stock kernel I can connect and this password is not forgotten. But it only works with stock kernel, not with an open mode. Did I miss something here? |
Re: Introducing ubiboot N9 (multiboot OS loader)
peterleinchen,
Seems like you forgot to delete the 3 folders as user: Code:
rm -rf /home/user/.aegis Try not to change between open mode and stock kernels. Changing between openmode kernels is fine but once you involve stock you are going back to aegis configs which cause the issue ;) |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
Have you ever had those BME-related "connect charger" problems? Have you done some tweaking to device init or are you running ubiboot-as-is? Could you please post your "dmesg" and "/var/log/syslog" after booting to Harmattan from ubiboot? |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
I was SO hopeful, I thought I could crack this 1603 problem with your help... well, I am now making a serial debug adapter that I hope to use to find out what is going on with the boot phase anyway. |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
thx in advance |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
Just put them in "/boot/" when you are running Harmattan. |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
Quote:
Quote:
Because then my second problem strikes again: 2. when I want to add a SIP account, this does not work (connection to SIP not possible) when I boot stock kernel I can connect and this password is not forgotten. But it only works with stock kernel, not with an open mode. Did I miss something here? Does SIP not work under open mode kernel? |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
And together with that aegis password sucker it is way more, otherwise I could boot to stock kernel when explicitly needed (which is 90%), but then the password prob strikes. "Bug loop". :( Another report experienced that "connect charger" today. But mainly/only when booting the default (l2 fix) and letting the menu time out. It happened only when menu timed out, then it started to boot, message, reboot to ubi and boot to default after another time out. So maybe something in second boot stage times out? Or it is really the pwr_off boot reason (from previous shutdown, which have not been handled) given to second kernel? And another report sometimes the menu does not react on touch. So I try to select a kernel, but the touch is not recognized. And then menu times out. Did you notice that, too? |
Re: Introducing ubiboot N9 (multiboot OS loader)
If someone has 1603 in Tampere region, I could connect serial cable to it and see whats wrong with the boot.
And regarding sip, most likely it is just because that you have booted into secure mode, ie you didnt do clean jump to open mode when you flashed into openmode. Which should be fixaple by removing and recreating the aegis store that holds the sip data. |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
looking forward to it:) |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
full reflash, boot, devel-su and disable disclaimer (no more), flashed open mode kernel, boot up What is wrong here? And about aegis store holding SIP data: if you refer to /home/user/.aegis I have already deleted and tried again under open mode kernel |
Re: Introducing ubiboot N9 (multiboot OS loader)
@peterleinchen
http://talk.maemo.org/showpost.php?p...&postcount=212 |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
@juiceme i want request. automatically boot to kernel if only one in list ;)
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
Not bad, will be implemented :) Actually I think I make it configurable ON/OFF as it's almost the same effort. |
Hello everybody!
It's possible to create a wiki or a pdf instruction for noob (like me) ? I need a very very very simple instruction... |
Re: Introducing ubiboot N9 (multiboot OS loader)
Well it's actually a bit of an overview rather than detailed step-by-step guide on purpose.
It is important that you have at least basic understanding of the required concepts, like unix filesystem and working on terminal in order not to blow your foot off with this. Part of this is that you DO have to tune this according to your own device setup. This is because ubiboot is really most useful for developers that want and need to boot different OS'es and kernels easily. |
Re: Introducing ubiboot N9 (multiboot OS loader)
Releasing ubiboot-02 (integrated) version.
This version of ubiboot introduces several niceties;
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)
Quote:
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)
Quote:
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)
Quote:
|
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 |
Quote:
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)
Quote:
Quote:
Quote:
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
All times are GMT. The time now is 07:22. |
vBulletin® Version 3.8.8