From: Chad Carlin <chad@dallas.sgi.com>
To: ralf@uni-koblenz.de, linux <linux@cthulhu.engr.sgi.com>
Subject: Re: able to bootp/NFS-install/reboot R4400SC Indy
Date: Mon, 22 Feb 1999 19:28:04 -0600 [thread overview]
Message-ID: <36D20423.1B7513D1@dallas.sgi.com> (raw)
In-Reply-To: 19990223000909.B502@uni-koblenz.de
Ralf,
On closer observation......
The message in the syslog is as follows:
kernel: kmod: failed to exec /sbin/modprobe -s -k net-pf-N, errno = 2
ls -l /sbin/modprobe
.....No such file or directory
Obviously, I need modprobe. I wonder how I didn't get modprobe?
Other info:
uname -r = 2.1.131
cat /proc/cpuinfo
cpu: MIPS
cpu model: R4000SC V6.0
system type: SGI Indy
BogoMIPS: 99.94
........
Let me know if you want to see more.
ralf@uni-koblenz.de wrote:
> On Mon, Feb 22, 1999 at 12:14:22PM -0600, Chad Carlin wrote:
>
> > I got my 200MHz R4400 working too. Yes it actually boots. I guess you guys
> > weren't making all this stuff up after all.
> >
> > I have one problem though. Something is broken in modules. The networking
> > stuff is working incorrectly because of this. When I try to telnet in from
> > another host, the linux-indy panics. I can hand copy more verbose
> > information when I get home if this is not a common problem that everyone
> > else knows the answer to.
>
> I'd appreciate a more detailed bug report with all the messages you got.
> Which kernel binary exactly were you using?
>
> Ralf
--
-----------------------------------------------------
Chad Carlin Special Systems
Silicon Graphics Inc. 972.205.5911
Pager 888.754.1597 VMail 800.414.7994 X5344
chad@sgi.com http://reality.sgi.com/chad
-----------------------------------------------------
"flying through hyper space ain't like dusting crops, boy"
next prev parent reply other threads:[~1999-02-23 1:31 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
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 [this message]
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=36D20423.1B7513D1@dallas.sgi.com \
--to=chad@dallas.sgi.com \
--cc=chad@sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@uni-koblenz.de \
/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