Active Topics

 


Reply
Thread Tools
Posts: 20 | Thanked: 14 times | Joined on Oct 2011
#71
Originally Posted by Hurrian View Post
I found the problem with my crapola not working.
fatls mmc 1 was listing down my Music folder off my eMMC. What the actual ****? It might be because of damaged fat32 though.
Moved bootmenu files to ~/MyDocs/Music/ and it worked.

Would probably still be banging rocks together if not for the Gumstix wiki.
Have the same here. Details:
  1. 1. Have the healthy FAT at /home/user/MyDocs
  2. 2. U-boot shows default menu
  3. 3. U-boot console:
    Code:
    mmc init
    mmc dev 1
    fatls 1
    It shows the contents of /home/user/MyDocs/Text/0scraps/20111026223145
So U-boot indeed handles (v)FAT incorrectly.
My guess it is due to misaligned partition OR parted resize. I mean I used parted to resize /dev/mmcblk0p1 so that I could put another system on eMMC.

Any ideas howto fix?
 

The Following 2 Users Say Thank You to ildar For This Useful Post:
Posts: 323 | Thanked: 180 times | Joined on Oct 2009 @ Gent, Belgium
#72
when creating the bootmenu.d file entry for the latest Nemo kernel, what extra boot arguments/options one needs enter in the file to boot Nemo from the SD card ?

or, what manual commands could be tried in the uboot console to boot nemo ?

stskeeps would be the best to answer this I guess, as he was the first person able to create the PR1.3+uboot kernel, able to boot from the external MMC.

Thanks.

Last edited by Netweaver; 2012-02-01 at 14:18.
 

The Following User Says Thank You to Netweaver For This Useful Post:
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#73
Originally Posted by Netweaver View Post
when creating the bootmenu.d file entry for the latest Nemo kernel, what extra boot arguments/options one needs enter in the file to boot Nemo from the SD card ?
All I had to pass in was the normal root=/dev/mmcblk0pX argument to tell it which partition to boot to.
 

The Following 2 Users Say Thank You to Rob1n For This Useful Post:
Posts: 2,153 | Thanked: 8,462 times | Joined on May 2010
#74
Here are all supported variables for bootmenu entry:

ITEM_NAME=""
ITEM_DEVICE=""
ITEM_FSTYPE=""
ITEM_KERNEL=""
ITEM_INITRD=""
ITEM_SCRIPT=""
ITEM_CMDLINE=""
ITEM_USEATAG=""

Try to play with it, maybe you can get nemo booting. Now I do not have time to playing with it.

I tried this (stored kernel uImage-nemo in MyDocs) but not worked:
ITEM_NAME="Nemo"
ITEM_KERNEL="uImage-nemo"
ITEM_DEVICE="${INT_CARD}p1"
ITEM_FSTYPE="fat"
 

The Following 3 Users Say Thank You to pali For This Useful Post:
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#75
Originally Posted by pali View Post
Here are all supported variables for bootmenu entry:

ITEM_NAME=""
ITEM_DEVICE=""
ITEM_FSTYPE=""
ITEM_KERNEL=""
ITEM_INITRD=""
ITEM_SCRIPT=""
ITEM_CMDLINE=""
ITEM_USEATAG=""

Try to play with it, maybe you can get nemo booting. Now I do not have time to playing with it.

I tried this (stored kernel uImage-nemo in MyDocs) but not worked:
ITEM_NAME="Nemo"
ITEM_KERNEL="uImage-nemo"
ITEM_DEVICE="${INT_CARD}p1"
ITEM_FSTYPE="fat"
I think you need to add:
ITEM_CMDLINE="root=${EXT_CARD}p6"

or wherever the Nemo partition is.
 

The Following User Says Thank You to Rob1n For This Useful Post:
Posts: 309 | Thanked: 456 times | Joined on Jan 2010
#76
Originally Posted by Rob1n View Post
I think you need to add:
ITEM_CMDLINE="root=${EXT_CARD}p6"

or wherever the Nemo partition is.
How did you build the Nemo uImage to add to the boot entry?
Is it the same procedure used for a merged image (uboot + p49) and setting that one instead?

I would guess this will allow more than one O/S can be loaded from several partitions on the sdcard?

Last edited by [DarkGUNMAN]; 2012-02-01 at 17:13.
 
Posts: 2,153 | Thanked: 8,462 times | Joined on May 2010
#77
Originally Posted by Rob1n View Post
I think you need to add:
ITEM_CMDLINE="root=${EXT_CARD}p6"

or wherever the Nemo partition is.
!! ${EXT_CARD} is variable ONLY for ITEM_DEVICE !!

in ITEM_CMDLINE you should use root=/dev/mmcblk...
 
Posts: 2,153 | Thanked: 8,462 times | Joined on May 2010
#78
Originally Posted by [DarkGUNMAN] View Post
How did you build the Nemo uImage to add to the boot entry?
Is it the same procedure used for a merged image (uboot + p49) and setting that one instead?

I would guess this will allow more than one O/S can be loaded from several partitions on the sdcard?
store kernel image (must be in uImage format) to internal/external mmc and set correct variables.

script u-boot-update-bootmenu will then create correct bootmenu configuration
 
Posts: 4 | Thanked: 2 times | Joined on Feb 2012
#79
The nemo mobile project releases ready made raw images that you write to an sd card. I should be configured as follows:
partition 1: root filesystem
partition 2: swap
partition 3: /boot

So something like this:
ITEM_NAME="Nemo"
ITEM_KERNEL="uImage"
ITEM_DEVICE="${EXT_CARD}p3"
ITEM_FSTPE="fat"
ITEM_CMDLINE="root=/dev/mmcblk1p1"

Should work, right? But nope, it loads the right kernel (as does run sdboot in the console), but then it just shuts down.

Any suggestions?
 

The Following User Says Thank You to plipp For This Useful Post:
Posts: 2,153 | Thanked: 8,462 times | Joined on May 2010
#80
Originally Posted by plipp View Post
The nemo mobile project releases ready made raw images that you write to an sd card. I should be configured as follows:
partition 1: root filesystem
partition 2: swap
partition 3: /boot

So something like this:
ITEM_NAME="Nemo"
ITEM_KERNEL="uImage"
ITEM_DEVICE="${EXT_CARD}p3"
ITEM_FSTPE="fat"
ITEM_CMDLINE="root=/dev/mmcblk1p1"

Should work, right? But nope, it loads the right kernel (as does run sdboot in the console), but then it just shuts down.

Any suggestions?
I had same problem when tested.
 
Reply

Tags
bootmenu, u-boot


 
Forum Jump


All times are GMT. The time now is 06:58.