All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Melville <m_thrope@rigelfore.com>
To: linux@cthulhu.engr.sgi.com
Subject: Re: able to bootp/NFS-install/reboot R4400SC Indy
Date: Tue, 16 Feb 1999 22:43:57 -0800	[thread overview]
Message-ID: <36CA652D.5A165E86@rigelfore.com> (raw)
In-Reply-To: 199902170627.WAA09135@kilimanjaro.engr.sgi.com

drats... that's the kernel (er, one of the kernels) that hangs on
"freeing unused kernel memory" for me :(

-E

> So, I've had an old Indy in my office, waiting for me to try installing
> Linux on in my spare time, and today I finally got around to it. Lucky
> for me I didn't try before today, because the kernel that finally worked
> was the very latest, vmlinux-indy-990212.
> 
> After the one in the big hardhat tar.gz file didn't work (no R4400SC
> support) I hit the mailing list archive, found the pointer to
> vmlinux-2.1.131 (which didn't work because it didn't have NFS), noticed
> also vmlinux-sc-indy-2.1.116 (also didn't work, probably also no NFS),
> and tried a couple of others while going through the archive.
> vmlinux-indy-990205 got a little farther, but complained it couldn't
> make a device node in the ram disk or some such thing.
> 
> Anyway, vmlinux-indy-990212 was the winner: it booted up into the
> installer, I was able to do a complete install (ignoring swap, as web
> page says), and it's up and running. I'm sending this out to let those
> who've been having trouble with Indy/R4400SC know that it can be done
> now!

  reply	other threads:[~1999-02-17  6:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-17  6:27 able to bootp/NFS-install/reboot R4400SC Indy Joan Eslinger
1999-02-17  6:43 ` Eric Melville [this message]
1999-02-17  7:08 ` Alex deVries
1999-02-17  7:14   ` Joan Eslinger
1999-02-18  6:54     ` Eric Melville
1999-02-20  0:52       ` Thomas Bogendoerfer
1999-02-20 10:08         ` Eric Melville
     [not found]       ` <9902181451.ZM96@chaos.boston.sgi.com>
1999-02-20 10:04         ` Eric Melville
1999-02-22 18:14   ` Chad Carlin
1999-02-22 22:56     ` Eric Melville
1999-02-23  2:23       ` Mark A. Zottola
     [not found]     ` <19990223000909.B502@uni-koblenz.de>
1999-02-23  1:28       ` Chad Carlin
1999-02-23  5:20 ` Chad Carlin
1999-02-23  6:21   ` Alex deVries
1999-02-23 15:51     ` Chad Carlin

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=36CA652D.5A165E86@rigelfore.com \
    --to=m_thrope@rigelfore.com \
    --cc=linux@cthulhu.engr.sgi.com \
    /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.