Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@puffin.external.hp.com>
To: plaven@ozemail.com.au
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: NFS root setup question
Date: Wed, 18 Apr 2001 10:17:14 -0600	[thread overview]
Message-ID: <200104181617.KAA19403@puffin.external.hp.com> (raw)
In-Reply-To: Your message of "Wed, 18 Apr 2001 21:02:52 +1000." <3ADE00FC.9679.982D3D@localhost>

"Pete" wrote:
> I have a 715/64 that I'm trying to boot across the network.
...
> The hp box fails with an error on the console (I have a vga screen 
> on the box):
> 
> "ERROR: Cannot load IPL, error detected."
> 
> Since this is my first time with nfsbooting it's likely I'm not doing 
> something right there, ie, I don't have /etc/exports setup.. should I 
> od this?

Yes. But you also need a *lifimage*.

I don't think matching lifimage's (matching the baseplus /boot/vmlinux)
where posted to the ftp site. I've posted a NFSROOT enabled lifimage for
a 32-bit/serial console (not STI enabled):
	ftp://puffin.external.hp.com/pub/parisc/binaries/lifimages/lifimage_32_serial_20010418.gz

Matching Systemp.map and vmlinux are in ../kernels directory.

For the 715's, append 'y' to the "boot lan y" in order to interactively
change the nfsroot= param (IP needs to point to the NFS server).
I don't recall if you need a different vmlinux embedded in the LIF or
if you can interactively tweak the palo boot params to use STI console
instead of serial.

grant

Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253

  reply	other threads:[~2001-04-18 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18 11:02 [parisc-linux] dumb question of the day Pete
2001-04-18 16:17 ` Grant Grundler [this message]
2001-04-18 17:35 ` Oliver Flimm

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=200104181617.KAA19403@puffin.external.hp.com \
    --to=grundler@puffin.external.hp.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=plaven@ozemail.com.au \
    /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