4.3.1 Beta Feedback

[MW0MWZ]

Parking this thread as a place to give me feedback on 4.3.1

See the announcement here: viewtopic.php?t=5046
Download from here: https://www.pistar.uk/beta/

Primary focus is on crushing OS related bugs, but anything 4.3.1 related can go here.

[MW0MWZ]

pistar-findmodem - errors out, now fixed, update to cure that, along with the modem reset tool.
I also removed an errant legacy flash tool that was still in place.

Looks like one of the fixes I had tested and intended to fix is also missing... I'll make that part of the next upgrade I think.

[VA3UV]

Hello Andy!

Very grateful for this new update. I have just updated VA3PMO Charlie; no issues - restored the config from my backup and we're off.

I did update mmdvmhost manually (to the 20250319 revision), as that fixes the long-awaited DTMF issue on D-STAR.

Will let this run for a week or two and see how it goes.

Again, a thousand thanks. Very nice to see a reliable platform continuing to move forward.

Cheers,

Ramesh, VA3UV, WA3UV, G4PNQ
Usually found on XLX405 A

[G8SEZ]

Andy

Is it simple to just use a previous backup to get a newly imaged system back to where it was? Or do I need to fool about some more? Currently I have at least one Pi-Star that isn't on my network due to the problems with Bookworm and NetworkManager and I would like recover it without too much pain.

[MW0MWZ]

Brian,

Yep, if you back it up you can restore in the normal way, either build the image let it boot and restore from the dashboard, or drop the zipped backup file onto the SD card after you write it and before you put it into the Pi, it will restore it on boot.

If you have any concerns, write a new card, you can always go back to the old one.

One issue I am seeing if the nextion port is set incorrectly in mmdvmhost's config:

Incorrect /etc/mmdvmhost

Code: Select all

[Nextion]
Port=/dev/ttyAMA0

Correct /etc/mmdvmhost

Code: Select all

[Nextion]
Port=/dev/ttyNextionDriver

This will cause you some pain, the dashboard config page will now fix that for you, or you can change it by hand to use /dev/ttyNextionDriver
EDIT: You may need a reboot once fixed to finish cleaning up the mess.

You may say "but I don't use a Nextion screen", and that is fine, but it will STILL stop MMDVMHost form running.

Other fixes are coming in via updates currently, I expect to re-spin this image in a couple of days (weekend ish) with the updates/fixes pre-installed.

[VE3OZW]

I am having an issue with 4.3.1 not picking up the MMDVM board. It works find with 4.2.1 but after the flashing and also updating the MMDVM board is still not recognized. Modes are red and when running the findmodem command, I get errors. The firmware for the hat is v1.6.1. Any thoughts? Could it be hat specific?

[AA7US]

I am having an issue with 4.3.1 not picking up the MMDVM board. Any thoughts?

I had a similar problem with a Raspberry Pi Zero 2W Zumspot with a 1.3” OLED display configured to use DMR only. After a fresh install of 4.3.1 and configuring, it initially worked fine. Then I started messing around with the display settings (changing and saving settings) and I noticed the MMDVM board wasn’t active anymore. Nothing I tried would make it work until I eventually tried a simple reboot and that solved the problem. It's been working fine and is stable ever since. In short, I'm learning that after making certain setting changes, simply saving those changes isn’t enough and a reboot is required.

73,

AA7US

[KA1PIT]

4.2.1 with update running fine, nextion screen working. burned 4.3.1, installed, no nextion screen. This has happened on two Pi Zeros/mmdvm hotspots.

a side tiny bug: expect -> CSS tools -> BannerExtText, enble 1, Text box: if you enter the word "no", just no as the first two characters, the expect editors screen comes up in black and white.

I now have four pi zeros working. three running DMR, two with nextion screens. I also have a pi zero 2 running P25.

[MW0MWZ]

a reboot is required.

73,

AA7US

Good point, edited my post and added this in too.

[VE3OZW]

Rebooted a couple times and also reinstalled OS. Will try again.