4.3.2 / 4.3.3 / 4.3.4 Beta Feedback

[VA3UV]

I know what you are thinking... what manner of madness is this, another new beta release.. in short, yes....

Release Announcement here: viewtopic.php?t=5055
Download link: https://www.pistar.uk/beta/

Please use this thread for discussing 4.3.2 - I hope this one will go to production release, but I really value those brave souls that beta test it and help me work the kinks out, so please download, burn, enjoy - and let me know how you get on...

Changelog:

Code: Select all

10-Apr-2025 **Version 4.3.2 BETA RESPIN #3** - Available for Download.
    You will find that you cannot upgrade 4.3.x to 4.3.2, this is
        because too much of the core system needed to be
        modified to produce 4.3.2, yes that really does mean
        that you need to burn yet another card to use this one.
        I hope this will be the last beta, and *should* go into
        mainline / production use once you all have a chance
        to test it.
    4.3.2 has a seperate set of binaries from all previous versions,
        it does still share the scripts etc, but all of the DV
        software is new/up to date with current. This may cause
        some of you some issues, but please do your testing,
        this is why we release as beta after all.
    IPv6 has been enabled in this system matching the lastest 4.2.2
        build.
    Wi-Fi bugs as seen specifically on Pi02W (and only this SBC)
        have been resolved *I think*. Thank you to Chip (W0CHP)
        from WPSD for the tips.
    Kernel changes, I have removed the v7/v7l kernels, they are just
        not required, they have some GPU performance advantage
        on Pi2 boards, Pi-Star does not need/use the GPU.
        Everything from the Pi3 and onwards uses the 64Bit
        kernel by default, including the Pi400, Pi500 and the
        Pi02W. Please do not confuse this informaton, Pi-Star
        still supports ALL Raspberry Pi Foundation hardware,
        and should boot perfectly well on all platforms.
    Temperature control / Reduction - there was an issue with Pi4
        and Pi5 hardware that was causing the CPU to run at
        max clock ALL the time, we just don't need that, and it
        was causing Pi4 and Pi5 SBCs to run REALLY hot. Now
        resolved.
    GPU Underclock - This is required on the Pi02W for Wi-Fi
        stability, yes this sounds insane, it relates to how
        the Wi-Fi is connected to the the SoC, I have also
        applied the same GPU underclock on other models, I do
        not expect any issues arising from that, but this is
        a deliberate move to slightly reduce power use and SoC
        temps.
    CPU Underclock - Again this might sound a little crazy, but
        the idea here is to slightly under clock the CPU to
        help keep the operating temps down. Keep in mind that
        we already set the throttling temp to 75C (rather than
        the factory 85C) in order to prolong the life of any
        Raspberry Pi Foundataion boards, this step is more
        about helping knock the edge of running temps rather
        prolonging life. Pi 4 / Pi 5 retain full clock speed
        since most people are running coolers on them already.

Hi Andy: I just updated my hotspot (running 4.3.3) using the dashboard update method, the script seemingly pulled the update. Rebooted the Pi, but the dashboard as well as the Pi-Star splash logo still reports 4.3.3

Appreciate all the work you are doing to keep us on the bleeding edge!

Cheers,

Ramesh, VA3UV, WA3UV, G4PNQ

[MW0MWZ]

Hi Andy: I just updated my hotspot (running 4.3.3) using the dashboard update method, the script seemingly pulled the update. Rebooted the Pi, but the dashboard as well as the Pi-Star splash logo still reports 4.3.3

Appreciate all the work you are doing to keep us on the bleeding edge!

Cheers,

Ramesh, VA3UV, WA3UV, G4PNQ

Updated, or upgraded? Upgrade option is in the config > expert section, the normal Update will not push the version up or do the system changes related to the upgrade.....

http://pi-star/admin/expert/upgrade.php

[VA3UV]

Hi Andy: I just updated my hotspot (running 4.3.3) using the dashboard update method, the script seemingly pulled the update. Rebooted the Pi, but the dashboard as well as the Pi-Star splash logo still reports 4.3.3

Appreciate all the work you are doing to keep us on the bleeding edge!

Cheers,

Ramesh, VA3UV, WA3UV, G4PNQ

Updated, or upgraded? Upgrade option is in the config > expert section, the normal Update will not push the version up or do the system changes related to the upgrade.....

http://pi-star/admin/expert/upgrade.php

Ah - got it... trying to study today, so missed that step.

All good now.

Thanks, Andy!

Ramesh.

[KD8DVR]

Anytime you change the host "mane", you need to (almost) immediately reboot to propagate that change throughout the rest of the system before you do anything else (like backing up configurations). The errors you got (e.g. "sudo: unable to resolve host pi-star-bm: Name or service not known") are indicative that you attempted to continue to use the app for other tasks before rebooting.

I just rebooted repeatedly. No change.

[MW0MWZ]

Anytime you change the host "mane", you need to (almost) immediately reboot to propagate that change throughout the rest of the system before you do anything else (like backing up configurations). The errors you got (e.g. "sudo: unable to resolve host pi-star-bm: Name or service not known") are indicative that you attempted to continue to use the app for other tasks before rebooting.

I just rebooted repeatedly. No change.

Don't think this is a hostname issue, more likly that your browser doesn't like the file being sent - what browser are you using?

[W1TG]

Hello some feedback -
Using Pi-Star:4.3.4 / Dashboard: 20250418
MMDVMHost 20250419_PS4 git #65ebb55
Platform Raspberry Pi 4 Model B Rev 1.5
DVMEGA HR3.26

Since the update - upgrade - reboot after installing 20250419 MMDVMHost DStar seems to work normally. Prior I experienced the occasional reported TX lock. It's been about 24 hours now without issue. I've had it in use on D+ and XRF reflectors. Tailing the logs the info looks great.

Thanks for all your work to make the move on the OS!

Please continue to support the DStarRepeater module, I support several sites using this technology and it would be a shame to abandon those that simply want to run a single mode on some older modems like the DVRptr.

Tom - W1TG

[oe7abh]

Hello Andy,

unfortunately the Nextion drivers from ON7LDS in the current Pi-Star image (V4.2.3 or V4.2.2) for the USB interface (USB to TTL) are not well implemented, there are a lot of problems! Maybe you can renew the driver integration! Thank you!

The Nextion drivers in the current WPSD image, on the other hand, work very well and without any problems!

73 Alfred OE7ABH

[M1DNS]

Hello Andy,

unfortunately the Nextion drivers from ON7LDS in the current Pi-Star image (V4.2.3 or V4.2.2) for the USB interface (USB to TTL) are not well implemented, there are a lot of problems! Maybe you can renew the driver integration! Thank you!


73 Alfred OE7ABH

Yes. This has been discussed higher up the thread.

Sent via smoke signals using my SM-G960F

[VE3RD]

Hello Andy,

unfortunately the Nextion drivers from ON7LDS in the current Pi-Star image (V4.2.3 or V4.2.2) for the USB interface (USB to TTL) are not well implemented, there are a lot of problems! Maybe you can renew the driver integration! Thank you!


73 Alfred OE7ABH

Yes. This has been discussed higher up the thread.

Sent via smoke signals using my SM-G960F

We are all hoping for an update for this issue. But in the mean time the TGIF groups has a workaround solution.
I created a script several years ago, before pi-star implemented the NextionDriver. This script will perform all the steps necessary to install the Nextion Driver. Soon this script will no longer be necessary

Menu

OPTIONS=(1 "Pi-Star Update + Install Nextion Driver"
2 "Install Nextion Driver - No Update"
3 "Continue after Reboot from Option 1 or 2"
4 "Check Nextion Driver Installation"
5 "Update stripped.csv"
6 "Remove NextionDriver Configuration"
7 "Download & Install Nextion Screen Support Files"
8 "Quit")


Menu Item 1 & 2 will compile and install the driver. This is NO LONGER Necessary, as pi-star has version 1.26 of the driver installed
Menu Item 3 will provide a choice to install for the ttl adapter or gpio interface, then it will install bc for temperature calculations and then install a firewall rule so the the TGIF Spot can contact the server and disconnect a TG regardless of what the hotspot/radio is doing.

if you need an interface other than modem(gpio) or ttl-seral adapter, sorry, your on your own.

To obtain this script do the following

Log into your hotspot via an ssh shell (putty)
Type
rpi-rw
sudo su
git clone https://github.com/TGIF-Network/Scripts
cd Scripts

run the following script as follows
./IND.sh
and run menu item 3 as indicated in the menu above

Phil VE3RD

[KD8DVR]

Anytime you change the host "mane", you need to (almost) immediately reboot to propagate that change throughout the rest of the system before you do anything else (like backing up configurations). The errors you got (e.g. "sudo: unable to resolve host pi-star-bm: Name or service not known") are indicative that you attempted to continue to use the app for other tasks before rebooting.

I just rebooted repeatedly. No change.

Don't think this is a hostname issue, more likly that your browser doesn't like the file being sent - what browser are you using?

I also noticed when doing a pistar os update, it can't find what I named may hotspot either, so I don't think it's a browser issue. I did try with both edge and firefox with the same results.