RPi4 with 7i96: LinuxCNC wont start
- notJamesLee
- Offline
- New Member
-
Less
More
- Posts: 2
- Thank you received: 1
21 Oct 2023 04:27 - 21 Oct 2023 04:54 #283418
by notJamesLee
RPi4 with 7i96: LinuxCNC wont start was created by notJamesLee
Hi Friends,
I am having an issue getting LCNC to start on my new RPi4 with the mesa 7i96s. I set the jumpers to W4 up and W5 down which should have set the ip to 10.10.10.10 (i think) and have the mesa card connected to a 5v PSU and the pi via ethernet.
After running a basic setup through PNCconf Wizard I tried open LinuxCNC and get the below error (I will move to the pi and edit/reply to this post with exact output)
hm2_eth : ERROR: could not retrieve hardware address (MAC): of 10.10.10.10: Resources temporarily unavailable Below is the exact output copied and pasted:
Here's what i've tried:
I am able to ping 10.10.10.10 and get the following output, which tells me that the IP should be set correctly
from other similar threads on here i also ran
ifconfig -a
and got this output
I saw an ip in there that i didn't recognize and tried to put that in my .hal file but to no avail.
The next thing i tried was to use mesaflash and i got it all installed but wasn't able to find the device.
I have a feeling its an easy fix but i am just a little over my ski's here. attached is my .hal file as well. (once i move to the pi)
also unsure if this is related but after running the pncconf wizard I have two folders that have the exact same files one is in the Linuxcnc folder(and based on the error logs it looks like thats the one its using) and the other on my desktop, am i good to delete the des ktop repository?
Any help is appreciated
James
I am having an issue getting LCNC to start on my new RPi4 with the mesa 7i96s. I set the jumpers to W4 up and W5 down which should have set the ip to 10.10.10.10 (i think) and have the mesa card connected to a 5v PSU and the pi via ethernet.
After running a basic setup through PNCconf Wizard I tried open LinuxCNC and get the below error (I will move to the pi and edit/reply to this post with exact output)
hm2_eth : ERROR: could not retrieve hardware address (MAC): of 10.10.10.10: Resources temporarily unavailable Below is the exact output copied and pasted:
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/lib/tcltk/linuxcnc/msgs INIVAR=inivar HALCMD=halcmd LINUXCNC_EMCSH=/usr/bin/wish8.6 LINUXCNC - 2.9.0~pre0 Machine configuration directory is '/home/linuxcnc/linuxcnc/configs/WorkBeeCutter' Machine configuration file is 'WorkBeeCutter.ini' INIFILE=/home/linuxcnc/linuxcnc/configs/WorkBeeCutter/WorkBeeCutter.ini VERSION=1.1 PARAMETER_FILE=linuxcnc.var TPMOD= HOMEMOD= TASK=milltask HALUI=halui DISPLAY=gmoccapy COORDINATES=XYZ KINEMATICS=trivkins coordinates=XYZ 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 linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod Found file(REL): ./WorkBeeCutter.hal Shutting down and cleaning up LinuxCNC... Running HAL shutdown script hm2: loading Mesa HostMot2 driver version 0.15 hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2 hm2_eth: ERROR: Could not retrieve hardware address (MAC) of 10.10.10.10: Resource temporarily unavailable 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) ./WorkBeeCutter.hal:9: waitpid failed /usr/bin/rtapi_app hm2_eth ./WorkBeeCutter.hal:9: /usr/bin/rtapi_app exited without becoming ready ./WorkBeeCutter.hal:9: insmod for hm2_eth failed, returned -1 11230 Stopping realtime threads Unloading hal components Note: Using POSIX realtimeHere's what i've tried:
I am able to ping 10.10.10.10 and get the following output, which tells me that the IP should be set correctly
--- 10.10.10.10 ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9015ms rtt min/avg/max/mdev = 16.609/22.012/57.478/11.908 msfrom other similar threads on here i also ran
ifconfig -a
and got this output
linuxcnc@raspberrypi:~/mesaflash $ ifconfig -a eth0: flags=4163 mtu 1500 inet 169.254.38.74 netmask 255.255.0.0 broadcast 169.254.255.255 inet6 fe80::a998:e092:b503:7931 prefixlen 64 scopeid 0x20 ether d8:3a:dd:75:c3:aa txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 867 bytes 155099 (151.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 35 bytes 3266 (3.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 35 bytes 3266 (3.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4163 mtu 1500 inet 192.168.0.60 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 2600:8800:520a:5b00:5a60:c90a:ef25:a812 prefixlen 64 scopeid 0x0 inet6 fe80::bb7:c629:94:de1c prefixlen 64 scopeid 0x20 ether d8:3a:dd:75:c3:ab txqueuelen 1000 (Ethernet) RX packets 43364 bytes 41763515 (39.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 28694 bytes 4055965 (3.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0I saw an ip in there that i didn't recognize and tried to put that in my .hal file but to no avail.
The next thing i tried was to use mesaflash and i got it all installed but wasn't able to find the device.
I have a feeling its an easy fix but i am just a little over my ski's here. attached is my .hal file as well. (once i move to the pi)
also unsure if this is related but after running the pncconf wizard I have two folders that have the exact same files one is in the Linuxcnc folder(and based on the error logs it looks like thats the one its using) and the other on my desktop, am i good to delete the des ktop repository?
Any help is appreciated
James
Attachments:
Last edit: 21 Oct 2023 04:54 by notJamesLee. Reason: adding error logs from machine thats harder to access, editing code tags
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
Less
More
- Posts: 18080
- Thank you received: 5997
21 Oct 2023 05:58 #283423
by tommylight
Replied by tommylight on topic RPi4 with 7i96: LinuxCNC wont start
Incorrect network settings, this:
linuxcnc@raspberrypi:~/mesaflash $ ifconfig -a eth0: flags=4163 mtu 1500 inet 169.254.38.74
should be
linuxcnc@raspberrypi:~/mesaflash $ ifconfig -a eth0: flags=4163 mtu 1500 inet 10.10.10.11
Search for "network setup for mesa cards".
Also, do not use MesaFlash unless explicitly needing firmware flash or reading HMID info.
linuxcnc@raspberrypi:~/mesaflash $ ifconfig -a eth0: flags=4163 mtu 1500 inet 169.254.38.74
should be
linuxcnc@raspberrypi:~/mesaflash $ ifconfig -a eth0: flags=4163 mtu 1500 inet 10.10.10.11
Search for "network setup for mesa cards".
Also, do not use MesaFlash unless explicitly needing firmware flash or reading HMID info.
Please Log in or Create an account to join the conversation.
- notJamesLee
- Offline
- New Member
-
Less
More
- Posts: 2
- Thank you received: 1
21 Oct 2023 18:53 #283453
by notJamesLee
Replied by notJamesLee on topic RPi4 with 7i96: LinuxCNC wont start
Amazing, thank you very much.
I had to install the network manager through command line, then I hopped into the pi config to enable the network manager, and finally was able to follow the post you suggested. I now have it open and am ready to move on to test.
Thanks again
James
I had to install the network manager through command line, then I hopped into the pi config to enable the network manager, and finally was able to follow the post you suggested. I now have it open and am ready to move on to test.
Thanks again
James
The following user(s) said Thank You: tommylight
Please Log in or Create an account to join the conversation.
Time to create page: 0.390 seconds