From: Andrew <ald2@arrakis.es>
To: linux-newbie@vger.kernel.org
Subject: Re: ethernet nic install
Date: Wed, 04 Aug 2004 18:49:40 +0200 [thread overview]
Message-ID: <411113A4.9020800@arrakis.es> (raw)
In-Reply-To: <200408032120.37112.pa3gcu@zeelandnet.nl>
pa3gcu wrote:
>
> Firstly, you said "486"
Sorry. I was suffering from heatstroke. It's a very ancient pentium 60Mhz.
> Now secondly, why i ask are you using the 8139cp driver when your type of card
> needs the 8139too driver.?????
Good question. I'm not. I have only used the 8139too driver and can't
figure out why there is any reference at all to the 8139cp (I didn't
even know it existed and didn't notice it until after my first post).
>
> I would place into /etc/rc.d/rc.netdevice the following;
>
> /sbin/modprobe 8139too
So far I have loaded it manually, from /etc.rc.d/rc.modules and with
'netconfig', which detects the nic if I remove the other one (see below).
> Another thing here is that you state "eth1" is the interface concerned, that
> means its the second ethernet device in your system, do you have a working
> eth0 device and if so what is it and is it working.???
Yes, 3c509 isapnp and yes.
I shall have another go at the BIOS (It is the strangest I have ever
seen) and maybe come back to you.
Thanks, anyway,
Andrew
-
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:[~2004-08-04 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 10:30 ethernet nic install Andrew
2004-08-03 19:20 ` pa3gcu
2004-08-04 16:49 ` Andrew [this message]
2004-08-04 18:41 ` pa3gcu
2004-08-05 10:49 ` Andrew
-- strict thread matches above, loose matches on Subject: below --
2004-08-05 14:37 pa3gcu
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=411113A4.9020800@arrakis.es \
--to=ald2@arrakis.es \
--cc=linux-newbie@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox