If nit is on p2 and nemo on p3, then please correct above!

set
ITEM_CMDLINE=root=/dev/mmcblk1p3
and try again

[QUOTE=peterleinchen;1338935]If nit is on p2 and nemo on p3, then please correct above!


Sorry my error. So it correct.

/dev/mmcblk1p1 /media/mmc1 (FAT32)
/dev/mmcblk1p2 /media/mmc1p2 (EXT3), NitDroid
/dev/mmcblk1p3 /media/mmc1p3 (EXT4), Nemo

In Maemo my Nemo rootfs partition is /dev/mmcblk1p3.

In Nemo this partition is /dev/mmcblk0p3, because /dev/mmcblk1p3 is the third partition on the Internal EMMC.

Nemo booting correct, it loads more then only kernel ( i see the nemo background).

But then i got a loop. Freezing on background, trying to remount, freezing on background...

I tried to change to
ITEM_CMDLINE=root=/dev/mmcblk1p3
like you wrote it, I get no filesystem found on /dev/mmcblk1p3

I checked the ext4 Nemo partition for errors and found a lot of !
fsck.ext4 quit after a while with Segmentation fault.

I created an new ext4 fs on /dev/mmcbl1p3, wrote an Nemo raw image on another card and than tar the ext4 partition with Nemo Rootfs to file and than i have untar this file on my mmcblk1p3.
Then I copied the uImage and 3 other files from Nemo FAT16 Partition also to my mmcblk1p3 and tryed to boot afterwards...
I got the same problem...

If i try to boot Nemo from the other card, i have created, it boots fine.
Can I read out the Nemo logs or dmesg from the Maemo ?

Or maybe, someone, who has Nemo and Nitdroid on the same Card, can post his configuration?

Here are my Nemo.item configiguration:

ITEM_NAME="NEMO 2.6.37"
ITEM_KERNEL="uImage"
ITEM_DEVICE="${EXT_CARD}p3"
ITEM_FSTYPE="ext4"
ITEM_CMDLINE="root=/dev/mmcblk0p3 rootwait rw console=tty02,115200n8 console=tty0 omapfb.vram=0:2M,1:2M,2:2M mtdoops.mtddev=2"
ITEM_OMAPATAG="1"

Thanks

It's been 6 days since my post above and no input.....

Can some kind soul please give me some guidance as to what to do to get U-Boot to install ?

I really need to get it installed....

Thank you!

Try installing via apt-get.

Thanks....

So, installed u-boot-flasher via apt-get....

I created a new u-boot menu entry as follows:

Then I did


FYI, I am trying to get Arch Linux up and running....per these instructions on this blog page:

http://blog.jakgibb.com/2013/03/28/a...stall-on-n900/


Any suggestions?

Thanks!

I haven't tried this as I am not planning to get arch linux installed, but might try later.
Did you extract Arch Linux rootfs to partition mentioned in the ".item" file ?
u-boot-update-bootmenu needs to be run after that.
From the error message it seems it can't find the kernel image which should be in that partition.

Yes, I did extract the rootfs to the partition mentioned....

The only thing I can think of now is that particular partition that I created is not getting mounted automatically when I boot to maemo. So, maybe same thing happening when I boot up using u-boot, ie, if not mounted, then can't find kernel....

hmm...
Can you make sure your u-boot tools are also updated ?
By running the command below.
apt-get install u-boot-tools
Then run u-boot-update-bootmenu

I had a problem in which u-boot-tools weren't updated automatically after installing u-boot from HAM/FAM.

Edit: I didn't notice the new version.
Check if your u-boot is updated as well:
Update: 20.04.2013 10:00 UTC: Version 2013.04-1 is in Extras-Devel, support for bootmenu ext2/3/4 partition

Thanks for your help....

I just did as you instructed...says I already have the latest version....

You're welcome.
Now, I can think of few things as below:
1. Check if the partition created is ext3,p5 and on your internal sd.
2. Check if you are still able to correctly mount in /mnt, also go through the data once mounted.
3. If the above 2 things look fine, try extracting again.

Hope you know the commands to check those things.

I might give a try sometime this week.
Will let you know if it works for me.