Pi-Star Remote
Re: Pi-Star Remote
both result in the screen on my zumspot elite saying “mmdvm stopped” and it sits there indefinitely. it does not “power down”. both commands appear to do exactly the same thing
Re: Pi-Star Remote
The screen is driven by mmdvmhost...
mmdvmhost is a service...
When you action the kill request
you stop mmdvmhost.
You could restart services with a cli command.
You can't do that after shutdown.
Sent via smoke signals from my SM-G935F M1DNS (Admin)
mmdvmhost is a service...
When you action the kill request
you stop mmdvmhost.
You could restart services with a cli command.
You can't do that after shutdown.
Sent via smoke signals from my SM-G935F M1DNS (Admin)
Andrew M1DNS.
Pi-star Admin Team.
Pi-star Admin Team.
Re: Pi-Star Remote
What is a cli command?
When I do shutdown... it disables everything and the screen ends up saying "mmdvm stopped" and it sits there indefinitely.. screen is still on, indefinitely...pi does not respond to any rf commands
when i do svckill...it disables everything and the screen ends up saying "mmdvdm stopped" and it sits there indefinitely. screen is still on, pi does not respond to any rf commands.
How do these differ? end result appears to be exactly the same. you said "shutdown" powers down the pi... it certainly does not power down anything. power stays on. both commands result in a non-functioning hotspot.
When I do shutdown... it disables everything and the screen ends up saying "mmdvm stopped" and it sits there indefinitely.. screen is still on, indefinitely...pi does not respond to any rf commands
when i do svckill...it disables everything and the screen ends up saying "mmdvdm stopped" and it sits there indefinitely. screen is still on, pi does not respond to any rf commands.
How do these differ? end result appears to be exactly the same. you said "shutdown" powers down the pi... it certainly does not power down anything. power stays on. both commands result in a non-functioning hotspot.
Re: Pi-Star Remote
If you kill a service, you can start them back up agn using the command line.
If you shutdown, you cannot.
Whilst they may appear a similiar outcome, they are both quite different.
Sent via smoke signals from my SM-G935F M1DNS (Admin)
Andrew M1DNS.
Pi-star Admin Team.
Pi-star Admin Team.
Re: Pi-Star Remote
Bottom up...Ki6anr wrote: ↑Fri Feb 25, 2022 6:06 pm What is a cli command?
When I do shutdown... it disables everything and the screen ends up saying "mmdvm stopped" and it sits there indefinitely.. screen is still on, indefinitely...pi does not respond to any rf commands
when i do svckill...it disables everything and the screen ends up saying "mmdvdm stopped" and it sits there indefinitely. screen is still on, pi does not respond to any rf commands.
How do these differ? end result appears to be exactly the same. you said "shutdown" powers down the pi... it certainly does not power down anything. power stays on. both commands result in a non-functioning hotspot.
Raspberry-Pi boards ALWAYS show a live power connection, even if the OS and processor have been shutdown. It is one complaint about the R-Pi -- one has to issue a shutdown, and then wait some period of time before pulling the power cable. (Beaglebone Blacks have a power management chip that can do an actual shutdown of the full power system, and have a button that can turn it back on).
SVCKILL kills system services, but does not shutdown the OS. You can still log into the R-Pi using a SSH client (PuTTY, for example), and could even issue commands to restart the services.
{See comment about R-Pi board power connection} A system shutdown sequentially stops all programs running on the board, followed by doing something to halt the processor -- only toggling the power supply will wake it back up.
In both situations, the on-board display is controlled by MMDVM -- when that is stopped, the display retains the last data until the power is pulled. And since the service is stopped, there is no process running that can interpret any commands issued via the RF remote feature
CLI => Command Line Interpreter, AKA "shell". Typically BASH is the system shell on many Linux systems. It is what you see when you log into the R-Pi.
Code: Select all
Using username "pi-star".
pi-star@pi-star-3b's password:
Linux pi-star-3b 5.10.63-v7+ #1496 SMP Wed Dec 1 15:58:11 GMT 2021 armv7l
╔═══════════════════════════════════════════════════════════════════════╗
║ ║
║ ██████╗ ██╗ ███████╗████████╗ █████╗ ██████╗ ║
║ ██╔══██╗██║ ██╔════╝╚══██╔══╝██╔══██╗██╔══██╗ ║
║ ██████╔╝██║█████╗███████╗ ██║ ███████║██████╔╝ ║
║ ██╔═══╝ ██║╚════╝╚════██║ ██║ ██╔══██║██╔══██╗ ║
║ ██║ ██║ ███████║ ██║ ██║ ██║██║ ██║ ║
║ ╚═╝ ╚═╝ ╚══════╝ ╚═╝ ╚═╝ ╚═╝╚═╝ ╚═╝ ║
║ ║
╚═══════════════════════════════════════════════════════════════════════╝
The Pi-Star Dashboard can be found at one of the following locations:
http://pi-star-3b/ http://pi-star-3b.local/ http://192.168.1.79/
Pi-Star's disk is read-only by default, enable read-write with "rpi-rw".
Pi-Star built by Andy Taylor (MW0MWZ), pi-star tools all start "pistar-".
Welcome to Pi-Star: v4.1.6
pi-star@pi-star-3b(ro):~$ ps -aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.3 0.8 33760 8256 ? Ss 15:54 1:15 /sbin/init noswap
root 2 0.0 0.0 0 0 ? S 15:54 0:00 [kthreadd]
root 3 0.0 0.0 0 0 ? I< 15:54 0:00 [rcu_gp]
root 4 0.0 0.0 0 0 ? I< 15:54 0:00 [rcu_par_gp]
root 8 0.0 0.0 0 0 ? I< 15:54 0:00 [mm_percpu_wq]
root 9 0.0 0.0 0 0 ? S 15:54 0:00 [rcu_tasks_rude_]
root 10 0.0 0.0 0 0 ? S 15:54 0:00 [rcu_tasks_trace]
root 11 0.0 0.0 0 0 ? S 15:54 0:01 [ksoftirqd/0]
root 12 0.0 0.0 0 0 ? I 15:54 0:02 [rcu_sched]
root 13 0.0 0.0 0 0 ? S 15:54 0:00 [migration/0]
root 14 0.0 0.0 0 0 ? S 15:54 0:00 [cpuhp/0]
root 15 0.0 0.0 0 0 ? S 15:54 0:00 [cpuhp/1]
root 16 0.0 0.0 0 0 ? S 15:54 0:00 [migration/1]
root 17 0.0 0.0 0 0 ? S 15:54 0:01 [ksoftirqd/1]
root 20 0.0 0.0 0 0 ? S 15:54 0:00 [cpuhp/2]
root 21 0.0 0.0 0 0 ? S 15:54 0:00 [migration/2]
root 22 0.0 0.0 0 0 ? R 15:54 0:00 [ksoftirqd/2]
root 25 0.0 0.0 0 0 ? S 15:54 0:00 [cpuhp/3]
root 26 0.0 0.0 0 0 ? S 15:54 0:00 [migration/3]
root 27 0.0 0.0 0 0 ? S 15:54 0:00 [ksoftirqd/3]
root 30 0.0 0.0 0 0 ? S 15:54 0:00 [kdevtmpfs]
root 31 0.0 0.0 0 0 ? I< 15:54 0:00 [netns]
root 35 0.0 0.0 0 0 ? S 15:54 0:00 [kauditd]
root 37 0.0 0.0 0 0 ? S 15:54 0:00 [khungtaskd]
root 38 0.0 0.0 0 0 ? S 15:54 0:00 [oom_reaper]
root 39 0.0 0.0 0 0 ? I< 15:54 0:00 [writeback]
root 40 0.0 0.0 0 0 ? S 15:54 0:01 [kcompactd0]
root 58 0.0 0.0 0 0 ? I< 15:54 0:00 [kblockd]
root 59 0.0 0.0 0 0 ? I< 15:54 0:00 [blkcg_punt_bio]
root 60 0.0 0.0 0 0 ? S 15:54 0:00 [watchdogd]
root 61 0.0 0.0 0 0 ? I< 15:54 0:00 [kworker/2:1H-kblockd]
root 62 0.0 0.0 0 0 ? I< 15:54 0:00 [rpciod]
root 63 0.0 0.0 0 0 ? I< 15:54 0:00 [kworker/u9:0-hci0]
root 64 0.0 0.0 0 0 ? I< 15:54 0:00 [xprtiod]
root 65 0.0 0.0 0 0 ? S 15:54 0:00 [kswapd0]
root 66 0.0 0.0 0 0 ? I< 15:54 0:00 [nfsiod]
root 69 0.0 0.0 0 0 ? I< 15:54 0:00 [iscsi_eh]
root 70 0.0 0.0 0 0 ? I< 15:54 0:00 [iscsi_destroy]
root 71 0.0 0.0 0 0 ? I< 15:54 0:00 [dwc_otg]
root 73 0.0 0.0 0 0 ? I< 15:54 0:00 [DWC Notificatio]
root 75 0.0 0.0 0 0 ? S< 15:54 0:00 [vchiq-slot/0]
root 76 0.0 0.0 0 0 ? S< 15:54 0:00 [vchiq-recy/0]
root 77 0.0 0.0 0 0 ? S< 15:54 0:00 [vchiq-sync/0]
root 78 0.0 0.0 0 0 ? I< 15:54 0:00 [zswap-shrink]
root 84 0.0 0.0 0 0 ? I< 15:54 0:00 [mmc_complete]
root 85 0.0 0.0 0 0 ? I< 15:54 0:00 [kworker/1:1H-kblockd]
root 86 0.0 0.0 0 0 ? I< 15:54 0:00 [kworker/0:1H-mmc_complete]
root 87 0.0 0.0 0 0 ? S 15:54 0:00 [jbd2/mmcblk0p2-]
root 88 0.0 0.0 0 0 ? I< 15:54 0:00 [ext4-rsv-conver]
root 89 0.0 0.0 0 0 ? I< 15:54 0:00 [kworker/0:2H]
root 108 0.0 0.0 0 0 ? I< 15:54 0:00 [kworker/2:2H]
root 115 0.0 0.0 0 0 ? I< 15:54 0:00 [kworker/3:2H-kblockd]
root 119 0.0 0.6 41896 6168 ? Ss 15:54 0:09 /lib/systemd/systemd-journald
root 152 0.0 0.3 18044 3760 ? Ss 15:54 0:00 /lib/systemd/systemd-udevd
root 173 0.0 0.0 0 0 ? S 15:54 0:00 [spi0]
root 182 0.0 0.0 0 0 ? S 15:54 0:00 [vchiq-keep/0]
root 261 0.0 0.0 0 0 ? I< 15:54 0:00 [cfg80211]
root 270 0.0 0.0 0 0 ? I< 15:54 0:00 [brcmf_wq/mmc1:0]
root 272 0.1 0.0 0 0 ? S 15:54 0:26 [brcmf_wdog/mmc1]
root 343 0.0 0.4 7628 4264 ? Ss 15:54 0:01 /usr/sbin/haveged --Foreground
_rpc 348 0.0 0.2 6492 2824 ? Ss 15:54 0:00 /sbin/rpcbind -f -w
root 354 0.0 0.5 13272 5884 ? Ss 15:54 0:04 /lib/systemd/systemd-logind
root 355 0.0 0.3 26080 3172 ? Ssl 15:54 0:01 /usr/sbin/rsyslogd -n -iNONE
message+ 358 0.0 0.3 7132 3836 ? Ss 15:54 0:14 /usr/bin/dbus-daemon --system -
root 365 0.0 0.4 10624 4112 ? Ss 15:54 0:00 /sbin/wpa_supplicant -u -s -O /
avahi 368 0.0 0.2 6336 2924 ? Ss 15:54 0:00 avahi-daemon: running [pi-star-
avahi 412 0.0 0.1 6336 1712 ? S 15:54 0:00 avahi-daemon: chroot helper
root 418 0.0 0.2 8240 2556 ? Ss 15:54 0:00 /usr/sbin/cron -f
root 425 0.0 0.0 27572 68 ? SLsl 15:54 0:00 /usr/sbin/rngd -r /dev/hwrng
root 444 0.0 0.3 11232 3676 ? Ss 15:54 0:00 /sbin/wpa_supplicant -s -B -P /
root 768 0.0 0.0 0 0 ? I< 15:54 0:00 [kworker/u9:1-hci0]
root 769 0.0 0.0 2056 120 ? S 15:54 0:00 /usr/bin/hciattach /dev/serial1
root 781 0.0 0.4 9724 4240 ? Ss 15:54 0:00 /usr/lib/bluetooth/bluetoothd
root 831 0.0 0.1 2820 1668 ? Ss 15:54 0:00 /sbin/dhcpcd -q -w
root 833 0.0 1.5 38988 15864 ? Ssl 15:54 0:00 /usr/bin/python3 /usr/share/una
root 838 0.0 2.1 126460 21112 ? Ss 15:54 0:02 php-fpm: master process (/etc/p
root 851 0.0 0.9 31896 9616 ? Ss 15:54 0:01 /usr/sbin/nmbd --foreground --n
root 867 0.0 0.0 1852 80 ? Ss 15:54 0:00 /usr/sbin/minissdpd -i eth0 -i
ntp 883 0.0 0.3 8604 3224 ? Ssl 15:54 0:03 /usr/sbin/ntpd -p /var/run/ntpd
root 897 0.0 0.5 10812 5324 ? Ss 15:54 0:00 /usr/sbin/sshd -D
shellin+ 900 0.0 0.2 6364 2008 ? Ss 15:54 0:00 /usr/bin/shellinaboxd -q --back
shellin+ 901 0.0 0.0 6364 480 ? S 15:54 0:00 /usr/bin/shellinaboxd -q --back
root 920 0.0 0.0 7292 688 ? Ss 15:54 0:00 nginx: master process /usr/sbin
www-data 921 0.0 0.3 7848 3172 ? S 15:54 0:00 nginx: worker process
www-data 922 0.0 0.3 7848 3160 ? S 15:54 0:00 nginx: worker process
www-data 923 0.0 0.3 7848 3172 ? S 15:54 0:00 nginx: worker process
www-data 924 0.0 0.3 7848 3160 ? S 15:54 0:00 nginx: worker process
root 946 0.0 0.1 4572 1424 tty1 Ss+ 15:54 0:00 /sbin/agetty -o -p -- \u --nocl
www-data 954 0.0 0.6 126764 6396 ? S 15:54 0:00 php-fpm: pool www
www-data 955 0.0 0.6 126764 6396 ? S 15:54 0:00 php-fpm: pool www
root 957 0.0 1.7 47948 16984 ? Ss 15:54 0:00 /usr/sbin/smbd --foreground --n
root 960 0.0 0.5 45344 5164 ? S 15:54 0:00 /usr/sbin/smbd --foreground --n
root 961 0.0 0.4 45336 4092 ? S 15:54 0:00 /usr/sbin/smbd --foreground --n
root 963 0.0 0.6 47948 6068 ? S 15:54 0:00 /usr/sbin/smbd --foreground --n
root 1274 1.7 0.6 51628 6848 ? S<sl 15:54 6:44 /usr/local/bin/ircddbgatewayd -
root 1342 1.8 4.2 53136 42736 ? S<sl 15:54 7:22 /usr/local/bin/MMDVMHost /etc/m
root 1372 0.0 0.6 12824 6452 ? S 15:55 0:04 /usr/bin/python /usr/local/sbin
root 11147 0.0 0.0 0 0 ? I< 19:18 0:00 [kworker/1:0H]
root 17275 0.0 0.0 0 0 ? I 21:25 0:01 [kworker/3:0-events]
root 17938 1.0 0.0 0 0 ? I 21:37 0:33 [kworker/2:2-events]
root 18682 0.5 0.0 0 0 ? I 21:54 0:12 [kworker/0:2-events]
root 19037 0.0 0.0 0 0 ? I 22:01 0:00 [kworker/1:2-events]
root 19372 0.5 0.0 0 0 ? I 22:07 0:07 [kworker/u8:2-events_unbound]
root 19758 0.0 0.0 0 0 ? I 22:13 0:00 [kworker/0:1-events]
root 19775 0.0 0.0 0 0 ? I 22:16 0:00 [kworker/1:0-events]
root 19776 1.4 0.0 0 0 ? D 22:16 0:10 [kworker/2:1+events_power_effic
root 19813 0.0 0.0 0 0 ? I< 22:17 0:00 [kworker/3:0H]
root 19821 0.0 0.0 0 0 ? I 22:17 0:00 [kworker/3:1-cgroup_destroy]
root 20130 0.1 0.0 0 0 ? I 22:20 0:00 [kworker/u8:0-events_unbound]
root 20131 0.0 0.0 0 0 ? I 22:21 0:00 [kworker/1:1-events]
root 20134 0.0 0.0 0 0 ? I 22:22 0:00 [kworker/2:3-events]
root 20135 0.0 0.0 0 0 ? I 22:24 0:00 [kworker/0:0-events]
root 20279 0.0 0.0 0 0 ? I 22:25 0:00 [kworker/u8:1-brcmf_wq/mmc1:000
root 20303 0.0 0.0 0 0 ? I 22:25 0:00 [kworker/3:2-cgroup_destroy]
root 20346 0.0 0.0 0 0 ? I 22:25 0:00 [kworker/1:3-events]
root 20471 1.1 0.6 12252 6284 ? Ss 22:28 0:00 sshd: pi-star [priv]
pi-star 20475 1.5 0.7 14592 7220 ? Ss 22:28 0:00 /lib/systemd/systemd --user
pi-star 20476 0.0 0.3 35736 3780 ? S 22:28 0:00 (sd-pam)
pi-star 20490 0.2 0.5 12556 5200 ? R 22:28 0:00 sshd: pi-star@pts/0
pi-star 20491 2.0 0.3 8748 3760 pts/0 Ss 22:28 0:00 -bash
pi-star 20499 0.0 0.3 10356 3000 pts/0 R+ 22:28 0:00 ps -aux
pi-star@pi-star-3b(ro):~$
--
AF6VN
Dennis L Bieber
Re: Pi-Star Remote
makes more sense. thank you