1. LinuxCNC
  3. General LinuxCNC Questions
  5. Mesa Ethernet only when WiFi disabled - why?

Mesa Ethernet only when WiFi disabled - why?

More
31 May 2020 19:15 #169549 by idea
Mesa Ethernet only when WiFi disabled - why? was created by idea
Hi,

Using linuxcnc from the debian 9 install.

I can connect to my 7i93 (MESA ethernet) controller when i disable Wi-Fi, and unable to startup linuxcnc when it is connected. The same behaviour occurs when using a laptop.

Does anyone know why this is happening and how I can make it so that both can be connected?

Thanks,
David

Please Log in or Create an account to join the conversation.

More
31 May 2020 19:33 #169556 by PCW
Replied by PCW on topic Mesa Ethernet only when WiFi disabled - why?
Did you setup the Ethernet as suggested in the hm2_eth manual page?

In general its best to use the 10.10.10.10 address for Mesa Ethernet cards
so they do not overlap with common NAT address ranges provided by your router

Please Log in or Create an account to join the conversation.

More
31 May 2020 19:50 #169561 by idea
Replied by idea on topic Mesa Ethernet only when WiFi disabled - why?
Yes the network is subnet1 at 192.168.20.x and the board is 192.168.1.121

Please Log in or Create an account to join the conversation.

More
31 May 2020 19:51 #169562 by idea
Replied by idea on topic Mesa Ethernet only when WiFi disabled - why?
It is not just with the WI-Fi disconnected from the network, for it to work the wireless interface needs to be disabled.

Please Log in or Create an account to join the conversation.

More
31 May 2020 19:51 #169563 by PCW
Replied by PCW on topic Mesa Ethernet only when WiFi disabled - why?
with WIFI enabled, what does

ip a

report?

Please Log in or Create an account to join the conversation.

More
31 May 2020 21:42 #169575 by idea
Replied by idea on topic Mesa Ethernet only when WiFi disabled - why?
Wifi disconnected - linux cnc connects
david@localhost:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:25:90:5b:17:12 brd ff:ff:ff:ff:ff:ff
    inet 169.254.4.13/16 brd 169.254.255.255 scope link eth0:avahi
       valid_lft forever preferred_lft forever
    inet6 fe80::225:90ff:fe5b:1712/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:25:90:5b:17:13 brd ff:ff:ff:ff:ff:ff
4: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:25:90:5b:17:14 brd ff:ff:ff:ff:ff:ff
5: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:25:90:5b:17:15 brd ff:ff:ff:ff:ff:ff
6: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether e8:de:27:1e:2b:5c brd ff:ff:ff:ff:ff:ff

wifi connected
david@localhost:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:25:90:5b:17:12 brd ff:ff:ff:ff:ff:ff
    inet 169.254.4.13/16 brd 169.254.255.255 scope link eth0:avahi
       valid_lft forever preferred_lft forever
    inet6 fe80::225:90ff:fe5b:1712/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:25:90:5b:17:13 brd ff:ff:ff:ff:ff:ff
4: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:25:90:5b:17:14 brd ff:ff:ff:ff:ff:ff
5: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:25:90:5b:17:15 brd ff:ff:ff:ff:ff:ff
6: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether e8:de:27:1e:2b:5c brd ff:ff:ff:ff:ff:ff
    inet 192.168.20.29/24 brd 192.168.20.255 scope global dynamic wlan0
       valid_lft 86390sec preferred_lft 86390sec
    inet6 fe80::d562:f436:a857:e9be/64 scope link 
       valid_lft forever preferred_lft forever

linux cnc error
Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.7.15
Machine configuration directory is '/home/david/linuxcnc/configs/7i93'
Machine configuration file is '7i93.ini'
INIFILE=/home/david/linuxcnc/configs/7i93/7i93.ini
PARAMETER_FILE=linuxcnc.var
TASK=milltask
HALUI=halui
DISPLAY=axis
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): ./7i93.hal
hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: ERROR: 192.168.1.121: Could not retrieve mac address
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
hm2: unloading
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
hm2_eth: rtapi_app_main: Resource temporarily unavailable (-11)
./7i93.hal:8: waitpid failed /usr/bin/rtapi_app hm2_eth
./7i93.hal:8: /usr/bin/rtapi_app exited without becoming ready
./7i93.hal:8: insmod for hm2_eth failed, returned -1
1726
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

Please Log in or Create an account to join the conversation.

More
31 May 2020 21:53 - 31 May 2020 21:53 #169576 by PCW
Replied by PCW on topic Mesa Ethernet only when WiFi disabled - why?
It looks like you have not setup eth0 with a static IP address.
This can be done either through the network manager or by editing
the etc/network/interfaces file as the hm2_eth manual page describes
Last edit: 31 May 2020 21:53 by PCW.
The following user(s) said Thank You: idea

Please Log in or Create an account to join the conversation.

More
01 Jun 2020 20:53 #169713 by idea
Replied by idea on topic Mesa Ethernet only when WiFi disabled - why?
Yes this was the issue, even though I was using network manager to make setting changes that were not propogating through.

It needed editing text files and restarting the machine for them to take affect.

Thank you for the help

Please Log in or Create an account to join the conversation.

  1. LinuxCNC
  3. General LinuxCNC Questions
  5. Mesa Ethernet only when WiFi disabled - why?
Time to create page: 0.112 seconds
Powered by Kunena Forum