ml403 u-boot can't load linux with nfs
hi all:
now i want to use u-boot load linux with avnet minimodule(like ml403 or
ml405) and EDK 10.1 .
after compliling the kernel, i use xmd down zImage.elf (nfs root),it
success
like this:
/
loaded at: 0040 005501A0
board data at: 0054E124 0054E1A0
relocated to: 004050B4 00405130
zimage at: 00405EE9 0054D16F
avail ram: 00551000 0400
Linux/PPC load: console=ttyS0,38400
ip=192.168.0.3:192.168.0.5:192.168.0.1:255.255.255.0 rw root=/dev/nfs
nfsroot=192.168.0.5:/myrootfs init=/bin/sh
Kernel command line: console=ttyS0,38400 root=/dev/nfs rw
nfsroot=192.168.0.5:/myrootfs
ip=192.168.0.3:192.168.0.5:192.168.0.1:255.255.255.0 init=/bin/sh
Uncompressing Linux...done.
Now booting the kernel
[0.00] Linux version 2.6.26 ([EMAIL PROTECTED]) (gcc version 4.1.1) #13
PREEMPT Sat Aug 23 17:02:29 CST 2008
[0.00] Xilinx Generic PowerPC board support package (Xilinx ML405)
(Virtex-4 FX)
[0.00] Zone PFN ranges:
[0.00] DMA 0 ->16384
..
[0.00] Kernel command line: console=ttyS0,38400
ip=192.168.0.3:192.168.0.5:192.168.0.1:255.255.255.0 rw root=/dev/nfs
nfsroot=192.168.0.5:/myrootfs init=/bin/sh
[0.00] Xilinx INTC #0 at 0x8180 mapped to 0xFDFFE000
..
[ 15.894120] eth0: XLlTemac: We renegotiated the speed to: 100
[ 15.921479] eth0: XLlTemac: speed set to 100Mb/s
[ 15.935472] eth0: XLlTemac: Send Threshold = 24, Receive Threshold = 4
[ 15.955208] eth0: XLlTemac: Send Wait bound = 254, Receive Wait bound =
254
[ 16.979388] IP-Config: Complete:
[ 16.988691] device=eth0, addr=192.168.0.3, mask=255.255.255.0,
gw=192.168.0.1,
[ 17.011779] host=192.168.0.3, domain=, nis-domain=(none),
[ 17.029405] bootserver=192.168.0.5, rootserver=192.168.0.5,
rootpath=
[ 17.051293] Looking up port of RPC 13/2 on 192.168.0.5
[ 17.078738] Looking up port of RPC 15/1 on 192.168.0.5
[ 17.150065] VFS: Mounted root (nfs filesystem).
[ 17.164245] Freeing unused kernel memory: 96k init
#
/
but when i use u-boot load,it die.
///
## Booting image at 0040 ...
Image Name: Linux-2.6.26
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size:1339912 Bytes = 1.3 MB
Load Address:
Entry Point:
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
[0.00] Linux version 2.6.26 ([EMAIL PROTECTED]) (gcc version 4.1.1) #14
PREEMPT Sat Aug 23 20:53:05 CST 2008
[0.00] Xilinx Generic PowerPC board support package (Xilinx ML405)
(Virtex-4 FX)
[0.00] Kernel command line: root=/dev/nfs console=ttyS0,38400
ip=192.168.0.3:192.168.0.5:192.168.0.1:255.255.255.0 rw
nfsroot=192.168.0.5:/myrootfs init=/bin/sh
[0.00] Xilinx INTC #0 at 0x8180 mapped to 0xFDFFE000
[0.00] PID hash table entries: 128 (order: 7, 512 bytes)
[1.234613] mice: PS/2 mouse device common for all mice
[1.255086] TCP cubic registered
[1.264907] NET: Registered protocol family 17
[1.279754] RPC: Registered udp transport module.
[1.294061] RPC: Registered tcp transport module.
[1.817329] eth0: XLlTemac: Options: 0x3fa
[1.829839] eth0: XLlTemac: allocating interrupt 0 for dma mode tx.
[1.848830] eth0: XLlTemac: allocating interrupt 1 for dma mode rx.
[ 13.840446] eth0: XLlTemac: Not able to set the speed to 1000 (status:
0x7949)
[ 15.858277] eth0: XLlTemac: We renegotiated the speed to: 100
[ 15.885639] eth0: XLlTemac: speed set to 100Mb/s
[ 15.899634] eth0: XLlTemac: Send Threshold = 24, Receive Threshold = 4
[ 15.919370] eth0: XLlTemac: Send Wait bound = 254, Receive Wait bound =
254
[ 16.943365] IP-Config: Complete:
[ 16.952670] device=eth0, addr=192.168.0.3, mask=255.255.255.0,
gw=192.168.0.1,
[ 16.975732] host=192.168.0.3, domain=, nis-domain=(none),
[ 16.993359] bootserver=192.168.0.5, rootserver=192.168.0.5,
rootpath=
[ 17.015238] Looking up port of RPC 13/2 on 192.168.0.5
[ 17.055939] Looking up port of RPC 15/1 on 192.168.0.5
[ 17.230661] VFS: Mounted root (nfs filesystem).
[ 17.244815] Freeing unused kernel memory: 96k init
[ 17.338452] [ cut here ]
[ 17.352390] Badness at kernel/mutex.c:134
[ 17.364431] NIP: c021bd20 LR: c021bd08 CTR: c00e0794
I find they are the same process except [ 17.338452] [ cut here ]--
so i trace the code.and find
run_init_process("/bin/sh")->kernel_execve(),here may be the proplem. but i
am not sure.
any suggestion will be very appreciated.thank you!
hsongjiang
--
View this message in context:
http://www.nabble.com/ml403--u-boot-can%27t-load-linux-with-nfs-tp19145094p19145094.html
Sent f
Re: [PATCH V2] MPC52XX: Don't touch pipelining for MPC5200B
roger blofeld wrote: Hi Since this bug is ATA specific, shouldn't this code be conditioned by CONFIG_IDE ? And then what happens if IDE is built as a module? -Scott ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: virt_to_phys() in drivers w/dma - MPC8xxx
Russell McGuire wrote: So shouldn't we be using like dma_alloc_coherent, and then tracking the dma address separately as a variable, and use it when necessary instead of calling virt_to_phys()? Yes. On 8xxx (but not 8xx, and not with 36-bit memory), there'll be no practical difference, but the DMA mapping API *should* be used. -Scott ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: porting linux 2.6.27 to embedded powerpc board
Hi,
I now have the system booted all the up to the shell prompt.
However, my two NIC cards are not up.
When the system is booting, I get the following error:
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
24520:00 not found
eth0: Could not attach to PHY
IP-Config: Failed to open eth0
IP-Config: Device `eth0' not found.
here is the networking section from my .dts file
[EMAIL PROTECTED] {
#address-cells = <1>;
#size-cells = <0>;
compatible = "fsl,gianfar-mdio";
reg = <0x24520 0x20>;
phy0: [EMAIL PROTECTED] {
interrupt-parent = <&ipic>;
interrupts = <17 0x8>;
reg = <0x0>;
device_type = "ethernet-phy";
};
phy1: [EMAIL PROTECTED] {
interrupt-parent = <&ipic>;
interrupts = <18 0x8>;
reg = <0x1>;
device_type = "ethernet-phy";
};
};
enet0: [EMAIL PROTECTED] {
cell-index = <0>;
device_type = "network";
model = "TSEC";
compatible = "gianfar";
reg = <0x24000 0x1000>;
local-mac-address = [ 00 00 00 00 00 00 ];
interrupts = <32 0x8 33 0x8 34 0x8>;
interrupt-parent = <&ipic>;
phy-handle = <&phy0>;
linux,network-index = <0>;
};
enet1: [EMAIL PROTECTED] {
cell-index = <1>;
device_type = "network";
model = "TSEC";
compatible = "gianfar";
reg = <0x25000 0x1000>;
local-mac-address = [ 00 00 00 00 00 00 ];
interrupts = <35 0x8 36 0x8 37 0x8>;
interrupt-parent = <&ipic>;
phy-handle = <&phy1>;
linux,network-index = <1>;
};
Does anything here seem to be wrong?
thanks for your help
LK
- Original Message
From: David Jander <[EMAIL PROTECTED]>
To: linuxppc-embedded@ozlabs.org
Cc: Laxmikant Rashinkar <[EMAIL PROTECTED]>
Sent: Thursday, August 21, 2008 2:43:45 AM
Subject: Re: porting linux 2.6.27 to embedded powerpc board
On Thursday 21 August 2008 01:24:46 Laxmikant Rashinkar wrote:
> Hi,
>
> I have an embedded PowerPC (MPC8347) board that works fine with uboot and
> Linux 2.6.15.
>
> I am trying to upgrade the kernel so that it runs on the latest release -
> Linux 2.6.27. So far, I have gotten the kernel to compile on my platform,
> but of course it does not boot.
Well, honestly I don't know where to look for information either (other than
the source-code and examples from others), but here is a list with points to
look out for (I have just done the same thing as you for a MPC5200B-based
board):
1. Upgrade to latest u-boot first (recent git seems to be fine). There have
been a lot of changes in u-boot lately about OF and device-tree related
things. I suspect you need a fairly recent version of u-boot to go well with
the latest kernel. It's also generally a good idea IMHO.
2. I assume you are porting to arch/powerpc (the old arch/ppc you used back in
2.6.15 is obsolete and broken now).
3. Look at other platforms that use the same processor, and pick a simple one
as starting point. Look out for the dts (device-tree-source file in
arch/powerpc/boot/dts), copy and modify one to reflect your hardware.
Recently a lot of changes happend in the kernel, changing device names,
obsoleting "device-type" tags, etc..., so some of the current DTS sources
included in the kernel might not even work (wrong device name, missing
information, wrong use of "device-type", etc...), so watch out for these kind
of issues too.
4. Be sure that the device(s) necessary to produce output on your console are
correctly placed in the DT. Also make sure that u-boot knows about it
(#define OF_STDOUT_PATH... in your u-boot board config file)
5. When compiling the device tree, it may be necessary to add some extra
reserved entries to the compiled tree (I am using dtc -p 10240 -R 20, which
might be slightly exaggerated), because u-boot may add something to it, and
if it can't, linux won't boot.
6. Remember to always specify the "rootfstype=" option on the commandline if
booting from anything other than NFS. This was not necessary back in the
2.6.15-times AFAICR.
7. Boot with a device-tree (in u-boot: "bootm $addrofkernel - $addrof
