日期:2014-05-16  浏览次数:20747 次

求助!!用NFS模式启动Micro2440时出现下面错误请问是怎么回事?
用NFS模式启动Micro2440时出现下面错误请问是怎么回事?
No OV9650 found!!!
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq enabled
s3c-sdi s3c2440-sdi: powered down.
s3c-sdi s3c2440-sdi: mmc0 - using pio, sw SDIO IRQ
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.21.
No device for DAI UDA134X
No device for DAI s3c24xx-i2s
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: UDA134X <-> s3c24xx-i2s mapping ok
ALSA device list:
  #0: S3C24XX_UDA134X (UDA134X)
TCP cubic registered
NET: Registered protocol family 17
s3c2410-rtc s3c2410-rtc: setting system clock to 2006-10-10 07:05:55 UTC (116046
3955)
eth0: link down
IP-Config: Gateway not on directly connected network.
Looking up port of RPC 100003/2 on 192.168.1.108
eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
rpcbind: server 192.168.1.108 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 192.168.1.108
rpcbind: server 192.168.1.108 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
Root-NFS: Server returned error -5 while mounting /opt/FriendlyARM/mini2440/root
_qtopia
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
VFS: Cannot open root device "nfs" or unknown-block(2,0)
1f00 256 mtdblock0 (driver?)
1f01 128 mtdblock1 (driver?)
1f02 5120 mtdblock2 (driver?)
1f03 256640 mtdblock3 (driver?)
1f04 262144 mtdblock4 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Backtrace:
[<c00341cc>] (dump_backtrace+0x0/0x10c) from [<c03297d0>] (dump_stack+0x18/0x1c)

 r7:c03db108 r6:00008000 r5:c3923000 r4:c0481b10
[<c03297b8>] (dump_stack+0x0/0x1c) from [<c0329820>] (panic+0x4c/0x114)
[<c03297d4>] (panic+0x0/0x114) from [<c0008dbc>] (mount_block_root+0x174/0x228)
 r3:c38599ec r2:00000000 r1:c3823f60 r0:c03db0a0
[<c0008c48>] (mount_block_root+0x0/0x228) from [<c0008f34>] (mount_root+0xc4/0xf
c)
[<c0008e70>] (mount_root+0x0/0xfc) from [<c0009094>] (prepare_namespace+0x128/0x
180)
 r5:c002081d r4:c04814e0
[<c0008f6c>] (prepare_namespace+0x0/0x180) from [<c00084b0>] (kernel_init+0xe0/0
x114)
 r5:c001f180 r4:c04812a0
[<c00083d0>] (kernel_init+0x0/0x114) from [<c004bbbc>] (do_exit+0x0/0x620)
 r5:00000000 r4:00000000


------解决方案--------------------
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq enabled
s3c-sdi s3c2440-sdi: powered down.
s3c-sdi s3c2440-sdi: mmc0 - using pio, sw SDIO IRQ
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.21.
No device for DAI UDA134X
No device for DAI s3c24xx-i2s
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: UDA134X <-> s3c24xx-i2s mapping ok
ALSA device list:
#0: S3C24XX_UDA134X (UDA134X)
TCP cubic registered
NET: Registered protocol family 17
s3c2410-rtc s3c2410-rtc: setting system clock to 2006-10-10 07:05:55 UTC (116046
3955)
eth0: link down
IP-Config: Gateway not on directly connected network.
Looking up port of RPC 100003/2 on 192.168.1.108
eth0: link up, 100Mbps, f