* problems on building root filesystem using scratchbox and meamo
@ 2005-12-05 13:37 xuxian
2005-12-05 22:11 ` Matthew Percival
0 siblings, 1 reply; 6+ messages in thread
From: xuxian @ 2005-12-05 13:37 UTC (permalink / raw)
To: maemo-users; +Cc: linux-arm, linux-omap-open-source, scratchbox-users
Hi all,
I'm using scratchbox and meamo to build my root filesystem. I fallow the
steps shown in the HOWTO: Using flasher and the reference root filesystem.
The link is:
http://www.maemo.org/platform/docs/howtos/howto_use_flasher_rootfs.html
Finally, I got the jffs2 image of my root filesystem and download it to my
board OSK5912 successfully. But I meet the following error messages when
boot the kernel:
............................................................................
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 192.168.4.1, my address is 192.168.4.190
IP-Config: Complete:
device=eth0, addr=192.168.4.190, mask=255.255.255.0, gw=192.168.4.1,
host=192.168.4.190, domain=omap1_eth1, nis-domain=(none),
bootserver=192.168.4.1, rootserver=192.168.4.1, rootpath=
Node at 0x0062e3b8 with length 0x80001044 would run over the end of the
erase block
Perhaps the file system was created with the wrong erase size?
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0062e3bc:
0x1044 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0062e3c0:
0x586d instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0062e3c4:
0x030c instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0062e3c8:
0x001a instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0062e3cc:
0x81a4 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0062e3d4:
0xacc3 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0062e3d8:
0x2317 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0062e3dc:
0x2317 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0062e3e0:
0x2317 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0062e3e4:
0x9000 instead
Further such events for this erase block will not be printed
Node at 0x00630138 with length 0x80000777 would run over the end of the
erase block
Perhaps the file system was created with the wrong erase size?
Node at 0x006311f8 with length 0x80000f3d would run over the end of the
erase block
Perhaps the file system was created with the wrong erase size?
Node at 0x00632138 with length 0x80000fe5 would run over the end of the
erase block
Perhaps the file system was created with the wrong erase size?
Node at 0x00635138 with length 0x8000103f would run over the end of the
erase block
Perhaps the file system was created with the wrong erase size?
Node at 0x00636178 with length 0x80000045 would run over the end of the
erase block
Perhaps the file system was created with the wrong erase size?
............................................................................
It seems the filesystem can work as NFS, but not stable. It can work once in
three times approximately, and in the other times it can't go further more
when the following messages shown on the console:
............................................................................
Looking up port of RPC 100003/2 on 192.168.0.11
Looking up port of RPC 100005/1 on 192.168.0.11
VFS: Mounted root (nfs filesystem).
Freeing init memory: 120K
............................................................................
My board is OSK5912 and the kernel is omap-linux-2.6.14.
I have had these problems for quite a while, but have never been able to
identify the cause. Dos anyone have experience in it? Any help will be
appreciated.
Thank in advance.
Best regards.
xuxian
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: problems on building root filesystem using scratchbox and meamo
2005-12-05 13:37 problems on building root filesystem using scratchbox and meamo xuxian
@ 2005-12-05 22:11 ` Matthew Percival
2005-12-07 6:14 ` xuxian
0 siblings, 1 reply; 6+ messages in thread
From: Matthew Percival @ 2005-12-05 22:11 UTC (permalink / raw)
To: Linux OMAP Open Source
G'Day,
> Perhaps the file system was created with the wrong erase size?
Could you share the command you used to make the filesystem image? It
seems likely you did not use the correct erase size. Try this command:
# cat /proc/mtd
It will tell you the correct erase block size. If you used a size
different to this (mkfs.jffs2 -e 0x####) then you will get errors like
you have seen here.
-- Matthew
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: problems on building root filesystem using scratchbox and meamo
2005-12-05 22:11 ` Matthew Percival
@ 2005-12-07 6:14 ` xuxian
2005-12-07 22:05 ` Matthew Percival
0 siblings, 1 reply; 6+ messages in thread
From: xuxian @ 2005-12-07 6:14 UTC (permalink / raw)
To: 'Matthew Percival', 'Linux OMAP Open Source'
Hi Matthew,
I use the command:
mkfs.jffs2 -p -l -e 0x20000 -n -v -r /home/xuxian/rootfs/fs -o
filesys.jffs2
to make the root filesystem image.
Several weeks ago, I mad a filesystem image use the same command without
scratchbox and maemo, and it work quite well. So I guess if the problem had
something to do with the scratchbox and maemo?
What size of the erase block will be fine? I can't access the file /proc/mtd
because I cannot mount the filesystem. Does the kernel determine the size of
erase block or anything else? Where can I set the erase block size?
Thank you and best regards
xuxian
-----Original Message-----
From: linux-omap-open-source-bounces@linux.omap.com
[mailto:linux-omap-open-source-bounces@linux.omap.com] On Behalf Of Matthew
Percival
Sent: Tuesday, December 06, 2005 6:11 AM
To: Linux OMAP Open Source
Subject: Re: problems on building root filesystem using scratchbox and meamo
G'Day,
> Perhaps the file system was created with the wrong erase size?
Could you share the command you used to make the filesystem image?
It
seems likely you did not use the correct erase size. Try this command:
# cat /proc/mtd
It will tell you the correct erase block size. If you used a size
different to this (mkfs.jffs2 -e 0x####) then you will get errors like
you have seen here.
-- Matthew
_______________________________________________
Linux-omap-open-source mailing list
Linux-omap-open-source@linux.omap.com
http://linux.omap.com/mailman/listinfo/linux-omap-open-source
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: problems on building root filesystem using scratchbox and meamo
2005-12-07 6:14 ` xuxian
@ 2005-12-07 22:05 ` Matthew Percival
2005-12-09 2:54 ` xuxian
0 siblings, 1 reply; 6+ messages in thread
From: Matthew Percival @ 2005-12-07 22:05 UTC (permalink / raw)
To: Linux OMAP Open Source
G'Day,
> I use the command:
> mkfs.jffs2 -p -l -e 0x20000 -n -v -r /home/xuxian/rootfs/fs -o
> filesys.jffs2
> to make the root filesystem image.
For my OSK, -e 0x20000 is the correct size; the command I use is
basically the same as you.
> What size of the erase block will be fine? I can't access the file /proc/mtd
> because I cannot mount the filesystem. Does the kernel determine the size of
> erase block or anything else? Where can I set the erase block size?
If you mount your filesystem as an NFS root rather than an image, then
you can read /proc/mtd, but I would say you are most likely correct in
your erase size.
I am not familiar with scratchbox or maemo, so it is possible your
problem relates to them, but I cannot be sure. Sorry, I probably will
not be of much help here.
-- Matthew
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: problems on building root filesystem using scratchbox and meamo
2005-12-07 22:05 ` Matthew Percival
@ 2005-12-09 2:54 ` xuxian
2005-12-09 3:45 ` Menon, Nishanth
0 siblings, 1 reply; 6+ messages in thread
From: xuxian @ 2005-12-09 2:54 UTC (permalink / raw)
To: 'Matthew Percival', 'Linux OMAP Open Source'
Hi,
What part decides the size of erase block? The hardware, the kernel or the
root filesystem?
Best regards,
xuxian
-----Original Message-----
From: linux-omap-open-source-bounces@linux.omap.com
[mailto:linux-omap-open-source-bounces@linux.omap.com] On Behalf Of Matthew
Percival
Sent: Thursday, December 08, 2005 6:05 AM
To: Linux OMAP Open Source
Subject: RE: problems on building root filesystem using scratchbox and meamo
G'Day,
> I use the command:
> mkfs.jffs2 -p -l -e 0x20000 -n -v -r /home/xuxian/rootfs/fs -o
> filesys.jffs2
> to make the root filesystem image.
For my OSK, -e 0x20000 is the correct size; the command I use is
basically the same as you.
> What size of the erase block will be fine? I can't access the file
/proc/mtd
> because I cannot mount the filesystem. Does the kernel determine the size
of
> erase block or anything else? Where can I set the erase block size?
If you mount your filesystem as an NFS root rather than an image,
then
you can read /proc/mtd, but I would say you are most likely correct in
your erase size.
I am not familiar with scratchbox or maemo, so it is possible your
problem relates to them, but I cannot be sure. Sorry, I probably will
not be of much help here.
-- Matthew
_______________________________________________
Linux-omap-open-source mailing list
Linux-omap-open-source@linux.omap.com
http://linux.omap.com/mailman/listinfo/linux-omap-open-source
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: problems on building root filesystem using scratchbox and meamo
2005-12-09 2:54 ` xuxian
@ 2005-12-09 3:45 ` Menon, Nishanth
0 siblings, 0 replies; 6+ messages in thread
From: Menon, Nishanth @ 2005-12-09 3:45 UTC (permalink / raw)
To: xuxian, Matthew Percival, Linux OMAP Open Source
Hi,
It is the hardware that decides the erase block.
E.g. on L18 (Intel Strata Flash), it will be 128K. This information is used to put the cleanmarker (in JFFS2) or EBH (Erase Block Header) to the start of the block to notify that this block is erased.
Regards,
Nishanth Menon
________________________________
From: linux-omap-open-source-bounces@linux.omap.com on behalf of xuxian
Sent: Thu 12/8/2005 8:54 PM
To: 'Matthew Percival'; 'Linux OMAP Open Source'
Subject: RE: problems on building root filesystem using scratchbox and meamo
Hi,
What part decides the size of erase block? The hardware, the kernel or the
root filesystem?
Best regards,
xuxian
-----Original Message-----
From: linux-omap-open-source-bounces@linux.omap.com
[mailto:linux-omap-open-source-bounces@linux.omap.com] On Behalf Of Matthew
Percival
Sent: Thursday, December 08, 2005 6:05 AM
To: Linux OMAP Open Source
Subject: RE: problems on building root filesystem using scratchbox and meamo
G'Day,
> I use the command:
> mkfs.jffs2 -p -l -e 0x20000 -n -v -r /home/xuxian/rootfs/fs -o
> filesys.jffs2
> to make the root filesystem image.
For my OSK, -e 0x20000 is the correct size; the command I use is
basically the same as you.
> What size of the erase block will be fine? I can't access the file
/proc/mtd
> because I cannot mount the filesystem. Does the kernel determine the size
of
> erase block or anything else? Where can I set the erase block size?
If you mount your filesystem as an NFS root rather than an image,
then
you can read /proc/mtd, but I would say you are most likely correct in
your erase size.
I am not familiar with scratchbox or maemo, so it is possible your
problem relates to them, but I cannot be sure. Sorry, I probably will
not be of much help here.
-- Matthew
_______________________________________________
Linux-omap-open-source mailing list
Linux-omap-open-source@linux.omap.com
http://linux.omap.com/mailman/listinfo/linux-omap-open-source
_______________________________________________
Linux-omap-open-source mailing list
Linux-omap-open-source@linux.omap.com
http://linux.omap.com/mailman/listinfo/linux-omap-open-source
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2005-12-09 3:45 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-12-05 13:37 problems on building root filesystem using scratchbox and meamo xuxian
2005-12-05 22:11 ` Matthew Percival
2005-12-07 6:14 ` xuxian
2005-12-07 22:05 ` Matthew Percival
2005-12-09 2:54 ` xuxian
2005-12-09 3:45 ` Menon, Nishanth
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox