Debian uspace and 7i80

Hi Peter
Do you have a sample config that I could work from please.

I also noticed that there are no firmware files in the lib directory for the 7i80.

Hi Peter
I reprogrammed the ip of the 7i80 to 10.10.10.10. but the problem persists. In fact it is exactly the same error reported.

What does uname -a print?

300 usec is pretty bad for a ping time and probably indicates something is wrong

Also If your motherboard has a Intel MAC you probably need to add the ethtool utility
and run

sudo ethtool -C rx-usecs 0

to turn off receive interrupt coalescing

PCW wrote:

What does uname -a print?

300 usec is pretty bad for a ping time and probably indicates something is wrong

It prints : Linux Debian 3.2.0-4-rt-686-pae #1 SMP PREEMPT RT Dbian 3,2,65-1+deb7u2 i686 GNU/Linux

I just pinged again and it is under 100us most the time since I changed to the private ip number.

I would try two things, first turn off interrupt coalescing if you have a Intel MAC
then if that doest help, lower the thread rate, like I said 300 usec is probably
just too slow

Here's a 7I76E responding to a ping on a old Core Duo machine with a PCI 8139 NIC:

PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
64 bytes from 10.10.10.10: icmp_seq=1 ttl=64 time=0.121 ms
64 bytes from 10.10.10.10: icmp_seq=2 ttl=64 time=0.069 ms
64 bytes from 10.10.10.10: icmp_seq=3 ttl=64 time=0.069 ms
64 bytes from 10.10.10.10: icmp_seq=4 ttl=64 time=0.069 ms
64 bytes from 10.10.10.10: icmp_seq=5 ttl=64 time=0.071 ms
64 bytes from 10.10.10.10: icmp_seq=6 ttl=64 time=0.070 ms
64 bytes from 10.10.10.10: icmp_seq=7 ttl=64 time=0.070 ms
64 bytes from 10.10.10.10: icmp_seq=8 ttl=64 time=0.069 ms
64 bytes from 10.10.10.10: icmp_seq=9 ttl=64 time=0.070 ms
64 bytes from 10.10.10.10: icmp_seq=10 ttl=64 time=0.071 ms
64 bytes from 10.10.10.10: icmp_seq=11 ttl=64 time=0.071 ms
64 bytes from 10.10.10.10: icmp_seq=12 ttl=64 time=0.070 ms
64 bytes from 10.10.10.10: icmp_seq=13 ttl=64 time=0.069 ms

The ping rate came down to under 100usec since I used the private ip.
My ISP connection just went down so I cannot get the ethtool utility at the moment. I will try in the morning again and let you know.

I am running a USB Ethernet adapter alongside the eth0 interface now without problems. The onboard (Intel) NIC serves the 7i80 on the 10.10.10.10 ip.

PCW wrote:

Also If your motherboard has a Intel MAC you probably need to add the ethtool utility
and run

sudo ethtool -C rx-usecs 0

to turn off receive interrupt coalescing

Is this the complete command. I tried to run it any all sorts of ways but it keeps giving me "bad command line arguments"

It seems that you need to run the tool as root. It sets the parameter but when I reboot it is lost again.
Anyway, the setting did not change anything as I still have the same problem.

What are your ping times now?

D2700's are typically very slow (about the same as the old Atom D525s)
you may need to restrict the number of modules enabled in the config line