From: Michael Buesch <mb@bu3sch.de>
To: "bastard operater" <bofh1234@hotmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: recommend a network card
Date: Sun, 18 Jun 2006 17:48:55 +0200 [thread overview]
Message-ID: <200606181748.55398.mb@bu3sch.de> (raw)
In-Reply-To: <BAY101-F198A641697A687C99F13FEC8810@phx.gbl>
On Sunday 18 June 2006 17:28, bastard operater wrote:
> >I never had a malfunctioning NIC. What does it look like?
> >Broken packages?
>
> It loses its network connection (the systems says the card is unplugged) for
> a second or two and then the connection comes back. Sometimes the
> connection just stops working and I have to restart the network service.
uh, oh. Interresting.
Sure it is not a software bug in PCI hotplug or something?
(or something accidentally poking with fakephp)
I would test the card in another machine, before throwing it away.
> > > I am in the market for a new NIC. The card has to work on Linux
> >(natively)
> > > and windows. I thought I would ask the experts if you have any
> > > recommendations for a good 100MB PCI card?
> >
> >I have mostly RTL based cards (ranging from 10 to 1000 mbit).
> >No problems so far. (But also no problem with my 3c905 since
> >quite some time ;) )
>
> How can I tell which cards use which chipset?
Look at the chip ;)
One of my cards (100mbit) has a chip with the string
RTL8139D
printed on it.
There's usually only one or two chips on the card. You can't miss it.
It's the chip, which is connected directly to the PCI pins.
btw: This is not really the right list to ask such questions,
as it is not development related, but well... :)
--
Greetings Michael.
next prev parent reply other threads:[~2006-06-18 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 21:12 recommend a network card bastard operater
2006-06-17 21:23 ` Michael Buesch
2006-06-18 15:28 ` bastard operater
2006-06-18 15:48 ` Michael Buesch [this message]
2006-06-18 16:13 ` Jason operater
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=200606181748.55398.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bofh1234@hotmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).