watchdog and network connection problems
- jg00163206
- Topic Author
- Offline
- Premium Member
Less
More
- Posts: 92
- Thank you received: 4
08 Jul 2024 21:35 #304705
by jg00163206
watchdog and network connection problems was created by jg00163206
hello everyone, im having some issues after i installed debian and linuxcnc according to this post docs.google.com/document/d/1jeV_4VKzVmOI...m1x7oiw8VcLFdiY/edit. everything worked great until i had an idea to install another realtec network card. it worked for about a day and then the watchdog bite came on but it would still run. i shut it down and the next day, nothing worked. the watchdog would come on as soon as i booted the machine and wouldnt even go off when i reset the 7i96s. next, i removed the additional ethernet card but it still wouldnt work so i reinstalled everything according the preceding post. now, no matter how i configure it (through /ect/network/interfaces or through the gui) the network shows up somestimes but most of the time it doesnt show up in the list and i followed that post to the letter. ocationally i can ping the board and the ping times are >200 usec. im at a loss at this point and had to walk away from it. im wondering if anyone has any ideas. i have nothing but issues with this setup and it shouldnt be so hard to setup. i shouldnt have this many issues. what am i missing?
linuxcnc 2.9.2
mesa 7i96s
cw5045 stepper drives
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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 noprefixroute
valid_lft forever preferred_lft forever
2: enp46s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether c4:65:16:21:b4:9c brd ff:ff:ff:ff:ff:ff
inet 10.10.10.1/8 brd 10.255.255.255 scope global enp46s0
valid_lft forever preferred_lft forever
3: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ec:5c:68:34:dd:41 brd ff:ff:ff:ff:ff:ff
altname wlp23s0
inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic noprefixroute wlo1
valid_lft 40349sec preferred_lft 40349sec
inet6 2603:7080:e936:2933::12d6/128 scope global dynamic noprefixroute
valid_lft 601947sec preferred_lft 601947sec
inet6 fd00:f405:95cf:605a::12d6/128 scope global dynamic noprefixroute
valid_lft 601947sec preferred_lft 601947sec
inet6 fd00:f405:95cf:605a:d8f0:4dfe:89e:a4af/64 scope global dynamic noprefixroute
valid_lft 604502sec preferred_lft 604502sec
inet6 2603:7080:e936:2933:90c0:f9fd:7e98:5239/64 scope global dynamic noprefixroute
valid_lft 604502sec preferred_lft 604502sec
inet6 fe80::3c3a:67a9:98f3:3549/64 scope link noprefixroute
valid_lft forever preferred_lft forever
linuxcnc 2.9.2
mesa 7i96s
cw5045 stepper drives
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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 noprefixroute
valid_lft forever preferred_lft forever
2: enp46s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether c4:65:16:21:b4:9c brd ff:ff:ff:ff:ff:ff
inet 10.10.10.1/8 brd 10.255.255.255 scope global enp46s0
valid_lft forever preferred_lft forever
3: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ec:5c:68:34:dd:41 brd ff:ff:ff:ff:ff:ff
altname wlp23s0
inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic noprefixroute wlo1
valid_lft 40349sec preferred_lft 40349sec
inet6 2603:7080:e936:2933::12d6/128 scope global dynamic noprefixroute
valid_lft 601947sec preferred_lft 601947sec
inet6 fd00:f405:95cf:605a::12d6/128 scope global dynamic noprefixroute
valid_lft 601947sec preferred_lft 601947sec
inet6 fd00:f405:95cf:605a:d8f0:4dfe:89e:a4af/64 scope global dynamic noprefixroute
valid_lft 604502sec preferred_lft 604502sec
inet6 2603:7080:e936:2933:90c0:f9fd:7e98:5239/64 scope global dynamic noprefixroute
valid_lft 604502sec preferred_lft 604502sec
inet6 fe80::3c3a:67a9:98f3:3549/64 scope link noprefixroute
valid_lft forever preferred_lft forever
Please Log in or Create an account to join the conversation.
08 Jul 2024 22:08 - 09 Jul 2024 02:33 #304708
by PCW
Replied by PCW on topic watchdog and network connection problems
2: enp46s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether c4:65:16:21:b4:9c brd ff:ff:ff:ff:ff:ff
inet 10.10.10.1/8 brd 10.255.255.255 scope global enp46s0
valid_lft forever preferred_lft forever
Shows that the link is down which means that you have no connection with the 7I96S
Also its not suggested to use a /8 netmask, a /24 should be used instead
Not sure why adding a additional network card would cause an issue unless
its somehow affected the driver (didn't you inslal the DKMS driver for the
RealTek Ethernet previously?)
Also not sure what you mean by:
"the watchdog would come on as soon as i booted the machine and wouldnt even go off when i reset the 7i96s"
link/ether c4:65:16:21:b4:9c brd ff:ff:ff:ff:ff:ff
inet 10.10.10.1/8 brd 10.255.255.255 scope global enp46s0
valid_lft forever preferred_lft forever
Shows that the link is down which means that you have no connection with the 7I96S
Also its not suggested to use a /8 netmask, a /24 should be used instead
Not sure why adding a additional network card would cause an issue unless
its somehow affected the driver (didn't you inslal the DKMS driver for the
RealTek Ethernet previously?)
Also not sure what you mean by:
"the watchdog would come on as soon as i booted the machine and wouldnt even go off when i reset the 7i96s"
Last edit: 09 Jul 2024 02:33 by PCW.
Please Log in or Create an account to join the conversation.
- jg00163206
- Topic Author
- Offline
- Premium Member
Less
More
- Posts: 92
- Thank you received: 4
09 Jul 2024 17:08 #304763
by jg00163206
Replied by jg00163206 on topic watchdog and network connection problems
i did install the dkms drivers. what i mean by watchdog; the red light on the mesa 7i96s will illuminate as soon as i turn the pc on. when i go into pncconf and try to test an axis, i get an error that the halcmd is not running and i should invoke halcmd start to resolve it but that has no effect. also, i am unable to flash new firmware to this board. i have installed mesact a number of times and the firmware section is greyed out every time. no matter what i do. and when i run mesaflash --addr 10.10.10.10 --device=ETHER --readhmid, it does nothing. no output. i have to hit ctl+c to get my terminal back. i am at a lose here. i don't know why installing a new ethernet board would give me these issues either. maybe someone knows of a different setup that wouldn't be so complicated to setup. heres the error report i amd getting when i run lcnc; Error report created by /usr/lib/tcltk/linuxcnc/show_errors.tcl:
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.2
Machine configuration directory is '/home/mill/linuxcnc/configs/mill'
Machine configuration file is 'mill.ini'
INIFILE=/home/mill/linuxcnc/configs/mill/mill.ini
VERSION=1.1
PARAMETER_FILE=linuxcnc.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=halui
DISPLAY=qtvcp qtdragon
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): ./mill.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: INFO: Hardware address (MAC): 00:60:1b:16:8a:7b
hm2_eth: ERROR: receiving packet: Resource temporarily unavailable
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
Debug file information:
Note: Using POSIX realtime
rtapi_app: caught signal 11 - dumping core
./mill.hal:9: waitpid failed /usr/bin/rtapi_app hm2_eth
./mill.hal:9: /usr/bin/rtapi_app exited without becoming ready
./mill.hal:9: insmod for hm2_eth failed, returned -1
5535
Stopping realtime threads
Unloading hal components
Waited 3 seconds for master. giving up.
Note: Using POSIX realtime
hm2_eth: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
hostmot2: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
motmod: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
trivkins: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
homemod: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
tpmod: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
<commandline>:0: unloadrt failed
Note: Using POSIX realtime
Info report created by linuxcnc_info:
The file: /tmp/linuxcnc_info.txt
can be posted to a forum or a web site like:
pastebin.com
in order to provide information about the linuxcnc
system and configuration.
Date: Tue Jul 9 01:06:19 PM EDT 2024
UTC Date: Tue Jul 9 05:06:19 PM UTC 2024
this program: /usr/bin/linuxcnc_info
uptime: 13:06:19 up 52 min, 1 user, load average: 0.58, 1.10, 1.50
lsb_release -sa: Debian Debian GNU/Linux 12 (bookworm) 12 bookworm
linuxcnc: /usr/bin/linuxcnc
pwd: /home/mill/linuxcnc/configs/mill
USER: mill
LOGNAME: mill
HOME: /home/mill
EDITOR:
VISUAL:
LANGUAGE:
TERM: dumb
COLORTERM:
DISPLAY: :0.0
DESKTOP: lightdm-xsession
display size: 1360x768 pixels (360x203 millimeters)
PATH: /usr/bin:/home/mill/linuxcnc/configs/mill/bin:/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
uname items:
nodename -n: 4axis
kernel-name -s: Linux
kernel-vers -v: #2 SMP PREEMPT_RT Mon May 1 17:18:20 AEST 2023
machine -m: x86_64
processor -p: unknown
platform -i: unknown
oper system -o: GNU/Linux
/proc items:
cmdline: BOOT_IMAGE=/boot/vmlinuz-6.3.0-rt11-linuxcnc root=UUID=639fe864-e67c-4bdd-ba74-542c16092335 ro quiet nomodeset
model name: AMD Ryzen 5 2400G with Radeon Vega Graphics
cores: 4
cpu MHz: 2986.156
parport:
serial:
Versions:
gcc: gcc (Debian 12.2.0-14) 12.2.0
python: Python 3.11.2
git: not_in_PATH
git commit: NA
tcl: 8.6
tk: 8.6
glade: not_in_PATH
linuxcnc_var all:
LINUXCNCVERSION: 2.9.2
LINUXCNC_AUX_GLADEVCP: /usr/share/linuxcnc/aux_gladevcp
LINUXCNC_AUX_EXAMPLES: /usr/share/linuxcnc/aux_examples
REALTIME: /usr/lib/linuxcnc/realtime
RTS: uspace
HALLIB_DIR: /usr/share/linuxcnc/hallib
PYTHON: /usr/bin/python3
dpkg -l '*linuxcnc*':
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=================================-============-============-=====================================================================
ii linux-headers-6.3.0-rt11-linuxcnc 6.3.0-2 amd64 Linux kernel headers for 6.3.0-rt11-linuxcnc on amd64
ii linux-image-6.3.0-rt11-linuxcnc 6.3.0-2 amd64 Linux kernel, version 6.3.0-rt11-linuxcnc
un linuxcnc <none> <none> (no description available)
un linuxcnc-doc <none> <none> (no description available)
ii linuxcnc-doc-en 1:2.9.2 all motion controller for CNC machines and robots (English documentation)
un linuxcnc-doc-es <none> <none> (no description available)
un linuxcnc-doc-fr <none> <none> (no description available)
un linuxcnc-sim <none> <none> (no description available)
ii linuxcnc-uspace 1:2.9.2 amd64 motion controller for CNC machines and robots
thanks for all the help. if anyone knows of a less complicated setup, i would open to any and all suggestions.
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.2
Machine configuration directory is '/home/mill/linuxcnc/configs/mill'
Machine configuration file is 'mill.ini'
INIFILE=/home/mill/linuxcnc/configs/mill/mill.ini
VERSION=1.1
PARAMETER_FILE=linuxcnc.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=halui
DISPLAY=qtvcp qtdragon
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): ./mill.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: INFO: Hardware address (MAC): 00:60:1b:16:8a:7b
hm2_eth: ERROR: receiving packet: Resource temporarily unavailable
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
Debug file information:
Note: Using POSIX realtime
rtapi_app: caught signal 11 - dumping core
./mill.hal:9: waitpid failed /usr/bin/rtapi_app hm2_eth
./mill.hal:9: /usr/bin/rtapi_app exited without becoming ready
./mill.hal:9: insmod for hm2_eth failed, returned -1
5535
Stopping realtime threads
Unloading hal components
Waited 3 seconds for master. giving up.
Note: Using POSIX realtime
hm2_eth: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
hostmot2: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
motmod: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
trivkins: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
homemod: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
tpmod: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
<commandline>:0: unloadrt failed
Note: Using POSIX realtime
Info report created by linuxcnc_info:
The file: /tmp/linuxcnc_info.txt
can be posted to a forum or a web site like:
pastebin.com
in order to provide information about the linuxcnc
system and configuration.
Date: Tue Jul 9 01:06:19 PM EDT 2024
UTC Date: Tue Jul 9 05:06:19 PM UTC 2024
this program: /usr/bin/linuxcnc_info
uptime: 13:06:19 up 52 min, 1 user, load average: 0.58, 1.10, 1.50
lsb_release -sa: Debian Debian GNU/Linux 12 (bookworm) 12 bookworm
linuxcnc: /usr/bin/linuxcnc
pwd: /home/mill/linuxcnc/configs/mill
USER: mill
LOGNAME: mill
HOME: /home/mill
EDITOR:
VISUAL:
LANGUAGE:
TERM: dumb
COLORTERM:
DISPLAY: :0.0
DESKTOP: lightdm-xsession
display size: 1360x768 pixels (360x203 millimeters)
PATH: /usr/bin:/home/mill/linuxcnc/configs/mill/bin:/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
uname items:
nodename -n: 4axis
kernel-name -s: Linux
kernel-vers -v: #2 SMP PREEMPT_RT Mon May 1 17:18:20 AEST 2023
machine -m: x86_64
processor -p: unknown
platform -i: unknown
oper system -o: GNU/Linux
/proc items:
cmdline: BOOT_IMAGE=/boot/vmlinuz-6.3.0-rt11-linuxcnc root=UUID=639fe864-e67c-4bdd-ba74-542c16092335 ro quiet nomodeset
model name: AMD Ryzen 5 2400G with Radeon Vega Graphics
cores: 4
cpu MHz: 2986.156
parport:
serial:
Versions:
gcc: gcc (Debian 12.2.0-14) 12.2.0
python: Python 3.11.2
git: not_in_PATH
git commit: NA
tcl: 8.6
tk: 8.6
glade: not_in_PATH
linuxcnc_var all:
LINUXCNCVERSION: 2.9.2
LINUXCNC_AUX_GLADEVCP: /usr/share/linuxcnc/aux_gladevcp
LINUXCNC_AUX_EXAMPLES: /usr/share/linuxcnc/aux_examples
REALTIME: /usr/lib/linuxcnc/realtime
RTS: uspace
HALLIB_DIR: /usr/share/linuxcnc/hallib
PYTHON: /usr/bin/python3
dpkg -l '*linuxcnc*':
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=================================-============-============-=====================================================================
ii linux-headers-6.3.0-rt11-linuxcnc 6.3.0-2 amd64 Linux kernel headers for 6.3.0-rt11-linuxcnc on amd64
ii linux-image-6.3.0-rt11-linuxcnc 6.3.0-2 amd64 Linux kernel, version 6.3.0-rt11-linuxcnc
un linuxcnc <none> <none> (no description available)
un linuxcnc-doc <none> <none> (no description available)
ii linuxcnc-doc-en 1:2.9.2 all motion controller for CNC machines and robots (English documentation)
un linuxcnc-doc-es <none> <none> (no description available)
un linuxcnc-doc-fr <none> <none> (no description available)
un linuxcnc-sim <none> <none> (no description available)
ii linuxcnc-uspace 1:2.9.2 amd64 motion controller for CNC machines and robots
thanks for all the help. if anyone knows of a less complicated setup, i would open to any and all suggestions.
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
Less
More
- Posts: 19196
- Thank you received: 6434
09 Jul 2024 18:22 #304764
by tommylight
Replied by tommylight on topic watchdog and network connection problems
Check that both RJ45 connectors are plugged in correctly
In a terminal do
ping 10.10.10.10
if the link is OK the LED lights on the mesa board will count binary, i think
use a different LAN cable wired directly from PC to Mesa
-
Do not flash or attempt to flash the board with flaky connection, there is no need to ever flash the board if you do not specifically need something extra from it
Do not keep on trying wizards as there is no link
In a terminal do
ping 10.10.10.10
if the link is OK the LED lights on the mesa board will count binary, i think
use a different LAN cable wired directly from PC to Mesa
-
Do not flash or attempt to flash the board with flaky connection, there is no need to ever flash the board if you do not specifically need something extra from it
Do not keep on trying wizards as there is no link
Please Log in or Create an account to join the conversation.
- jg00163206
- Topic Author
- Offline
- Premium Member
Less
More
- Posts: 92
- Thank you received: 4
09 Jul 2024 18:48 #304766
by jg00163206
Replied by jg00163206 on topic watchdog and network connection problems
i even used a different Ethernet cable to make sure it wasn't the cable and no improvement. there are only lights on the rj45 connector on the mesa board after i reboot the board. and i can get a ping time from it for a couple seconds then it goes to host unreachable and it drops most of the packets. i haven't installed ANY wizards lately. or tried to flash the firmware. if i can't read the board, i don't think flashing will do much good. at what point do we start to question the hardware? is there a way to test the board to make sure it is operation properly?
Please Log in or Create an account to join the conversation.
- jg00163206
- Topic Author
- Offline
- Premium Member
Less
More
- Posts: 92
- Thank you received: 4
09 Jul 2024 18:56 #304767
by jg00163206
Replied by jg00163206 on topic watchdog and network connection problems
okay, i just reinstalled Debian and setup the network interface and i am getting ping responses. and no red light. yet. i am going to go through the process of installing lcnc
Please Log in or Create an account to join the conversation.
- jg00163206
- Topic Author
- Offline
- Premium Member
Less
More
- Posts: 92
- Thank you received: 4
09 Jul 2024 19:23 #304768
by jg00163206
Replied by jg00163206 on topic watchdog and network connection problems
unable to run pncconf. it freezes and says its not responding and asks if i want to exit the program. and the red light on the board is on and i am unable to ping the 7i96s. host unreachable.
Please Log in or Create an account to join the conversation.
- jg00163206
- Topic Author
- Offline
- Premium Member
Less
More
- Posts: 92
- Thank you received: 4
09 Jul 2024 19:27 #304769
by jg00163206
Replied by jg00163206 on topic watchdog and network connection problems
heres what i get when i ping the 7i96s; ping 10.10.10.10
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
From 10.10.10.1 icmp_seq=1 Destination Host Unreachable
From 10.10.10.1 icmp_seq=2 Destination Host Unreachable
From 10.10.10.1 icmp_seq=3 Destination Host Unreachable
From 10.10.10.1 icmp_seq=4 Destination Host Unreachable
From 10.10.10.1 icmp_seq=5 Destination Host Unreachable
From 10.10.10.1 icmp_seq=6 Destination Host Unreachable
From 10.10.10.1 icmp_seq=7 Destination Host Unreachable
From 10.10.10.1 icmp_seq=8 Destination Host Unreachable
From 10.10.10.1 icmp_seq=9 Destination Host Unreachable
From 10.10.10.1 icmp_seq=10 Destination Host Unreachable
From 10.10.10.1 icmp_seq=11 Destination Host Unreachable
From 10.10.10.1 icmp_seq=12 Destination Host Unreachable
^C
--- 10.10.10.10 ping statistics ---
15 packets transmitted, 0 received, +12 errors, 100% packet loss, time 14380ms
pipe 4
and the red light is on on the mesa 7i96s.
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
From 10.10.10.1 icmp_seq=1 Destination Host Unreachable
From 10.10.10.1 icmp_seq=2 Destination Host Unreachable
From 10.10.10.1 icmp_seq=3 Destination Host Unreachable
From 10.10.10.1 icmp_seq=4 Destination Host Unreachable
From 10.10.10.1 icmp_seq=5 Destination Host Unreachable
From 10.10.10.1 icmp_seq=6 Destination Host Unreachable
From 10.10.10.1 icmp_seq=7 Destination Host Unreachable
From 10.10.10.1 icmp_seq=8 Destination Host Unreachable
From 10.10.10.1 icmp_seq=9 Destination Host Unreachable
From 10.10.10.1 icmp_seq=10 Destination Host Unreachable
From 10.10.10.1 icmp_seq=11 Destination Host Unreachable
From 10.10.10.1 icmp_seq=12 Destination Host Unreachable
^C
--- 10.10.10.10 ping statistics ---
15 packets transmitted, 0 received, +12 errors, 100% packet loss, time 14380ms
pipe 4
and the red light is on on the mesa 7i96s.
Please Log in or Create an account to join the conversation.
09 Jul 2024 19:29 #304770
by PCW
Replied by PCW on topic watchdog and network connection problems
A red light on 7I96S at power up likely means you have a marginal
5V power issue or corrupted flash memory.
5V power issue or corrupted flash memory.
Please Log in or Create an account to join the conversation.
- jg00163206
- Topic Author
- Offline
- Premium Member
Less
More
- Posts: 92
- Thank you received: 4
12 Jul 2024 21:34 #305032
by jg00163206
Replied by jg00163206 on topic watchdog and network connection problems
i've tried a couple different power supplies. how do reflash the 7i96s?
Please Log in or Create an account to join the conversation.
Time to create page: 0.094 seconds