D-Link DFE530TX Rev. C Problems

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi..

Just started to set up my Linux Server built upon Slackware 8.1 I have recompiled the kernel which is 2.4.20 and everything worked fine.. Until I decided that my 10Mbit 3Com 3c509 ISA NIC was a little slow, Have a 100Mbit Switch D-Link Des1008. So I went out and Bought my self a DFE530TX Rev.C and thaught it was like 1-2-3 to install it.. Checked out www.scyld.com for the Via-Rhine drivers. Built that and loaded it to the kernel, no errors or anything, Brought it up and made a ping to my other computer... Worked great, Looked at the Switch and it Said 100Mbit FullDuplex, Great.

But now the problems came I could use lynx to head out on the WWW worked really great, but when I decided to start the server stuff again the NIC went crazy.. It send and received some KB but after one sec or so it begun to blink constantly but it was only one LED blinking on the Switch... The server went really slow and kept filling my Syslog with thease kind of messages:

Jan 13 18:32:41 tux kernel: eth0: MII status changed: Auus changed: Autonegotiation advertising 05e1  partner 45e1.
Jan 13 18:32:41 tux kernel: eth0: MII status changed: Autonegotiation advertising 05e1  partner 45e1.
Jan 13 18:32:41 tux last message repeated 51 times

So I check out my Dlink CD where there was some Linux drivers, compiled these and got it to work, was called rhinefet. But here comes my really annoying problem, It is so dam slow! 
When I create 25MB file with some simple C++ code it takes me about 8 sec, Not so fast computer
When I download that file with Samba it takes me about 10sec, Enough 
When I send that file back it takes over 3 mins, never get over 3mbit/s
Tested download the file trough HTTP, took me about 7 sec, Great...
Just had to test it trought FTP also to make sure that it wasn't samba
Upload to the server 0.1mbit/s
Download 1.5mbit/s

That is how I figured out that it was some wrong with my NIC, Its not the Hardware because it worked great in Win98 about 35mbit/s both ways...

Some more output here from mii-diag from scyld.com

Using the default interface 'eth0'.
Basic registers of MII PHY #1:  3100 786d 0101 8f44 05e1 45e1 0005 2801.
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner advertised 45e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT, w/ 802.3X flow control.
   End of basic transceiver information.

And here from via-diag also from scyld.com
root@tux:~# ./a.out  -a
via-diag.c:v2.08 12/17/2002 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a VIA VT6105 Rhine-III (type 3106) adapter at 0xd000.
 Station address 00:05:5d:68:d8:3e.
 Tx enabled, Rx enabled, full-duplex (0x0c1a).
  Receive  mode is 0x0c: Normal unicast and hashed multicast.
  Transmit mode is 0x80: Normal transmit, transmitter set to store-and-forward.
VIA VT6105 Rhine-III (type 3106) chip registers at 0xd000
 0x000: 685d0500 800c3ed8 00000c1a 77ff0000 80000000 00000000 014c5220 014c5c00
 0x020: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 80000400
 0x040: 00000604 003e6810 014c5240 00000000 00e0809a 00000000 00b200b2 00000000
 0x060: 0177b85e 014c5c20 00000000 26002401 786d6180 08000080 80040003 00000000
 0x080: 001f0000 00080000 00000000 00000000 00000080 00000000 ffffbe40 00000000
 0x0A0: f0041000 f0041000 00000000 00000000 ffffffff ffffffff ffffffff ffffffff
 0x0C0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
 0x0E0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
 No interrupt sources are pending (0000).

And here is from lspci
00:0f.0 Ethernet controller: VIA Technologies, Inc.: Unknown device 3106 (rev 86)

Any ideas to get this thing to work better or should I just trough that NIC out thought  the Window(s) or what?



-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux