lkml.org 
[lkml]   [2000]   [Oct]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.2.x NFS service causing routing/networking failures?
The card is a DLink DFE 530TX:

via-rhine.c:v1.01 2/27/99 Written by Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/via-rhine.html
eth0: VIA VT3043 Rhine at 0xe000, 00:50:ba:a5:5f:e6, IRQ 5.
eth0: MII PHY found at address 8, status 0x782d advertising 05e1 Link 40a1.
PCI latency timer (CFLT) is unreasonably low at 32. Setting to 64 clocks.

I see there is a newer version (1.08) although the 2.2.16 source
RPM includes the version above. Is the newer one worth trying?

I had no difficulties copying 6-7GB of data ON to the machine
via NFS but "playing" the data from another machine with xmms
seemingly caused me problems both times. I've never seen this
behavior before or anything like it on this machine (which has
always been very docile and stable).

-joseph

On 5 Oct, David Woodhouse wrote:
>
> joseph@5sigma.com said:
>> Okay, twice this evening I've seen my 2.2.16-kernel based i586 (K6-2)
>> machine become ignorant of the utility of eth0. Both times I'd been
>> playing mp3 audio on another linux box from an NFS volume served by
>> the machine that went nuts.
>
> Let me guess - eth0 is a tulip card? Try a different driver. There are
> three in the kernel sources - de4x5, tulip and old_tulip.
>
> You're probably using 'tulip'. Switch to 'old_tulip'.
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:39    [W:0.055 / U:15.164 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site