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)

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)

Quote:

Originally Posted by byteninja2 (Post 1327719)

Okay, i flashed the zimage, and now i got farther into the steps, but now i get this: umount: can't umount /mnt: Invalid argument

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)

Quote:

Originally Posted by juiceme (Post 1327653)

All your basic settings seem to be in order, there is no reason that I see that the 2nd stage boot should fail.

Does your boot.conf list your kernels like you have set them up, meaning, does the boot menu for harmattan for example show the labels you have in conf file?

Could you post your boot.conf and the content of the directory you have your kernels on? (default, that is the directory /boot on mmcblk0p2)
And also, the content of the directory your modules are in (/lib/modules on mmcblk0p2)

I see you have the Nemo partition set up correctly, can you boot Nemo OK?

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)

Quote:

Originally Posted by peterleinchen (Post 1327937)

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)

Quote:

Originally Posted by coderus (Post 1327927)

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

are you unmounted mtd4 before reboot ?

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by farfary (Post 1327946)

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

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 ...