rootfs mounting

My system: ConnectME9210 4/8 Lx DigiEL-5.0 patched

I’ve worked several time on trying to make working the kernel with loading (or mounting, I don’t know what is the right word) the rootfs from flash AND NOT from nfs (then not from my /export/xxxx shared directory). No way!
I suppose that these assumptions are right:

The problem comes from the arguments given to the kernel (like root=, …), right?

There is a rootfs on flash (since I’ve flashed one) and it is that location that must be given as an arg to the kernel. Right? (then the kernel uncompress rootfs on RAM and use it)

I know that there are 5 partitions in flash. Is each partition is named mtdX? Where X = 0…4 ?

The only thing that works when booting kernel manually from U-Boot is “dboot linux tftp”. When I try “dboot linux flash” here is the message:

CME9210 # dboot linux flash
Reading: complete
*** Unsupported filesystem 0x7linux will be booted now

Booting image at 00200000 …

Image Name: Linux-
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1076016 Bytes = 1 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum … OK
fixing Load address and Entry Point: 00200040 00200040 …
XIP Kernel Image … OK

Starting kernel …

Uncompressing Linux… done, booting t
he kernel.
Linux version (monnoliv@PORTABLELINUX) (gcc version 4.3.2 (GCC) ) #3 Sun Aug 16 22:57:39 CEST 200
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Digi Connect ME 9210 on Devboard
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 2032
Kernel command line: ip= console=ttyNS0,
38400 mtdparts=physmap-flash.0:0x30000(U-Boot),0x20000@0x30000(NVRAM),0x140000@0x50000(Kernel),0x180000@0x
190000(RootFS-JFFS2),0xf0000@0x310000(User-JFFS2) root=/dev/ram rw
PID hash table entries: 32 (order: 5, 128 bytes)
Dentry cache hash table entries: 1024 (order: 0, 4096 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Memory: 8MB = 8MB total
Memory: 5844KB available (2016K code, 133K data, 76K init)
Calibrating delay loop… 37.06 BogoMIPS (lpj=185344)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 288 bytes
NET: Registered protocol family 16
ns921x CPU frequency change support initialized
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 512 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 512 bind 512)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 3.4 (2008/08/26) Phillip Lougher
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 16
io scheduler noop registered (default)
ns921x-serial.0: ttyNS0 at MMIO 0x90010000 (irq = 7) is a NS921X
console [ttyNS0] enabled
Digi NS921x UART driver
ns9xxx-eth-mii: probed
ns9xxx-eth ns9xxx-eth: eth0 at MMIO c105c000
Digi NS9XXX Ethernet driver
physmap platform flash device: 10000000 at 50000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
5 cmdlinepart partitions found on MTD device physmap-flash.0
Creating 5 MTD partitions on “physmap-flash.0”:
0x00000000-0x00030000 : “U-Boot”
0x00030000-0x00050000 : “NVRAM”
0x00050000-0x00190000 : “Kernel”
0x00190000-0x00310000 : “RootFS-JFFS2”
0x00310000-0x00400000 : “User-JFFS2”
ns9xxx-wdt ns9xxx-wdt: NS9xxx watchdog timer at 0xc105a174
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
IP-Config: Complete:
device=eth0, addr=, mask=, gw=,
host=cme9210js, domain=, nis-domain=(none),
bootserver=, rootserver=, rootpath=
VFS: Cannot open root device “ram” or unknown-block(1,0)
Please append a correct “root=” boot option; here are the available partitions:
1f00 192 mtdblock0 (driver?)
1f01 128 mtdblock1 (driver?)
1f02 1280 mtdblock2 (driver?)
1f03 1536 mtdblock3 (driver?)
1f04 960 mtdblock4 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

Someone can help me to answer to this questions?

Message was edited by: monnoliv

Message was edited by: monnoliv

Message was edited by: monnoliv

Message was edited by: monnoliv

Hi monnoliv,

does the kernel partiiton have the right fs?
Type in bootloader prompt “flpart”.


I had the same problem after flashing uboot from Linux 5.0 SDK. Uboot thinks that something’s wrong with the rootfs partition and tells the kernel (see kernel command line parameters in your post) to mount rootfs from /dev/ram.

Just use flpart and set proper image fs of rootfs partition (in my case it was jffs2).

Good luck,