Re: [uClinux-dev] port to Olimex SAM9-L9260 ( boot fsck: fsck.jffs2:not found message)
Hi Kris, On 07/04/2009 02:13 AM, Microbit_P43000 wrote: Thanks for reviewing. I will absorb the submit patches issue in the near future. Typical - with some further effort, I solved the mysterious fsck.jffs2 puzzle, it was more a matter of looking deeper again into the scripts. Once the script has decided that e2fsck indeed is executed, I noticed it uses file system info from fstab... I did not know however that fsck can't process jffs2 files (in hindsight it makes perfect sense of course since the mtd layers are needed on top of Flash for JFFS2). To cut a long story short, the root is there as type jffs2 which results in a concatenation of fsck with jffs2, hence the error, as this executable doesn't exist. Well, at least I'm glad I _did_ solve it myself after all - always has been and will be the best way to learn ! I just need to figure out now how to inhibit that futile fsck call, the start up error is irritating me.. :-) Finally, I wonder if you could clarify for me Greg : I added a kernel command parameter in (menu)config 'fastboot', but the error still persists ? From studying the script, I thought fastboot ensured that fsck is not run - at least not on rootcheck ? Which script are your referring to? This sounds like it is completely vendor dependant - in other words whatever Olimex put on there. Regards Greg -Original Message- From: uclinux-dev-boun...@uclinux.org [mailto:uclinux-dev-boun...@uclinux.org] On Behalf Of Greg Ungerer Sent: Friday, 3 July 2009 3:24 PM To: uClinux development list Subject: Re: [uClinux-dev] port to Olimex SAM9-L9260 ( boot fsck: fsck.jffs2:not found message) Hi Kris, Microbit_P43000 wrote: Hi all, I'm new to this list and (uC)linux overall. However, with some persistence (and great interest in uClinux :-) I got the uCLinux-dist (20080808) ported and running smoothly on the Olimex SAM9-L9260 board (similar to Atmel AT91SAM9260-EK). I don't know yet how to go about patches or implementing something so my effort can be incorporated into future versions. The best place to start is to read the documentation in linux-2.6.x/Documentation/SubmittingPatches Regards Greg ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev -- Greg Ungerer -- Principal EngineerEMAIL: g...@snapgear.com SnapGear Group, McAfee PHONE: +61 7 3435 2888 825 Stanley St, FAX: +61 7 3891 3630 Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] port to Olimex SAM9-L9260 ( boot fsck: fsck.jffs2:not found message)
On Mon, 2009-07-06 at 18:32 +1000, Greg Ungerer wrote: Hi Kris, On 07/04/2009 02:13 AM, Microbit_P43000 wrote: Thanks for reviewing. I will absorb the submit patches issue in the near future. Typical - with some further effort, I solved the mysterious fsck.jffs2 puzzle, it was more a matter of looking deeper again into the scripts. Once the script has decided that e2fsck indeed is executed, I noticed it uses file system info from fstab... I did not know however that fsck can't process jffs2 files (in hindsight it makes perfect sense of course since the mtd layers are needed on top of Flash for JFFS2). To cut a long story short, the root is there as type jffs2 which results in a concatenation of fsck with jffs2, hence the error, as this executable doesn't exist. Well, at least I'm glad I _did_ solve it myself after all - always has been and will be the best way to learn ! I just need to figure out now how to inhibit that futile fsck call, the start up error is irritating me.. :-) Finally, I wonder if you could clarify for me Greg : I added a kernel command parameter in (menu)config 'fastboot', but the error still persists ? From studying the script, I thought fastboot ensured that fsck is not run - at least not on rootcheck ? Which script are your referring to? This sounds like it is completely vendor dependant - in other words whatever Olimex put on there. Regards Greg -Original Message- From: uclinux-dev-boun...@uclinux.org [mailto:uclinux-dev-boun...@uclinux.org] On Behalf Of Greg Ungerer Sent: Friday, 3 July 2009 3:24 PM To: uClinux development list Subject: Re: [uClinux-dev] port to Olimex SAM9-L9260 ( boot fsck: fsck.jffs2:not found message) Hi Kris, Microbit_P43000 wrote: Hi all, I'm new to this list and (uC)linux overall. However, with some persistence (and great interest in uClinux :-) I got the uCLinux-dist (20080808) ported and running smoothly on the Olimex SAM9-L9260 board (similar to Atmel AT91SAM9260-EK). I don't know yet how to go about patches or implementing something so my effort can be incorporated into future versions. The best place to start is to read the documentation in linux-2.6.x/Documentation/SubmittingPatches Regards Greg ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev Hi Greg, Which script are your referring to? This sounds like it is completely vendor dependant - in other words whatever Olimex put on there. I did figure that out in the interim. In hindsight a bit dumb of me - I suppose that's the whole idea behind it, its flexibility with runlevels. Unfortunately it also (can) make it very confusing for newbies like me... :-) I checked again - it's rcS.d- S10checkroot.sh, but this is what had me stumped : FSCKCODE=0 if [ -f /fastboot ] then [ $rootcheck = yes ] log_warning_msg Fast boot enabled, so skipping file system check. rootcheck=no fi I couldn't identify another var in the shell that forces fsck after all (overriding the decision to NOT execute e2fsk). But in the interim I wondered about building my own minimal rootfs, so it's a lot clearer (I prefer the 'hands-on' approach, rather than just reading it). I installed buildroot, am close to creatin' a small jffs2 image. Once I got the loose ends right wrt mapping uboot handover to the kernel, then I can think/see clearer :-) Thanks in any case, Greg. Best regards, Kris ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
RE: [uClinux-dev] port to Olimex SAM9-L9260 ( boot fsck: fsck.jffs2:not found message)
Hi Greg, Thanks for reviewing. I will absorb the submit patches issue in the near future. Typical - with some further effort, I solved the mysterious fsck.jffs2 puzzle, it was more a matter of looking deeper again into the scripts. Once the script has decided that e2fsck indeed is executed, I noticed it uses file system info from fstab... I did not know however that fsck can't process jffs2 files (in hindsight it makes perfect sense of course since the mtd layers are needed on top of Flash for JFFS2). To cut a long story short, the root is there as type jffs2 which results in a concatenation of fsck with jffs2, hence the error, as this executable doesn't exist. Well, at least I'm glad I _did_ solve it myself after all - always has been and will be the best way to learn ! I just need to figure out now how to inhibit that futile fsck call, the start up error is irritating me.. :-) Finally, I wonder if you could clarify for me Greg : I added a kernel command parameter in (menu)config 'fastboot', but the error still persists ? From studying the script, I thought fastboot ensured that fsck is not run - at least not on rootcheck ? Best Regards, Kris -Original Message- From: uclinux-dev-boun...@uclinux.org [mailto:uclinux-dev-boun...@uclinux.org] On Behalf Of Greg Ungerer Sent: Friday, 3 July 2009 3:24 PM To: uClinux development list Subject: Re: [uClinux-dev] port to Olimex SAM9-L9260 ( boot fsck: fsck.jffs2:not found message) Hi Kris, Microbit_P43000 wrote: Hi all, I'm new to this list and (uC)linux overall. However, with some persistence (and great interest in uClinux :-) I got the uCLinux-dist (20080808) ported and running smoothly on the Olimex SAM9-L9260 board (similar to Atmel AT91SAM9260-EK). I don't know yet how to go about patches or implementing something so my effort can be incorporated into future versions. The best place to start is to read the documentation in linux-2.6.x/Documentation/SubmittingPatches Regards Greg ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
RE: [uClinux-dev] port to Olimex SAM9-L9260 ( boot fsck: fsck.jffs2:not found message)
Oh, I should stipulate that I also went through the sources of U-boot etc.
Could it also be possible that the DataFlash environment section has
something in it
that is read during start up ?
Best Regards,
Kris
-Original Message-
From: uclinux-dev-boun...@uclinux.org
[mailto:uclinux-dev-boun...@uclinux.org] On Behalf
Of
Microbit_P43000
Sent: Wednesday, 1 July 2009 9:13 PM
To: 'uClinux development list'
Subject: [uClinux-dev] port to Olimex SAM9-L9260 ( boot fsck: fsck.jffs2:not
found
message)
Hi all,
I'm new to this list and (uC)linux overall.
However, with some persistence (and great interest in uClinux :-) I got the
uCLinux-dist
(20080808) ported and running smoothly on the Olimex SAM9-L9260 board
(similar to Atmel AT91SAM9260-EK).
I don't know yet how to go about patches or implementing something so my
effort can be
incorporated into future versions. I expanded the Kernel config so you can
select the
board there.
I should enunciate that I'm not posting to cop out on a problem, on the
contrary, I want
to learn as much as possible about (uC)linux under the bonnet :-)
My actual question is about the start up and init :
The original included Linux has root file image that goes into the 512 MB
Flash.
There are/were a few bizarre error messages on booting that I can't get rid
of. Since
I
now run a completely different kernel and these messages stay, they must
result from
some
file or script somewhere on the JFFS root image.
I have spent days on scouring through all the init.d scripts and what have
you, and I
still can't find the source of these pests
Is there anyone here that could help me, or maybe even someone that uses
AT91SAM9 ?
The most bizarre message on boot I get is :
Checking root file system...fsck 1.40-WIP (14-Nov-2006)
fsck: fsck.jffs2: not found
fsck: Error 2 while executing fsck.jffs2 for /dev/mtdblock1
done.
I can't find for the life of me where it is invoked.
I also can't figure out how to stop these occasional messages :
JFFS2 notice: (863) check_node_data: wrong data CRC in data node at
0x149fed7c:
read.
{although I've set the noise level in the kernel config to 0 (debug) for
JFFS2,
this starts after I have modified file/files on the JFFS2 image}.
Lastly, is there anyone that can give a push in the right direction how to
turn off this
time consuming Flash check after init boot, resulting in the Empty flash at
0x0c89630c
ends at 0x0c896800and the likes. These are before the init freed log.
I include a recent boot log for reference if anyone can give a hint :
RomBOOT
AT91Bootstrap loading from 0x8400...
U-Boot 1.3.4-1-g8ed2f5f-dirty (Aug 20 2008 - 18:26:55)
DRAM: 64 MB
NAND: 512 MiB
DataFlash:AT45DB161
Nb pages: 4096
Page Size:528
Size= 2162688 bytes
Logical address: 0xD000
Area 0: D000 to D00041FF (RO) Bootstrap
Area 1: D0004200 to D00083FF Environment
Area 2: D0008400 to D0041FFF (RO) U-Boot
Area 3: D0042000 to D0251FFF Kernel
Area 4: D0252000 to D020 FS
In:serial
Out: serial
Err: serial
Net: macb0
macb0: link up, 100Mbps full-duplex (lpa: 0x45e1)
Hit any key to stop autoboot: 3 2 1 0
## Booting kernel from Legacy Image at 2220 ...
Image Name: Linux-2.6.25-uc0-my_uClinux
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:1486708 Bytes = 1.4 MB
Load Address: 20008000
Entry Point: 20008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing
Linux.
done, booting the kernel.
Linux version 2.6.25-uc0-my_uClinux (k...@ubuntu) (gcc version 4.2.3
(Sourcery G++ Lite
2008q1-126)) #12 Tue Jun 30 04:14:19 BST 2009
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Olimex SAM9-L9260
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 180 MHz, master 90 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: mem=64M console=ttyS0,115200 root=/dev/mtdblock1 rw
rootfstype=jffs2
AT91: 96 gpio irqs in 3 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
console [ttyS0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61824KB available (2760K code, 210K data, 104K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 152 bytes
NET: Registered protocol family 16
SCSI subsystem initialized
usbcore:
