4.3.0 Beta feedback

[G8SEZ]

I have 4.3.0 running on 3 RPi Zero 2W boards, all of them function normally despite being updated from the Feb 2024 image.

You do need to work around the OS updates in the small amount of memory on these boards, the steps to do this are shown above.

[SV1SSL]

Pi-Star:4.3.0 Br_2021_Greece brandmeister ?
where is it ?

[W1TG]

SOLVED - I found an issue with the 4.3.0 default image. It's resulted in a few hours of trouble-shooting to get the image working with a single band DV-Mega daughter board on Pi 3's & 4's. Others here on the forum have had the same issues with other modems and configurations. This has been discussed here in the "4.3.0 Beta Feedback" thread and in the "Cannot get the control attributes" thread. Some have developed very creative work arounds. I found the solution today and solved my problem by making one simple change.

PROBLEM - After installing a new image and inserting all your data in the sections of the configuration page the hotspot will function normally. You can reboot the image etc... The problems come into play when you make a change to an entry on the Configuration Page and apply the change. All the services restart as they should but /dev/ttyAMA0 gets reassigned. Now your DV Mega etc...won't run because the port has been assigned to another system user.

FACTS - On the Configuration Page in the MMDVMHost Section - "MMDVM Display Type" field = "None". "Port" is prepopulated = /dev/ttyAMA0

SOLUTION: Change the MMDVM Display Type Port = "None". Apply the Changes.

With that one simple change my DV-Mega returned to life. Prior to that I'd disabled bluetooth, purged bluetooth, reassigned ownership of the port by cli, etc...uggg, but an interesting learning experience.

My thanks to Andy and the PiStar Team for providing and maintaining this resource for us to use.

Tom - W1TG

[2E0BSL]

SOLVED - I found an issue with the 4.3.0 default image. It's resulted in a few hours of trouble-shooting to get the image working with a single band DV-Mega daughter board on Pi 3's & 4's. Others here on the forum have had the same issues with other modems and configurations. This has been discussed here in the "4.3.0 Beta Feedback" thread and in the "Cannot get the control attributes" thread. Some have developed very creative work arounds. I found the solution today and solved my problem by making one simple change.

PROBLEM - After installing a new image and inserting all your data in the sections of the configuration page the hotspot will function normally. You can reboot the image etc... The problems come into play when you make a change to an entry on the Configuration Page and apply the change. All the services restart as they should but /dev/ttyAMA0 gets reassigned. Now your DV Mega etc...won't run because the port has been assigned to another system user.

FACTS - On the Configuration Page in the MMDVMHost Section - "MMDVM Display Type" field = "None". "Port" is prepopulated = /dev/ttyAMA0

SOLUTIt wON: Change the MMDVM Display Type Port = "None". Apply the Changes.

With that one simple change my DV-Mega returned to life. Prior to that I'd disabled bluetooth, purged bluetooth, reassigned ownership of the port by cli, etc...uggg, but an interesting learning experience.

My thanks to Andy and the PiStar Team for providing and maintaining this resource for us to use.

Tom - W1TG

My pi zero is headless. The display has always been set to none. I can change anything and it works fine until I update from within 4.3.0. I may try the other suggestions but am tired of having to re image when I do the update from within 4.3.0. The update is broken certainly for pi zero which is why its stuck at beta stage.

[W1TG]

SOLVED - I found an issue with the 4.3.0 default image. It's resulted in a few hours of trouble-shooting to get the image working with a single band DV-Mega daughter board on Pi 3's & 4's. Others here on the forum have had the same issues with other modems and configurations. This has been discussed here in the "4.3.0 Beta Feedback" thread and in the "Cannot get the control attributes" thread. Some have developed very creative work arounds. I found the solution today and solved my problem by making one simple change.

PROBLEM - After installing a new image and inserting all your data in the sections of the configuration page the hotspot will function normally. You can reboot the image etc... The problems come into play when you make a change to an entry on the Configuration Page and apply the change. All the services restart as they should but /dev/ttyAMA0 gets reassigned. Now your DV Mega etc...won't run because the port has been assigned to another system user.

FACTS - On the Configuration Page in the MMDVMHost Section - "MMDVM Display Type" field = "None". "Port" is prepopulated = /dev/ttyAMA0

SOLUTIt wON: Change the MMDVM Display Type Port = "None". Apply the Changes.

With that one simple change my DV-Mega returned to life. Prior to that I'd disabled bluetooth, purged bluetooth, reassigned ownership of the port by cli, etc...uggg, but an interesting learning experience.

My thanks to Andy and the PiStar Team for providing and maintaining this resource for us to use.

Tom - W1TG

My pi zero is headless. The display has always been set to none. I can change anything and it works fine until I update from within 4.3.0. I may try the other suggestions but am tired of having to re image when I do the update from within 4.3.0. The update is broken certainly for pi zero which is why its stuck at beta stage.

That's the point. My Dv-Mega also doesn't have a display. Regardless of whether or not your hotspot has the display. Change the Display Port Setting to "None". Apply the change. The service update will reassign the port even though you're not trying to use the display. It's a simple fix. No more reflashing etc...

[2E0BSL]

SOLVED - I found an issue with the 4.3.0 default image. It's resulted in a few hours of trouble-shooting to get the image working with a single band DV-Mega daughter board on Pi 3's & 4's. Others here on the forum have had the same issues with other modems and configurations. This has been discussed here in the "4.3.0 Beta Feedback" thread and in the "Cannot get the control attributes" thread. Some have developed very creative work arounds. I found the solution today and solved my problem by making one simple change.

PROBLEM - After installing a new image and inserting all your data in the sections of the configuration page the hotspot will function normally. You can reboot the image etc... The problems come into play when you make a change to an entry on the Configuration Page and apply the change. All the services restart as they should but /dev/ttyAMA0 gets reassigned. Now your DV Mega etc...won't run because the port has been assigned to another system user.

FACTS - On the Configuration Page in the MMDVMHost Section - "MMDVM Display Type" field = "None". "Port" is prepopulated = /dev/ttyAMA0

SOLUTIt wON: Change the MMDVM Display Type Port = "None". Apply the Changes.

With that one simple change my DV-Mega returned to life. Prior to that I'd disabled bluetooth, purged bluetooth, reassigned ownership of the port by cli, etc...uggg, but an interesting learning experience.

My thanks to Andy and the PiStar Team for providing and maintaining this resource for us to use.

Tom - W1TG

My pi zero is headless. The display has always been set to none. I can change anything and it works fine until I update from within 4.3.0. I may try the other suggestions but am tired of having to re image when I do the update from within 4.3.0. The update is broken certainly for pi zero which is why its stuck at beta stage.

That's the point. My Dv-Mega also doesn't have a display. Regardless of whether or not your hotspot has the display. Change the Display Port Setting to "None". Apply the change. The service update will reassign the port even though you're not trying to use the display. It's a simple fix. No more reflashing etc...

Its always been set to no display for me. Maybe toggling it off/on would do it.Im back on 4.1.8 currently

[W1TG]

My pi zero is headless. The display has always been set to none. I can change anything and it works fine until I update from within 4.3.0. I may try the other suggestions but am tired of having to re image when I do the update from within 4.3.0. The update is broken certainly for pi zero which is why its stuck at beta stage.

That's the point. My Dv-Mega also doesn't have a display. Regardless of whether or not your hotspot has the display. Change the Display Port Setting to "None". Apply the change. The service update will reassign the port even though you're not trying to use the display. It's a simple fix. No more reflashing etc...

Its always been set to no display for me. Maybe toggling it off/on would do it.Im back on 4.1.8 currently

For the third tme...Understood on the "no display"...that's not the problem. You need to change the MMDVM Display "Port" entry right after it. As it's published on the image the port field says, "/dev/ttyAMA0". That's what causes the issue. It needs to be changed to "none". Apply the change and the problem goes away.

[2E0BSL]

That's the point. My Dv-Mega also doesn't have a display. Regardless of whether or not your hotspot has the display. Change the Display Port Setting to "None". Apply the change. The service update will reassign the port even though you're not trying to use the display. It's a simple fix. No more reflashing etc...

Its always been set to no display for me. Maybe toggling it off/on would do it.Im back on 4.1.8 currently

For the third tme...Understood on the "no display"...that's not the problem. You need to change the MMDVM Display "Port" entry right after it. As it's published on the image the port field says, "/dev/ttyAMA0". That's what causes the issue. It needs to be changed to "none". Apply the change and the problem goes away.

For the 2nd time, Im on 4.1.8 now. Your fix is no good there. You sound a bit salty, maybe someone else can confirm your fix.

[W1TG]

Its always been set to no display for me. Maybe toggling it off/on would do it.Im back on 4.1.8 currently

For the third tme...Understood on the "no display"...that's not the problem. You need to change the MMDVM Display "Port" entry right after it. As it's published on the image the port field says, "/dev/ttyAMA0". That's what causes the issue. It needs to be changed to "none". Apply the change and the problem goes away.

For the 2nd time, Im on 4.1.8 now. Your fix is no good there. You sound a bit salty, maybe someone else can confirm your fix.

My apologies for offending you in some way. I guess that I'm doing a poor job of clearly explaining the fix I found for the 4.3.0 Beta Release. My intent was trying to point you at the field on the Configuration Page that needs to be changed to fix the Beta Release.

This thread doesn't apply to 4.1.8 and I never discussed it. You brought that up. I was simply pointing at the field that needs to be changed in 4.3.0 to help you.

I found the answer to a problem that a lot of people have with 4.3.0. It's a simple fix to change one entry on the Configuration Page and then 4.3.0 can be used effectively. I've done it on Pi 3's, 4's and 5's with a DV-Mega board.

I'm sharing that fix here on the "Feedback" thread so others in the community can benefit from the change over to Bookworm and it's security updates.

You chose to reply to my post. It appeared to me from the context of your replies that you are not clear on what field needs to be changed to fix 4.3.0. That's why I tried to clarify.

I apologize for trying to help you and not being successful. I'm sorry for not saying it clearly enough in three tries. I tried to attach a small graphic but the board quota has been maxed out.

The FIX: MMDVMHost Configuration
Change the "Port" Field to "NONE" and "Apply Changes"

Thanks for helping me refine my explanation.

Tom - W1TG

[G8SEZ]

I ran an apt dist-upgrade on one of my current 4.3.0 systems today, which I do from time to time. It updated a whole load of packages.
The result is that it's broken dhcp at least, so now the Pi-Star doesn't get an IP address.

Anyone have any bright ideas? The general problem with updates where I need to kill off the RAM disks and then re-enable them is manageable, but this is definitely not.

I am rather attached to Pi-Star but it does need to be a bit less painful.