Loss of ttyAMA0 with 4.2.0
Re: Loss of ttyAMA0 with 4.2.0
Bob,
I saw this on the other post. I have not have a chance to try it.
viewtopic.php?p=24271&fbclid=IwAR21r0b8 ... hcJqU8ZOG4
I never deleted the ttyAMA0, I just unlinked it. I will try that when I get home and -recreates a special file with type and major/minor number with the owner and group he suggested.
If I get to try that sooner I will let you know. But keep in mind that I will be working with 4.3.0 as I never saw this with 4.2.0
73, Kit
I saw this on the other post. I have not have a chance to try it.
viewtopic.php?p=24271&fbclid=IwAR21r0b8 ... hcJqU8ZOG4
I never deleted the ttyAMA0, I just unlinked it. I will try that when I get home and -recreates a special file with type and major/minor number with the owner and group he suggested.
If I get to try that sooner I will let you know. But keep in mind that I will be working with 4.3.0 as I never saw this with 4.2.0
73, Kit
Re: Loss of ttyAMA0 with 4.2.0
Hey Kit,
Yep, those are the instructions I used to recreate ttyAMA0 correctly.
Here's a speculation - if the hotpsot is never configured with a display, maybe the problem never occurs.
I had set my display type to None, but the display port was still ttyAMA0. One I set the port to None it
seems like my problems have gone away.
Bob, NS2B
Yep, those are the instructions I used to recreate ttyAMA0 correctly.
Here's a speculation - if the hotpsot is never configured with a display, maybe the problem never occurs.
I had set my display type to None, but the display port was still ttyAMA0. One I set the port to None it
seems like my problems have gone away.
Bob, NS2B
Re: Loss of ttyAMA0 with 4.2.0
Workaround seems to work but after reboot the pi-star the issue is back. At least for me.
73, Kit
73, Kit
Re: Loss of ttyAMA0 with 4.2.0
Update to 4.2.1 and let me know if that cures it for you
Re: Loss of ttyAMA0 with 4.2.0
Hmmm....
I'd have to say 4.2.1 is broken even worse.
This was performed on a jumbospot using a pi zero 2W configured as a D-Star hotspot.
I formatted my memory card.
Imaged the card with the 4.2.1 download.
Dropped my saved config from 4.1.8 into the boot partition.
Booted the hotspot
/dev/ttyAMA0 stayed put.
BUT...
The D-Star label kept toggling from red to green and audio received was one syllable at a time.
Tried powering down and up. It didn't connect to my wifi but instead ran home to access point mode.
Truly weird.
A second power cycle and it came up with wifi and behaved as described above.
Tailing the MMDVM log it looks like mmdvmhost is continuously restarting.
Bob, NS2B
I'd have to say 4.2.1 is broken even worse.
This was performed on a jumbospot using a pi zero 2W configured as a D-Star hotspot.
I formatted my memory card.
Imaged the card with the 4.2.1 download.
Dropped my saved config from 4.1.8 into the boot partition.
Booted the hotspot
/dev/ttyAMA0 stayed put.
BUT...
The D-Star label kept toggling from red to green and audio received was one syllable at a time.
Tried powering down and up. It didn't connect to my wifi but instead ran home to access point mode.
Truly weird.
A second power cycle and it came up with wifi and behaved as described above.
Tailing the MMDVM log it looks like mmdvmhost is continuously restarting.
Bob, NS2B
Re: Loss of ttyAMA0 with 4.2.0
Yep.
3 of my Pi-Star 4.2.1 hotspots are sitting there and continuously restarting, going offline, initialising, rinse and repeat.
3 of my Pi-Star 4.2.1 hotspots are sitting there and continuously restarting, going offline, initialising, rinse and repeat.
--
Brian G8SEZ
Brian G8SEZ
Re: Loss of ttyAMA0 with 4.2.0
Well damn
EDIT: Update pulled, I'll figure it out tomorrow.
EDIT: Update pulled, I'll figure it out tomorrow.
Re: Loss of ttyAMA0 with 4.2.0
check and see if
Code: Select all
/etc/systemd/system/mmdvmhost.service.requires
Code: Select all
sed -i '/Requires=nextiondriver\.service/d' /lib/systemd/system/mmdvmhost.service
systemctl daemon-reload
See if that clears them up
Re: Loss of ttyAMA0 with 4.2.0
/etc/systemd/system/mmdvmhost.service.requires did exist, did a sudo rm -rf on the folderMW0MWZ wrote: ↑Sat Feb 17, 2024 2:11 amcheck and see ifexists, and if it does remove the whole folder, and runCode: Select all
/etc/systemd/system/mmdvmhost.service.requires
and then reboot.Code: Select all
sed -i '/Requires=nextiondriver\.service/d' /lib/systemd/system/mmdvmhost.service systemctl daemon-reload
See if that clears them up
Ran the commands above using sudo, rebooted.
No change, sorry.
--
Brian G8SEZ
Brian G8SEZ
Re: Loss of ttyAMA0 with 4.2.0
Can we do some kind of remote session, I'd love to know more about how this is broken for you.
In the mean time I'll also do some more testing here and see if I can see what is up, the above cleaned mine up at least.
In the mean time I'll also do some more testing here and see if I can see what is up, the above cleaned mine up at least.