From: Peter <heisspf@skyinet.net>
To: Ray Olszewski <ray@comarre.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Netconfig Fail
Date: Sun, 9 Oct 2005 09:33:19 +0800 [thread overview]
Message-ID: <20051009093319.584ebc9b.heisspf@skyinet.net> (raw)
In-Reply-To: <4347ED53.50105@comarre.com>
On Sat, 08 Oct 2005 09:01:23 -0700
Ray Olszewski <ray@comarre.com> wrote:
> Peter -- The new NIC is not a standard tulip NIC. It is a Davicom NIC
> (see Slack's dmesg output) and needs the dmfe module, not the tulip
> module. (Yes, I know Slackware *thinks* it needs the tulip module;
> Slackware is wrong. Or perhaps you are, if you added it by hand.)
No slackware added it.
> Both Fedora and DSL get it right. Look in the lsmod output from the 2
> distros that work and you will see that dmfe is present but not tulip.
> Also review the dmesg output you sent us.
>
> Finally ... Peter, once you sent all this stuff, it took me less than a
> minute to spot the problem. I mention this because so often I ask (you
> and others) for a complete problem description, not a fragmentary one.
> It can make a real difference in ease and speed of troubleshooting.
>
It seems it needs always someone like you to help to put on the right shoes.
Yes, I saw it myself as well when I had all the sent outputs that I need the dmfe module. When I tried to install it I got an error message. Did not catch it. Have to go over to slackware gain and will let you know.
Thanks & regards
--
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2005-10-09 1:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-08 18:33 Netconfig Fail Peter
2005-10-08 16:01 ` Ray Olszewski
2005-10-09 1:33 ` Peter [this message]
2005-10-09 7:04 ` Peter
2005-10-09 15:29 ` Peter
2005-10-09 18:00 ` chuck gelm
-- strict thread matches above, loose matches on Subject: below --
2005-10-09 7:08 Peter
2005-10-06 13:15 Peter
2005-10-06 7:33 ` Ray Olszewski
2005-10-07 16:23 ` Peter
2005-10-07 5:49 ` Ray Olszewski
2005-10-07 11:20 ` chuck gelm
2005-10-07 17:23 ` Ray Olszewski
2005-10-08 15:43 ` Peter
2005-10-08 15:22 ` Peter
2005-10-07 11:36 ` chuck gelm
2005-10-08 15:39 ` Peter
2005-10-08 4:18 ` Ray Olszewski
[not found] ` <200510052204.15272.david@fierbaugh.org>
2005-10-06 14:54 ` Peter
2005-10-06 12:53 ` David Fierbaugh
2005-10-06 18:52 ` chuck gelm
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=20051009093319.584ebc9b.heisspf@skyinet.net \
--to=heisspf@skyinet.net \
--cc=linux-newbie@vger.kernel.org \
--cc=ray@comarre.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