From: "Art Haas" <ahaas@airmail.net>
To: sparclinux@vger.kernel.org
Subject: Re: Compiling sunlance as a module
Date: Wed, 31 Mar 2004 01:42:16 +0000 [thread overview]
Message-ID: <20040331014216.GC6522@artsapartment.org> (raw)
In-Reply-To: <20040330234412.GB5439@artsapartment.org>
On Tue, Mar 30, 2004 at 05:21:08PM -0700, Jason Wever wrote:
> On Tue, 30 Mar 2004 18:09:24 -0600
> "Art Haas" <ahaas@airmail.net> wrote:
>
> > My main computer is an old Pentium computer, and I have an ethernet card
> > using the 8139too driver, and this machine doesn't have any problem
> > loading the module, and I haven't (knowingly) done anything special to
> > load it prior to the machine bringing up the eth0 interface. It would
> > not be surprising if my problem is a configuration error, but when I
> > compare my sparc-configuration to the i386-configuration, things look
> > similiar in the networking type areas.
>
> Are you running hotplug on the i386 box? That can result in the module
> being auto-loaded as well as any other automatic hardware detection
> software.
The machine is configured for hotplug; as I was curious to fiddle around
with the 'udev' stuff in development. I'm still using a static '/dev'
directory, though.
> If the kernel is auto-loading the module without outside assistance, I'd
> be interested to know how that works.
I'm certain that my ethernet driver was being successfully loaded as a
module long before I'd begun to configure the kernel with hotplug
capabilities. I should add a few 'lsmod' statements here and there in
the initscripts and see if I can find just where and when this module is
getting loaded.
Art Haas
--
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.
-Thomas Jefferson to James Smith, 1822
next prev parent reply other threads:[~2004-03-31 1:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 23:44 Compiling sunlance as a module Art Haas
2004-03-31 0:00 ` Jason Wever
2004-03-31 0:09 ` Art Haas
2004-03-31 0:21 ` Jason Wever
2004-03-31 0:25 ` C.Newport
2004-03-31 0:38 ` Ciaran McCreesh
2004-03-31 1:38 ` Art Haas
2004-03-31 1:42 ` Art Haas [this message]
2004-03-31 1:51 ` Pete Zaitcev
2004-03-31 2:40 ` Keith M Wesolowski
2004-03-31 3:30 ` Art Haas
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=20040331014216.GC6522@artsapartment.org \
--to=ahaas@airmail.net \
--cc=sparclinux@vger.kernel.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 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.