4.3.0 Beta feedback

[G8SEZ]

Have you considered trying with a smaller card? 128GB seems very large.

[KN2TOD]

Now that the Nextion processing has been integrated into the mix, consider adding the stop/start of the Nextion driver to pistar-daily.cron:

Code: Select all

  :
# Stop all the services...
systemctl stop pistar-watchdog.service > /dev/null 2>&1
systemctl stop nextiondriver.service  > /dev/null 2>&1       <-----
systemctl stop mmdvmhost.service > /dev/null 2>&1
systemctl stop dstarrepeater.service > /dev/null 2>&1
  :

  :
# Start all the services...
systemctl start ircddbgateway.service > /dev/null 2>&1
  :
systemctl start nextiondriver.service > /dev/null 2>&1         <-----
systemctl start mmdvmhost.service > /dev/null 2>&1
  :

This insures that the latest list of user ids gets loaded afresh each day.

Also, load in the lastest NextionDriver binary that allows more than the current 200K user ids.

[G8SEZ]

Andy is there a view from you and the other developers about whether 4.3.0 is now able to become a release version?

I've been running it for a good while on a Pi Zero 2W and it seems very good and stable.

I don't think I have seen any complaints about anything other than the Nextion-related stuff.

[PA5WIL]

why is there no more news about version 4.3.0?

[KD8DVR]

I just can't get 4.3.0 to work; the DMR flags on the left remain in RED. I have it working in 4.1.8, 4.2.1.

Same here. I scrapped 4.3

[DD8BA]

4.3.0 works fine on my Pi5

but i have to change ttyAMA0 back
see viewtopic.php?p=24271
and yes still if
dtoverlay=disable-bt
is set in the config.txt

GPIO sysfs interface is deprecated, it works with Kernel 6.1. which is used in the image, but for me is gpio20 => gpio591
and with Kernel 6.8. i can not access my dual_ms_hat anymore

73

[G8SEZ]

I am finding that it's pretty much impossible to run sudo apt dist-upgrade or full-upgrade, the errors seen are typically like this:

dpkg: error processing package linux-headers-rpi-v6 (--configure):
dependency problems - leaving unconfigured
Processing triggers for initramfs-tools (0.142+deb12u1) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-rpi8-rpi-v8
cpio: write error: No space left on device
E: mkinitramfs failure cpio 2
update-initramfs: failed for /boot/initrd.img-6.1.0-rpi8-rpi-v8 with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1

I think this is down to a lack of memory, but after trying to use the process here:

https://github.com/garyexplains/example ... erry_Pi.md

I don't get any improvement.

Perhaps a Pi Zero 2W is just not up to the job, but I have not seen this until trying it with Bookworm.

Any thoughts on how to fix this appreciated.

[DD8BA]

remove temporly the tmpfs entrys in the fstab for update
you can add a # at the beginnig, and reboot
After Update undo the edits

but be carefull with kernel 6.8. my MMDVM Modem stopped to work

[G8SEZ]

remove temporly the tmpfs entrys in the fstab for update
you can add a # at the beginnig, and reboot
After Update undo the edits

but be carefull with kernel 6.8. my MMDVM Modem stopped to work

Thanks for this, it does work although it doesn't make for nice automation.

So far I have kernel-6.6.47 which seems OK, I don't know when or if kernel-6.8 will reach Bookworm.

[2E0BSL]

I just can't get 4.3.0 to work; the DMR flags on the left remain in RED. I have it working in 4.1.8, 4.2.1.

Same here. I scrapped 4.3

Can confirm. This happens if you do an update from within 4.3.0. Any changes after result in red DMR flag requiring reflash to clear. If you dont update, it works fine.