LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: gt bradley <baykelper@yahoo.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: nfs booting PS3, mount failed. (Geoff Levand)
Date: Tue, 17 Feb 2009 23:32:43 -0800 (PST)	[thread overview]
Message-ID: <710103.68816.qm@web56208.mail.re3.yahoo.com> (raw)
In-Reply-To: <mailman.0.1234918803.22420.linuxppc-dev@ozlabs.org>

[-- Attachment #1: Type: text/plain, Size: 4974 bytes --]



--- On Tue, 2/17/09, linuxppc-dev-request@ozlabs.org <linuxppc-dev-request@ozlabs.org> wrote:
From: linuxppc-dev-request@ozlabs.org <linuxppc-dev-request@ozlabs.org>
Subject: Linuxppc-dev Digest, Vol 54, Issue 101
To: linuxppc-dev@ozlabs.org
Date: Tuesday, February 17, 2009, 5:00 PM

Send Linuxppc-dev mailing list submissions to
	linuxppc-dev@ozlabs.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://ozlabs.org/mailman/listinfo/linuxppc-dev
or, via email, send a message with subject or body 'help' to
	linuxppc-dev-request@ozlabs.org

You can reach the person managing the list at
	linuxppc-dev-owner@ozlabs.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Linuxppc-dev digest..."
Today's Topics:

   1. NFS-boot on PS3, kboot can't mount nfs-dir.s (gt bradley)
   2. Re: nfs booting PS3, mount failed. (Geoff Levand)
   3. Re: nfs booting PS3, mount failed. (Geoff Levand)
I'm trying to set up my PS3 to netboot (with an nfsroot).

I'm using instructions at http://www.kernel.org/pub/linux/kernel/people/geoff/cell/ps3-howto/ps3-nfs-root-howto.txt

I've
passed section 3 (using tftp) to verify network /dhcp etc.   (i.e. I'm
able to tftp-get a file to ps3 from kboot's ash shell (busybox).

i'm trying to mount the nfs server as per section 4. with
 ~# mount -t nfs -o nolock 192.168.99.1:/target /mnt/remote

I get the following error message:
  mount: mounting 192.168.99.1:/target on /mnt/remote failed

if I boot the PS3 from the HD, then I am able to mount the nfs directory.
Using wireshark, I can see the initial dhcp traffic, (and when present the tftp traffic).
the mount command doesn't open a network connection to the server, 
So I have pretty much ruled out server
 configuration.

running "strings" on the decompressed kboot image yeilds serveral nfs symbols, so it 
appears to still support nfs mounting.  (using version kboot-20080609.bld from geoff's dir at kernel.org)
I have tried googling, and searching the various mailing lists, but am stuck.

any help would be
 appreciated
GT



      On 02/17/2009 04:20 PM, Geoff Levand wrote:

> Another thing to try is to use a 'rescue' disk/mode to copy the
files.
> Most distros have them.  Fedora has a rescue mode in their installer:
> 
>  
http://download.fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/ppc/iso/Fedora-10-ppc-netinst.iso
> 
> Just select 'rescue' instead of 'install', or you can add
> these to the boot options: 'text rescue video=720p'.

I forgot to mention an important point when using a rescue disk.
Most will mount all the runtime directories like /sys, /dev, /proc,
etc. onto the HD file system.  Those directories should not be
mounted the when you make the HD root FS copy.

Either choose the rescue option to not mount the HD file system,
and mount it yourself later, or unmount all those directories.
Just use the 'mount' command to see what has been mounted on the
HD's root FS.

-Geoff


On 02/16/2009 09:22 PM, gt bradley wrote:
> I'm trying to set up my PS3 to netboot (with an nfsroot).
> 
> I'm using instructions at
>
http://www.kernel.org/pub/linux/kernel/people/geoff/cell/ps3-howto/ps3-nfs-root-howto.txt
> 
> I've passed section 3 (using tftp) to verify network /dhcp etc.  
(i.e.
> I'm able to tftp-get a file to ps3 from kboot's ash shell
(busybox).
> 
> i'm trying to mount the nfs server as per section 4. with
> 
>  ~# mount -t nfs -o nolock 192.168.99.1:/target /mnt/remote
> 
> I get the following error message:
>   mount: mounting 192.168.99.1:/target on /mnt/remote failed
> 
> if I boot the PS3 from the HD, then I am able to mount the nfs directory.
> Using wireshark, I can see the initial dhcp traffic, (and when present the
tftp traffic).
> the mount command doesn't open a network connection to the server, 
> So I have pretty much ruled out server
>  configuration.
> 
> running "strings" on the decompressed kboot image yeilds
serveral nfs symbols, so it 
> appears to still support nfs mounting.  (using version kboot-20080609.bld
from geoff's dir at kernel.org)

I have sometimes seen nfs problems with kboot.  You could you
try petitboot.  Get the latest 'experimental' one from here:

  http://www.kernel.org/pub/linux/kernel/people/geoff/cell/ps3-petitboot/

Another thing to try is to use a 'rescue' disk/mode to copy the files.
Most distros have them.  Fedora has a rescue mode in their installer:

 
http://download.fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/ppc/iso/Fedora-10-ppc-netinst.iso

Just select 'rescue' instead of 'install', or you can add
these to the boot options: 'text rescue video=720p'.

You don't need kboot/petitboot to do nfs.  To load the kernel
they just need to do tftp.

-Geoff
  


I'll try this this week-end, and let you know how it goes, 
 Thank-you for the quick response.
GT


      

[-- Attachment #2: Type: text/html, Size: 6041 bytes --]

           reply	other threads:[~2009-02-18  7:32 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <mailman.0.1234918803.22420.linuxppc-dev@ozlabs.org>]

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=710103.68816.qm@web56208.mail.re3.yahoo.com \
    --to=baykelper@yahoo.com \
    --cc=linuxppc-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox