Originally Posted by topet2k12001

Hi Friends,

I attempted to make my first Wiki Page. I used the Ubiboot Steps to make it. Please review and hope you like it. Feedback is most welcome (preferably via PM as I am not always online on the forums).

http://wiki.maemo.org/Ubiboot

Originally Posted by ncik

I followed the procedure that have mentioned for installing nemo but when I when I try to boot into it the phone just switches off and nothing else happens. I have mounted /dev/mmcblk0p4 to make sure that nemo was extracted properly. Do I need to add prenit files for it like Harmattan and Nitdroid?

Originally Posted by ncik

I followed the procedure that have mentioned for installing nemo but when I when I try to boot into it the phone just switches off and nothing else happens. I have mounted /dev/mmcblk0p4 to make sure that nemo was extracted properly. Do I need to add prenit files for it like Harmattan and Nitdroid?

Originally Posted by death_jax

No need of custom preinit file for Nemo.
Do you check if the Nemo kernel path in ubiboot.conf is correct?
It should be (this is mine):

Code:

# Nemo kernels
G_NEMO_NUM=1
G_NEMO_AUTOBOOT=1
G_NEMO_1_LABEL="Latest 2.6.32"
G_NEMO_1_FILE="/boot/Nemo/boot/bzImage"
G_NEMO_2_LABEL=""
G_NEMO_2_FILE=""
G_NEMO_3_LABEL=""
G_NEMO_3_FILE=""
G_NEMO_4_LABEL=""
G_NEMO_4_FILE=""
G_NEMO_5_LABEL=""
G_NEMO_5_FILE=""
G_NEMO_6_LABEL=""
G_NEMO_6_FILE=""

The bzImage kernel is placed into /boot folder into Nemo root, against the Harmattan and NITdroid kernels that are placed both in Harmattan /boot folder.

Originally Posted by topet2k12001

@ncik:

Yup...I encountered that as well when I was learning how to install Ubiboot.

That's why in the "TIPS" under the "Install Nemo Mobile OS" section (#5) I mentioned NOT to turn on the device yet until you finish the rest of the steps...because the latter part of the Wiki talks about the "bzImage" of Nemo and how to go about it.

@death_jax

Hm..."bzImage" to be saved in the /boot folder of the Nemo partition...that I did not do, since there is already a file named "bzImage" in that location when I checked it; it is a symlink that points to a file named "vmlinuz-2.6.32.20130129.1-n950".

What I did is (as I have written in the Wiki):

1. I took a look at the properties of the "bzImage" file that is located in /boot of the Nemo partition and found out that it is a "symlink" (symbolic link) that points to a file named "vmlinuz-2.6.32.20130129.1-n950", which is also already there (in /boot of Nemo partition). I never got Nemo to boot up (turns off after turning on, or reboot loop).

2. So I took that "vmlinuz-2.6.32.20130129.1-n950" file and copy-pasted it to the /boot folder of the N9 root partition (not the /boot folder that we created inside the N9 "MyDocs" partition), and then renamed it as "bzImage".

3. That was the only time I got to resolve the "reboot loop" or "not booting/turning off" problem whenever I tried to use Nemo.

These steps are documented in the Wiki as "FINAL STEPS" under the section of "Flash the Device with Ubiboot-02".

The nice thing about Ubiboot is, you don't have to start from scratch. While the device is turned off, plug the USB cable to the computer. The device will turn on in "maintenance mode" and (if you are using a Linux-based OS), all the partitions will be mounted (i.e. your File Manager will fire up, showing the partitions). Once that happens, copy-paste the files as indicated in the Wiki.

The only exception is that if you failed to extract the "preinits.tar" file prior. I read all the IRC logs and in one of those conversations, extraction of the "preinits.tar" file needs to happen at the earlier part of the process. So that is what I have followed.

By the way, I documented the steps in such a way that it conforms to how the author (juiceme) already designed the "ubiboot.conf" file so as to lessen the number of things that a user would need to do (example: I wrote the steps such that "zImage" would be renamed to be spelled the same way as it was in the ubiboot.conf file, e.g. "zImage_e-yes_nitdroid+l2fix"...under "NITDroid Files"section).

Hopefully this allows more end-users to be able to install Ubiboot with the least amount of trouble, as long as they follow the steps in the order it was written in the Wiki. Of course, more experienced users can afford to alter the order of steps as they know what they are doing (editing ubiboot.conf, etc.). I targeted the Wiki/guide to end-users so as to gain patronage of Ubiboot.

Originally Posted by ncik

Although I couldn't keep the device off like you mentioned (it wouldn't stay off).. but the bzImage is at the location as it should be. I reconfirmed. I have some issues flashing because I use a linux VM. I am not sure if that is what is causing the issues. I don't how it should since I saw and Alt_OS partition and made sure all the files were extracted there properly.

Originally Posted by topet2k12001

@ncik:

Yup...I encountered that as well when I was learning how to install Ubiboot.

That's why in the "TIPS" under the "Install Nemo Mobile OS" section (#5) I mentioned NOT to turn on the device yet until you finish the rest of the steps...because the latter part of the Wiki talks about the "bzImage" of Nemo and how to go about it.

@death_jax

Hm..."bzImage" to be saved in the /boot folder of the Nemo partition...that I did not do, since there is already a file named "bzImage" in that location when I checked it; it is a symlink that points to a file named "vmlinuz-2.6.32.20130129.1-n950".

What I did is (as I have written in the Wiki):

1. I took a look at the properties of the "bzImage" file that is located in /boot of the Nemo partition and found out that it is a "symlink" (symbolic link) that points to a file named "vmlinuz-2.6.32.20130129.1-n950", which is also already there (in /boot of Nemo partition). I never got Nemo to boot up (turns off after turning on, or reboot loop).

2. So I took that "vmlinuz-2.6.32.20130129.1-n950" file and copy-pasted it to the /boot folder of the N9 root partition (not the /boot folder that we created inside the N9 "MyDocs" partition), and then renamed it as "bzImage".

3. That was the only time I got to resolve the "reboot loop" or "not booting/turning off" problem whenever I tried to use Nemo.

Originally Posted by caveman

There is a similar situation when remote-unlocking an encrypted hard drive. In that scenario, passwd is empty and the auth is key-based. This may be feasible in this case.

Originally Posted by ncik

I followed the procedure that have mentioned for installing nemo but when I when I try to boot into it the phone just switches off and nothing else happens. I have mounted /dev/mmcblk0p4 to make sure that nemo was extracted properly. Do I need to add prenit files for it like Harmattan and Nitdroid?

Originally Posted by topet2k12001

Hm..."bzImage" to be saved in the /boot folder of the Nemo partition...that I did not do, since there is already a file named "bzImage" in that location when I checked it; it is a symlink that points to a file named "vmlinuz-2.6.32.20130129.1-n950".

Originally Posted by juiceme

Normally when the Nemo rootFS is extracted to device partition, all the files needed to boot it up (including the most recent kernel at the time of package creation) are set to correct locations.
This is why ubiboot refers to the Nemo kernel as "/boot/Nemo/boot/bzImage", which in turn is the symlink inside Nemo to the vmlinuz-2.6.32.xxxxxxxx in the same directory.

It just works, out-of-the-box.

One thing, when you say the device "turns off after Nemo boot", did you check that it did not actually start Nemo, but without GUI?
If you plug the device in USB, if the IP interface appears on your computer, you can configure, for example 192.168.0.100 as the IP address there and SSH as root to your Nemo in 192.168.2.15

If that happens, rebooting the device should get you GUI on the next boot.

BTW, can you check the ubiboot logs on Harmattan side /var/log/ubiboot.log and /var/log/ubiboot.dmesg. From there you can see if there was some problem in the kernel selection.