On Fri, 2010-07-30 at 19:22 -0400, Ciro Iriarte wrote:

2010/7/30 James Pifer <jep@obrien-pifer.com>:

...

Anyone know if SLES11SP1 has working gigabit drivers for a D-Link DGE-530T? I installed a couple Via network cards and I'm not able to achieve gigabit speeds, even though I have a gigabit link. Even connecting them directly I can only get 10/100 speed.

I tried compiling newer drivers for the Via cards but couldn't get them to compile.

Looking at a couple D-Link DGE-530T cards on ebay would like to know they work before purchasing.

Any help is appreciated.

Thanks, James

That card comes with a linux driver (sk98lin) from what I could find. With the Via cards, did you try forcing the speed with ethtool?, make sure that on the switch end you have the right port configuration.

If you're buying a new one, Intel gigabit cards always work.

Regards, CI.-

Thanks for the reply. ethtool looks like it already shows it at 1000. I'm trying to set it anyway but maybe my syntax is wrong? # ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: Not reported Advertised auto-negotiation: No Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: puag Wake-on: g Current message level: 0x00000002 (2) Link detected: yes # ethtool -s eth0 speed 1000 duplex full Cannot set new settings: Invalid argument not setting speed not setting duplex Thanks, James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, 2010-07-30 at 22:50 -0400, Ciro Iriarte wrote:

2010/7/30 James Pifer <jep@obrien-pifer.com>:

...

Thanks for the reply. ethtool looks like it already shows it at 1000. I'm trying to set it anyway but maybe my syntax is wrong?

# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: Not reported Advertised auto-negotiation: No Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: puag Wake-on: g Current message level: 0x00000002 (2) Link detected: yes

# ethtool -s eth0 speed 1000 duplex full Cannot set new settings: Invalid argument not setting speed not setting duplex

Thanks, James

Weird... Given that you already get 1Gbit/s connection without touching it, why did you state: "Even connecting them directly I can only get 10/100 speed."

Sorry I wasn't more clear. It says it's gigabit, but iperf shows much different results: # iperf -c 192.168.1.5 -f g ------------------------------------------------------------ Client connecting to 192.168.1.5, TCP port 5001 TCP window size: 0.00 GByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.6 port 58345 connected with 192.168.1.5 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 0.03 GBytes 0.02 Gbits/sec # iperf -c 192.168.1.5 ------------------------------------------------------------ Client connecting to 192.168.1.5, TCP port 5001 TCP window size: 16.0 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.6 port 52787 connected with 192.168.1.5 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 28.2 MBytes 23.6 Mbits/sec thanks, james -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sat, 2010-07-31 at 20:37 -0400, Ciro Iriarte wrote:

2010/7/31 James Pifer <jep@obrien-pifer.com>:

...

Sorry I wasn't more clear. It says it's gigabit, but iperf shows much different results:

# iperf -c 192.168.1.5 -f g ------------------------------------------------------------ Client connecting to 192.168.1.5, TCP port 5001 TCP window size: 0.00 GByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.6 port 58345 connected with 192.168.1.5 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 0.03 GBytes 0.02 Gbits/sec

# iperf -c 192.168.1.5 ------------------------------------------------------------ Client connecting to 192.168.1.5, TCP port 5001 TCP window size: 16.0 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.6 port 52787 connected with 192.168.1.5 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 28.2 MBytes 23.6 Mbits/sec

thanks, james

Weird.. Have to check it on one of my hosts... What about transferring with FTP/rsyncd and checking with iptraf?

It was definitely still very slow when I scp'ed a file and when trying to migrate a xen virtual machine between the two hosts. That's what lead me to iperf. Thanks, James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sat, 2010-07-31 at 23:24 -0400, Ciro Iriarte wrote:

2010/7/31 James Pifer <jep@obrien-pifer.com>:

...

It was definitely still very slow when I scp'ed a file and when trying to migrate a xen virtual machine between the two hosts. That's what lead me to iperf.

Thanks, James

You won't get proper performance with scp, ever!. Try with "rcp" or "rsh+dd" or "rsync with empty destination directory"

Regards,

-- Ciro Iriarte http://cyruspy.wordpress.com --

Getting an 80meg iso file from the same source: With ftp I see about 2.55 MB/s. With rsync I see 2.85 MB/s. On another PC hitting the same machine, getting the same file I see: With ftp: 42591.23 Kbytes/sec (not sure what that is in MB/s) With rsync: 15.77 MB/s with rsync ftp on the second machine was almost instantaneous. Thanks, James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Any relevant messages in logs?. Assuming we're talking about eth0

grep eth0 /var/log/messages

Some cards have issues when RX/TX offload is enabled. To check: ethtool -k eth0

To disable offload (taken from help):

ethtool -K|--offload DEVNAME Set protocol offload [ rx on|off ] [ tx on|off ] [ sg on|off ] [ tso on|off ] [ ufo on|off ] [ gso on|off ] [ lro on|off ]

If that doesn't work, the last thing to try is changing the kernel module for the published by Via at http://www.via.com.tw/en/support/drivers.jsp, I assume the needed file would be http://www.viaarena.com/Driver/velocity_linux_v1.41.zip.

The easier way out would be to get a Intel or Broadcom NIC.

Thanks for all the help. I was not able to set the offloads. rx/tx are set to on, but every time I try to change them it says it can't: # ethtool -k eth0 Offload parameters for eth0: rx-checksumming: on tx-checksumming: on scatter-gather: off tcp segmentation offload: off udp fragmentation offload: off generic segmentation offload: off large receive offload: off # ethtool --offload eth0 rx off Cannot set device rx csum settings: Operation not supported I did try that driver, but I'm not able to compile it on SLES11SP1. I posted to Via's forum but got no responses. I'd prefer that I use NICs that work instead of dealing with compiling anyway. I will have to try and get some NICs that work, possibly as you suggest Intel or Broadcom. Thanks, James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org