Linux MIPS Architecture development
 help / color / mirror / Atom feed
* Booting with NFS fails
@ 2005-11-05  7:13 Nguyen Thanh Binh
  2005-11-05  9:08 ` Manish Lachwani
  0 siblings, 1 reply; 4+ messages in thread
From: Nguyen Thanh Binh @ 2005-11-05  7:13 UTC (permalink / raw)
  To: linux-mips; +Cc: mlachwani

Hello all,

I have installed Red Hat Enterprise 3 on the host
(x86) and MontaVista Linux (previewkit) on the target
(memec virtex-4 Fx12 LC board). When booting the
target using NFS from the host, the following error
appeared:

   eth0: Link carrier lost.
   eth0: Could not read PHY control register; error
1003
   eth0: Terminating link monitoring.

It is very strange, because ethernet does not work as
the error shows but I can ping the target from the
host with the IP got with DHCP.

Your help or experience would be appreciated.

Thank you.

Nguyen Binh



		
___________________________________________________________ 
How much free photo storage do you get? Store your holiday 
snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Booting with NFS fails
  2005-11-05  7:13 Booting with NFS fails Nguyen Thanh Binh
@ 2005-11-05  9:08 ` Manish Lachwani
  2005-11-08  7:03   ` Nguyen Thanh Binh
  0 siblings, 1 reply; 4+ messages in thread
From: Manish Lachwani @ 2005-11-05  9:08 UTC (permalink / raw)
  To: Nguyen Thanh Binh, linux-mips; +Cc: mlachwani

Can you please post the complete boot log?

Thanks
Manish Lachwani

--- Nguyen Thanh Binh <n_tbinh@yahoo.com> wrote:

> Hello all,
> 
> I have installed Red Hat Enterprise 3 on the host
> (x86) and MontaVista Linux (previewkit) on the
> target
> (memec virtex-4 Fx12 LC board). When booting the
> target using NFS from the host, the following error
> appeared:
> 
>    eth0: Link carrier lost.
>    eth0: Could not read PHY control register; error
> 1003
>    eth0: Terminating link monitoring.
> 
> It is very strange, because ethernet does not work
> as
> the error shows but I can ping the target from the
> host with the IP got with DHCP.
> 
> Your help or experience would be appreciated.
> 
> Thank you.
> 
> Nguyen Binh
> 
> 
> 
> 		
>
___________________________________________________________
> 
> How much free photo storage do you get? Store your
> holiday 
> snaps for FREE with Yahoo! Photos
> http://uk.photos.yahoo.com
> 
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Booting with NFS fails
  2005-11-05  9:08 ` Manish Lachwani
@ 2005-11-08  7:03   ` Nguyen Thanh Binh
  2005-11-08 20:49     ` Stuart Anderson
  0 siblings, 1 reply; 4+ messages in thread
From: Nguyen Thanh Binh @ 2005-11-08  7:03 UTC (permalink / raw)
  To: Manish Lachwani, linux-mips; +Cc: mlachwani

Hi,

I do not know if you could receive the complete boot
log. I am resending that as follows:

====================================================
loaded at:     00400000 004A01E4
board data at: 0049D13C 0049D154
relocated to:  00405650 00405668
zimage at:     00405C1B 0049C4F1
avail ram:     004A1000 04000000
                                                      
                         
Linux/PPC load: console=ttyS0,9600 ip=on
nfsroot=192.168.114.27:/home/memec/MyDwUncompressing
Linux...done.
Now booting the kernel
Linux version 2.4.20_mvl31-ml300 (memec@TTT) (gcc
version 3.3.1 (MontaVista 3.35Xilinx Virtex-II Pro
port (C) 2002 MontaVista Software, Inc.
(source@mvista.com)On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: console=ttyS0,9600 ip=on
nfsroot=192.168.114.27:/home/memewXilinx INTC #0 at
0x41200000 mapped to 0xFDFFE000
Calibrating delay loop... 97.48 BogoMIPS
Memory: 63264k available (1068k kernel code, 368k
data, 60k init, 0k highmem)
Dentry cache hash table entries: 8192 (order: 4, 65536
bytes)
Inode cache hash table entries: 4096 (order: 3, 32768
bytes)
Mount-cache hash table entries: 1024 (order: 1, 8192
bytes)
Buffer-cache hash table entries: 4096 (order: 2, 16384
bytes)
Page-cache hash table entries: 16384 (order: 4, 65536
bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society
NET3.039
Initializing RT netlink socket
OCP uart ver 1.6.2 init complete
LSP Revision 42
ikconfig 0.5 with /proc/ikconfig
Starting kswapd
Disabling the Out Of Memory Killer
devfs: v1.12c (20020818) Richard Gooch
(rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with no
serial options enabled
ttyS00 at 0xfdfff003 (irq = 26) is a 16450
RAMDISK driver initialized: 16 RAM disks of 8192K size
1024 blocksize
loop: loaded (max 8 devices)
eth0: using fifo mode.
eth0: Xilinx EMAC #0 at 0x80400000 mapped to
0xC500D000, irq=31
eth0: id 2.0a; block id 0, type 8
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind
8192)
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 192.168.114.27, my
address is 192.168.114.30
IP-Config: Complete:
      device=eth0, addr=192.168.114.30,
mask=255.255.255.0, gw=192.168.114.27,
     host=192.168.114.30, domain=, nis-domain=(none),
     bootserver=192.168.114.27,
rootserver=192.168.114.27, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 192.168.114.27
Looking up port of RPC 100005/1 on 192.168.114.27
eth0: Link carrier lost.
VFS: Mounted root (nfs filesystem).
Mounted devfs on /dev
Freeing unused kernel memory: 60k init
eth0: Could not read PHY status register; error 1003
eth0: Terminating link monitoring.
====================================================



Thank you for your help.

Nguyen Binh

--- Manish Lachwani <m_lachwani@yahoo.com> wrote:

> Can you please post the complete boot log?
> 
> Thanks
> Manish Lachwani
> 
> --- Nguyen Thanh Binh <n_tbinh@yahoo.com> wrote:
> 
> > Hello all,
> > 
> > I have installed Red Hat Enterprise 3 on the host
> > (x86) and MontaVista Linux (previewkit) on the
> > target
> > (memec virtex-4 Fx12 LC board). When booting the
> > target using NFS from the host, the following
> error
> > appeared:
> > 
> >    eth0: Link carrier lost.
> >    eth0: Could not read PHY control register;
> error
> > 1003
> >    eth0: Terminating link monitoring.
> > 
> > It is very strange, because ethernet does not work
> > as
> > the error shows but I can ping the target from the
> > host with the IP got with DHCP.
> > 
> > Your help or experience would be appreciated.
> > 
> > Thank you.
> > 
> > Nguyen Binh
> > 
> > 
> > 
> > 		
> >
>
___________________________________________________________
> > 
> > How much free photo storage do you get? Store your
> > holiday 
> > snaps for FREE with Yahoo! Photos
> > http://uk.photos.yahoo.com
> > 
> > 
> 
> 
> 


Nguy&#7877;n Thanh Bình


		
___________________________________________________________ 
To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Booting with NFS fails
  2005-11-08  7:03   ` Nguyen Thanh Binh
@ 2005-11-08 20:49     ` Stuart Anderson
  0 siblings, 0 replies; 4+ messages in thread
From: Stuart Anderson @ 2005-11-08 20:49 UTC (permalink / raw)
  To: linux-mips


This looks consistant with the problem I have been seeing as well.


On Tue, 8 Nov 2005, Nguyen Thanh Binh wrote:

> Hi,
>
> I do not know if you could receive the complete boot
> log. I am resending that as follows:
>
> ====================================================
> loaded at:     00400000 004A01E4
> board data at: 0049D13C 0049D154
> relocated to:  00405650 00405668
> zimage at:     00405C1B 0049C4F1
> avail ram:     004A1000 04000000
>
>
> Linux/PPC load: console=ttyS0,9600 ip=on
> nfsroot=192.168.114.27:/home/memec/MyDwUncompressing
 	.
 	.
 	.
> Sending DHCP requests ., OK
> IP-Config: Got DHCP answer from 192.168.114.27, my
> address is 192.168.114.30
> IP-Config: Complete:
>      device=eth0, addr=192.168.114.30,
> mask=255.255.255.0, gw=192.168.114.27,
>     host=192.168.114.30, domain=, nis-domain=(none),
>     bootserver=192.168.114.27,
> rootserver=192.168.114.27, rootpath=
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> Looking up port of RPC 100003/2 on 192.168.114.27
> Looking up port of RPC 100005/1 on 192.168.114.27
> eth0: Link carrier lost.
> VFS: Mounted root (nfs filesystem).
> Mounted devfs on /dev
> Freeing unused kernel memory: 60k init
> eth0: Could not read PHY status register; error 1003
> eth0: Terminating link monitoring.
> ====================================================


                                 Stuart

Stuart R. Anderson                               anderson@netsweng.com
Network & Software Engineering                   http://www.netsweng.com/
1024D/37A79149:                                  0791 D3B8 9A4C 2CDC A31F
                                                  BD03 0A62 E534 37A7 9149

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2005-11-08 20:48 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-11-05  7:13 Booting with NFS fails Nguyen Thanh Binh
2005-11-05  9:08 ` Manish Lachwani
2005-11-08  7:03   ` Nguyen Thanh Binh
2005-11-08 20:49     ` Stuart Anderson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox