Re: Introducing ubiboot N9 (multiboot OS loader)
 

strange, flashing the zImage is what actually fixed my '/mnt' problem ...
Try flashing zImage again, and start again from the beginning the full procedure.
But wait for JuiceMe answer he knows more than me ... :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

If you get the error "umount: can't umount /mnt: Invalid argument" this just means that you have not mounted anything on your "/mnt/" :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I updated the README file for a bit more thorough instructions

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I'll be terse as usual: GREAT WORK, MAN!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Nemo was not installed. But just did and now it is updating the OS to the latest version. So yes Nemo does start. Actually it starts pretty fast....

The boot menu does show all entries of the boot.conf file. Not all images are there, but I added them already to the boot.conf file.

I will post the contents and the file listing later on, when the update of Nemo is completed.
I think it is something with the kernel modules... probably not all correct. I'll post it as soon as possible.

Thanks a lot for helping

Re: Introducing ubiboot N9 (multiboot OS loader)
 

i need help.
setted mtd4, unpacked ubiboot here, unpacked preinits, flashed ubiboot kernel.
after reboot: nokia logo - phone turns off. no menu, nothing.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Still in the preparation process ...

A bit offtopic, but still related:
I tried to repartition my N9 64GB. Decrementing p3 (MyDocs) to 37 GB, reserving 16GB for other OSes (partitions).
Had to use --force, as disk was mounted (done on dvice), so far so ...
Everything went well, sfdisk shows correct partitions. BUT the MyDocs is still presented to be 53 GB, both when using df or even in mass storage mode on Win.
Any ideas what I have done wrong? Or missed?
Just want to be sure this to fix before continue.

--edit
reason I ask here is juiceme told already in other thread that he repartitioned (used 4th for nemo) and I did not find related answer in TMO

Of course did a reboot.
And tried again with unmounted MyDocs, to no avail.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

try to remove all partition with sfdisk in a linux pc and creat theme again ( i did it and worked very well for me )

Re: Introducing ubiboot N9 (multiboot OS loader)
 

are you unmounted mtd4 before reboot ?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks. Think this will work, of course.

But:
DUMB me ;), I just forgot to do mkfs.vfat on p1, so internal FAT still thought it is 53GB instead of shrinked size.

Continuing ...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Funky... got just a message that says that my phone is in problems. A lot of reboots detected.... :D:D

That was a new screen that I haven't seen before...

But still I have the boot issues. But the three OS-es will run. It takes some extra booting to get it running.

Another thing is that I don't have the depmod command on my phone. So I can't change modules, and that could causes this...?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Did you try flashing back the normal Open Mode kernel, and after in harmattan do "/usr/sbin/ubiattach /dev/ubi_ctrl -m 4 ; mount -t ubifs ubi0:var /mnt"
Then you could check if there is some problem accessing the rootFS.

Did you try to connect the USB during the boot? Didi it make any difference?

What I think the almost only problem that coud cause this is that for some reason your mtd4 cannot be mounted as root FS, and so kernel cannot find/load the init... The zImage_2.6.32.54-ubiboot-01 kernel is selfcontained so that lack of any modules does not make it fail a boot. Only not finding init may do so.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

You should have "/sbin/depmod" in your Harmattan installation.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hmmmm.... I should know that.... :o

Re: Introducing ubiboot N9 (multiboot OS loader)
 

sure. sync && umount /mnt

now i'm in nitdroid kernel, phone works. ubi mounting, i can read and write in it.

Connecting usb changing nothing. Phone still powering off after nokia logo.

------
did again:
http://paste.ubuntu.com/5601080/

---------
also i have log in /mnt/var/log/messages:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Okay, no errors on umout now, but i cant find boot.conf under /etc, maybe uts because filebox wont detect it, but i cant get it on my pc either as nokia locks the n9 from going deeper than MyDocs i think, so how do i access it?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@byteninja2 you should mount ubi0 back to /mnt to get boot.conf in /mnt/etc/boot.conf

Re: Introducing ubiboot N9 (multiboot OS loader)
 

How do i do that?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Okay, did it. Now how do i find and edit the boot.conf file?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hi byteninja2,

sorry for being frank.
If you do not know how to do the above, this tweak may not be for you (at this time). At least minmimum Linux/shell knowledge might be needed.
The boot.conf is located in folder etc/ in root of ubifs, so
/mnt/etc/boot.conf
and use vi to edit on device. Or extract from tar, edit on (Linux) PC and copy to device.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hey juiceme,

many many thanks for this release. I have been waiting for this since I read about multiboot for N9.
It was a hell of a ride. But now I got (almost) all working.
Nit is starting, Harmattan with all kernels.
Very very nice.

I only have problems with Nemo. But I think it is my own fault. I have installed Nemo on mmcblk0p7.
I modified boot.conf, fstab, init, select_os_animated.sh, kexec_load to match my needs (grepped for mmcblk and replaced p4 with p7). But still Nemo does not boot up.
Is there more to adapt?
Or any chance to find logs, what went wrong? ubifs/mnt/var/log/messages does not show anything, neither logs of Nemo partition.
--edit2
Just found that cmdline of Nemo also points to mmcblk0p4. Modified, but still to no avail. Somenone knows where p4 is also hardcoded on Nemo partition?

Again thanks for that piece of OSS.

P.S.: a request: is there a possibility to add a shell to the boot menu, maybe under info tab? So it is much easier/faster to recover from bad tweaking or log checking on device without need of USB/PC.


--edit
P.P.S.: I have another problem, but related to repartitioning. So a bit offtopic here, that is why I posted here my question regarding maximum number of devices/partitions on mmcblk0

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I got this far, and I have experience with Linux. But how do I use vi? And which tar, there are multiple tars for download.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

nano /mnt/etc/boot.conf

Re: Introducing ubiboot N9 (multiboot OS loader)
 

/bin/sh: nano: not found
Now i get this with that command.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

install Developer mode "Utilities"

btw, i agree with peterleinchen about your linux knowledge. you haven't it.

peterleinchen, have you created mnt/5 mnt/6 mnt/7 for partitions? have you modifyed init # Mount the partitions that got kernels on them section?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yep, yep and yep for other sections, too. (will add my mods later)
Maybe I missed something, but after I found hard-coded "mmcblkp04" in /boot/cmdline of Nemo image, I believe the problem is with that?

Or maybe, as thinking while writing, I have added p7 to "kernels on them" section, maybe just replace? (i could not dig any deeper into code due to missing free time. It took me already two days to get here :( OK, with a lot of breaks ;))

Re: Introducing ubiboot N9 (multiboot OS loader)
 

i think you should look into nemo code and recompile some tools or hex edit it

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hmm, not sure if p4 is required. Here are the manual installation information: https://wiki.merproject.org/wiki/Nemo/Installing

I think you know them already.? The only I can think of is that in the old days, you were not allowed to boot an OS from an extended / logical partition.

And you can have max 4 partitions if you don't use extended and logical partitions. So I get the feeling, it is not booting because the OS is placed on a logical partition......

But I don't have any information that can confirm this. It is just a thought.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hey, for the people that have Nemo in non-standard location!!

As peterleinchen got it, I have indeed hardcoded the Nemo partition to be "/dev/mmcblkp04# in the menu selection logic!

When I made it I did not think that people would ever put Nemo somewhere else.

However, it is easy to correct:
Just edit your "/boot/menu/select_os_animated.sh", and find the function load_nemo()
On that function, replace the sed script "s/root\=\/dev\/mmcblk0p2/root\=\/dev\/mmcblk0p4/" with "s/root\=\/dev\/mmcblk0p2/root\=\/dev\/mmcblk0p7/", for example, if your Nemo is on partition#7

Re: Introducing ubiboot N9 (multiboot OS loader)
 

The Linux kernel can boot from extended partitions just fine.
Bootloaders like GRUB may have problems being installed to them, but we don't use that.

Actually, it may even be possible to partition the N9/50 with GPT, making the number of partitions made on it a non-issue.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

coderus, are you still having problems mounting the ubifs root when booting?

I am sure the install method goes exactly as I describe in the README document, as I tried it following my own instructions down to letter:

Just this morning, I helped a friend on the other side of country to install ubiboot and Nitdroid on his device.
The guy in question is total noob, so what we did is I instructed him to open a ssh connection for me, and then I created shared VNC session and remonte-operated his device staright from clean-flashing it to installing ubiboot & jellybean.

For this reason, I belive your device might have faulty NAND flash, and so unable to mount the ubifs root.

It is possible that people who have used their NAND for swap have burned it so badly it cannot be mounted :eek:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks theyosh, Hurrian and juiceme for your input.

Theyosh may be right, that Nemo may not be possible to boot from p7 instead of p4 (opposed to Hurrians -fully agreed from side- answer)?

@juiceme
of course I modified that func and edited some more passages where p4 was mentioned (even in kexec_load). And also modified cmdline of Nemo boot partition.

The kernel of Nemo bzImage is already located as link inside tarball, so there is no need to copy anything after untaring. Right?

I checked everything once again. And I do not get it. Grrr... :angry:
I have attached all my mods in a zip file.
Nitdroid and all kernels of Harmattan work fine.
If you could check that once again, please?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

On checking your modificatinos they seem to be OK.
How exactly does your nemo behave when you boot it, when you select the kernel does it boot after that, and stay hung or does it boot back to ubiboot?

Could you try to boot it manually, meaning: boot to the repair console and log in to the device. Then copy the /proc/original_cmdline and change the partition and give path to the kernel, and give kexec_load;

something like this:

If the return value is 0, then the kernel and command line was loaded correctly, and you can try to boot it with command;

There is one thing still that could affect it, maybe on the command line you need to specify that the boot partition is extended partition, similarily as on booting ubifs partition you need to specify the partition label?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Just came to "similar" conclusion ;)
No, not at least at your level regarding kernel tweaking ...

But according to your question: after selection the menu fades out and then the screen stays blank.
I have added a few log outputs, most important to you/me will be the result of eval --> it is 1.
You will find the used selections (cmdline) in log.txt.
But without knowing where the output comes from not so good, or?

So important message comes from load_nemo func
selected_os _ selected_kernel _ f_command_line _ bootkernel
selected_os _ selected_kernel _ f_command_line _ bootkernel
$?

What is the option to set for loading from logical instead of primary?

Thank you for caring.

--edit
had to modify your manual script to match my current situation. And struggled with virtual kb and not yet installed any text editor and BT and and and and
But got it up and did see something about func not implemented and something with proc_atags. now batt shutdown (N9s and mine also ;) )
Good night.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Good morning.

Seems I hit now another real serious problem.
After shutting down yesterday I attached the N9 to charger without looking at it. This morning I detached (again without looking) and it did not start up. No LED at all. Even after decoupling battery no lights/vibrates/starts.

Seems it started ubi, but did not start charging and battery drained fully. Have to find a charger now (and may flasher tools). Will report back.

P.S.: I had noticed some strange restart behaviour before, but had similar with u-boot and did not care.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@juiceme issue still exists for me. i tried to create ubi partition only 20MB, it before first bad area, but still not loading. is there any other way to set fixed size for ubi partiton?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hi!

Yes, this behaviour can be explained:
(this is a long posting but full of content, so forgive me)

The N9 (like most other modern handhelds) is powered by LiIon/LiPo battery, and charging the battery is a delicate process. This is made more complicated by the fact that the power is sourced from USB line which has it's own specific quirks; For the USB power to be available both ends need to negotiate and announce each other, only then can the source start providing full current to the sink. If the negotiation fails, the power draw is limited to 200mA as a safety feature.

How this is handled in N9: When USB power is applied, even from a dummy chager, the N9 will boot up the kernel and install the BME drivers to handle the charging. When it is "switched off" the user expects it to be dead, but it cannot be for purpose of charging. This is why, if the device is switched off and connected to a charger, it in reality boots up, but it "pretends to be off", it is in the ACT_DEAD state where it runs but user should think it is off.

Unfortunately ubiboot comes there on the way, and the device which normally would boot the stock Harmattan kernel in ACT_DEAD mode now boots to ubiboot. Ubiboot sees that the USB is connected and enters the repair console, exporting directories over USB and waiting for telnet connection.

This is actually a bug in ubiboot I know of but have not corrected yet, what it should do is to check the startup flags, and if NOLO instructed it to "play dead", then it should start up harmattan in ACT_DEAD mode.

Reason why it's not corrected is that I only now thought about it, since I never charge my own device when it is in poweroff state. (I actually tend not to ever power it off...)

Now, when all power has been drained from the N9 battery, it cannot any longer boot up so much that it would get to charging state.
(actually this is also true of Lumias, and propably other smartphones too, at least I know my son's Nexus7 has trouble charging when it is totally drained)

Luckily, there is simple solution how to fix it, you need to use the flasher to jump-start the battery to 10% capacity, and then connect it to charger to top up the charge.

Instructions can be found, for example here: http://talk.maemo.org/showthread.php?t=87709

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I have not tried to resize it, but I am fairly certain at least the whole hard partition size cannot be changed as the use of the partitions is determined by NOLO.
However it really might be possible to resize the filesystem size smaller than the actual partition size.
You might want to consult Jonni for example, as he should know better if it is possible and give some advice on that...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yep, thanks for explaining in detail (not that I was not aware of that, but it is good to reload to memory :))

That'll be nice, because I sometimes just connect to charger without even knowing it is off. Also for sleeping or charging purpose sometimes realy switch off (normally it is up and just flight mode, as you do).
Maybe add that to README or OP?

Oh. And I was able to start it up easily. Just connected charger, did see ubi screen and it was charging a bit. But ust for a minute or so, then the batt LED went off. so I assume no more power to batt. I detached it, started normally , booted to ubi then selected Harmattan kernel and immediately connected charger again. Then it booted up completely and everything fine (without need for flasher).

Thanks.

Any ideas regarding my p7 problem? (Will post the complete error log tonight, hopefully.)