Ethernet 10M only [solved]

The problem is in the title - my Pi will only connect at 10M to the ethernet switch - all other devices connect at 100M or 1000M as expected. I cannot find a way to force the network link speed on Arch. Not a big issue for me but one I would like to fix if possible. Any suggestions...

[mahjongg]

Try another distro (debian) to see it is software (distro) related.

Ok - good suggestion. Does the Debian startup without a keyboard and with SSH access enabled? I"m using the Arch distro headless and with no keyboard or mouse.
I"ll try it and see.

Ok - problem solved I think...

Its the same on Debian 6 so hardware issue.

Re-label orange 10M led to 100M

Is this right?

[mahjongg]

Well, maybe you have discovered something, I was thinking you could detect the connection speed somehow, but if you are only looking at the LED then yes, it being on probably means 100M, the schematic (sheet 3 G8) describes D9 as "yellow", and is labeled "100M", not 10M.

it might also be possible to program the chip to either go on or off for 100M, so it might be a software issue.

A reading of the datasheet of the LAN9512 chip might clarify this.

Maybe you should open a new thread about this issue.

For what it's worth, my 100M network has the Pi with it's 10M light on and I've used Debian & Arch on it thus far.

[dom]

@KevimM Can you check the dmesg log? I get:

smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1

Do you?

Also can you run iperf or similar to see what the actual speed is?

[jamesh]

Just out of interest I ran iperf betwen the Raspi and my Ubuntu box, and got these figures as something for people to compare against.

Client connecting to 192.168.1.13, TCP port 5001

TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 192.168.1.6 port 56756 connected with 192.168.1.13 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  91.0 MBytes  76.3 Mbits/sec

[dom]

My numbers (connecting to windows 7 machine)

pi@raspberrypi:~$ iperf -i2 -c 192.168.4.9

------------------------------------------------------------

Client connecting to 192.168.4.9, TCP port 5001

TCP window size: 16.0 KByte (default)

------------------------------------------------------------

[ 3] local 192.168.4.40 port 36334 connected with 192.168.4.9 port 5001

[ ID] Interval Transfer Bandwidth

[ 3] 0.0- 2.0 sec 21.5 MBytes 90.3 Mbits/sec

[ 3] 2.0- 4.0 sec 21.6 MBytes 90.4 Mbits/sec

[ 3] 4.0- 6.0 sec 21.6 MBytes 90.4 Mbits/sec

[ 3] 6.0- 8.0 sec 21.5 MBytes 90.2 Mbits/sec

[ 3] 8.0-10.0 sec 21.3 MBytes 89.5 Mbits/sec

[ 3] 0.0-10.0 sec 108 MBytes 90.2 Mbits/sec

I'm sure I read an interview with one of the hardware designers. He said that the 10/100 LED was labelled incorrectly but it was too late to change it.

Maybe I imagined it.

If you want to know what your RPi thinks of the network speed, try the following command

cat /var/log/messages | grep duplex

You should see the report of the ethernet speed.

@dom

p.s. this is Arch

The dmesg log only has these lines for the smsc95:

smsc95xx v1.0.4
smsc95xx 1-1.1:1.0: eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:85:2c:9f

Here is iPerf result - just confirms the led is labelled wrong... (it is

[root@alarmpi /]# iperf -c 192.168.1.9
------------------------------------------------------------
Client connecting to 192.168.1.9, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 192.168.1.97 port 57838 connected with 192.168.1.9 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec   112 MBytes  94.1 Mbits/sec
[root@alarmpi /]# 

Looks like its simply the ident on the PCB.

[mahjongg]

from the LAN9512 datasheet:

This pin is driven low (LED on) when the Ethernet

operating speed is 100Mbs, or during autonegotiation.

This pin is driven high during 10Mbs

operation, or during line isolation.

The pin also can act as a GPIO (under complete software control, as are the other two LED's) but its very unlikely that that is happening, so yes, the LED is ON during 100Mbps operation!

Perhaps this should be documented somewhere.

I added it to the "Troubleshooting" part of the wiki, but maybe it should be somewhere else as well (?)

http://elinux.org/R-Pi_Trouble.....ad_of_100M

Pretty impressed by the performance over USB actually, it's better than I'd expect.

Don't look in dmesg output for interface state. cat /sys/class/net/eth0/speed will give you current state.

jbeale said:

I added it to the "Troubleshooting" part of the wiki, but maybe it should be somewhere else as well (?)

http://elinux.org/R-Pi_Trouble.....ad_of_100M

It is also documented in the schematics errata.  Apparently it is due to space constraints on the silkscreen.

http://elinux.org/RPi_schemati.....fied_typos

Not that it matters much, perhaps but my 100 Mbps home network shows only 62 Mb/s, not the 90+ that others are reporting, is it something about my Pi, or my network? This is going from the Pi to a quad-core 2.5 GHz machine running WinXP.

Code: Select all

pi@raspberrypi:~$ iperf -c 192.168.10.104
------------------------------------------------------------
Client connecting to 192.168.10.104, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 192.168.10.113 port 40662 connected with 192.168.10.104 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  75.0 MBytes  62.9 Mbits/sec
pi@raspberrypi:~$ uname -a
Linux raspberrypi 3.1.9+ #138 PREEMPT Tue Jun 26 16:27:52 BST 2012 armv6l GNU/Linux

As a followup, my WinXP laptop does achieve about 90 Mbps going to the same desktop over the same network cable, although I see the TCP window size here is 63k instead of 16k.

Code: Select all

C:\Documents and Settings\John\My Documents\Downloads>iperf -c 192.168.10.104
------------------------------------------------------------
Client connecting to 192.168.10.104, TCP port 5001
TCP window size: 63.0 KByte (default)
------------------------------------------------------------
[1900] local 192.168.10.102 port 1225 connected with 192.168.10.104 port 5001
[ ID] Interval       Transfer     Bandwidth
[1900]  0.0-10.0 sec   107 MBytes  89.8 Mbits/sec