Schaublin 125-CNC retrofit.

Cool, the mini PC showed up, so I have installed 2.8.2 Buster Preempt
I am on a network cable which was auto connected during the install process. I'm trying to do the instruction here:
forum.linuxcnc.org/27-driver-boards/3559...ethernet-mesa-boards

Installed network-manager okay. But deinstalling WICD failed.

schaublin@Schaublin:~$ sudo apt-get remove wicd wicd-gtk
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package 'wicd' is not installed, so not removed
Package 'wicd-gtk' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 54 not upgraded.
I am wondering whether it is a good idea to change the network manager while connected over a wired network? Feel like sawing off the tree branch you are sitting on.

The instructions continue with:
====Network setup for mesa cards: ======
- left click on the network manager on the bottom right side or upper right side where the clock and volume is.
- choose "edit connections"
I have a clock icon top RH, but no volume or network manager buttons. I cant find the network manager in any menu either. Not sure whether this was a good idea, as I will not have WiFi on this machine anyway?

ip a returns:


schaublin@Schaublin:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether ec:8e:b5:71:16:f0 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.33/24 brd 10.0.0.255 scope global dynamic noprefixroute eno1
       valid_lft 85080sec preferred_lft 85080sec
    inet6 2001:871:25f:536:9a9:edaa:a5b2:821c/64 scope global temporary dynamic
       valid_lft 10589sec preferred_lft 5189sec
    inet6 2001:871:25f:536:ee8e:b5ff:fe71:16f0/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 10589sec preferred_lft 5189sec
    inet6 fe80::ee8e:b5ff:fe71:16f0/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

I need to have the local ethernet port mounted at eno0 for the automatic connection with the mesa 7i92 to work right?
Mark

help.ubuntu.com/community/WICD
Near the end is how to remove it and install network manager.
It is required to log out and back in for the network manager to change over, so it will cut the branch. !
And all my PC use wifi while the machines are working, just follow that tut.

Thanks Tommy. I got some help from my Linux guru, so now it is time to disconnect the mini pc and go and try it in the basement. Unfortunately it does not have a wifi adapter.

Now when I ping 192.168.1.121, I get one line with
ping 192.168.1.121 (192.168.1.121) 54 (86) bytes of data
 and then continuous lines of
from 10.10.10.11 icmp_seq=[line number] destintion host unreachable.

Pinging 10.10.10.10 returns the same behavior.

I have no network admin experience. Any help appreciated.
Mark

Got it. Needed to jumper for 10.10.10.10. Now it works.

When you do show pins, is there are suffix to make the list break into columns, or dump to a file, as you cant read them all in the terminal?
From Peters post...
forum.linuxcnc.org/38-general-linuxcnc-q...-7i85s?start=0#68002

You probably want this firmware:
7i92_7i85sx2D.bit
which you fetch from mesa and install with mesaflash

sudo apt-get install mesaflash

mesaflash --device 7i92 --write 7i92_7i85sx2D.bit (write the 7I92 flash memory with 7I85S firmware)
mesaflash --device 7i92 --reload (load the FPGA with the new firmware)
mesaflash --device 7i92 --readhmid (read out the current pinout/modules)
(I think mesaflash will use the default 192.168.1.121 IP address if not specified,
if not or if you changed the 7I92s IP address, you need to add the address to the mesaflash command line)


What is the correct syntax for adding the ip address? I tried:
mesaflash --device 7i92 --write 7i92_7i85sx2D.bit 10.10.10.10
mesaflash --device 7i92 --write 7i92_7i85sx2D.bit ip=10.10.10.10
...looked up mesaflash --help
mesaflash --device 7i92 --write 7i92_7i85sx2D.bit --addr 10.10.10.10
mesaflash --device 7i92 --write 7i92_7i85sx2D.bit --addr <10.10.10.10>
but keep getting "no 7i92 board found?
Mark

 mesaflash --device 7i92 --addr 10.10.10.10 --write 7i92_7i85sx2D.bit