Reply
Thread Tools
explit's Avatar
Posts: 592 | Thanked: 1,603 times | Joined on Apr 2010 @ Berlin / Germany
#781
Originally Posted by peterleinchen View Post
I remember some problems with MyDocs formatted in fat from gparted or other tools. But iirc pali enabled all 'default' file formats.
How did you format it?
Hallo peterleinchen. I have formattet my MyDOcs with this Howto:

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.....
 
Posts: 1,808 | Thanked: 4,272 times | Joined on Feb 2011 @ Germany
#782
Originally Posted by explit View Post
But on booting: bam...: Unrecognised file system.....
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?
 

The Following 2 Users Say Thank You to reinob For This Useful Post:
peterleinchen's Avatar
Posts: 4,118 | Thanked: 8,901 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#783
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?
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature
 

The Following 2 Users Say Thank You to peterleinchen For This Useful Post:
explit's Avatar
Posts: 592 | Thanked: 1,603 times | Joined on Apr 2010 @ Berlin / Germany
#784
Originally Posted by reinob View Post
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?

I can confirm i used the standard commands for creating ext3 partition. I copy-pasted each step from here:
https://talk.maemo.org/showthread.php?t=73478

Here is the exact command:

Code:
mkfs.ext3 -m 0 -L "Nokia N900" /dev/mmcblk0p1
Now i uninstalled u-boot at all and flashed kernel-power53 to the Nand. Backupmenu runs without U-boot, but it is just a workaround, not a solution ;-) U-Boot is a must if such freaks like I am wants to play with different OSes....
 

The Following User Says Thank You to explit For This Useful Post:
explit's Avatar
Posts: 592 | Thanked: 1,603 times | Joined on Apr 2010 @ Berlin / Germany
#785
Originally Posted by peterleinchen View Post
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?

Thanks Peter.
Tried this alredy and run u-boot-update-bootmenu afterwards = no success :-(
 
Posts: 2,153 | Thanked: 8,462 times | Joined on May 2010
#786
Hi! There is bug in u-boot-update-bootmenu script which cause that only FAT fs for MyDocs is supported. Fix is in (new) github git repository at: https://github.com/pali/u-boot-maemo
 

The Following 9 Users Say Thank You to pali For This Useful Post:
explit's Avatar
Posts: 592 | Thanked: 1,603 times | Joined on Apr 2010 @ Berlin / Germany
#787
Thanks for the fix Pali!
So we wait for the next u-boot update?
So much work for one small bug :-(
All kernel flash-packages with u-boot should be updated now...
Or am i wrong?
 
Posts: 2,153 | Thanked: 8,462 times | Joined on May 2010
#788
u-boot-update-bootmenu is shell script, you can download it from github and replace it in your n900. After that you can re-run it. No need to recompile/reflash anything.
 

The Following 2 Users Say Thank You to pali For This Useful Post:
explit's Avatar
Posts: 592 | Thanked: 1,603 times | Joined on Apr 2010 @ Berlin / Germany
#789
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!
Attached Images
 
 
Posts: 1,808 | Thanked: 4,272 times | Joined on Feb 2011 @ Germany
#790
Originally Posted by explit View Post
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!
Here the diff:
Code:
 
 		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'..."
Github doesn't let me copy the line numbers, but I'm sure you'll be able to deal with it.

EDIT: added attached file (gzipped)
Attached Files
File Type: gz u-boot-update-bootmenu.gz (3.1 KB, 92 views)
 

The Following User Says Thank You to reinob For This Useful Post:
Reply

Tags
bootmenu, u-boot

Thread Tools

 
Forum Jump


All times are GMT. The time now is 12:14.