|
I built a brand new pi (Pi 4 8GB) today. Pi OS 32 bit bullseye. Each time I try an ARDOP connection with Pat, piardopc locks after the first PTT attempt. Anyone else ran into this?
73, de KM4ACK
|
I was seeing that on x86 with ardopc and ardopc_64, but not with piardopc. It might be a Pat issue (especially if you're running Pat's beta build), but I haven't tracked it down yet. Does it continue if you're on Pat stable?
I built a brand new pi (Pi 4 8GB) today. Pi OS 32 bit bullseye. Each time I try an ARDOP connection with Pat, piardopc locks after the first PTT attempt. Anyone else ran into this?
73, de KM4ACK
|
Put the xmitter on a dummy load to make sure it’s not a RFI issue. ? Perry K4PWO ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of km4ack Sent: Thursday, March 31, 2022 1:44 PM To: [email protected]Subject: [bpq32] piardopc locks up ? I built a brand new pi (Pi 4 8GB) today. Pi OS 32 bit bullseye. Each time I try an ARDOP connection with Pat, piardopc locks after the first PTT attempt. Anyone else ran into this?
73, de KM4ACK
|
Thanks guys. It's probably something I have done but can't figure out what. It's a stable version of Pat and RFI isn't the issue. Same Pi and radio with a different (known working) SD card works as expected. I'll keep playing with it.
73, de KM4ACK
|
A bit more testing just to verify my sanity :-) I stated with a fresh copy of bullseye 32 bit that was last updated on 23FEB2022 running on a Pi 4 8GB. I installed FLRIG and hamlib 4.4 from source. Installed Pat Winlink, ARDOP_GUI, and ARDOP. Ran a test and confirmed that ADROP worked as expected and I could connect to a gateway. Next I ran the apt upgrade command and rebooted the Pi. Afterwards, I attempted the ARDOP connection again but this time ARDOP hangs at PTT during the first transmit cycle forcing me to power down the radio manually in order to stop the TX. Not sure what’s causing it but something in the upgrade process is breaking piardopc.
73, de KM4ACK
|
I have experienced this too on arm, aarch64,? and x86 so it's not just you.? Pulseaudio will induce the issue with 100% reproducibility for me, but I have experienced it without as well.? I have never been able to pin down the root cause.? My amd64 Ubuntu 20.04 system is working for the moment--no clue why though.? If any specific testing is needed I am available to help as time permits.
73, Ben - KU0HN
A bit more testing just to verify my sanity :-) I stated with a fresh copy of bullseye 32 bit that was last updated on 23FEB2022 running on a Pi 4 8GB. I installed FLRIG and hamlib 4.4 from source. Installed Pat Winlink, ARDOP_GUI, and ARDOP. Ran a test and confirmed that ADROP worked as expected and I could connect to a gateway. Next I ran the apt upgrade command and rebooted the Pi. Afterwards, I attempted the ARDOP connection again but this time ARDOP hangs at PTT during the first transmit cycle forcing me to power down the radio manually in order to stop the TX. Not sure what’s causing it but something in the upgrade process is breaking piardopc.
73, de KM4ACK
|
Hi Jason (and the rest of the group) - I'm apparently having the same issue. In my case, this morning I formatted a card with a 32-bit version of Raspberry Pi OS (from Raspberry Pi Imager) and then installed the Build-a-Pi series of programs. I'm using an IC-7300 so made the necessary adjustments to the radio's settings and those in Pat-Menu that I have long used. I then started Flrig, started Pat-Menu and clicked the START ARDOP Menu and everything seemed to connect appropriately.?? From the ARDOP menu I then selected Action > Connect > Show RMS list > (selected a gateway / highlighted it so the gateway is shown in target and the correct freq is indicated) > Connect and the radio started to transmit but never cycled - it just locked in the transmit cycle. I had to turn off the power to the radio to get it to stop.? I rebooted and experienced the same issue a couple of times more before calling it quits for the evening. I'll try a 64-bit version of the Raspberry Pi OS in the morning and see if that makes any difference. Comments much appreciated. 73, Ken NB6S
|
I have a fresh build on a 64 bit install of Bullseye that is exhibiting the same symptoms.? It's not limited to the 32 bit version.
73,
Jocelyn, AE8JG
|
@Chris Keller I don't think this is a Pat issue. I experienced the same lock up with GARIM trying to use the piardopc modem.
73, de KM4ACK
|
A bit more information. I downloaded Pi OS 32bit dated 2022-01-28. Put an apt hold on the raspberrypi-kernel and updated everything else. Rebooted and the PTT worked as expected. Removed the hold and updated the kernal. After a reboot the PTT again locks the radio in TX after the first connect attempt with piardopc.
73, de KM4ACK
|
Looks like something has changed in the sound code in the Kernel. I'll see if I can find a Pi4 to upgrade and find what is going wrong with ardop but I'm pretty busy at the moment so it may take a while.
73,
John G8BPQ
toggle quoted message
Show quoted text
On Wed, Apr 6, 2022 at 02:27 PM, km4ack wrote:
A bit more information. I downloaded Pi OS 32bit dated 2022-01-28. Put an apt hold on the raspberrypi-kernel and updated everything else. Rebooted and the PTT worked as expected. Removed the hold and updated the kernal. After a reboot the PTT again locks the radio in TX after the first connect attempt with piardopc.
73, de KM4ACK
|
On Thu, Apr 7, 2022 at 12:10 PM, John G8BPQ wrote:
Looks like something has changed in the sound code in the Kernel. I'll see if I can find a Pi4 to upgrade and find what is going wrong with ardop but I'm pretty busy at the moment so it may take a while.
Thanks John! Hopefully it is something simple to fix. Other users have reported that the same issue occurs on a Pi 3 as well. I have instructions on my forum for two work arounds for now. Either put a hold on the kernel or downgrade the kernel. Not the best solution but will allow users to continue using piardopc for the time being.
|
It looks like the way transmit complete is reported has changed.
I've changed the way I test for TX complete? and it seems ok on my
Pi 4 but it could potentially truncate the transmission or slightly
delay the link turnround.
I've uploaded the potential fix to my test download area. Could you
try them and let me know how it goes?
ardopc64 is for 64 bit Intel systems.
Thanks,
John
On 07/04/2022 18:10, John G8BPQ wrote:
toggle quoted message
Show quoted text
Looks like something has changed in the sound code in the Kernel.
I'll see if I can find a Pi4 to upgrade and find what is going
wrong with ardop but I'm pretty busy at the moment so it may take
a while.
73,
John G8BPQ
On Wed, Apr 6, 2022 at 02:27 PM, km4ack wrote:
A bit more information. I downloaded Pi OS 32bit dated
2022-01-28. Put an apt hold on the raspberrypi-kernel and
updated everything else. Rebooted and the PTT worked as
expected. Removed the hold and updated the kernal. After a
reboot the PTT again locks the radio in TX after the first
connect attempt with piardopc.
73, de KM4ACK
|
Just tested the above 32bit piardopc with a friend and it appears to work.? Using Pi4 with Bullseye.
|
The test versions of piardopc worked for me and eliminated the PTT hanging issue. Thanks John!
73, de KM4ACK
|
Likewise tested.? I am using a Signalink/BAP Pi setup and my previous issue was a single transmission (not a hang).? The difference is that the Signalink is a VOX controlled sound card.? The new version of ARDOP works OK here too.
|
I'm curious what new kernel version in the RPi OS drove this change.
Thanks, Lee K5DAT
The test versions of piardopc worked for me and eliminated the PTT hanging issue. Thanks John!
73, de KM4ACK
|
I don’t think it was a kernel issue… It was RPi’s change to PulseAudio that caused the problem from what I understood John to say. Of course, take that with a large dose of salt as I’ve slept several times since… HI! ? Perry K4PWO ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of Lee Bengston Sent: Sunday, May 1, 2022 8:28 PM To: [email protected]Subject: Re: [bpq32] piardopc locks up ? I'm curious what new kernel version in the RPi OS drove this change. ? The test versions of piardopc worked for me and eliminated the PTT hanging issue. Thanks John!
73, de KM4ACK
|
I don't think it was PulseAudio. The same sd card works on the Pi
Zero 2 and not the Pi 4. They use different kernels, which leads me
to suspect a Kernel change.
I'm don't know exactly when it changed, but? 5.15.32-v7l+ has the
problem.
73,
John
On 02/05/2022 03:15, Perry Ogletree
wrote:
toggle quoted message
Show quoted text
I don’t think it was a kernel issue… It was
RPi’s change to PulseAudio that caused the problem from what I
understood John to say. Of course, take that with a large dose
of salt as I’ve slept several times since… HI!
?
Perry K4PWO
?
?
I'm curious what new kernel version in
the RPi OS drove this change.
?
The test versions of piardopc worked
for me and eliminated the PTT hanging issue. Thanks John!
73, de KM4ACK
|
Hi John,
I noticed that piardopc is gone from the test folder on your server. Does the one in the beta folder now have the PTT fix applied?
73, de KM4ACK
|
km4ack