forum.pistar.uk

I'm running the latest release on a Pi Zero WH. Since I did an update on 11/14, the CPU utilization has been pretty high - over 3: pi-star@pi-star-blue(ro):~$ uptime 02:54:42 up 9:33, 1 user, load average: 2.07, 2.95, 3.29 So, I used ssh to get in and take a look: Screenshot from 2021-11-16 03-00-27...

It appears that this is either an MMDMV or Pi-Star issue, NOT a BM one.

And your proof is where??

By the simple, and quite logical, fact that when the Pi is rebooted, the problem goes away. Logically, if it were a BM issue, it would survive between reboots.

That's my proof.

You are supposed to key up 4000 when you no longer wish to monitor a talkgroup. That should remove it from the list FOR YOU AND stop sending you talkgroup network transmissions.

That was done. Several times.

AGAIN this is NOT something that Pi-Star has modified, so WE don't support it.

I made the comment because someone else had run up against the problem, and I was hoping that someone had found a solution. There was NO implication that this was or wasn't a Pi-Star issue.

Here's another example, after a reboot. Please not the talkgroup reverted to the last one that was used, but according to BM, there are no static or auto-static talkgroups.

Obviously, you haven't bothered to read Toshens documentation either. To avoid any sharp answers of this type, *I* bothered to read it. You are mistaken. REFRESH the dashboard and look again. Every talk group I've ever keyed on a simplex setup gets added AND DISPLAYED in the dynamic column of the A...

Pi-Star is designed to NOT have a monitor attached or even needed, therefore there is NO HDMI "display code" or even support really. I'm not talking about blanking the screen - please re-read what I wrote. I'm talking about waking the screen up. Whether or not Pi-Star is designed to be he...

I've also been able to duplicate this behavior in a fresh install of 4.1.5. I've got an application running on the console that refreshes the display every minute or so, and after a while the HDMI display signal shuts off. No amount of keyboard or mouse activity will wake it up. Rebooting the Pi (4B...

Instead of /etc/motd being displayed on the console on boot, how about a Curses/Ncurses version of the dashboard/config being displayed on the console? This would obviate the need to connect to the Pi with another machine running a browser, and a Ncurses programming written in Python would be pretty...

i also get the problem, at the first boot up, there is no modem in "findmodem" command, and the svc led doesnt appear. then i reboot, and just at the second boot i got the svc led and in findmodem there is the modem... That is an issue when using the RPi 4 models. They boot with their GPI...