From: Chad Carlin <chad@dallas.sgi.com>
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: linux <linux@cthulhu.engr.sgi.com>
Subject: Re: able to bootp/NFS-install/reboot R4400SC Indy
Date: Tue, 23 Feb 1999 09:51:24 -0600 [thread overview]
Message-ID: <36D2CE7C.A863C235@dallas.sgi.com> (raw)
In-Reply-To: Pine.LNX.3.96.990223011941.1617A-100000@lager.engsoc.carleton.ca
Alex,
I get this error message in my syslog.
kernel: kmod: failed to exec /sbin/modprobe -s -k net-pf-N, errno = 2
/sbin/modprobe is not on my system. Why is it trying to execute? According to
rpm -qf /sbin/modprobe on my intel-Linux system, this executable gets installed
with modutils. I am jumping to a conclusion that this error message is telling
me why networking is not running properly. More specifically, I have tried
rlogin, telnet, ftp and nfs. All of these panic the system.
I grabbed
ftp://linus.linux.sgi.com/pub/linux/mips/hardhat/5.2/RPMS/mipseb/modutils-2.1.121-4.mipseb.rpm
and put that in with the other rpms in my installation nfs filesystem. It didn't
get picked up during my nfsroot install. I guess I need to look at some sort of
installation script to find where it get's it's list of packages to install.
Heck, I might be barking up the wrong tree after all.
Thanks,
Chad
Alex deVries wrote:
> On Mon, 22 Feb 1999, Chad Carlin wrote:
> > Ok. Somebody shoot me. I went through and reinstalled linux on my Indy. I
> > thought that I screwed up and somehow did not get modutils-x.x.x-x because
> > I chose to install the wrong package set. I think I was wrong there too.
> >
> > Problem:
> > - modutils-x.x.x-x does not get installed by the base installer. (or I
> > don't know which one it goes with)
>
> Yup. modutils was broken at the time when Rough Cuts was put together.
> Theres a newer package that does work on the ftp site.
>
> > - Can't get this package over the network because if I try to use my
> > network interface, the system panics. It panics because I don't have
> > modutils.
>
> Why do you need modules to get your network going?
>
> > - BTW howto-french-5.1.1 seems to be corrupted in the distribution. My indy
> > always hangs when trying to install it. Hence, I have to deselect
> > optional-documentation during install.
>
> We know that. :)
>
> - Alex
--
-----------------------------------------------------
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"
prev parent reply other threads:[~1999-02-23 15:56 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
1999-02-23 5:20 ` Chad Carlin
1999-02-23 6:21 ` Alex deVries
1999-02-23 15:51 ` Chad Carlin [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=36D2CE7C.A863C235@dallas.sgi.com \
--to=chad@dallas.sgi.com \
--cc=adevries@engsoc.carleton.ca \
--cc=chad@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox