Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] LAN booting
Date: Tue, 14 Aug 2001 22:49:05 -0400	[thread overview]
Message-ID: <20010814224905.B26703@megatonmonkey.net> (raw)
In-Reply-To: <20010814135337.C345@familie-weerts.de>; from christian@familie-weerts.de on Tue, Aug 14, 2001 at 01:53:37PM +0000

> I will try, but first i had to boot the machine over LAN, that's my problem
> at the moment.
> The RISC-Machine tells something like "Error: cannot load IPL, error
> detected. Bootprocess failed..."
> Perhaps you could help me, so i attach the bootptab and the dhcp-conf. Also
> attached are the daemon.log and output from tcpdump. Btw., gorilla is the
> server and mirage the client.
> I don't know what's wrong. 
> On the risc-machine i told him to boot from the lan.<hw-addr-server>.
> 

There should be nothing wrong with booting over the lan.

I did not receive any attachments with this email?

> Ack.

Cross compiling is really not all that bad 8)

> > Could you mount the 0.92 ISO on an x86-linux box and steal that kernel?
> > (there are probably several but just try the 32-bit ones.)
> I'll try. So, you mean i don't need the nfsroot-package named in Martin's
> HOWTO?

You can use it.

If you handroll a kernel with nfs-root parameters 
and setup an nfs share for you root, you
can boot without a disk onto the nfs-root.

What do you put on your nfs-root?:

- The unpacked nfsroot tarball
- sid baseplus tarball (under the debian directories).
- nothing (You get to check if the setup is okay, 
  though the kernel will panic when it doesn't find /)

Cheers,
Carlos.

      reply	other threads:[~2001-08-15  2:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13 18:07 [parisc-linux] LAN booting Christian Weerts
2001-08-13 23:55 ` Grant Grundler
2001-08-14 13:53   ` Christian Weerts
2001-08-15  2:49     ` Carlos O'Donell Jr. [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=20010814224905.B26703@megatonmonkey.net \
    --to=carlos@baldric.uwo.ca \
    --cc=parisc-linux@lists.parisc-linux.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