Update from 2.7.0 to 2.7.6

I do run . ./scripts/rip-environment and start Linuxcnc by directing it to my .ini file so it runs in place.

Right now I have v2.7.0 and 2.7.6 and 2.8.0~pre1. All are installed as run in place. Unfortunately V2.7.6 and master 2.8.0~pre1 will not run due to my mesa 7I80 board not being registered even though its internal configurations seems to be read properly as shown in the attached file. The attached file has some debug lines included. When I use the same .ini and .hal file in V2.7.0 it registers the 7i80 board properly. I don't know what these updated versions are expecting to receive from the mesa 7I80 board to allow it to be registered.

My .ini file has:
[HOSTMOT2]
DRIVER=hm2_eth board_ip="10.10.10.2"
#Hardware Address="00:60:1b:11:80:23"
BOARD=7i80
CONFIG="num_encoders=6 num_stepgens=5 sserial_port_0=20xxxxxx"

My .hal file has:
loadrt hostmot2 debug_idrom=1 debug_module_descriptors=1 debug_pin_descriptors=1 debug_modules=1
#loadrt hostmot2
loadrt [HOSTMOT2](DRIVER) config=[HOSTMOT2](CONFIG)

The debug text file the attached file mentions at the end contains:
6966
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components

Log file is attached.

I would try updating your 7I80 firmware, The latest versions of LinuxCNC (2.7.6 and master) require V15 or better
Ethernet firmware to support their packet error checking

Andy, yes I use the./configure --with-realtime=uspace cmd.

PCW, I will try to find the V15 Ethernet firmware and re-flash the 7I80 if required to try to solve my issue.

Unless its a obscure configuration, you should not need to "find" it, its in the 7i80.zip file at Mesa

As per your suggestion I verified that the 7I80 card was flashed with firmware v.14 making it ot compatible with v2.7.6 and v2.8 of linuxcnc. I upgraded the etherhm2 firmware to v.15, re-generated my bit file and re-flashed the 7I80 card. The card now registers in both upgraded version on linuxcnc. Im using linuxcnc v2.8 right now and Gmocappy 5 axis is loading properly. I just have to verify all is working properly due to the changes required in the .ini and .hal files to remove some error messages that were generated while loading the files.