7i76e No 7i76e Board found

See if this helps (or maybe confuses things twice as much):

forum.linuxcnc.org/9-installing-linuxcnc...-for-dummies-like-me

I had trouble getting going with this too. I haven't used linux daily for years, but some things are beginning to come back to me. Some things have improved since then too.

PCW wrote:

If you are starting from scratch, I would use the stretch test ISO:

www.linuxcnc.org/testing-stretch-rtpreem...uspace-amd64-r10.iso

Ok I have this installed and edited the interfaces file without errors.
does this look right?

still having problems W2 is down W3 is up

If eth0 is the name of the interface you want to use.

The only reason I say that is unless you have made changes to the way the kernel names the network interfaces generally ethX (ie eth0) is not used.
Lists your interface names, if eth0 is listed all good, if not eth0 will not work in the above.

Ignore this post....I couldn't read.

some how I feel more lost and confused than before. so far I redid everything from scratch with linuxcnc-stretch-uspace-amd64-r10.iso suggested by PCW. Tried to make sense of hm2_eth manual linuxcnc.org/docs/html/man/man9/hm2_eth.9.html ?right link? and modified the interfaces file with a combination or advice about ip10.10.10.10 and got stopped at adding linuxcnc keyring with an error in previous post at this point I feel like I'm way off the correct path of a known working build, configuration, installation.

Ok let us see if we can sort this out.

NIC = Network Interface Card, either built into the motherboard or a PCI or PCIe card.

On my setup I have 1 network card built into the Motherboard and have added another PCIe card.
Let us refer to them thusly:
Motherboard NIC: we shall call lan0, as this connects to the local-network and to the internet via a router.....the normal way things are done
PCIe NIC: we shall call mesa0 as this connects only to my mesa card, 7i92 in my case, but the theory is mostly the same.

My home network uses 192.168.1.xxx addresses and this is what NIC lan0 connects to and we shall give this an address of 192.168.1.217 (as this is what it got via dhcp)

I'm using my mesa card as it came, I haven't touched any jumpers so it has the network address of 10.10.10.10, therefore the NIC mesa0 will have the address 10.10.10.1 (as this interface is static)

I chose this method as it was easier than changing settings if I only had one NIC.

So my /etc/network/interfaces file would be as such:
auto lan0
iface lan0 inet dhcp

auto mesa0
iface mes0 inet static
address 10.10.10.1
netmask 255.255.255.0

I'll leave this post here in case you have any questions.

I put a picture up of my interface and asked if it was right because that is essentially what I was trying to setup. except I am only using the on-board Ethernet port. here it is again.
and then I did command "ip a" to ask if that looked correct there that is again

but the board is still not seen.

But the interface is not called eth0, the interface is called enp2s0, that is the name you have to use.


auto enp2s0
iface enp2s0 inet static
address 10.10.10.1
netmask 255.255.255.0


If your mesa board is 192.168.1.121, your address must be 192.168.1.xxx

If your mesa board is 10.10.10.10, your address must be 10.10.10.xxx

When you change the /etc/network/interfaces file please reboot for the changes to take affect. Make sure too that there is NO HUB between the mesa card and your NIC. Just one cable. I use a patch cable, no need to dig out a crossover cable.
Once the networking side is good we can go further on.

If you do not have an interface named eth0 do not use that name in the interfaces file.

The mesaflash command looks odd, try this as mentioned before.

Your so awesome man that was it.