| To: | Tres Hofmeister <tres@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [vortex, eepro100] True on TRANSMIT ERROR TIMEOUT |
| From: | Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxx> |
| Date: | Thu, 15 Jun 2000 18:40:22 -0400 |
| Cc: | netdev <netdev@xxxxxxxxxxx> |
| Organization: | MandrakeSoft |
| References: | <39461BB3.299DD807@xxxxxxxxxx> <Pine.LNX.4.10.10006141420380.370-100000@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <39483426.B07E4BA@xxxxxxxxxx> <20000615161933.I30376@xxxxxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
Tres Hofmeister wrote:
> Indeed. I'm in the same boat as "Brian." I've tried everything
> I can think of to keep our web server up. In the end, it's looking like
> the answer is using watchdog(8) to monitor the Ethernet interface, with
> a repair script which reinitializes it when it fails. I've currently
> got a NetGear Tulip card in the machine, but I've had problems with
> the vortex and eepro100 drivers as well.
Problems with the Tulip driver nonwithstanding, the NetGear cards are
awful :/ They use an ancient chip design that should have never seen
the light of day in the first place. You're far better off finding a
better Tulip clone or a using a card w/ a real Tulip chip on it.
Jeff
--
Jeff Garzik |
Building 1024 | Free beer tomorrow.
MandrakeSoft, Inc. |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [vortex, eepro100] True on TRANSMIT ERROR TIMEOUT, Tres Hofmeister |
|---|---|
| Next by Date: | Re: [vortex, eepro100] True on TRANSMIT ERROR TIMEOUT, dancer |
| Previous by Thread: | Re: [vortex, eepro100] True on TRANSMIT ERROR TIMEOUT, Tres Hofmeister |
| Next by Thread: | Re: [vortex, eepro100] True on TRANSMIT ERROR TIMEOUT, dancer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |