Can't get Mesa 7i92 to connect without a hub.

OK GUI pops right up if I run through a hub. (Which I want to get rid of).

NOTE: a regular cable gets me no where.

Made a crossover cable.
Purchased an adapter to change a patch cable to crossover.
Purchased a cat 6 shielded crossover cable.

Spend most of the day trying all sorts of network configurations with no improvement. Is my card bad or what?

All three of these give me this... Find the card and MAC but error out.


RUN_IN_PLACE=yes
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/home/superman/linuxcnc-dev/bin
LINUXCNC_TCL_DIR=/home/superman/linuxcnc-dev/tcl
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/home/superman/linuxcnc-dev/rtlib
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/home/superman/linuxcnc-dev/src/objects
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.8.0~pre1
Machine configuration directory is '/home/superman/linuxcnc/configs/esab'
Machine configuration file is 'esab.ini'
INIFILE=/home/superman/linuxcnc/configs/esab/esab.ini
VERSION=1.0
PARAMETER_FILE=linuxcnc.var
TASK=milltask
HALUI=halui
DISPLAY=axis
COORDINATES=X Y Z
KINEMATICS=trivkins
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
Found file(REL): ./esab.hal
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
Killing task linuxcncsvr, PID=2050
hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: 10.100.100.121: Hardware address: 00:60:1b:13:00:9d
hm2_eth: discovered 7I92
hm2/hm2_7i92.0: Smart Serial Firmware Version 43
Board hm2_7i92.0.7i77.0.0 Hardware Mode 0 = standard
Board hm2_7i92.0.7i77.0.0 Software Mode 0 = input_output
Board hm2_7i92.0.7i77.0.0 Software Mode 1 = io_analog
Board hm2_7i92.0.7i77.0.0 Software Mode 2 = io_analog_fieldvoltage
Board hm2_7i92.0.7i77.0.0 Software Mode 3 = io_encoder_analog_fieldvoltage
Board hm2_7i92.0.7i77.0.1 Hardware Mode 0 = standard
Board hm2_7i92.0.7i77.0.1 Software Mode 0 = analogout_enables
board fails HM2 registration
hm2: unloading
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
Waiting for component 'hm2_eth' to become ready...........................hm2_eth: rtapi_app_main: Resource temporarily unavailable (-11)
./esab.hal:9: waitpid failed /home/superman/linuxcnc-dev/bin/rtapi_app hm2_eth

./esab.hal:9: /home/superman/linuxcnc-dev/bin/rtapi_app exited without becoming ready
./esab.hal:9: insmod for hm2_eth failed, returned -1
2050
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

Can you ping the card with a straight through cable?
What firmware are you using?

Now I can ping with a patch cable.... Didn't think that worked before.

When I boot the GUI same result.

7i92._7i77_7i76D.bit

what result?

Same as I posted above. Discovers, and gets MAC address but errors out and doesn't load.

Put on a hub pops right up.

These ports are 100MB Full?

Not sure whats going on, sounds like dropped packets, maybe something marginal on either the 7I92 or the host.

What is the host PC and host MAC?

Does ping ever drop packets?

Away from the screen now so can't get MAC. .120 ending IP

The little host unit is XCY 1900 with 4 Intel gigabit ports. These are used world wide with pfSence on them for professional high speed routers. So have trouble believing it is the problem. Only using one port at a time and tried them all.

I don't actually like that the only network change you make on Mesa is the IP number.

Never drops a packet.

I didn't mean the Hosts MAC address but rather the type

SInce these are Intel MACS, did you turn IRQ coalescing off?
(it plays havoc with real time)

What OS are you using? (uname -a)

Is it unusual for this to happen prior to loading the hm2 modules ?

Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
Killing task linuxcncsvr, PID=2050

Also can you post your hal/ini files? there's something odd about the messages as ozzyrob noticed