All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abhijit Naik <abhijit_naik27@rediffmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: nfs mounting problem
Date: Fri, 12 Oct 2007 02:13:17 -0700 (PDT)	[thread overview]
Message-ID: <13171747.post@talk.nabble.com> (raw)
In-Reply-To: <OF08754E94.1194DC2D-ON6525726C.0043EADB-6525726C.0044D6F4@lntemsys.com>


Hello Manjunath,
      You open the ports of portmaper and nfs from firewall. Refer
http://www.linuxquestions.org/questions/linux-security-4/firewall-blocking-nfs-even-though-ports-are-open-294069/.
Hope you get your problem solved.
     
All teh best


Manjunath AM wrote:
> 
> Hi,
> 
> We are using MPC8272 based target board, we are trying to mount montavista 
> Linux version 2.6.10 kernel image (with NFS enabled) to our target board,
> we are setting following bootargs in bootloader 
> 
> "setenv bootargs root=/dev/nfs 
> nfsroot=192.168.178.110:/opt/montavista/pro/devkit/ppc/82xx/target 
> ip=192.168.178.234:192.168.178.110:192.168.178.47:255.255.255.0:cashel:eth1:off"
> 
> when we boot the board, it is not able to mount nfs file system to board, 
> but the same image and configuration works with MPC8272ADS board.
> please suggest me, what could be the problem.
> 
> Booting image at 00200000 ...
>    Image Name:   Linux-2.6.10_mvl401-8272ads
>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>    Data Size:    948607 Bytes = 926.4 kB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
> Linux version 2.6.10_mvl401-8272ads (root@em178110) (gcc version 3.4.3 
> (MontaVista 3.4.3-25.0.70.050
> 1961 2005-12-18)) #2 Tue Jan 23 16:54:50 IST 2007
> Motorola PQ2 ADS PowerPC port
> Built 1 zonelists
> Kernel command line: root=/dev/nfs 
> nfsroot=192.168.178.110:/opt/montavista/pro/devkit/ppc/82xx/targe
> t 
> ip=192.168.178.234:192.168.178.110:192.168.178.47:255.255.255.0:cashel:eth1:off
> PID hash table entries: 128 (order: 7, 2048 bytes)
> hr_time_init: arch_to_nsec = 83886080, nsec_to_arch = 107374182
> Warning: real time clock seems stuck!
> Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
> Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> Memory: 13952k available (1684k kernel code, 468k data, 100k init, 0k 
> highmem)
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
> spawn_desched_task(00000000)
> desched cpu_callback 3/00000000
> ksoftirqd started up.
> desched cpu_callback 2/00000000
> desched thread 0 started up.
> NET: Registered protocol family 16
> Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> Initializing Cryptographic API
> Serial: CPM driver $Revision: 0.01 $
> ttyCPM0 at MMIO 0xf0011a00 (irq = 40) is a CPM UART
> ttyCPM1 at MMIO 0xf0011a60 (irq = 43) is a CPM UART
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> loop: loaded (max 8 devices)
> fs_enet.c:v1.0 (Aug 8, 2005)
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 50MHz system bus speed for PIO modes; override with 
> idebus=xx
> eth0: FCC ENET Version 0.3, 00:99:23:c4:ad:de
> eth1: FCC ENET Version 0.3, 00:99:23:44:ad:de
> eth2: FCC ENET Version 0.3, 00:99:23:64:ad:de
> NET: Registered protocol family 2
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 1024 bind 2048)
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> IP-Config: Complete:
>       device=eth1, addr=192.168.178.234, mask=255.255.255.0, 
> gw=192.168.178.47,
>      host=cashel, domain=, nis-domain=(none),
>      bootserver=192.168.178.110, rootserver=192.168.178.110, rootpath=
> Looking up port of RPC 100003/2 on 192.168.178.110
> portmap: server 192.168.178.110 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.178.110
> portmap: server 192.168.178.110 not responding, timed out
> Root-NFS: Unable to get mountd port number from server, using default
> mount: server 192.168.178.110 not responding, timed out
> Root-NFS: Server returned error -5 while mounting 
> /opt/montavista/pro/devkit/ppc/82xx/target
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device "nfs" or unknown-block(2,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on 
> unknown-block(2,0)
>  <0>Rebooting in 180 seconds..
> 
> Thanks and awaiting for your valuable feedback
> 
> 
> 
> Thanks & Regards
>  MANJUNATH AM
>  
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
:-)
-- 
View this message in context: http://www.nabble.com/nfs-mounting-problem-tf3063819.html#a13171747
Sent from the linuxppc-embedded mailing list archive at Nabble.com.

      parent reply	other threads:[~2007-10-12  9:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 12:33 nfs mounting problem Manjunath AM
2007-01-23 12:59 ` Andre Haupt
2007-01-23 13:23   ` Manjunath AM
2007-01-23 13:57     ` Andre Haupt
2007-01-23 15:32       ` Scott Wood
2007-01-24  8:10         ` Andre Haupt
2007-01-30 18:41           ` Manjunath AM
2007-10-12  9:13 ` Abhijit Naik [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=13171747.post@talk.nabble.com \
    --to=abhijit_naik27@rediffmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.