Re: New to Raspberry Pi and this group
I have done an extensive search on internet for solutions to the problem I have been having. It seems to be specific to the FUNCube Dongle Pro + and GQRX on the Raspberry Pi. It seems to be a problem that many are having, not just me. It has nothing to do with how much current the FUBCube is drawing. It is about the same for all three SDR dongles I am using and the other two, the RTL-SDR Blog V3 and the Airspy Discovery HF+, all work fine with GQRX on the Raspberry Pi. I have tried a couple suggested solutions I found but none of them worked (when the FUNCube is started, the mouse and keyboard lock up). At this time I am giving up on using the FUNCube with GQRX on the Pi. Maybe it will work on another SDR program. I still have two other SDRmodules that DO work.
73, Zack W9SZ
That line is already in the config.txt file. So much for that.
Zack W9SZ
The problem I have had is evidently a common and well-known problem with the FUNCube dongle on GQRX. After some searching, I found a site that outlined a repair. It said
Add this
line to the bottom of /boot/config.txt: ? dtoverlay=dwc2,dr_mode=host
I am going to try that this evening.
Zack W9SZ
Disconnect the USB keyboard and mouse to check the difference in current draw with each of those. And remember, you are limited to 1.2 amps TOTAL current combined from all 4 USB ports
Get
|
Re: New to Raspberry Pi and this group
That line is already in the config.txt file. So much for that.
Zack W9SZ
The problem I have had is evidently a common and well-known problem with the FUNCube dongle on GQRX. After some searching, I found a site that outlined a repair. It said
Add this
line to the bottom of /boot/config.txt: ? dtoverlay=dwc2,dr_mode=host
I am going to try that this evening.
Zack W9SZ
Disconnect the USB keyboard and mouse to check the difference in current draw with each of those. And remember, you are limited to 1.2 amps TOTAL current combined from all 4 USB ports
Get
|
Re: New to Raspberry Pi and this group
The problem I have had is evidently a common and well-known problem with the FUNCube dongle on GQRX. After some searching, I found a site that outlined a repair. It said
Add this
line to the bottom of /boot/config.txt: ? dtoverlay=dwc2,dr_mode=host
I am going to try that this evening.
Zack W9SZ
Disconnect the USB keyboard and mouse to check the difference in current draw with each of those. And remember, you are limited to 1.2 amps TOTAL current combined from all 4 USB ports
Get
|
Re: New to Raspberry Pi and this group
Also, the current at 5v will be 2.4x the current at 12v.
Get
Disconnect the USB keyboard and mouse to check the difference in current draw with each of those. And remember, you are limited to 1.2 amps TOTAL current combined from all 4 USB ports
Get
|
Re: New to Raspberry Pi and this group
Disconnect the USB keyboard and mouse to check the difference in current draw with each of those. And remember, you are limited to 1.2 amps TOTAL current combined from all 4 USB ports
Get
|
Re: New to Raspberry Pi and this group
Chuck N7CHS
toggle quoted message
Show quoted text
On 8/6/2024 8:44 PM, Zack Widup via groups.io wrote: I have no way of measuring the current on a USB-C line.
|
Re: New to Raspberry Pi and this group
I got curious and used a 12 to 5 volt adaptor with a USB-C plug on it. I have no way of measuring the current on a USB-C line. But I can measure the current on the 12 volt line. Current at 5 volts is probably slightly more than twice the 12 volt draw.
With the Raspberry Pi 4 with a USB keyboard and mouse connected to the USB 2.0 ports and an HDMI cable to a monitor, after it's booted up and in a quiescent state, I measure 120 mA draw at 12.4 volts to the adaptor. Plugging in each SDR dongle I have, one at a time, into a USB 3.0 port, I measure on the 12 v line: RTL-SDR Blog V3 = 180 mA FUNCube Pro + = 220 mA Airspy Discovery HF+ = 190 mA
These do not look excessive to me and are well within the 3A maximum draw of the Raspberry Pi. I cannot imagine the USB ports drawing anything near their maximum capacity with those measurements. I don't think that's the problem. These are with the 32 bit Raspberry Pi OS. I installed the 64 bit OS on another micro-SD card and installed GQRX on it. I haven't measured the currents on that, but the same thing happens. The RTL-SDR Blog V3 and the Airspy unit continue to work fine when I click on "play SDR." The Funcube causes the mouse to freeze up. I think there is some bug in the software for the Funcube.
By the way, my laptop draws 5 amps at 12 volts. That's what I'm trying to get away from. It looks like the Raspberry Pi will be far below that current draw.
Zack W9SZ
Most SDR dongles use quite a bit of current. The issue with the FUNCube causing loss of mouse is very typical of what happens when you exceed the power capabilities of the USB ports. You need a powered USB hub to get around that limitation
Get
|
Re: fldigi / flrig Pi Question
So I followed the instructions . Everything looked great, program seemed to compile. I? get all the way to the last step to install : make && sudo make install
and I get the following error:
make[3]: Entering directory '/home/mark/dev/fldigi-4.2.05/src'
? CXX ? ? ?network/fldigi-xmlrpc.o
g++: error: unrecognized command-line option ‘-mno-3dnow’
g++: error: unrecognized command-line option ‘-mfpmath=sse’
make[3]: *** [Makefile:5452: network/fldigi-xmlrpc.o] Error 1
make[3]: Leaving directory '/home/mark/dev/fldigi-4.2.05/src'
Any thoughts? (Please remember, I'm very new at this)
-Mark
N2UEM
|
Re: fldigi / flrig Pi Question
Thanks! I am going to give it a try this weekend when I have a few min to go threw it methodically. I will certainly update you on my progress!
?
Mark
N2UEM
|
Re: New to Raspberry Pi and this group
Most SDR dongles use quite a bit of current. The issue with the FUNCube causing loss of mouse is very typical of what happens when you exceed the power capabilities of the USB ports. You need a powered USB hub to get around that limitation
Get
|
New to Raspberry Pi and this group
I just recently joined this group. I'm new to the Raspberry Pi and actually new to Linux. My original purpose for the Ras[berry Pi was to use it as a spectrum monitor for the IF of microwave transverters. This would hopefully take one unknown (the frequency) out of the picture when trying to peak a signal with a dish antenna.? My laptop is an energy hog and is also bulky. Not very conducive to microwave hilltopping operations.
I got a Raspberry Pi 4B. I found these instructions for installation of a program called Freqshow on the Adafruit website:
This seems ideal and exactly what I want. The only problem right now is that the Adafruit 3.5 inch PiTFT display is nowhere to be found. Everyone who carries them is out of them. So that project is on the back burner right now.
I successfully installed the OS for the Raspberry Pi on a 64 Gb micro-SD card. Then I found this site:
So far, I have successfully installed GNU Radio, GQRX, RTL-SDR, FLDIGI, FLRIG, WSJTX , JS8CALL and QSSTV on the Pi using the instructions there. I think it's successful because FLRIG connects OK to my FT897D using a CT62 USB cable.It seems more limited than what the webpage shows with installation instructions shows. I am only able to change frequency and mode of the radio, For some reason I have no controls shown for volume, squelch, noise reduction, etc. Maybe these aren't available for that rig in that program.
GQRX seems to work OK with the SDR dongles I have, except when I use it with the FUNCube dongle, the mouse locks up and I have to unplug the dongle to get mouse use back again. I'm not sure why that is, either. It works fine with RTL-SDR Blog V3 and Airspy Discovery HF+ dongles.
Hopefully some day the 3.5 inch PiTFT displays will be available again and I can start playing around with using that on the Raspberry Pi.
73, Zack W9SZ
|
Re: fldigi / flrig Pi Question
One of the issues with Linux is package management—meaning the software isn’t always kept up to date by the volunteer package owner. It’s pretty easy for the software to fall out of date, especially something like the fldigi suite.?
The good news is the fldigi suite is relatively easy to compile and install. Navigate to??and the source is there to roll your own. You’ll probably want to remove the fldigi suite before you start though.
The building instructions are at??for the Pi. There’s also a script to take care of most of this for you at??however I’ve never run it.
You should be able to download that last script, run it in a terminal session and have it build for you—but please post back if you are still having issues.
Thanks, Dan
— . Same errors, more misspelings.
toggle quoted message
Show quoted text
On Aug 2, 2024, at 12:59?PM, Mark Acierno <acierno@...> wrote:
?
Question for any fldigi / flrig gurus. I installed both on a new Raspberry Pi 5 using the “add /remove software “ available in the GUI. Noticed that my FT-710 wasn’t supported, further investigation shows that I am running version 1.4.7 of flrig. I believe the latest is 2.2 - so I tried : sudo apt-get -y flrig. The system tells me that I already have the latest version 1.4.7–1. ? am I correct that there’s a more recent version. Also, I posted a question about this on facebook and was told the FT-710 was not supported on any version of flrig - is this correct? If it is supported, how do I get the latest version. Please keep in mind I am a Pi novice.....
Any guidance would be greatly appreciated
|
Re: fldigi / flrig Pi Question
Sorry, FT-710. On 02/08/2024 15:38 EDT Nigel Gunn, G8IFF/W8IFF <nigel@...> wrote:
FL-701 IS in the latest version. (2.0.05)
Get it from the FLDIGI website, not from your out of date repository.
On 02/08/2024 14:17 EDT Mark Acierno <acierno@...> wrote:
Question for any fldigi / flrig gurus. I installed both on a new Raspberry Pi 5 using the “add /remove software “ available in the GUI. Noticed that my FT-710 wasn’t supported, further investigation shows that I am running version 1.4.7 of flrig. I believe the latest is 2.2 - so I tried : sudo apt-get -y flrig. The system tells me that I already have the latest version 1.4.7–1. ? am I correct that there’s a more recent version. Also, I posted a question about this on facebook and was told the FT-710 was not supported on any version of flrig - is this correct? If it is supported, how do I get the latest version. Please keep in mind I am a Pi novice.....
Any guidance would be greatly appreciated
Nigel A. Gunn, ///shoulders.outwards.resolutions tel +1-937-971-0366
Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail nigel@... www
Nigel A. Gunn, ///shoulders.outwards.resolutions tel +1-937-971-0366 Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail nigel@... www
|
Re: fldigi / flrig Pi Question
FL-701 IS in the latest version. (2.0.05) Get it from the FLDIGI website, not from your out of date repository. On 02/08/2024 14:17 EDT Mark Acierno <acierno@...> wrote:
Question for any fldigi / flrig gurus. I installed both on a new Raspberry Pi 5 using the “add /remove software “ available in the GUI. Noticed that my FT-710 wasn’t supported, further investigation shows that I am running version 1.4.7 of flrig. I believe the latest is 2.2 - so I tried : sudo apt-get -y flrig. The system tells me that I already have the latest version 1.4.7–1. ? am I correct that there’s a more recent version. Also, I posted a question about this on facebook and was told the FT-710 was not supported on any version of flrig - is this correct? If it is supported, how do I get the latest version. Please keep in mind I am a Pi novice.....
Any guidance would be greatly appreciated
Nigel A. Gunn, ///shoulders.outwards.resolutions tel +1-937-971-0366 Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail nigel@... www
|
fldigi / flrig Pi Question
Question for any fldigi / flrig gurus. I installed both on a new Raspberry Pi 5 using the “add /remove software “ available in the GUI. Noticed that my FT-710 wasn’t supported, further investigation shows that I am running version 1.4.7 of flrig. I believe the latest is 2.2 - so I tried : sudo apt-get -y flrig. The system tells me that I already have the latest version 1.4.7–1. ? am I correct that there’s a more recent version. Also, I posted a question about this on facebook and was told the FT-710 was not supported on any version of flrig - is this correct? If it is supported, how do I get the latest version. Please keep in mind I am a Pi novice.....
Any guidance would be greatly appreciated
|
Re: 2B direwolf gpio errors
Hello Jim,
You need to install the required dependency packages and then
compile the Direwolf 1.8-DEV (not 1.6) meaning the DEV branch of
Direwolf:
??
--David
KI6ZHD
On 07/24/2024 08:44 PM, Jim KX0U wrote:
toggle quoted message
Show quoted text
Thanks, David, for the information.
I have compiled direwolf 1.6 according to the steps listed in
the PDF you provided a link to.? However, I didn't get the
"Includes optional support for:? libgpiod" I should have.? (I
did successfully install gpiod and libgpiod-dev prior to
building direwolf.)
Can anyone recommend additional steps I should take to get
the required support compiled into direwolf?
73,
Jim? KX0U
On Wed, Jul 24, 2024 at
9:02?AM David Ranch via
<rpi4hamradio-groupsio= [email protected]>
wrote:
Hello Jim,
A recent Raspberry Pi OS upgrade made many disruptive
changes including deprecating the old way of interfacing to
the GPIO pins.? To resolve this for Direwolf you need to
compile a new Direwolf using the Direwolf DEV branch which
will bring you up to the 1.8-D version:
?? Section 7.2.2
??
--David
KI6ZHD
On 07/23/2024 09:49 PM, Jim KX0U wrote:
I'm getting an error when I try to use direwolf with GPIO configured for PTT.
I'm running Raspberry Pi OS on a Pi 2B.
Raspberry Pi OS with desktop and recommended software
Release date: July 4th 2024
System: 32-bit
Kernel version: 6.6
Debian version: 12 (bookworm)
Any suggestions for troubleshooting or alternatives would be appreciated.
$ cat direwolf.conf
PTT GPIO 13
ADEVICE plughw:2,0
$ direwolf
Dire Wolf version 1.6
Includes optional support for: gpsd hamlib cm108-ptt
Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument
$ sudo direwolf -c ~/direwolf.conf
Dire Wolf version 1.6
Includes optional support for: gpsd hamlib cm108-ptt
Reading config file /home/radio/direwolf.conf
Audio device for both receive and transmit: plughw:2,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument
$ ls -ld /sys /sys/class /sys/class/gpio /sys/class/gpio/export
dr-xr-xr-x 12 root root 0 Dec 31 1969 /sys
drwxr-xr-x 59 root root 0 Dec 31 1969 /sys/class
drwxrwxr-x 2 root gpio 0 Jul 23 22:32 /sys/class/gpio
--w--w---- 1 root gpio 4096 Jul 23 22:32 /sys/class/gpio/export
$ ls -l /sys/class/gpio/
total 0
--w--w---- 1 root gpio 4096 Jul 23 22:32 export
lrwxrwxrwx 1 root gpio 0 Jul 23 22:32 gpiochip512 -> ../../devices/platform/soc/3f200000.gpio/gpio/gpiochip512
lrwxrwxrwx 1 root gpio 0 Jul 23 22:32 gpiochip566 -> ../../devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5.2/1-1.5.2:1.0/gpio/gpiochip566
--w--w---- 1 root gpio 4096 Jul 23 22:32 unexport
$ lsmod | grep gpio
raspberrypi_gpiomem 12288 0
$
|
Re: 2B direwolf gpio errors
Thanks, David, for the information.
I have compiled direwolf 1.6 according to the steps listed in the PDF you provided a link to.? However, I didn't get the "Includes optional support for:? libgpiod" I should have.? (I did successfully install gpiod and libgpiod-dev prior to building direwolf.)
Can anyone recommend additional steps I should take to get the required support compiled into direwolf?
73, Jim? KX0U
On Wed, Jul 24, 2024 at 9:02?AM David Ranch via <rpi4hamradio-groupsio= [email protected]> wrote:
Hello Jim,
A recent Raspberry Pi OS upgrade made many disruptive changes
including deprecating the old way of interfacing to the GPIO pins.?
To resolve this for Direwolf you need to compile a new Direwolf
using the Direwolf DEV branch which will bring you up to the 1.8-D
version:
?? Section 7.2.2
??
--David
KI6ZHD
On 07/23/2024 09:49 PM, Jim KX0U wrote:
I'm getting an error when I try to use direwolf with GPIO configured for PTT.
I'm running Raspberry Pi OS on a Pi 2B.
Raspberry Pi OS with desktop and recommended software
Release date: July 4th 2024
System: 32-bit
Kernel version: 6.6
Debian version: 12 (bookworm)
Any suggestions for troubleshooting or alternatives would be appreciated.
$ cat direwolf.conf
PTT GPIO 13
ADEVICE plughw:2,0
$ direwolf
Dire Wolf version 1.6
Includes optional support for: gpsd hamlib cm108-ptt
Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument
$ sudo direwolf -c ~/direwolf.conf
Dire Wolf version 1.6
Includes optional support for: gpsd hamlib cm108-ptt
Reading config file /home/radio/direwolf.conf
Audio device for both receive and transmit: plughw:2,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument
$ ls -ld /sys /sys/class /sys/class/gpio /sys/class/gpio/export
dr-xr-xr-x 12 root root 0 Dec 31 1969 /sys
drwxr-xr-x 59 root root 0 Dec 31 1969 /sys/class
drwxrwxr-x 2 root gpio 0 Jul 23 22:32 /sys/class/gpio
--w--w---- 1 root gpio 4096 Jul 23 22:32 /sys/class/gpio/export
$ ls -l /sys/class/gpio/
total 0
--w--w---- 1 root gpio 4096 Jul 23 22:32 export
lrwxrwxrwx 1 root gpio 0 Jul 23 22:32 gpiochip512 -> ../../devices/platform/soc/3f200000.gpio/gpio/gpiochip512
lrwxrwxrwx 1 root gpio 0 Jul 23 22:32 gpiochip566 -> ../../devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5.2/1-1.5.2:1.0/gpio/gpiochip566
--w--w---- 1 root gpio 4096 Jul 23 22:32 unexport
$ lsmod | grep gpio
raspberrypi_gpiomem 12288 0
$
|
Re: 2B direwolf gpio errors
Another option is downgrading the kernel to 6.1.74 which was the last kernel with the deprecated GPIO. A lot more software will be affected for GPIO access and this fix will fix it for all
sudo rpi-update d86b5843d68b9972a5430a6d3da1b271cfc83521
Get
Hello Jim,
A recent Raspberry Pi OS upgrade made many disruptive changes including deprecating the old way of interfacing to the GPIO pins.? To resolve this for Direwolf you need to compile a new Direwolf using the Direwolf DEV branch which will bring you up to the 1.8-D version:
?? Section 7.2.2
??
--David
KI6ZHD
On 07/23/2024 09:49 PM, Jim KX0U wrote:
I'm getting an error when I try to use direwolf with GPIO configured for PTT.
I'm running Raspberry Pi OS on a Pi 2B.
Raspberry Pi OS with desktop and recommended software
Release date: July 4th 2024
System: 32-bit
Kernel version: 6.6
Debian version: 12 (bookworm)
Any suggestions for troubleshooting or alternatives would be appreciated.
$ cat direwolf.conf
PTT GPIO 13
ADEVICE plughw:2,0
$ direwolf
Dire Wolf version 1.6
Includes optional support for: gpsd hamlib cm108-ptt
Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument
$ sudo direwolf -c ~/direwolf.conf
Dire Wolf version 1.6
Includes optional support for: gpsd hamlib cm108-ptt
Reading config file /home/radio/direwolf.conf
Audio device for both receive and transmit: plughw:2,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument
$ ls -ld /sys /sys/class /sys/class/gpio /sys/class/gpio/export
dr-xr-xr-x 12 root root 0 Dec 31 1969 /sys
drwxr-xr-x 59 root root 0 Dec 31 1969 /sys/class
drwxrwxr-x 2 root gpio 0 Jul 23 22:32 /sys/class/gpio
--w--w---- 1 root gpio 4096 Jul 23 22:32 /sys/class/gpio/export
$ ls -l /sys/class/gpio/
total 0
--w--w---- 1 root gpio 4096 Jul 23 22:32 export
lrwxrwxrwx 1 root gpio 0 Jul 23 22:32 gpiochip512 -> ../../devices/platform/soc/3f200000.gpio/gpio/gpiochip512
lrwxrwxrwx 1 root gpio 0 Jul 23 22:32 gpiochip566 -> ../../devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5.2/1-1.5.2:1.0/gpio/gpiochip566
--w--w---- 1 root gpio 4096 Jul 23 22:32 unexport
$ lsmod | grep gpio
raspberrypi_gpiomem 12288 0
$
|
Re: 2B direwolf gpio errors
Hello Jim,
A recent Raspberry Pi OS upgrade made many disruptive changes
including deprecating the old way of interfacing to the GPIO pins.?
To resolve this for Direwolf you need to compile a new Direwolf
using the Direwolf DEV branch which will bring you up to the 1.8-D
version:
?? Section 7.2.2
??
--David
KI6ZHD
On 07/23/2024 09:49 PM, Jim KX0U wrote:
toggle quoted message
Show quoted text
I'm getting an error when I try to use direwolf with GPIO configured for PTT.
I'm running Raspberry Pi OS on a Pi 2B.
Raspberry Pi OS with desktop and recommended software
Release date: July 4th 2024
System: 32-bit
Kernel version: 6.6
Debian version: 12 (bookworm)
Any suggestions for troubleshooting or alternatives would be appreciated.
$ cat direwolf.conf
PTT GPIO 13
ADEVICE plughw:2,0
$ direwolf
Dire Wolf version 1.6
Includes optional support for: gpsd hamlib cm108-ptt
Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument
$ sudo direwolf -c ~/direwolf.conf
Dire Wolf version 1.6
Includes optional support for: gpsd hamlib cm108-ptt
Reading config file /home/radio/direwolf.conf
Audio device for both receive and transmit: plughw:2,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument
$ ls -ld /sys /sys/class /sys/class/gpio /sys/class/gpio/export
dr-xr-xr-x 12 root root 0 Dec 31 1969 /sys
drwxr-xr-x 59 root root 0 Dec 31 1969 /sys/class
drwxrwxr-x 2 root gpio 0 Jul 23 22:32 /sys/class/gpio
--w--w---- 1 root gpio 4096 Jul 23 22:32 /sys/class/gpio/export
$ ls -l /sys/class/gpio/
total 0
--w--w---- 1 root gpio 4096 Jul 23 22:32 export
lrwxrwxrwx 1 root gpio 0 Jul 23 22:32 gpiochip512 -> ../../devices/platform/soc/3f200000.gpio/gpio/gpiochip512
lrwxrwxrwx 1 root gpio 0 Jul 23 22:32 gpiochip566 -> ../../devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5.2/1-1.5.2:1.0/gpio/gpiochip566
--w--w---- 1 root gpio 4096 Jul 23 22:32 unexport
$ lsmod | grep gpio
raspberrypi_gpiomem 12288 0
$
|
Re: 2B direwolf gpio errors
I think this is the same issue.? Might give it a try on Debian version: 11 (bullseye).
?
Hope this helps...
|
Mark Acierno
Nigel Gunn, G8IFF/W8IFF