Strange 7i76e problem when starting linuxcnc

Hi guys,

I'm building my own gantry cnc and want to use linuxcnc, i've ordered a mesa 7i76e card and wired it up. Used the pnfconfig to make a linuxcnc configuration for my machine. changed the ip in the hal file to 10.10.10.10 (jumper 3 up). Now when i want to start linuxcnc i get the error see attachment. i've also included some other information.
Now the strange thing is that i can ping to the mesa card and even managed to start linuxcnc but got another error (attachment). it seems that powering/dispowering my drives influences the starting of linuxcnc in some weird way.
And also, mesaflash doesn't recognize my card??

Anyone knows what im doing wrong? btw im not realy familiar in this "IT" stuff, more of a nuts and bolts guy but willing to learn ofcourse!

What does

mesaflash --device 7i76e --addr 10.10.10.10 --readhmid

report?

Also what does

ip a

report

wow quick reply, mesaflash --device 7i76e says: No 7i76e board found. Also just added some more attachments

mesaflash --device 7i76e says: No 7i76e board found

That's expected unless you use the entire command I showed

Your ping times are pretty terrible, It may be that you need to turn off IRQ
coalescing in the driver as mentioned in the hm2_eth man page

You could try the by hand first with:

sudo ethtool -C eth0 rx-usecs 0

and then retry pinging the card

I've tried to set it up as described in the sticky topic. But that didn't seem to fix it, is it right that that way should change the address of eth0 if I type ip a. Because it doesn't on my pc.

I've just changed 10.10.10.1 to 10.10.10.11 for eth0 which now is shown in ip a. That should be right?
Tomorrow I'll try to turn off IRQ.

Any thoughts on why sometimes linux does start and sometimes doesn't. More often than not. And is there some particular order of powering the pc, mesa card and the drivers?

The 7I76E needs to be powered before LinuxCNC starts, thats about it.
The error could be due to loss of packets because of some network setup error
(note the > 1 ms ping time, that's completely unusable)

Edit: here's the result of pinging a 7I76E here:

peter@pcw-HP-EliteDesk-800-G1-USDT:~/bitfiles$ ping 10.10.10.10
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.116 ms
64 bytes from 10.10.10.10: icmp_seq=2 ttl=64 time=0.119 ms
64 bytes from 10.10.10.10: icmp_seq=3 ttl=64 time=0.117 ms
64 bytes from 10.10.10.10: icmp_seq=4 ttl=64 time=0.118 ms
64 bytes from 10.10.10.10: icmp_seq=5 ttl=64 time=0.120 ms
64 bytes from 10.10.10.10: icmp_seq=6 ttl=64 time=0.118 ms
64 bytes from 10.10.10.10: icmp_seq=7 ttl=64 time=0.117 ms
64 bytes from 10.10.10.10: icmp_seq=8 ttl=64 time=0.120 ms
64 bytes from 10.10.10.10: icmp_seq=9 ttl=64 time=0.118 ms
64 bytes from 10.10.10.10: icmp_seq=10 ttl=64 time=0.119 ms
64 bytes from 10.10.10.10: icmp_seq=11 ttl=64 time=0.118 ms
64 bytes from 10.10.10.10: icmp_seq=12 ttl=64 time=0.119 ms
^C
--- 10.10.10.10 ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 11247ms
rtt min/avg/max/mdev = 0.116/0.118/0.120/0.007 ms