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)

Quote:

Originally Posted by juiceme (Post 1369478)

Well, if you do it on the device (that is running harmattan) give the following commands.

Prerequisite; copy your NEMO tar archive to /home/user/MyDocs for example.

## go to root
devel-su

## mount your Nemo partition somewhere to access it
mount /dev/mmcblk0p4 -t ext4 /mnt

## now confirm that you REALLY have the correct partition there, this should give you some info about your Nemo release:
cat /mnt/etc/meego-release

## now, wipe the stuff you have got there:
rm -rf /mnt
sync

## now, extract the archive to partition:
tar --numeric-owner -xf filename+path-of-your-tar-archive -C /mnt/
sync

## now, detach the mount
umount /mnt

That's how to do it. Now if everything went dandies, just boot your device and retry booting to Nemo.

sir im having problems with that one,it says no such file or directory. i stopped there,can i skip with that?

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by afropanda (Post 1369505)

sir im having problems with that one,it says no such file or directory. i stopped there,can i skip with that?

Okay, so check what do you have there, the command is "ls -la /mnt"

If you have Nemo installed, you get something like this:

Code:

~ # 

~ # ls -la /mnt

total 84

drwxr-xr-x   21 root     root          4096 Jun 27 09:09 .

drwxrwxr-x   29 1000     1000          4096 Jan  1  1970 ..

drwxr-xr-x    2 root     root          4096 Jun 27 09:08 .config

drwxr-xr-x    2 root     root          4096 Jun 27 09:30 bin

drwxr-xr-x    2 root     root          4096 Jun 27 09:26 boot

drwxr-xr-x    3 root     root          4096 Jun 27 09:07 dev

drwxr-xr-x   68 root     root          4096 Jan  1  1970 etc

drwxr-xr-x    3 root     root          4096 Jun 27 09:08 home

drwxr-xr-x    9 root     root          4096 Jun 27 09:28 lib

drwxr-xr-x    2 root     root          4096 Mar  3 19:43 media

drwxr-xr-x    2 root     root          4096 Mar  3 19:43 mnt

drwxr-xr-x   15 root     root          4096 Jun 27 09:09 opt

drwxr-xr-x    2 root     root          4096 Apr 26 14:31 proc

drwxr-x---    3 root     root          4096 Jun 27 09:07 root

drwxr-xr-x    9 root     root          4096 Jun 27 09:07 run

drwxr-xr-x    2 root     root          4096 Jun 27 09:30 sbin

drwxr-xr-x    2 root     root          4096 Mar  3 19:43 srv

drwxr-xr-x    2 root     root          4096 Apr 26 14:31 sys

d-wxr----t    2 root     root          4096 Jun 27 09:07 tmp

drwxr-xr-x   12 root     root          4096 Jun 27 09:08 usr

drwxr-xr-x   17 root     root          4096 Jun 27 09:07 var

~ #

If you do not see this, please show me what you see.

Also, to mke sure you mounted it correctly, give command "mount | grep mmcblk0p4"

This is what you should see:

Code:

~ # 

~ # mount | grep mmcblk0p4

/dev/mmcblk0p4 on /mnt type ext4 (rw,relatime,barrier=1,data=ordered)

~ #

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1369518)

Okay, so check what do you have there, the command is "ls -la /mnt"

If you have Nemo installed, you get something like this:

Code:

~ # 

~ # ls -la /mnt

total 84

drwxr-xr-x   21 root     root          4096 Jun 27 09:09 .

drwxrwxr-x   29 1000     1000          4096 Jan  1  1970 ..

drwxr-xr-x    2 root     root          4096 Jun 27 09:08 .config

drwxr-xr-x    2 root     root          4096 Jun 27 09:30 bin

drwxr-xr-x    2 root     root          4096 Jun 27 09:26 boot

drwxr-xr-x    3 root     root          4096 Jun 27 09:07 dev

drwxr-xr-x   68 root     root          4096 Jan  1  1970 etc

drwxr-xr-x    3 root     root          4096 Jun 27 09:08 home

drwxr-xr-x    9 root     root          4096 Jun 27 09:28 lib

drwxr-xr-x    2 root     root          4096 Mar  3 19:43 media

drwxr-xr-x    2 root     root          4096 Mar  3 19:43 mnt

drwxr-xr-x   15 root     root          4096 Jun 27 09:09 opt

drwxr-xr-x    2 root     root          4096 Apr 26 14:31 proc

drwxr-x---    3 root     root          4096 Jun 27 09:07 root

drwxr-xr-x    9 root     root          4096 Jun 27 09:07 run

drwxr-xr-x    2 root     root          4096 Jun 27 09:30 sbin

drwxr-xr-x    2 root     root          4096 Mar  3 19:43 srv

drwxr-xr-x    2 root     root          4096 Apr 26 14:31 sys

d-wxr----t    2 root     root          4096 Jun 27 09:07 tmp

drwxr-xr-x   12 root     root          4096 Jun 27 09:08 usr

drwxr-xr-x   17 root     root          4096 Jun 27 09:07 var

~ #

If you do not see this, please show me what you see.

mine is
total 24
drwxr-xr-x 3 root root 4096 Jan
1 1970 .
drwxrwxr-x 26 root root 4096 Jan
1 1970
drwx------ 2 root root 16384 Jan
1 1970 lost+found

Also, to mke sure you mounted it correctly, give command "mount | grep mmcblk0p4"

This is what you should see:

Code:

~ # 

~ # mount | grep mmcblk0p4

/dev/mmcblk0p4 on /mnt type ext4 (rw,relatime,barrier=1,data=ordered)

~ #

we are same here

Re: Introducing ubiboot N9 (multiboot OS loader)

Okay, so you do not have anything there, on your mmcblk0p4, it seems to be completely empty :)

Now you can proceed with extracting the FS image from the tarfile.

Re: Introducing ubiboot N9 (multiboot OS loader)

Its now working! Hahahahaha

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by afropanda (Post 1369533)

Its now working! Hahahahaha

As it should :D

Nice to know you finally got it running all 3 OS'es :p

Re: Introducing ubiboot N9 (multiboot OS loader)

I am almost out of the wood... Is that expected ?

Code:

~ # /sbin/sfdisk -l /dev/mmcblk0



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  1632511  1632496   52239872    c  W95 FAT32 (LBA)

end: (c,h,s) expected (1023,3,16) found (1023,63,32)

/dev/mmcblk0p2     1760512  1891583  131072    4194304   83  Linux

/dev/mmcblk0p3     1891584  1957119   65536    2097152   83  Linux

/dev/mmcblk0p4     1632512  1760511  128000    4096000   83  Linux

start: (c,h,s) expected (1023,3,16) found (1023,63,32)

end: (c,h,s) expected (1023,3,16) found (1023,63,32)

~ #

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by KTy (Post 1369666)

I am almost out of the wood... Is that expected ?

[code]~ # /sbin/sfdisk -l /dev/mmcblk0

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 1632511 1632496 52239872 c W95 FAT32 (LBA)
end: (c,h,s) expected (1023,3,16) found (1023,63,32)
/dev/mmcblk0p2 1760512 1891583 131072 4194304 83 Linux
/dev/mmcblk0p3 1891584 1957119 65536 2097152 83 Linux
/dev/mmcblk0p4 1632512 1760511 128000 4096000 83 Linux
start: (c,h,s) expected (1023,3,16) found (1023,63,32)
end: (c,h,s) expected (1023,3,16) found (1023,63,32)
~ #[code]

This is exactly as it should be :D
Congratulations on at least partitioning the device correctly!

Re: Introducing ubiboot N9 (multiboot OS loader)

Ok, last step in progress -> Flashing Ubiboot

Code:

flasher -a main.bin -k zImage_2.6.32.54-ubiboot-02_040613 --flash-only=kernel -f -R

Re: Introducing ubiboot N9 (multiboot OS loader)

And fail.... like in the last 3 days...
Can reach Ubiboot menu, can reach repair console, cannot start any of the OS.... ?!

...

Hum.... wtf... The zImage_2.6.32.54-ubiboot-02_040613 I flashed is 7,899,680Bytes while the one I just downloaded is 6,706,056 bytes ?!

Edit: MD5S matches on the image I originally downloaded. Which file could prevent any OS to load, if corrupted ?

EDIT2: Duhhhh... I untar the preinits.tar directly in "/sbin/" not in "/" :D