I did some further testing.
I have pipewire disabled and am only using alsa. If I use aplay to send
to the FT-710 sound device, it succeeds. If I open any one of the two
serial ports with something like "cat /dev/ttyUSB0", aplay shows reset
errors in syslog.
So, this is not pipewire, wsjtx or hamlib related, rather some issue
with the RPi USB controller.
The topology of the FT-710 usb is:
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 5, If 3, Class=Human Interface Device, Driver=usbhid,
12M
|__ Port 2: Dev 5, If 1, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 2: Dev 5, If 2, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 2: Dev 5, If 0, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 1: Dev 4, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M
|__ Port 1: Dev 4, If 1, Class=Vendor Specific Class, Driver=cp210x, 12M
The devices are:
Bus 003 Device 005: ID 0d8c:0013 C-Media Electronics, Inc. USB Audio Device
Bus 003 Device 004: ID 10c4:ea70 Silicon Labs CP2105 Dual UART Bridge
Bus 003 Device 002: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0
"TetraHub"
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
It appears that alsa has to be built with debugging enabled, which it's
not. So, maybe build alsa with debug and see what's going on?
Steve WA9OLA
On Sun, 2024-06-30 at 12:07 -0300, Glenn via wsjt-devel wrote:
> FWIW I am finding the same thing here.
> Ft-710
> Pi5
> Ubuntu 24.04 stock pipewire but using x11 not wayland
> Wsjtx 2.7.0-rc3 set to pipewire
> Pressing tune or enable tx would not produce any audio drive on the
> 710
> I then installed pavucontrol.
> When trying to tx audio output in pavucontrol would cycle between the
> 710 and HDMI out every second or so.
> If I then start mumble configured to use pipewire also and then try
> to tx in wsjtx all is now OK.
> Made many QSOs this way with mumble running in the background.
> Dunno why as that is as far as I got troubleshooting.
>
> 73
> Glenn VE9GJ
>
>
>
> On June 30, 2024 11:32:31 a.m. ADT, Steve Brown via wsjt-devel
> <wsjt-devel@lists.sourceforge.net> wrote:
> > Hi Kari,
> >
> > It's installed on both systems.
> >
> > Some more evidence:
> >
> > I can run aplay and output to the fig's sound output device without
> > error. However, if I run wsjtx with the audio output set to the
> > hdmi
> > device, when I run aplay, I get the same "no such device" error.
> >
> > I don't this is a wsjtx issue, rather a problem in pipewire. I'll
> > look.
> >
> > I'm especially suspicious of the rig's long device name.
> >
> > Steve WA9OLA
> >
> > On Sat, 2024-06-29 at 22:27 +0300, Kari Sillanmäki via wsjt-devel
> > wrote:
> > > Hi Steve,
> > >
> > > Do you have "libqt5multimedia5-plugins" installed?
> > >
> > > 73's de Kari, oh2gqc
> > >
> > > On 6/29/24 22:04, Steve Brown via wsjt-devel wrote:
> > > > Hi,
> > > >
> > > > No problem on Ubuntu 24.04 on an amd64, but no audio on RPi 5
> > > > with
> > > > the
> > > > same OS. Receive works on both.
> > > >
> > > > I rebuilt wsjtx so the images are identical on both (2b9d65).
> > > >
> > > > The settings are identical.
> > > >
> > > > The sound output name is
> > > > "alsa_output.usb-C-Media_Electronics_Inc._USB_Audio_Device-
> > > > 00.analog-
> > > > stereo"
> > > >
> > > > The log is spammed with
> > > >
> > > > Jun 28 14:48:00 wsjtx kernel: retire_capture_urb: 1014
> > > > callbacks
> > > > suppressed
> > > > Jun 28 14:48:01 wsjtx pipewire[1007]: spa.alsa: hw:2:
> > > > snd_pcm_status error: No such device
> > > > Jun 28 14:48:01 wsjtx pipewire[1007]: spa.alsa: hw:2:
> > > > snd_pcm_recover error: No such device
> > > > Jun 28 14:48:01 wsjtx pipewire[1007]: spa.alsa: get_status
> > > > error
> > > > Jun 28 14:48:01 wsjtx pipewire[1007]: spa.alsa: hw:2:
> > > > snd_pcm_drop
> > > > No such device
> > > > Jun 28 14:48:01 wsjtx pipewire[1007]: spa.alsa: hw:2: close
> > > > failed:
> > > > No such device
> > > > Jun 28 14:48:01 wsjtx pipewire[1007]: spa.alsa: front:2:
> > > > snd_pcm_drop No such device
> > > > Jun 28 14:48:01 wsjtx pipewire[1007]: spa.alsa: front:2: close
> > > > failed: No such device
> > > > Jun 28 14:48:01 wsjtx kernel: usb 1-2.2: reset full-speed USB
> > > > device number 4 using xhci-hcd
> > > > Jun 28 14:48:03 wsjtx pipewire[1007]: spa.alsa: front:2:
> > > > snd_pcm_drop No such device
> > > > Jun 28 14:48:03 wsjtx pipewire[1007]: spa.alsa: front:2: close
> > > > failed: No such device
> > > > Jun 28 14:48:03 wsjtx kernel: usb 1-2.2: reset full-speed USB
> > > > device number 4 using xhci-hcd
> > > > Jun 28 14:48:05 wsjtx pipewire[1007]: spa.alsa: front:2:
> > > > snd_pcm_drop No such device
> > > > Jun 28 14:48:05 wsjtx pipewire[1007]: spa.alsa: front:2: close
> > > > failed: No such device
> > > > Jun 28 14:48:05 wsjtx kernel: usb 1-2.2: reset full-speed USB
> > > > device number 4 using xhci-hcd
> > > >
> > > > If I set wsjtx audio output to the hdmi audio device, I get FT8
> > > > tones
> > > > and no complaints in the log.
> > > >
> > > > The rig indicates transmit, but no audio, so no RF.
> > > >
> > > > Any suggestions on tracking this down?
> > > >
> > > > I tried uncommenting some of the qDebug calls, but can't
> > > > find/enable
> > > > the output.
> > > >
> > > > Steve WA9OLAwsjt-devel mailing list
> > > > wsjt-devel@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> > > >
> > > wsjt-devel mailing list
> > > wsjt-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> > >
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
