Some thoughts.
I think the clue here might be the inability to mount devfs_fs.
I recall building a boot yaffs image where the root was not read/write and that caused trouble. Do check permissions.
I note that devfs_debug is zero. Increasing that may be useful.
You are not using ECC it seems. Hmm .. be very afraid.
Nick Bane
> -----Original Message-----
> From: balloon-admin@balloonboard.org
> [mailto:balloon-admin@balloonboard.org]On Behalf Of jeanwelly
> Sent: 10 May 2005 09:55
> To: manningc2@actrix.gen.nz
> Cc: yaffs@stoneboat.aleph1.co.uk; Balloon@balloonboard.org
> Subject: [Balloon] Re: [Yaffs] Yaffs on 2.6.11
>
>
> Thanks.
> I have compiled yaffs into kernel.
> It can work with cramfs(root fs partition) and yaffs(usr partition).
> But error found when use yaffs as root fs :
> I use mkyaffsimage to get the rootyaffs.img.
>
> linux command line is: "noinitrd root=/dev/mtdblock/3 init=/linuxrc
> console=tty"MACH_TYPE = 193
> NOW, Booting Linux......
> Uncompressing
> Linux.............................................................Linux
> version 2.6.11 (root@localhost.localdomain) (gcc version 3.4.1) #35
> Tue M5CPU: ARM920Tid(wb) [41129200] revision 0 (ARMv4T)
> CPU0: D VIVT write-back cache
> CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
> CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
> Machine: SMDK2410
> ATAG_INITRD is deprecated; please update your bootloader.
> Memory policy: ECC disabled, Data cache writeback
> CPU S3C2410 (id 0x32410000)
> S3C2410: core 200.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz
> S3C2410 Clock control, (c) 2004 Simtec Electronics
> Built 1 zonelists
> Kernel command line: noinitrd root=/dev/mtdblock/3 init=/linuxrc
> console=ttySAC0irq: clearing pending ext status 00000300
> irq: clearing subpending status 00000003
> irq: clearing subpending status 00000002
> PID hash table entries: 512 (order: 9, 8192 bytes)
> timer tcon=00000000, tcnt a2c1, tcfg 00000200,00000000, usec 00001eb8
> Console: colour dummy device 80x30
> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Memory: 64MB = 64MB total
> Memory: 62848KB available (1573K code, 347K data, 80K init)
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
> CPU: Testing write buffer coherency: ok
> NET: Registered protocol family 16
> S3C2410: Initialising architecture
> NetWinder Floating Point Emulator V0.97 (double precision)
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
> devfs: devfs_debug: 0x0
> devfs: boot_options: 0x1
> Initializing Cryptographic API
> Real Time Clock Driver v1.12
> S3C2410 RTC, (c) 2004 Simtec Electronics
> S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
> s3c2410_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2410
> s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2410
> s3c2410_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2410
> io scheduler noop registered
> Cirrus Logic CS8900A driver for Linux (Modified for SMDK2410)
> eth0: CS8900A rev E at 0xe0000300 irq=53, no eeprom , addr: 08:
> 0:3E:26:0A:5B
> S3C2410 NAND Driver, (c) 2004 Simtec Electronics
> s3c2410-nand: mapped registers at c4a00000
> s3c2410-nand: timing: Tacls 10ns, Twrph0 40ns, Twrph1 10ns
> NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB
> 3,3V 8-bi)NAND_ECC_NONE selected by board driver. This is not
> recommended !!
> Scanning device for bad blocks
> Bad eraseblock 307 at 0x004cc000 >>>>>>>>>> bad block???? !!!!!!!!!!!!
> Bad eraseblock 308 at 0x004d0000
> Bad eraseblock 309 at 0x004d4000
> Creating 5 MTD partitions on "NAND 64MiB 3,3V 8-bit":
> 0x00000000-0x00020000 : "vivi"
> mtd: Giving out device 0 to vivi
> 0x00020000-0x00030000 : "param"
> mtd: Giving out device 1 to param
> 0x00030000-0x00200000 : "kernel"
> mtd: Giving out device 2 to kernel
> 0x00200000-0x00500000 : "root"
> mtd: Giving out device 3 to root
> 0x00400000-0x03f00000 : "usr"
> mtd: Giving out device 4 to usr
> mice: PS/2 mouse device common for all mice
> NET: Registered protocol family 2
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP established hash table entries: 4096 (order: 3, 32768 bytes)
> TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
> TCP: Hash tables configured (established 4096 bind 4096)
> NET: Registered protocol family 1
> Root-NFS: No NFS server available, giving up.
> VFS: Unable to mount root fs via NFS, trying floppy.
> Reading data from NAND FLASH without ECC is not recommended
> yaffs: dev is 32505859 name is "(unavailable)"
> VFS: Mounted root (yaffs filesystem).
> mount_devfs_fs(): unable to mount devfs, err: -2
> Freeing init memory: 80K
> Warning: unable to open an initial console.
> Kernel panic - not syncing: No init found. Try passing init=
> option to kernel.
>
> So I want to erase the nand first.
> Using NFS, then,
> [root@localhost root_china]# file mkyaffs.arm
> mkyaffs.arm: ELF 32-bit LSB executable, ARM, version 1 (ARM), for
> GNU/Linux 2.4.0, dynamically linked (uses shared libs), not stripped
> [root@localhost root_china]# file mkyaffsimage
> mkyaffsimage: ELF 32-bit LSB executable, Intel 80386, version 1
> (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs),
> not stripped
>
> How can I successfully use yaffs as root fs.
>
>
>
> On 5/9/05, Charles Manning <manningc2@actrix.gen.nz> wrote:
> > On Monday 09 May 2005 01:39, jeanwelly wrote:
> > > I want to usr yaffs on 2.6.11 + s3c2410, K9F1208 nandflash.
> > > I can't access the CVS now, can you send me the yaffs.tar.gz file that
> > > can be used as root fs on 2.6.11.
> >
> > You can fetch an automatic tar file from
> > http://www.aleph1.co.uk/cgi-bin/viewcvs.cgi/cvs_root.tar.gz?tarball=1
> >
> > -- CHarles
> >
> >
>
>
> --
> jeanwelly
> Email: jeanwelly@gmail.com
> China
>
> _______________________________________________
> Balloon mailing list
> Balloon@balloonboard.org
> http://balloonboard.org/mailman/listinfo/balloon
> --
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.11.7 - Release Date: 09/05/2005
>
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.11.7 - Release Date: 09/05/2005
(text/plain)