救助：无法启动文件系统（busybox 的问题）

huangzhendi

Your elf file is little endian.
arch: arm
cpu info: armv4, arm920t, 41009200, ff00fff0, 2
mach info: name s3c2410x, mach_init addr 0x806e790
Your elf file will be load to: base address=0x30000000,mask=0xffffff
dbct info: turn on dbct!
uart_mod:0, desc_in:, desc_out:, converter:
SKYEYE: use arm920t mmu ops
Loaded RAM   ./ramfs.img
exec file "vmlinux"'s format is elf32-little.
load section .note.gnu.build-id: addr = 0x00000000  size = 0x00000024.
load section .text.head: addr = 0xc0008000  size = 0x000003c0.
load section .init: addr = 0xc00083c0  size = 0x00016c40.
load section .text: addr = 0xc001f000  size = 0x00179c4c.
load section .text.unlikely: addr = 0xc0198c4c  size = 0x00000164.
load section __ksymtab: addr = 0xc0199000  size = 0x00002b48.
load section __ksymtab_gpl: addr = 0xc019bb48  size = 0x00000d50.
load section __ksymtab_strings: addr = 0xc019c898  size = 0x000074c9.
load section __param: addr = 0xc01a3d64  size = 0x00000154.
load section .data: addr = 0xc01a4000  size = 0x000164e8.
not load section .bss: addr = 0xc01ba500  size = 0x000231f0 .
not load section .comment: addr = 0x00000000  size = 0x00004806 .
not load section .ARM.attributes: addr = 0x00000000  size = 0x00000026 .
not load section .debug_line: addr = 0x00000000  size = 0x000b72cd .
not load section .debug_info: addr = 0x00000000  size = 0x00b54f9f .
not load section .debug_abbrev: addr = 0x00000000  size = 0x0007093f .
not load section .debug_aranges: addr = 0x00000000  size = 0x00004aa8 .
not load section .debug_pubnames: addr = 0x00000000  size = 0x00014857 .
not load section .debug_str: addr = 0x00000000  size = 0x000516c5 .
not load section .debug_frame: addr = 0x00000000  size = 0x00039bb4 .
not load section .debug_loc: addr = 0x00000000  size = 0x00116bbc .
not load section .debug_ranges: addr = 0x00000000  size = 0x0003a848 .
call ARMul_InitSymTable,kernel filename is vmlinux.
start addr is set to 0x30008000 by exec file.
SKYEYE:Error in mem_read_word, no bank found, NumInstrs 31, mem_read_word addr = 0 no bank
Linux version 2.6.24.2 ([email protected]) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #8 Thu Apr 23 19:13:54 CST 2009
CPU: ARM920T [41009200] revision 0 (ARMvundefined/unknown), cr=00003177
Machine: SMDK2410
Warning: bad configuration page, trying to continue
Memory policy: ECC disabled, Data cache writeback
CPU S3C2410 (id 0x32410000)
S3C2410: core 62.400 MHz, memory 62.400 MHz, peripheral 62.400 MHz
S3C24XX Clocks, (c) 2004 Simtec Electronics
CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
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
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
Kernel command line: mem=32M console=ttySAC0 root=/dev/ram initrd=0x30800000,0x00800000 ramdisk_size=8192 rw
PID hash table entries: 128 (order: 7, 512 bytes)
timer tcon=00000000, tcnt cb1f, tcfg 00000200,00000000, usec 0000189e
Console: colour dummy device 80x30
console [ttySAC0] enabled
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 22376KB available (1556K code, 229K data, 92K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
S3C2410: Initialising architecture
S3C24XX DMA Driver, (c) 2003-2004,2006 Simtec Electronics
DMA channel 0 at c2800000, irq 33
DMA channel 1 at c2800040, irq 34
DMA channel 2 at c2800080, irq 35
DMA channel 3 at c28000c0, irq 36
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd
Freeing initrd memory: 8192K
NetWinder Floating Point Emulator V0.97 (extended precision)
JFFS2 version 2.2. (NAND) ? 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
s3c2410-uart.0: s3c2410_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2410
s3c2410-uart.1: s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2410
s3c2410-uart.2: s3c2410_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2410
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: module loaded
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 6144KiB [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 92K
在skyeye下仿真linux 2.6.24,busybox为1.13.3，gcc编译器是从"友善之臂"的网站上下的，版本为4.3.2，skyeye提供的编译环境arm-2008-11-24.iso也试过，出现同样的问题。
我尝试将skyeye-testsuite-1.2.5中s3c2410x-2.6.14的文件系统的内容复制到我自己做的文件系统中，结果文件系统可以正常启动了。
可以肯定是busybox编译的问题。
怀疑是mdev原因，但可能性不大，因为skyeye-testsuite-1.2.5中s3c2410x-2.6.14的文件系统并不支持mdev,文件系统还是可以启动的，网上提到的要支持tmpfs、sysfs、Kernel Features  、Floating point emulation  等相关项也已经选择上的，问题依旧。
此外，我还尝试过用qemu仿真过自己做的文件系统，结果动态编译的可以正常运行，而静态编译的则提示找不到设备，skyeye-testsuite-1.2.5中s3c2410x-2.6.14的文件系统是静态编译的，在qemu下也是可以运行的。

busybox编译到最后，无论是动态编译还是静态编译都会揭示：
Trying libraries: crypt m
Library crypt is needed
Library m is needed
Final link with: crypt m
我的理解静态编译时不应该出现，不知道是什么原因？

现可确定是busybox的问题，但不知道问题在哪里，请高人指点。

实验中的skyeye.conf内容
#skyeye config file sample

cpu:  arm920t
mach: s3c2410x

#physical memory
#mem_bank: map=M, type=RW, addr=0x20000000, size=0x01000000
mem_bank: map=M, type=RW, addr=0x30000000, size=0x00800000
mem_bank: map=M, type=RW, addr=0x30800000, size=0x00800000, file=./ramfs.img
mem_bank: map=M, type=RW, addr=0x31000000, size=0x01000000
#all peripherals I/O mapping area
#mem_bank: map=I, type=RW, addr=0xfefa0000, size=0x00060000
mem_bank: map=I, type=RW, addr=0x48000000, size=0x20000000
mem_bank: map=I, type=RW, addr=0x19000300, size=0x00000020
#net: type=cs8900a, base=0x19000300, size=0x20,int=9, mac=0:4:3:2:1:f, ethmod=tuntap, hostip=10.0.0.1
#lcd:type=s3c2410x,mod=gtk
load_addr:base=0x30000000, mask=0xFFFFFF
dbct:state=on
如果实在解决不了，请兄弟们传我一个已经编译好的busybox(带mdev功能)，静态或动态编译的都行，谢谢!!!
QQ:243594257 email:[email protected]

[ 本帖最后由 huangzhendi 于 2009-4-23 21:29 编辑 ]

liujianwei

我也是同样的问题静态动态编译都不行