您的位置:首页 > 其它

DIM3517 NFS无法挂载解决办法

2012-07-22 15:13 357 查看
NFS无法挂载,用S3C2440的板子测试NFS完好,结果用DIM3517的板子始终挂载不上,纳闷

Texas Instruments X-Loader 1.44 (Jun 24 2010 - 15:48:14)

Starting OS Bootloader...

U-Boot 2009.11 ( 9月 29 2010 - 14:33:05)

OMAP34xx/35xx-GP ES1.0, CPU-OPP2 L3-165MHz

AM3517EVM Board + LPDDR/NAND

I2C: ready

DRAM: 256 MB

NAND: 512 MiB

In: serial

Out: serial

Err: serial

Die ID #0dcc0000000000000155dc1402014022

Net: davinci_emac_initialize

Ethernet PHY: GENERIC @ 0x00

DaVinci EMAC

Hit any key to stop autoboot: 0

Using DaVinci EMAC device

TFTP from server 192.168.0.7; our IP address is 192.168.0.11

Filename 'uImage'.

Load address: 0x82000000

Loading: T #################################################################

#################################################################

#################################################################

#################################################################

#################################################################

#################################################################

#################################################################

##############################################################

done

Bytes transferred = 2642944 (285400 hex)

## Booting kernel from Legacy Image at 82000000 ...

Image Name: Linux-2.6.32

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 2642880 Bytes = 2.5 MB

Load Address: 80008000

Entry Point: 80008000

Verifying Checksum ... OK

Loading Kernel Image ... OK

OK

Starting kernel ...

Uncompressing Linux..........................................................................................................................................

Linux version 2.6.32 (mry@mry) (gcc version 4.5.2 (Sourcery G++ Lite 2011.03-42) ) #8 Sun Jun 26 11:10:47 CST 2011

CPU: ARMv7 Processor [411fc087] revision 7 (ARMv7), cr=10c53c7f

CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache

Machine: OMAP3517/AM3517 EVM

Memory policy: ECC disabled, Data cache writeback

AM3517 ES1.0 (l2cache iva sgx neon isp )

SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000

Reserving 4194304 bytes SDRAM for VRAM

Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024

Kernel command line: noinitrd init=/linuxrc root=/dev/nfs rw nfsroot=192.168.0.7:/home/mry/nfs/fs ip=192.168.0.11:192.168.0.7:192.168.0.1:255.255.255.0
cons8

PID hash table entries: 1024 (order: 0, 4096 bytes)

Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

Memory: 256MB = 256MB total

Memory: 249984KB available (4788K code, 437K data, 168K init, 0K highmem)

Hierarchical RCU implementation.

NR_IRQS:368

Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz

GPMC revision 5.0

IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts

Total of 96 interrupts on 1 active controller

OMAP GPIO hardware version 2.5

OMAP clockevent source: GPTIMER1 at 32768 Hz

Console: colour dummy device 80x30

Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696)

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

regulator: core version 0.5

NET: Registered protocol family 16

mux: Could not set signal i2c2_scl

mux: Could not set signal i2c2_sda

mux: Could not set signal i2c3_scl

mux: Could not set signal i2c3_sda

Display option not selected

OMAP DMA hardware revision 4.0

bio: create slab <bio-0> at 0

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

i2c_omap i2c_omap.1: bus 1 rev3.12 at 400 kHz

regulator: VDCDC1: 1200 mV normal

regulator: VDCDC2: 3300 mV normal

regulator: VDCDC3: 1800 mV normal

regulator: LDO1: 1800 mV normal

regulator: LDO2: 3300 mV normal

i2c_omap i2c_omap.2: bus 2 rev3.12 at 400 kHz

pca953x 2-0021: failed reading register

pca953x: probe of 2-0021 failed with error -5

i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz

tca6416-keypad 3-0020: failed reading register

tca6416-keypad: probe of 3-0020 failed with error -5

pca953x 3-0021: failed reading register

pca953x: probe of 3-0021 failed with error -5

Switching to clocksource 32k_counter

musb_hdrc: version 6.0, cppi4.1-dma, otg (peripheral+host), debug=0

AM3517 OTG revision 4ea41001, PHY f0036a2, control 00

musb_hdrc: USB OTG mode controller at d0810000 using DMA, IRQ 71

NET: Registered protocol family 2

IP route cache hash table entries: 2048 (order: 1, 8192 bytes)

TCP established hash table entries: 8192 (order: 4, 65536 bytes)

TCP bind hash table entries: 8192 (order: 3, 32768 bytes)

TCP: Hash tables configured (established 8192 bind 8192)

TCP reno registered

UDP hash table entries: 256 (order: 0, 4096 bytes)

UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

NET: Registered protocol family 1

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

RPC: Registered tcp NFSv4.1 backchannel transport module.

AM3517 Linux PSP version 03.00.01.06 (AM3517EVM)

NetWinder Floating Point Emulator V0.97 (double precision)

VFS: Disk quotas dquot_6.5.2

Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

Installing knfsd (copyright (C) 1996 okir@monad.swb.de).

JFFS2 version 2.2. (NAND) 2001-2006 Red Hat, Inc.

yaffs Jun 26 2011 08:42:07 Installing.

msgmni has been set to 488

alg: No test for stdrng (krng)

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

OMAP DSS rev 2.0

OMAP DISPC rev 3.0

OMAP VENC rev 2

OMAP DSI rev 1.0

Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654

serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654

serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654

console [ttyS2] enabled

brd: module loaded

loop: module loaded

omap2-nand driver initializing

NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung omap2-nand.0)

NAND bus width 16 instead 8 bit

No NAND device found!!!

NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit)

Creating 5 MTD partitions on "omap2-nand.0":

0x000000000000-0x000000080000 : "xloader-nand"

0x000000080000-0x000000240000 : "uboot-nand"

0x000000240000-0x000000280000 : "params-nand"

0x000000280000-0x000000780000 : "linux-nand"

0x000000780000-0x000020000000 : "jffs2-nand"

vcan: Virtual CAN interface driver

CAN device driver interface

TI High End CAN Controller Driver 0.7

failed to get can_stb

ti_hecc ti_hecc.1: device registered (reg_base=d0870000, irq=24)

usbcore: registered new interface driver hwa-rc

usbmon: debugfs is not available

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

~~~~~~~~~~~~~~~~~~~~~0!!!!!!!!!!!~~~~~~~~~`

~~~~~~~~~~~~~~~~~~~~~1!!!!!!!!!!!~~~~~~~~~`

ehci-omap ehci-omap.0: OMAP-EHCI Host Controller

ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1

ehci-omap ehci-omap.0: irq 77, io mem 0x48064800

ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 3 ports detected

ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver

usbcore: registered new interface driver hwa-hc

usbcore: registered new interface driver wusb-cbaf

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

g_ether gadget: using random self ethernet address

g_ether gadget: using random host ethernet address

usb0: MAC a2:9d:ef:cc:99:2f

usb0: HOST MAC 92:26:66:e2:6d:f3

g_ether gadget: Ethernet Gadget, version: Memorial Day 2008

g_ether gadget: g_ether ready

musb_hdrc musb_hdrc: MUSB HDRC host driver

musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected

mice: PS/2 mouse device common for all mice

tsc2003 init

tsc2003 probe

tsc2003 begin

GPIO176 irqqq :336

input: tsc2003 as /class/input/input0

tsc2003 x:2352 y:3072 z:2064 bate:4080

rtc-s35390a 1-0030: error resetting chip

rtc-s35390a: probe of 1-0030 failed with error -5

Linux video capture interface: v2.00

vpfe_init

vpfe-capture vpfe-capture: v4l2 device registered

vpfe-capture vpfe-capture: video device registered

tvp514x 3-005c: tvp514x 3-005c decoder driver registered !!

vpfe-capture vpfe-capture: v4l2 sub device tvp5146 registered

vpfe_register_ccdc_device: DM6446 CCDC

DM6446 CCDC is registered with vpfe.

OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec

mmci-omap-hs mmci-omap-hs.1: err -16 configuring card detect

usbcore: registered new interface driver usbhid

usbhid: USB HID core driver

Advanced Linux Sound Architecture Driver Version 1.0.21.

No device for DAI AD73311

Asahi Kasei AK4104 ALSA SoC Codec Driver

No device for DAI AK4535

Cirrus Logic CS4270 ALSA SoC Codec Driver

No device for DAI PCM3008 HiFi

No device for DAI SSM2602

No device for DAI tlv320aic23

No device for DAI tlv320aic3x

No device for DAI UDA134X

No device for DAI WM8510 HiFi

No device for DAI WM8728

No device for DAI WM8750

No device for DAI WM8971

usb 1-1: new high speed USB device using ehci-omap and address 2

No device for DAI WM8990 ADC/DAC Primary

No device for DAI omap-mcbsp-dai-0

No device for DAI omap-mcbsp-dai-1

No device for DAI omap-mcbsp-dai-2

No device for DAI omap-mcbsp-dai-3

No device for DAI omap-mcbsp-dai-4

OMAP3517 / AM3517 EVM SoC init

asoc: tlv320aic3x <-> omap-mcbsp-dai-0 mapping ok

Failed to add route IN1L->LINE1L

dapm: tlv320aic3x: configuring unknown pin Line Out

ALSA device list:

#0: am3517evm (tlv320aic3x)

TCP cubic registered

NET: Registered protocol family 17

NET: Registered protocol family 15

can: controller area network core (rev 20090105 abi 8)

NET: Registered protocol family 29

can: raw protocol (rev 20090105)

can: broadcast manager protocol (rev 20090105 t)

Power Management for TI OMAP3.

VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1

Console: switching to colour frame buffer device 100x30

omapdss DPI: Could not find exact pixel clock. Requested 35087 kHz, got 35086 kHz

davinci_emac_probe: using random MAC addr: 46:fb:37:90:95:76

emac-mii: probed

/home/mry/src/DIM3517_kernel_2.6.32/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

omapdss DPI error: display already enabled

omap_vout omap_vout: 'lcd' Display already enabled

omapdss DPI error: display already enabled

omap_vout omap_vout: 'lcd' Display already enabled

omap_vout omap_vout: Buffer Size = 3686400

omap_vout omap_vout: : registered and initialized video device 1

omap_vout omap_vout: Buffer Size = 3686400

omap_vout omap_vout: : registered and initialized video device 2

hub 1-1:1.0: USB hub found

hub 1-1:1.0: 4 ports detected

eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, id=22161a)

Sending DHCP and RARP requests .

PHY: ffffffff:00 - Link is Up - 100/Full

..... timed out!

IP-Config: Retrying forever (NFS root)...

eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, id=22161a)

Sending DHCP and RARP requests .

PHY: ffffffff:00 - Link is Up - 100/Full

..... timed out!

IP-Config: Retrying forever (NFS root)...

eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, id=22161a)

Sending DHCP and RARP requests .

PHY: ffffffff:00 - Link is Up - 100/Full

你的ip参数为ip=192.168.0.11:192.168.0.7:192.168.0.1:255.255.255.0

由于TI采用的内核较S3C2440的要新许多,当需要通过内核参数来设置ip时,最近的内核其实要求比较高。

在内核树的documentation/file systems/nfsroot.txt中关于ip参数和的描述如下。

ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>

This parameter tells the kernel how to configure IP addresses of devices

and also how to set up the IP routing table. It was originally called

`nfsaddrs', but now the boot-time IP configuration works independently of

NFS, so it was renamed to `ip' and the old name remained as an alias for

compatibility reasons.

If this parameter is missing from the kernel command line, all fields are

assumed to be empty, and the defaults mentioned below apply. In general

this means that the kernel tries to configure everything using

autoconfiguration.

The <autoconf> parameter can appear alone as the value to the `ip'

parameter (without all the ':' characters before). If the value is

"ip=off" or "ip=none", no autoconfiguration will take place, otherwise

autoconfiguration will take place. The most common way to use this

is "ip=dhcp".

<client-ip> IP address of the client.

Default: Determined using autoconfiguration.

<server-ip> IP address of the NFS server. If RARP is used to determine

the client address and this parameter is NOT empty only

replies from the specified server are accepted.

Only required for NFS root. That is autoconfiguration

will not be triggered if it is missing and NFS root is not

in operation.

Default: Determined using autoconfiguration.

The address of the autoconfiguration server is used.

<gw-ip> IP address of a gateway if the server is on a different subnet.

Default: Determined using autoconfiguration.

<netmask> Netmask for local network interface. If unspecified

the netmask is derived from the client IP address assuming

classful addressing.

Default: Determined using autoconfiguration.

<hostname> Name of the client. May be supplied by autoconfiguration,

but its absence will not trigger autoconfiguration.

Default: Client IP address is used in ASCII notation.

<device> Name of network device to use.

Default: If the host only has one device, it is used.

Otherwise the device is determined using

autoconfiguration. This is done by sending

autoconfiguration requests out of all devices,

and using the device that received the first reply.

<autoconf> Method to use for autoconfiguration. In the case of options

which specify multiple autoconfiguration protocols,

requests are sent using all protocols, and the first one

to reply is used.

Only autoconfiguration protocols that have been compiled

into the kernel will be used, regardless of the value of

this option.

off or none: don't use autoconfiguration

(do static IP assignment instead)

on or any: use any protocol available in the kernel

(default)

dhcp: use DHCP

bootp: use BOOTP

rarp: use RARP

both: use both BOOTP and RARP but not DHCP

(old option kept for backwards compatibility)

Default: any

建议你的参数设成这样,ip=192.168.0.11:192.168.0.7:192.168.0.1:255.255.255.0::eth0:off

最后的off可以有效的避免内核不停的去查找DHCP服务器,从而确保启动成功及极大的加快启动速度。
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息
标签: