From: "Steve Lee" <steve@tuxsoft.com>
To: "'Zwane Mwaikambo'" <zwane@linuxpower.ca>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: 2.6.4-rc1 problems with e100 & 3c59x
Date: Tue, 2 Mar 2004 08:05:32 -0600 [thread overview]
Message-ID: <008301c4005f$708fec70$e501a8c0@saturn> (raw)
In-Reply-To: <Pine.LNX.4.58.0403020258110.29087@montezuma.fsmlabs.com>
I am using /etc/modprobe.conf and I don't load any modules manually.
This is mostly a module kernel, the only problem I'm having is with the
network. 2.6.3 does work with the drivers compiled in (but not as
modules). 2.6.4-rc1 I can not get to work at all (modules or builtin).
Thanks for your suggestion.
Steve
-----Original Message-----
From: Zwane Mwaikambo [mailto:zwane@linuxpower.ca]
Sent: Tuesday, March 02, 2004 2:00 AM
To: Steve Lee
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.4-rc1 problems with e100 & 3c59x
On Mon, 1 Mar 2004, Steve Lee wrote:
> I've searched the archives as well as googled around without any luck
> regarding my situation. BTW, please CC me as I'm no longer subscribed
> (furthering my education has prevented me from keeping up with the
> list).
>
> Can anyone please give me some clue as to what might be wrong? My
> network is working fine with the drivers compiled in 2.6.3 (but not as
> modules). I can't get 2.6.4-rc1 to work at all with my network cards.
One thing to make sure is that you're using /etc/modprobe.conf and don't
load the modules manually.
Zwane
next prev parent reply other threads:[~2004-03-02 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 21:22 Steve Lee
2004-03-01 21:37 ` szonyi calin
2004-03-02 4:30 ` Jeff Garzik
2004-03-02 8:00 ` Zwane Mwaikambo
2004-03-02 14:05 ` Steve Lee [this message]
2004-03-02 20:04 ` Zwane Mwaikambo
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='008301c4005f$708fec70$e501a8c0@saturn' \
--to=steve@tuxsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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
all inboxes | Powered by JetHome®