maemo.org - Talk
Page 11 of 35 « First 910 11 121321 Last »
Show 40 post(s) from this thread on one page

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)

juiceme 2013-08-23 07:12
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by afropanda (Post 1368857)
can this be done in terminal in meego?
This is meant to be done in your Linux PC.
(this makes it easy to connect to your N9 running Nemo from your computer)

afropanda 2013-08-23 07:13
Re: Introducing ubiboot N9 (multiboot OS loader)
 
I see. Thanks. so how will i be able to make Nemo work. im using Windows hahaha

juiceme 2013-08-23 07:44
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by afropanda (Post 1368862)
I see. Thanks. so how will i be able to make Nemo work. im using Windows hahaha
Well, you should be okay with the next boot, you can just swithc off the N9 and reboot to Nemo, and if all went okay you will get the graphical UI the next boot.

If you don't, then you would need to ssh to the device to find out from logs why it does not boot to UI.
(or it may be that it did not boot correctly at all, then you can look in your Harmattan side /var/log/ directory, you will find 2 files there; ubiboot.log and ubiboot.dmesg that should show you some info on the boot process...)

How to do that in windows; you need advice of somebody using windows, I am afraid I cannot help you there. The ubiboot wiki page http://wiki.maemo.org/Ubiboot shows some advice for windows users.

afropanda 2013-08-23 08:45
Re: Introducing ubiboot N9 (multiboot OS loader)
 
maybe its for linux users only. Thanks for the help. Sadly it didnt boot after the restart:(

juiceme 2013-08-23 08:52
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by afropanda (Post 1368879)
maybe its for linux users only. Thanks for the help. Sadly it didnt boot after the restart:(
Well at least it makes it lot easier if you have used linux before.
Currently Nemo is far from complete even as it is very usable in certain situations.

Did you check the /var/log/ubiboot.log and /var/log/ubiboot.dmesg for any funny business?

afropanda 2013-08-23 10:41
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by juiceme (Post 1368881)
Well at least it makes it lot easier if you have used linux before.
Currently Nemo is far from complete even as it is very usable in certain situations.

Did you check the /var/log/ubiboot.log and /var/log/ubiboot.dmesg for any funny business?
yes i did and i cant paste it here,lol can i send it to you?

juiceme 2013-08-23 11:29
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by afropanda (Post 1368893)
yes i did and i cant paste it here,lol can i send it to you?
use for example http://pastie.org/

afropanda 2013-08-23 11:45
Re: Introducing ubiboot N9 (multiboot OS loader)
 
now it says Your paste cannot be larger than 64 kb. Sorry. haha

juiceme 2013-08-23 12:33
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by afropanda (Post 1368902)
now it says Your paste cannot be larger than 64 kb. Sorry. haha
hm. OK what about http://pastebin.com , does it accept larger pastes?

afropanda 2013-08-23 12:39
Re: Introducing ubiboot N9 (multiboot OS loader)
 
ubiboot.dmesg

http://pastebin.com/wg0T8Vmm

ubiboot.log

http://pastebin.com/wUPDDK4p

juiceme 2013-08-23 16:08
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by afropanda (Post 1368913)

According to your ubiboot.log at least Nemo partition is OK and kernel was found and loaded correctly:
Code:
Aug 22 18:15:21 (none) user.notice root: Selecting Nemo OS, running kernel /boot/Nemo/boot/bzImage
Aug 22 18:15:22 (none) user.notice root: kexec_load() successful
Aug 22 18:15:22 (none) user.notice root: Restarting to selected OS
Aug 22 18:15:22 (none) user.notice root: Saving ubiboot log files
So, whatever the problem now is in the domain of Nemo, and not in domain of ubiboot.

How does the device behave exactly when you try to start up Nemo?
Does it just hang with black screen but possibly running SW or does it turn the power off?

(You can determine if it is running or turned off by behaviour when you quickly press and release the power button. Do not keep it held, just press quickly.
If it is powered OFF, the power led will blink once. If it is hung or blind but power ON, led will not blink)

afropanda 2013-08-23 16:26
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by juiceme (Post 1368943)
According to your ubiboot.log at least Nemo partition is OK and kernel was found and loaded correctly:
Code:
Aug 22 18:15:21 (none) user.notice root: Selecting Nemo OS, running kernel /boot/Nemo/boot/bzImage
Aug 22 18:15:22 (none) user.notice root: kexec_load() successful
Aug 22 18:15:22 (none) user.notice root: Restarting to selected OS
Aug 22 18:15:22 (none) user.notice root: Saving ubiboot log files
So, whatever the problem now is in the domain of Nemo, and not in domain of ubiboot.

How does the device behave exactly when you try to start up Nemo?
Does it just hang with black screen but possibly running SW or does it turn the power off?

(You can determine if it is running or turned off by behaviour when you quickly press and release the power button. Do not keep it held, just press quickly.
If it is powered OFF, the power led will blink once. If it is hung or blind but power ON, led will not blink)
I pressed it and the led did not blink so i assume its the second one.

afropanda 2013-08-23 16:34
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Maybe the destination of my Nemo is wrong, based on the walkthrough it should create a folder with a name Alt_OS but mine it didnt,so I created manually and put it in /media . May I know where is the Alt_OS should be located?

Van-ess 2013-08-23 16:51
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Alt_OS should be the mmcblk0p4 partition and the point of moounting does not matter. The firts boot can be very slow, so try to wait ~30min or check the release of Nemo and Its unpacking.

afropanda 2013-08-23 16:54
Re: Introducing ubiboot N9 (multiboot OS loader)
 
where will i see that mmcblk0p4

juiceme 2013-08-23 17:26
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Do command "/sbin/sfdisk -l /dev/mmcblk0" as root.
You sould see 4 partitions.

edit:
-----------

Besides, based on your log the Nemo kernel was loaded correctly by ubiboot so I am fairly sure you do have to have something there....

And the fact that the power led did not blink suggests that some kernel is running....

afropanda 2013-08-23 17:38
Re: Introducing ubiboot N9 (multiboot OS loader)
 
yes i do have 4 partitions

KTy 2013-08-24 11:37
Re: Introducing ubiboot N9 (multiboot OS loader)
 
My turn to have issues while installing....

Baseline is my existing PR1.3 install on top of which I have executed:

flasher -f -F main.bin -R
Followed by:
flasher -a main.bin -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f -R

I can (apparently) install correctly the openmode kernel as it keeps my passwords upon reboot.

After that, I skip everything related to Nemo and I jump to flashing Ubiboot with:

D:\Nokia\Flasher>flasher -a main.bin -k zImage_2.6.32.54-ubiboot-02_040613 --flash-only=kernel -f -R

After reboot, I can see the Moslo maintenance screen. Once I unplugged USB, I go to graphical multiboot. I click on the Meego guys and then select "Open mode +L2 fix" (or so).
Cool animation, black screen, some USB sound disconnecting and.... that's it.

If I select Nitdroid (e-eyes fix...), same problem.

Van-ess 2013-08-24 12:12
Re: Introducing ubiboot N9 (multiboot OS loader)
 
@KTy have you put neccesarry kernels to the /boot folder and edited ubiboot.conf?

peterleinchen 2013-08-24 13:19
Re: Introducing ubiboot N9 (multiboot OS loader)
 
And/or also put cpio in correct place? You did mention but I assume you did?
You may check the /var/log/ubiboot* logs in maintenance mode for what's going wrong.

juiceme's readme is very clear and.there is also a wiki page.

KTy 2013-08-24 16:14
Re: Introducing ubiboot N9 (multiboot OS loader)
 
I have followed the Wiki and cant remember anything related to editing the ubiboot.conf... Did I miss that ?!

peterleinchen 2013-08-24 18:29
Re: Introducing ubiboot N9 (multiboot OS loader)
 
And I cannot remember if there is the need to edit at all. Afair juiceme named the kernels in conf according to their image names (but when downloaded from other site or using own name schema or using other kernel/partition then it is needed).

What about the logs? They will tell you what's wrong.
Power off device and connect to USB. Open a telnet session to 192.168.2.14 and check /var/log...

juiceme 2013-08-24 22:28
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Most times when booting fails is because you do not have the kernels in /boot/, or do not have the correct modules for the kernels in /lib/modules/<kernel_id_string>/

In case of Nitdroid kernels, "standard" open mode kernels and l2fixed open mode kernels the modules are same as with the Nokia original PR1.3 kernel, so your modules are propably correct.

So, it is possible that the kernels are missing from /boot/ or are named differently than in ubiboot.conf file.

Just as peterleinchen says, look up the log file from /var/log/ubiboot.log, there will be cleartext indication of the selected kernel/OS, and if the loading succeeded or failed.

afropanda 2013-08-25 06:20
Re: Introducing ubiboot N9 (multiboot OS loader)
 
how bout my problem haha

peterleinchen 2013-08-25 08:19
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by afropanda (Post 1369166)
how bout my problem haha
and what about already given hints? he he.

juiceme 2013-08-25 10:18
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by afropanda (Post 1369166)
how bout my problem haha
Well, based on what you have told, it looks to me like you are actually running Nemo but you do not have visible UI.

So, to make sure, you need to ssh to the device.

Possibilities:
  • What was the Nemo Image release you copied to your mmcblk0p4 partition, it imight be possible you had some development image?
  • Maybe there was some problem unpacking the tar file to the partition, and kernel can be loaded OK but for example init is corrupted?

afropanda 2013-08-25 17:33
Re: Introducing ubiboot N9 (multiboot OS loader)
 
i used this one nemo-armv7hl-n950-0.20130411.1.NEMO.2013-04-26.1.tar

juiceme 2013-08-26 09:27
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by afropanda (Post 1369292)
i used this one nemo-armv7hl-n950-0.20130411.1.NEMO.2013-04-26.1.tar
Yes, that's the correct one.

What you could do is try to wipe your mmcblk0p4 and re-extract the FS image, in case something went wrong with unpacking...

afropanda 2013-08-26 10:44
Re: Introducing ubiboot N9 (multiboot OS loader)
 
how? what do i need to type in terminal?

juiceme 2013-08-26 12:14
Re: Introducing ubiboot N9 (multiboot OS loader)
 
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.

afropanda 2013-08-26 14:20
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?

juiceme 2013-08-26 15:08
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)
~ #

afropanda 2013-08-26 15:19
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

juiceme 2013-08-26 15:22
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.

afropanda 2013-08-26 16:06
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Its now working! Hahahahaha

juiceme 2013-08-26 20:11
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

KTy 2013-08-27 08:39
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)
~ #

juiceme 2013-08-27 08:45
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!

KTy 2013-08-27 08:51
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

KTy 2013-08-27 09:07
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


All times are GMT. The time now is 23:09.
Page 11 of 35 « First 910 11 121321 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8