![]() |
2015-12-10
, 15:06
|
Posts: 1,808 |
Thanked: 4,272 times |
Joined on Feb 2011
@ Germany
|
#782
|
The Following 2 Users Say Thank You to reinob For This Useful Post: | ||
![]() |
2015-12-10
, 19:39
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#783
|
![]() |
2015-12-10
, 23:54
|
|
Posts: 592 |
Thanked: 1,603 times |
Joined on Apr 2010
@ Berlin / Germany
|
#784
|
The only reason I can think of is that U-boot's ext3 driver is most likely not as capable as the kernel's, so the question is if you used any special parameters or ext3 features when you created the file system.
I imagine "-m 0" should pose no problem, but using things like "-E ..." or "-O ..." might make U-boot confused. Can you confirm you didn't use any voodoo options when mkfs'ing MyDocs?
mkfs.ext3 -m 0 -L "Nokia N900" /dev/mmcblk0p1
The Following User Says Thank You to explit For This Useful Post: | ||
![]() |
2015-12-10
, 23:56
|
|
Posts: 592 |
Thanked: 1,603 times |
Joined on Apr 2010
@ Berlin / Germany
|
#785
|
Hmm, I do not know.
But I guess Maemo's mkfs is not really the latest technology!
So it should be hard to not fulfill uboots needs? But I really do not know, so please confirm reinob's question.
Meanwhile I checked my older (all) configs and I found for nitdroid an entry of
ITEM_FSTYPE=vfat
Maybe you can try it with
ITEM_FSTYPE=ext3
or ITEM_FSTYPE="ext3"
and of course run u-boot-update-bootmenu.
But I do not think that solves your prob but worth a shot, right?
![]() |
2016-03-31
, 20:51
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#786
|
The Following 9 Users Say Thank You to pali For This Useful Post: | ||
![]() |
2016-03-31
, 21:19
|
|
Posts: 592 |
Thanked: 1,603 times |
Joined on Apr 2010
@ Berlin / Germany
|
#787
|
![]() |
2016-03-31
, 21:33
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#788
|
![]() |
2016-04-05
, 08:39
|
|
Posts: 592 |
Thanked: 1,603 times |
Joined on Apr 2010
@ Berlin / Germany
|
#789
|
![]() |
2016-04-05
, 08:43
|
Posts: 1,808 |
Thanked: 4,272 times |
Joined on Feb 2011
@ Germany
|
#790
|
It seems, that the github page is down. I get an error:
This page is taking way too long to load.
Sorry about that. Please try refreshing and contact us if the problem persists.
Could somebody opload the updated u-boot-configuration file here?
Thanks guys!
mmcnum="$INT_CARD" mmcpart="1" - mmctype="fat" + mmctype="$type" mmckernfile="$BOOTMENU_IMG_DIR/$ITEM_KERNEL" + if test "$mmctype" = "vfat"; then + mmctype="fat" + elif test "$mmctype" = "ext3"; then + mmctype="ext2" + fi + if ! test -z "$(mkimage -l $kernel_path 2>&1 1>/dev/null)"; then echo "Generating u-boot image for kernel '$ITEM_KERNEL'..."
The Following User Says Thank You to reinob For This Useful Post: | ||
![]() |
Tags |
bootmenu, u-boot |
Thread Tools | |
|
https://talk.maemo.org/showthread.php?t=73478
The conversion from FAT32 to ext3 was done on N900. Yesterday i ran fsck.ext3 on the MyDocs: Anything was fine.
That is total frustrating because i don't really know where to dig.
tha las U-Boot from Pali should support MyDocs as ext3, it stands explicit in the u-boot thread.
All kernels and the menu items are in right place.
u-boot-update-bootmenu finds anything and create all menu items correctly without any error....
But on booting: bam...: Unrecognised file system.....