Hi Charlie & ts-7000 group members,
The boot portion is running just fine, it’s the runtime
linux startup that is having the problem…
At least that is what I believe..
Jayne
Linux version 2.4.26-ts11 (gcc version
3.3.4) #2 Tue Jun 10 13:55:19 MST 2008
CPU: Arm920Tid(wb) revision 0
Machine: ep9301
On node 0 totalpages: 2048
zone(0): 2048 pages.
zone(1): 0 pages.
zone(2): 0 pages.
On node 1 totalpages: 2048
zone(0): 2048 pages.
zone(1): 0 pages.
zone(2): 0 pages.
On node 4 totalpages: 2048
zone(0): 2048 pages.
zone(1): 0 pages.
zone(2): 0 pages.
On node 5 totalpages: 2048
zone(0): 2048 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/ram0 init=/linuxrc
printk=4 loops=499712
Relocating machine vectors to 0xffff0000
Console: colour dummy device 80x30
99.94 BogoMIPS
Memory: 8MB 8MB 8MB 8MB = 32MB total
Memory: 24504KB available (1223K code, 342K data,
76K init)
Dentry cache hash table entries: 4096 (order: 3,
32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384
bytes)
Mount cache hash table entries: 512 (order: 0, 4096
bytes)
Buffer cache hash table entries: 1024 (order: 0,
4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768
bytes)
CPU: Testing write buffer: pass
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society
NET3.039
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch
devfs: boot_options: 0x1
yaffs Jun 10 2008 13:37:26 Installing.
ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA
ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA
ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA
TS-UART/7400 detected a TS-7400 board
ttyTS0 at MMIO 0x12400000 (irq = 33) is a TSUART
pty: 1024 Unix98 ptys configured
Using DIO to access RTC
Real Time Clock Driver v1.10f
ep93xx_eth() version: ep93xx_eth.c: V1.0 09/04/2003
Cirrus Logic
RAMDISK driver initialized: 16 RAM disks of 12288K
size 1024 blocksize
Searching for NAND flash...
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1
(Samsung NAND 128MiB 3,3V 8-bit)
Using MBR partition definition
Creating 4 MTD partitions on "NAND 128MiB 3,3V
8-bit":
0x00000000-0x08000000 : "whole chip"
0x00020000-0x00220000 : "kernel"
0x00220000-0x00420000 : "initrd"
0x00440000-0x08000000 : "rootfs"
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind
4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NetWinder Floating Point Emulator V0.97 (double
precision)
RAMDISK: ext2 filesystem found at block 0
RAMDISK:
Loading 1024 blocks [1 disk] into ram disk...
done.
Freeing initrd memory: 4096K
EXT2-fs warning: mounting unchecked fs, running
e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Mounted devfs on /dev
Freeing init memory: 76K
smiCmDio initialized.
Searching for NAND flash...
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung
NAND 128MiB 3,3V 8-bit)
nand_scan(): Buffers not set. Scan aborted
VFS: Can't find ext2 filesystem on dev
mtdblock(31,3).
yaffs: dev is 7939 name is "1f:03"
yaffs: Attempting MTD mount on 31.3,
"1f:03"
block 544 is bad
sdcard0: Technologic Systems SD card controller,
address 0x13000000
sdcard0: no card found
Unable to register driver
TS-UART/7260 did not detect a TS-7260 board
TS-UART/RF2 did not detect a TS-RF2 board
From:
[ On Behalf Of charliem_1216
Sent: Tuesday, January 20, 2009 3:03 PM
To:
Subject: [ts-7000] Re: TS7400-32-128F NAND startup info question
Hi Jayne --
--- In ts-7000%40yahoogroups.com,
"Jayne Dickinson" <> wrote:
> Here's a snippet of dmesg .... what does VFS: Can't find ext2
filesystem
> message mean? Is this bad??
> If so, what to do??
>
> Thanks for your help
> NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB
> 3,3V 8-bit)
> nand_scan(): Buffers not set. Scan aborted
> VFS: Can't find ext2 filesystem on dev mtdblock(31,3).
> yaffs: dev is 7939 name is "1f:03"
> yaffs: Attempting MTD mount on 31.3, "1f:03
What kernel version?
Is this part of a boot log, or is userspace running here?
Do you have an ext2 entry in /etc/fstab that is trying to be mounted
at startup?
regards, ........ Charlie
__._,_.___
![]()
__,_._,___