MAC address not retrieved (after 2 years stop)
- Jocman
- Offline
- Premium Member
-
Less
More
- Posts: 106
- Thank you received: 10
14 Jan 2026 13:43 #341365
by Jocman
MAC address not retrieved (after 2 years stop) was created by Jocman
Hi.
After 2 years I went to my home made hobbystic cnc to realize a project.
When used last time, the machine worked perfectly.
But today, starting LinuxCNC, I got a message error then LinuxCNC quit.
Here you can find the message (only the Print File Information section):
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.14
Machine configuration directory is '/home/joccnc/linuxcnc/configs/Prova01'
Machine configuration file is 'Prova01.ini'
INIFILE=/home/joccnc/linuxcnc/configs/Prova01/Prova01.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): ./Prova01.hal
hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: ERROR: 10.10.10.10: Could not retrieve mac address
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
Killing task linuxcncsvr, PID=2058
hm2: unloading
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
As I can see, the problem should be the Mesa board MAC address.
I didn't make any change (configuration, setup or else) last time I used the system (2 years ago), so I don't understand what happens.
Honestly, I made a first try with ChatGPT (I know, not the best idea but at the moment maybe.... - moreover it looks to me AS - Artificial Stupidity - more than AI - Intelligence....), but its suggestions were totally useless (some changes to ini and hal files), so I resumed my original files (attached).
Currently, LinuxCNC keep quitting; LinuxCNC correctly connects to the MESA Board.
My OS is LinuxCNC 2.7.14 + MESA 7i76e (Hybrid stepper drivers)
Can anyone help me to fix it?
Thanks
Andrea
After 2 years I went to my home made hobbystic cnc to realize a project.
When used last time, the machine worked perfectly.
But today, starting LinuxCNC, I got a message error then LinuxCNC quit.
Here you can find the message (only the Print File Information section):
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.14
Machine configuration directory is '/home/joccnc/linuxcnc/configs/Prova01'
Machine configuration file is 'Prova01.ini'
INIFILE=/home/joccnc/linuxcnc/configs/Prova01/Prova01.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): ./Prova01.hal
hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: ERROR: 10.10.10.10: Could not retrieve mac address
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
Killing task linuxcncsvr, PID=2058
hm2: unloading
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
As I can see, the problem should be the Mesa board MAC address.
I didn't make any change (configuration, setup or else) last time I used the system (2 years ago), so I don't understand what happens.
Honestly, I made a first try with ChatGPT (I know, not the best idea but at the moment maybe.... - moreover it looks to me AS - Artificial Stupidity - more than AI - Intelligence....), but its suggestions were totally useless (some changes to ini and hal files), so I resumed my original files (attached).
Currently, LinuxCNC keep quitting; LinuxCNC correctly connects to the MESA Board.
My OS is LinuxCNC 2.7.14 + MESA 7i76e (Hybrid stepper drivers)
Can anyone help me to fix it?
Thanks
Andrea
Please Log in or Create an account to join the conversation.
- PCW
-
- Offline
- Moderator
-
Less
More
- Posts: 17605
- Thank you received: 5147
14 Jan 2026 15:28 #341372
by PCW
Replied by PCW on topic MAC address not retrieved (after 2 years stop)
Whats does the command:
ip a
report?
What happens if you:
ping 10.10.10.10
?
ip a
report?
What happens if you:
ping 10.10.10.10
?
Please Log in or Create an account to join the conversation.
- rodw
-
- Online
- Platinum Member
-
Less
More
- Posts: 11645
- Thank you received: 3919
14 Jan 2026 20:15 #341385
by rodw
Replied by rodw on topic MAC address not retrieved (after 2 years stop)
did you turn on power to the Mesa card before starting linuxcnc?
Please Log in or Create an account to join the conversation.
- Jocman
- Offline
- Premium Member
-
Less
More
- Posts: 106
- Thank you received: 10
15 Jan 2026 17:50 #341434
by Jocman
Replied by Jocman on topic MAC address not retrieved (after 2 years stop)
did you turn on power to the Mesa card before starting linuxcnc?
yep, first thing I tried (a lot of times I got an error then I realized I forgot to switch on the machine)
Whats does the command:
ip a
report?
What happens if you:
ping 10.10.10.10
This is what I get with "ip a" and giving a ping:
eth0 is my second network card, I use it to reach my NAS, my LAN and the WEB
eth1 is the integrated network card, used by Mesa
giving the ping 10.10.10.10 I get response from Mesa
I just don't understand why eth1 report IP 10.10.10.11, when my hal file is set 10.10.10.10, and ping to 10.10.10.10 works.
BTW, after these tests I tried to start LinuxCNC, I get again an error message, but this time no mention about the MAC (is correctly reported), now the error is about HM2 registration:
yep, first thing I tried (a lot of times I got an error then I realized I forgot to switch on the machine)
Whats does the command:
ip a
report?
What happens if you:
ping 10.10.10.10
This is what I get with "ip a" and giving a ping:
joccnc@JocCnc:~$ 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 pfifo_fast state UP group default qlen 1000
link/ether e8:4e:06:84:dc:c9 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.245/24 brd 192.168.1.255 scope global dynamic eth0
valid_lft 863950sec preferred_lft 863950sec
inet6 fd59:b8bd:be6f:0:6bdd:2ca7:6e73:aa7b/64 scope global noprefixroute dynamic
valid_lft 7152sec preferred_lft 3552sec
inet6 fe80::6ed6:c856:a0cb:2db8/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 70:85:c2:6a:f0:3d brd ff:ff:ff:ff:ff:ff
inet 10.10.10.11/8 brd 10.255.255.255 scope global eth1
valid_lft forever preferred_lft forever
inet6 fe80::8ede:25a1:ff4d:99b4/64 scope link
valid_lft forever preferred_lft forever
joccnc@JocCnc:~$ ping 10.10.10.10
PING 10.10.10.10 (10.10.10.10): 56 data bytes
64 bytes from 10.10.10.10: icmp_seq=0 ttl=64 time=0.779 ms
64 bytes from 10.10.10.10: icmp_seq=1 ttl=64 time=0.418 ms
64 bytes from 10.10.10.10: icmp_seq=2 ttl=64 time=0.402 ms
64 bytes from 10.10.10.10: icmp_seq=3 ttl=64 time=0.424 ms
64 bytes from 10.10.10.10: icmp_seq=4 ttl=64 time=0.365 mseth0 is my second network card, I use it to reach my NAS, my LAN and the WEB
eth1 is the integrated network card, used by Mesa
giving the ping 10.10.10.10 I get response from Mesa
I just don't understand why eth1 report IP 10.10.10.11, when my hal file is set 10.10.10.10, and ping to 10.10.10.10 works.
BTW, after these tests I tried to start LinuxCNC, I get again an error message, but this time no mention about the MAC (is correctly reported), now the error is about HM2 registration:
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.14
Machine configuration directory is '/home/joccnc/linuxcnc/configs/Prova01'
Machine configuration file is 'Prova01.ini'
INIFILE=/home/joccnc/linuxcnc/configs/Prova01/Prova01.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): ./Prova01.hal
hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: 10.10.10.10: Hardware address: 00:60:1b:10:45:59
hm2_eth: discovered 7I76E-16
hm2/hm2_7i76e.0: Smart Serial Firmware Version 43
Board hm2_7i76e.0.7i76.0.0 Hardware Mode 0 = standard
Board hm2_7i76e.0.7i76.0.0 Software Mode 0 = io_spin
Board hm2_7i76e.0.7i76.0.0 Software Mode 1 = io_ana_spin
Board hm2_7i76e.0.7i76.0.0 Software Mode 2 = io_enc_ana_spin_fv
board fails HM2 registration
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
Killing task linuxcncsvr, PID=1208
hm2: unloading
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segmentsPlease Log in or Create an account to join the conversation.
- PCW
-
- Offline
- Moderator
-
Less
More
- Posts: 17605
- Thank you received: 5147
15 Jan 2026 18:03 - 15 Jan 2026 18:04 #341437
by PCW
Replied by PCW on topic MAC address not retrieved (after 2 years stop)
The host address of 10.10.10.11 is fine, it must be different than the FPGA card
(but in the same subnet)
A failed HM2 registration usually means dropped packets, so there is something marginal
with the Ethernet connection.
What does:
sudo chrt 99 ping -i .001 -c 60000 -q 10.10.10.10
report?
(it will run 1 minute before printing statistics)
(but in the same subnet)
A failed HM2 registration usually means dropped packets, so there is something marginal
with the Ethernet connection.
What does:
sudo chrt 99 ping -i .001 -c 60000 -q 10.10.10.10
report?
(it will run 1 minute before printing statistics)
Last edit: 15 Jan 2026 18:04 by PCW. Reason: sp
Please Log in or Create an account to join the conversation.
- Jocman
- Offline
- Premium Member
-
Less
More
- Posts: 106
- Thank you received: 10
21 Jan 2026 13:18 #341647
by Jocman
Replied by Jocman on topic MAC address not retrieved (after 2 years stop)
sorry for being late in my answer, but job and family demand their time too.....This is what i get : joccnc@JocCnc:~$ sudo chrt 99 ping -i.001 -c 60000 -q 10.10.10.10
[sudo] password for joccnc:
PING 10.10.10.10 (10.10.10.10): 56 data bytes
--- 10.10.10.10 ping statistics ---
60000 packets transmitted, 60000 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.246/0.395/0.733/0.032 ms
[sudo] password for joccnc:
PING 10.10.10.10 (10.10.10.10): 56 data bytes
--- 10.10.10.10 ping statistics ---
60000 packets transmitted, 60000 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.246/0.395/0.733/0.032 ms
Please Log in or Create an account to join the conversation.
- PCW
-
- Offline
- Moderator
-
Less
More
- Posts: 17605
- Thank you received: 5147
21 Jan 2026 16:03 #341651
by PCW
Replied by PCW on topic MAC address not retrieved (after 2 years stop)
Those are fairly dismal ping results, What is the Ethernet hardware?
If Intel, make sure you disable IRQ coalescing (see hm2_eth manual page)
If Intel, make sure you disable IRQ coalescing (see hm2_eth manual page)
Please Log in or Create an account to join the conversation.
- Jocman
- Offline
- Premium Member
-
Less
More
- Posts: 106
- Thank you received: 10
21 Jan 2026 16:39 #341654
by Jocman
Replied by Jocman on topic MAC address not retrieved (after 2 years stop)
I'm really poor in network matter....
Why my results are so dismal?
I red "60000 packets transmitted, 60000 packets received, 0% packet loss" and I was almost happy.....
BTW, the Mesa in wired to the onboard ethernet card, while the router (LAN, WEB) is wired to a PCI board (a commercial, very cheap one, this PC is intended only for CNC machining)
At the moment I don't remember the MB specification, but as soon as I can, I'll check e post it.
Why my results are so dismal?
I red "60000 packets transmitted, 60000 packets received, 0% packet loss" and I was almost happy.....
BTW, the Mesa in wired to the onboard ethernet card, while the router (LAN, WEB) is wired to a PCI board (a commercial, very cheap one, this PC is intended only for CNC machining)
At the moment I don't remember the MB specification, but as soon as I can, I'll check e post it.
Please Log in or Create an account to join the conversation.
- Jocman
- Offline
- Premium Member
-
Less
More
- Posts: 106
- Thank you received: 10
21 Jan 2026 17:28 #341659
by Jocman
Replied by Jocman on topic MAC address not retrieved (after 2 years stop)
Ok, here you find the specs of my system:
MB Asrock Q1900M
Intel celeron J1900 1.99Ghz
RAM 8 Gb
About the onboard LAN section:
- PCIE x1 Gigabit LAN 10/100/1000 Mb/s
- Realtek RTL8111GR
- Supports Wake-On-WAN
- Supports Wake-On-LAN
- Supports Lightning/ESD Protection (ASRock Full Spike Protection)
- Supports LAN Cable Detection
- Supports Energy Efficient Ethernet 802.3az
- Supports PXE
The PCI LAN card:
EP-9602GS
Chip Realtek RTL8111F
10/100/1000Mbps
PCI Express x1
Port RJ45
IEEE 802.3, IEEE 802.3u, IEEE 802.3x, IEEE 802.3ab
Auto MDIX Yes
Full Duplex Support Yes
Jumbo Frame Support 9k max
MTBF 376,212 hours
Supported Protocols CSMA/CD
MB Asrock Q1900M
Intel celeron J1900 1.99Ghz
RAM 8 Gb
About the onboard LAN section:
- PCIE x1 Gigabit LAN 10/100/1000 Mb/s
- Realtek RTL8111GR
- Supports Wake-On-WAN
- Supports Wake-On-LAN
- Supports Lightning/ESD Protection (ASRock Full Spike Protection)
- Supports LAN Cable Detection
- Supports Energy Efficient Ethernet 802.3az
- Supports PXE
The PCI LAN card:
EP-9602GS
Chip Realtek RTL8111F
10/100/1000Mbps
PCI Express x1
Port RJ45
IEEE 802.3, IEEE 802.3u, IEEE 802.3x, IEEE 802.3ab
Auto MDIX Yes
Full Duplex Support Yes
Jumbo Frame Support 9k max
MTBF 376,212 hours
Supported Protocols CSMA/CD
Please Log in or Create an account to join the conversation.
- rodw
-
- Online
- Platinum Member
-
Less
More
- Posts: 11645
- Thank you received: 3919
21 Jan 2026 18:52 #341664
by rodw
Replied by rodw on topic MAC address not retrieved (after 2 years stop)
try sudo apt install r8168-dkms which is the driver for your R8111 (requires non-free)
Follow my YouTube tutorial for PREEMPT_RT tuning for a detailed process to tune your kernel and the steps required to install this and more
www.youtube.com/playlist?list=PLG0NtQtZP...aAlFBsmYP1ay8VNQwsyY
Follow my YouTube tutorial for PREEMPT_RT tuning for a detailed process to tune your kernel and the steps required to install this and more
www.youtube.com/playlist?list=PLG0NtQtZP...aAlFBsmYP1ay8VNQwsyY
Please Log in or Create an account to join the conversation.
Moderators: PCW, jmelson
Time to create page: 0.074 seconds