Thanks for your answer,
I've compiled with CONFIG_BLK_DEV_INITRD enabled, but CONFIG_MTD is
disabled.
What is the function or the procedure responsible for the search of the
magic number -rom1fs- ?
Thanks in advance.
S.Lambert
Jate Sujjavanich a e'crit :
What is the device driver which will give access to the romfs in memory?
Blkmem or mtd?
- Jate
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Stephane Lambert
Sent: Thursday, January 08, 2009 4:27 AM
To: [email protected]; [email protected]
Subject: [uClinux-dev] Problem with romfs
Hi all,
I'm trying to boot kernel 2.6.19 in a new architecture and I have a
problem concerning romfs.
During compilation I've created a section .romfs which contains
romfs.img. I have checked with GDB and I found correctly the magic
number -rom1fs- at the expected location.
But I don't understand how the kernel points to this location in order
to find romfs during initialisation?
Of course the boot crashs during the execution of prepare-namespace()
with the well-known errors (see kernel output).
Does my root=boot option correct?
I've read a lot of things about this but I haven't found the details
that I'm looking for.
Thanks in advance for your help.
************************************************************************
*********************
Sections:
Idx Name Size VMA LMA File off Algn
0 .text.init 0000a7ac 80000000 80000000 00090000 2**2
CONTENTS, ALLOC, LOAD, READONLY, CODE
1 .text 00086b54 8000a7b0 8000a7b0 000017b0 2**4
CONTENTS, ALLOC, LOAD, READONLY, CODE
2 .sbss 000004a8 00000000 00000000 000000b4 2**4
ALLOC
3 .data 00007b58 000004a8 80091304 000884a8 2**2
CONTENTS, ALLOC, LOAD, DATA
4 .init 00000730 00008000 00008000 00001000 2**2
CONTENTS, ALLOC, LOAD, READONLY, CODE
5 .bss 000098d0 00008730 00008730 00001730 2**2
ALLOC
6 .comment 000021b0 00000000 00000000 0009a7ac 2**0
CONTENTS, READONLY
7 .debug_aranges 00002018 00000000 00000000 0009c95c 2**0
CONTENTS, READONLY, DEBUGGING
8 .debug_pubnames 0000d32c 00000000 00000000 0009e974 2**0
CONTENTS, READONLY, DEBUGGING
9 .debug_info 00470883 00000000 00000000 000abca0 2**0
CONTENTS, READONLY, DEBUGGING 10 .debug_abbrev
0003728d 00000000 00000000 0051c523 2**0
CONTENTS, READONLY, DEBUGGING
11 .debug_line 000f928b 00000000 00000000 005537b0 2**0
CONTENTS, READONLY, DEBUGGING
12 .debug_frame 00014290 00000000 00000000 0064ca3c 2**2
CONTENTS, READONLY, DEBUGGING
13 .debug_str 001f58a1 00000000 00000000 00660ccc 2**0
CONTENTS, READONLY, DEBUGGING
14 .debug_loc 0009b58f 00000000 00000000 0085656d 2**0
CONTENTS, READONLY, DEBUGGING
15 .debug_ranges 0002d970 0009b58f 0009b58f 008f1afc 2**0
CONTENTS, READONLY, DEBUGGING
16 .heap 00020000 000c8f00 000c8f00 0091f46c 2**2
CONTENTS, READONLY
17 .romfs 00018400 00012000 00012000 00940000 2**0
CONTENTS, ALLOC, LOAD, DATA
************************************************************************
*********************
Linux version 2.6.19-uc1 (gcc version 4.1.2 20080812 (Cortus release))
#157 Wed Jan 7 15:23:23 CET 2009
Built 1 zonelists. Total pages: 1524
Kernel command line: root=/dev/ram0
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)
Mem_init: start=212000, end=600000
Memory available: 1006k/3936k RAM, (538k kernel code, 68k data)
Mount-cache hash table entries: 512 io scheduler noop registered io
scheduler anticipatory registered io scheduler deadline registered io
scheduler cfq registered (default) RAMDISK driver initialized: 16 RAM
disks of 4096K size 1024 blocksize
*******
VFS: test name = </dev/root>
VFS: fs_name = <romfs>
VFS: tried fs_name = <romfs> err= -6
*******
VFS: Cannot open root device "ram0" or unknown-block(0,0) Please append
a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to
mount root fs on
unknown-block(0,0)
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected] To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
************************************************************************
************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals &
computer viruses.
************************************************************************
************
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
