Re: Introducing ubiboot N9 (multiboot OS loader)
 

Sometimes the automount does not work, I am not sure why but it might depend on your setup. However, if you check your dmesg and see there that the device has been recognized, for example as /dev/sdb, then you can manually mount the partitions.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Now you are looking into the ubiboot FS, not any of the guest FS'es, (Harmattan, Nemo, whatever)

When you run ubiboot, you have a separate ramFS as root, it is not any real partition.
You need to mount your "real" flash partitions somewhere to be able to look/modify those.
In ubiboot the place to do that is the /mnt/1/, /mnt/2/, /mnt/3/... and so on.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

When you ssh to the device in ubiboot as root, your home dir is /root/ of the ubiboot FS.
Before attempting this, you need to do the following things:

Unexport your USB partitions: (if this gives you error, then you have the partitions mounted on your PC and you have to umount them first, cannot really have a partition mounted to 2 different devices at the same time, can you? :))

echo "" > /sys/devices/platform/musb_hdrc/gadget/lun0/file

Mount the drive you have your TAR file on, for example if it is on your My Docs then you need to do:

mount /dev/mmcblk0p1 /mnt/1

Then mount the target you want to extract your preinits to:

mount /dev/mmcblk0p2 /mnt/2

Then, extract the archive:

tar -xvf /mnt/1/preinits.tar -C /mnt/2/

Last thing, sync and umount partitions:

sync ; umount /mnt/1 ; umount /mnt/2

Re: Introducing ubiboot N9 (multiboot OS loader)
 

There are two different things here, and you are mixing them up :)

See, you can have either the partitions mounted to your PC, and then you are working on them on the PC, or you can ssh into the device and mount the partitions on the device and work on them there.

You cannot mix these methods, you cannot have single partition mounted to 2 different devices at the same time.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Ok, on my system, /home/user/MyDocs/boot is a folder, not a file, containing ubiboot.conf, ubiboot-02.menus.cpio, zImage_2.6.32.54-ubiboot-02_040613 and zImage_2.6.32.54-ubiboot-02_301013. I don't see a log anywhere.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@garp
juice explained (again) correct and better than me

@taixzo
what about output of
ls -l /boot (when in harmattan, so /dev/mmcblk0p2/boot()?
Could it be you copied the kernel only to MyDocs/boot and not to /boot? (Of course the listed kernels in MyDocs/boot are only the ubi kernel which needs to be flashed to device)
output of
ls -l /boot
and ubiboot.conf

--
reread and possibly you have old configuration on mtd4/5?
if so, you need to decide to use either of mtd4/5 or MyDocs. Order is mtd4, mtd5, MyDocs
your log files will reside on /var/log/ubiboot*

Re: Introducing ubiboot N9 (multiboot OS loader)
 

The kernels (zImage*) you should put on the /boot/ folder on your Harmattan root.
The log files, ubiboot.log & ubiboot.dmesg will be created after you run ubiboot at least once, in your p1 /boot/ directory which is /home/user/MyDocs/boot in Harmattan.
If you do not have the log files, then check your ubiboot.conf, as there are keys G_LOGFILE_PARTITION="1" and G_LOGFILE_DIRECTORY="/boot" which determine where the log files go.

Ah, one thing to remember! If you are using an older ubiboot version, then the log files go to /var/log/ of your Harmattan installation, and the location is not configurable!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks for your explanation above.
Main problem is not mixing this 2 methods, I think - that's normal in Windows too, connected to masstorage you can't use Filebox in MyDocs at the same time, and if mounted /home, /rootfs etc with Paragon you can't use them either. And you have to choose masstorage or SDK(ssh)/Putty can't do both.

In Ubuntu you dont need Paragon to get device mounted to PC and terminal act as Cmd on Windows (meaning on PC)
But strange thing and my misunderstanding here starts with Ubiboot behavior as I see it, because terminal - and Putty too ! - suddenly can be on device (n9) in maintenance mode - which not the case in Windows (Cmd) - or is it ? -and you have this mounting problem I get into?

Is that correct understood?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Exactly, the automounter daemon (usb-moded actually) in Harmattan makes sure that when you export MyDoxs via USB the device-internal mount is disconnected.
Reason for that is, when a raw partition is mounted in 2 devices simoultaneously, you cannot cache the filesystem accesses and if you try to write something on it, it will get corrupted. (Read-Only access however could be possible)


Yes. Linux can mount ext4fs partitions as native, because that is what it uses for it's own disks usually. (could be some other FS too, but nowdays I'd say ext4 is the most widely used...)
Windows cannot do it by itself, it only knows about DOS and NTFS filesystems and so needs drivers like Paragon.

Windows "CMD-prompt", yes, it is like terminal in Linux, in a way like a Mouse and an Elephant are both animals :D
Only one is a little more powerful than the other.


I am not sure if I understand correctly, but when using telnet client on Linux, or ssh client, or Putty on Windows, then you connect to the internals of the device itself, it is same as if you'd open a terminal application on Harmattan itself.
When you work in a telnet/ssh connection, then your commands are directly executed on the device, not on the PC computer.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hi, like that with the Mouse and Elephant:D
And that's the point I think (?) being in Cmd you can't get access direct to device you have to stay on PC - as far as I know - but be in Ubuntu terminal you can change to device direct - but is it due to Ubiboot or Ubuntu or both - I'm not sure?

OK but nevertheless it don't move my main problem - so near to Ubiboot and even so long away. :confused:
Have been there once before no problem boot to Harmattan, NITDroid and Firefox then mixed up with extracting Nemo OS to Alt_OS. Now this seems to be solved but then can't boot at all!
Before long I need to flash back in lack of battery and don't want to be caught in 11% flash trap!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@garp
For battery, try the following:
shut down device
plug in ac/wall charger
check if you get the green maintenance console or the LPS charging symbol
in first case push power off button for approx. 8 seconds (device will power cycle and reboot)
check again, you may have to repeat a few times but I always get it working after a few tries

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Followed this eactly (but of course changed 2 with 3!) and no problems but also no boot!:o:

Found out however:

Disk /dev/mmcblk0: 64.1 GB, 64130908160 bytes
4 heads, 16 sectors/track, 1957120 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 17 1632512 52239872 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary

/dev/mmcblk0p2 1632513 1760512 4096000 83 Linux
Partition 2 does not end on cylinder boundary

/dev/mmcblk0p3 1760513 1891584 4194304 83 Linux

/dev/mmcblk0p4 1891585 1957120 2097152 83 Linux

That p1= Mydocs
p2= Alt_OS
p3= /rootfs
p4= /home

Could it be a reason to boot not function? (Gparted it seems OK no red marks etc) But what re Ubiboot.conf etc? It must give problems here I think!
Have had a lot of problems with partitions also tried to run ext4 on p1 due to this http://talk.maemo.org/showthread.php?t=90687
But end up total flash --no-preserve and thougt problems were solved, but....(and it seems that the 4GB limit on rootfs is broken)??

NB. @ peter leinchen The battery work around don't function at my N9 -tried nearly 10 times!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Ubiboot.config seems to have a problem due to my partition mess. What will happen if I change so:
G_EXPORTED_PARTITONS="/dev/mmcblk0" # This exports all partitons of the device
#G_EXPORTED_PARTITONS="/dev/mmcblk0p1" # this exports just the Mydocs partiton
#G_EXPORTED_PARTITONS="/dev/mmcblk0p2" # this exports just the root (nemo) partition
#G_EXPORTED_PARTITONS="/dev/mmcblk0p3" # this exports just the home (root) partiton
#G_EXPORTED_PARTITONS="/dev/mmcblk0p4" # this exports just the nemo (home) partition
#G_EXPORTED_PARTITONS="/dev/mmcblk0p5" # some people have more than 4 partitions
#G_EXPORTED_PARTITONS="/dev/mmcblk0p6" # some people have more than 5 partitions
#G_EXPORTED_PARTITONS="/dev/mmcblk0p7" # this is the last supported partition I guess
#G_EXPORTED_PARTITONS="" # this turns off partition exporting

And then change partitions number due to that in the section stating with:
# The first OS is usually Nitdroid.
# This section lists the Nitdroid specific switches and kernels
G_OS1_NUM=3
G_OS1_AUTOBOOT=0
G_OS1_PARTITION=2 (to 3 for Harmattan and Firefox too.)
And the Nemo now 4 to 2

But what about : "It's important that the versions of the kernel, config and cpio are compatible or else you will run into no end of trouble.":confused:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yes, that is really a mess! :eek:
Or nicely stacked, as juiceme would say. ;)

You somehow managed to shift roots and home from p2/3 to p3/4.
Your approach above editing ubiboot.conf may work (for sure this is the reason why kernels are not found), as it searches on harmattan rootfs (i.e. /dev/mmcblk0p2) boot folder. But due to your partition layout they reside on /dev/mmcblk0p4.

I suggest you do a reflash --no-preserve and start all over.
But before you should try editing ubiboot.conf as stated above.
And you will end up with a system having the home partition not mounted (would need editing at least /etc/fstab). Juiceme may tell more here.

--
did you ever try to flash standard open mode kernel and see how the N9 behaves?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I think this is time for asking how to partitioning the emmc other than nemo′s Alt_OS :)
Sorry I am lazy :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Me too. :p

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Portal
10 char

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks, I have tried everything nearly but need maybe to try once more, and will begin the easy way by change Ubiboot.conf and then lets see.:p
editing /etc/fstab can look here it seems: http://talk.maemo.org/showthread.php?t=91914

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I can't boot into harmattan, but when I try from over usb, here's what I see:
ubiboot.conf: http://pastebin.com/BdHvGLKU

I found the logs in /var/log/ although I'm not sure why they're there, as I just installed the latest version of Ubiboot before everything broke. Here is /var/log/ubiboot.log starting from yesterday: http://pastebin.com/X1YzUD32
And here is /var/log/ubiboot.dmesg for the last three boots: http://pastebin.com/USQhMqUL

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@taixzo
Just looking at log file I do see you do not have latest version of ubiboot. Log says 0.3.3 but current version is 0.3.5.
So best guess is you haxe mixed setup.
Try again by getting latest ubiboot kernel and latest cpio. Put cpio to MyDocs/boot and flash the kernel.
-- oops, and ubiboot.conf of course needs to be latest version (please use newest version and adapt to your setup)
You may also wait for juiceme as he is much much better reading his log files....

Re: Introducing ubiboot N9 (multiboot OS loader)
 

OK now made full flash --no-preserve then Back-to-back flash due to @juiceme and now in zImage_2.6.32.54-openmode_l2fix

# /sbin/sfdisk -l

Disk /dev/mmcblk0: 1957120 cylinders, 4 heads,16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 16 1760511 1760496 56335872 c W95 FAT32 (LBA)
/dev/mmcblk0p2 1760512 1891583 1310724194304 0 Empty
/dev/mmcblk0p3 1891584 1957119 655362097152 83 Linux
/dev/mmcblk0p4 0 - 0 0 0 Empty

Disk /dev/dm-0: 0 cylinders, 0 heads, 0 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/dm-0: unrecognized partition table type
No partitions found
~ #

How to solve that problems with 0p2 etc?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

So you have done this on purpose?
As the normal partition layout is as follows:

p1= Mydocs
p2= /rootfs
p4= /home
p4= Alt_OS

If you change partition layouts/assignments you need to change other things too, it is not enough just to switch labels and copy the FS content to differen partition, you need to modify inits and check that everything is mounted and brought up correctly...

Unless you have done this, I am fairly sure this is the reason you are having boot problems :D:D

The battery workaround, to get the device boot up to the "ACT_DEAD" state and start charging only works if you have bootable Harmattan installation on your device... but I really suspect you have messed up the partitions so that you cannot boot to Harmattan, right?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

This means, you should use ubiboot files from one of my ready-made TAR achives, for example ubiboot-02_0.3.5_301013.tar, you should not take CPIO from one ubiboot version and kernel or configuration from another, for example. All three files must match each other.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yes, I propably would really say that! :D:D


@Garp; Your device could be saved from the state it is, yes, even easily I'd say but it does require that somebody who knows how to do that could be there on-site to do it, it is too difficult to do by giving instructions to you how to do it.

Unless you have very valuable data with no backups of it, I suggest doing as peterleinchen says, reflash with --no-preserve option and then do everything from start.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

i suggest to Garp to reflash prone with then flash ubiboot
connect to Ubuntu
make repartition with GParted manyally by cropping first partition and creating new primary 4GB partition for Nemo
unpack nemo image by tar, dont use filemanager
copy kernels, configs, preinits edit configs, if need
boot and use Nemo :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Have already done please see above #861!:): But what to do with Empty op2 etc?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Have you seen my #861? And is your suggestion that I do it once more or?:cool:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well, now as you see that is really just a cosmetic thing, since you are running Harmattan OK, right?
Even as partiton table type is undefined it is correctly formatted as ext4 and mounted as your root.

If you really want to cange it, you can do so by sfdisk but it is not necessary.

Now, next thing to do is to run the MOSLO partitioner to get the Nemo partition set up again, then install ubiboot and Nemo rootFS.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

No, your system looks good now.
I am reading the postings in order and replying to them, it takes time to catch up so many postings :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@Taixo; It seems to be like peterleinchen says, unless the logs from your /var/log/ubiboot.log are older remains of the previous ubiboot version 0.3.3 you had there, you are still running the old ubiboot kernel.

Your ubiboot.conf, however is from the new version, so might it be possible that you have the nef conf, new CPIO but flashing has failed so you are still running with the old ubiboot kernel.
If that was the case, it sure would cause problems like these.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

OK I see, Thanks for your help:): But above ? was to @coderus #865:)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

So many postings, and nothing to add... ;)

@garp
I have also no idea why your p2 shows empty, but as juiceme already said it is no problem at all (and could be easily fixed with sfdisk).
I have this back to back in suspicion. Could you give us in detail and exactly the steps you made?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks, maybe it was no problem but now I'm caught again after run
sudo flasher -k usr/share/moslo/zImage-moslo -n usr/share/moslo/initrd-moslo -l -b
FATAL: Re-partitioning failed! You might be in trouble!
Try to repair in Gparted and by fdisk!
Do you know how to mount the partitions again?

dont use moslo. do repartition manually with GParted.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

fyi: https://wiki.merproject.org/wiki/Nem..._in_trouble.21
Just noticed ubiboot repair/maintanance mode can used with gparted, but gparted said limit of 4 primary partitions (MBR ?) How to create more partition?
already reserved space for new partition

Re: Introducing ubiboot N9 (multiboot OS loader)
 

You need to delete one primary partition and create a new extended partition in its place. Then, create the rest of the partitions inside it.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Here is my partition layout (to be seen as example):
NB: p1 is shrunk by 16GB, p4 is just a container (extended) for p5/p6/p7, also note that I left a 4GB spare between p1 and p4
Done manually on device.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

How to load boot menu or specific OS when connect to computer via telent?
I always connect and disconnect the usb now:(

You don't...

This is a feature if ubiboot!

Why would you want to start with USB connected if not for maintenance mode?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Run this in Ubuntu terminal: sudo flasher -k zImage_2.6.32.54-ubiboot-02_301013 -l -b