v 17.5 sudden failure SDRPlay RSP1A

[Richard Bown]

Hi

All nicely working for ages

then  cant find device.

I know it works as the SDRPlay sw works on windows 10 and this version
of linux LM22.2

richard@richard-Inspiron-3580:~$ SoapySDRUtil --probe="driver=sdrplay"
######################################################
##     Soapy SDR -- the SDR abstraction library     ##
######################################################

Probe device driver=sdrplay
[INFO] devIdx: 0
[INFO] SerNo: 1807071393
[INFO] hwVer: 255
[INFO] rspDuoMode: 0
[INFO] tuner: 1
[INFO] rspDuoSampleFreq: 0.000000
[ERROR] SelectDevice Error: sdrplay_api_Fail
Error probing device: SelectDevice() failed

richard@richard-Inspiron-3580:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp.
Integrated_Webcam_HD
Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 011: ID 1df7:3000 SDRplay RSP1a
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Any ideas please

Thanks

--
Best wishes /73
Richard Bown

Email : ric...@g8jvm.com

HTTP : https://www.g8jvm.com

##############################################################################

Ham Call: G8JVM . QRV: HF + 50-432 MHz + Microwave
Maidenhead QRA: IO82SP38, LAT. 52.6620 N LONG. 2.4696 W
VHF: 6mtrs 200W, 4mtrs 150W, 2mtrs 300W, 70cms 200W,
Microwave: 1296MHz 90W, 2320MHz 90W, 3400MHz 15W, 5760MHz 10W & 10368MHz 5W
OS: Linux Mint 21.3 Victoria, on a Dell Inspiron 3580 laptop
##############################################################################

[Dave Baxter]

Hi.

Did you get a recent Kernel update, like many others did recently?

My system now doesn't recognise the keyboard after a cold boot!

I have to re-plug it to resume normal service after every cold start.

I guess you've tried all the usual stuff though.

New kernel here is 6.1.158-1

73

Dave G0WBX 

If it aint broke, hit it harder.

--
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+uns...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/gqrx/f1903c02-481c-40e8-9c8c-8581263463d3%40g8jvm.com.

[Richard Bown]

Just did a apt update, and there were a few

starting from the console

gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.10.9.2
built-in source types: file fcd rtl_tcp rfspace soapy redpitaya 
rx_nb_cc :info: set_min_output_buffer on block 12 to 32768
Resampling audio 96000 -> 48000
BandPlanFile is /home/richard/.config/gqrx/bandplan.csv
BookmarksFile is /home/richard/.config/gqrx/bookmarks.csv
gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.10.9.2
built-in source types: file fcd rtl_tcp rfspace soapy redpitaya 

[INFO] devIdx: 0
[INFO] SerNo: 1807071393
[INFO] hwVer: 255
[INFO] rspDuoMode: 0
[INFO] tuner: 1
[INFO] rspDuoSampleFreq: 0.000000

[INFO] Using format CF32.
[WARNING] Not updating IFGR gain because AGC is enabled
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt.
You must not let any exception whatsoever propagate through Qt code.

Gqrx started and the QT exception was when run

crash message 

inhierarchical block source_impl, output is not connected internally

Oh what fun 

To view this discussion visit https://groups.google.com/d/msgid/gqrx/CABDW77KhEWPmg11pdiFX7q8Cex4ceELEKhnvd2q_H_vyK%2Bfemw%40mail.gmail.com.

[Dave Baxter]

Hmmm...

I built GQRX and Soapy from source whe a friend gave me an old (genuine) original SDRPlay.

It worked well for months.

Then 'a Kernel update' caused creeping time slippage, that even recompiling didn't fix.

Then the change from LMDE 4 to 6, and I've never got it working again even from source.

I love Linux, but it can be soooo...  Frustrating at times.

And I'm considering getting NI GPIB drivers compiled and installed on one box.  "What am I thinking of!"  I must be mad.

73.

Dave.

To view this discussion visit https://groups.google.com/d/msgid/gqrx/85e92a03-73db-4a31-9a46-6367ada41aa0%40g8jvm.com.

[Richard Bown]

Took the bull by the horns and updated the shack laptop to LM22.2 

used the SoapySDR and SoapySDRPlay directories from the previous install, recompiled gqrx 2.17.5

after compiling ran make install on all. loaded the gr-osmosdr  from repos

and ran it

UGHHHHHHHHHHHHHHHHHHHH !

same as before

Loaded SDRPLAY connect and that runs.  too complicated !

so played with the config , and on both laptops running Linux Mint 22.2 the device string soapy=2

and both working now 

now to put the stuff back on the shack laptop again ! 

Richard

[Chris Vine]

It looks like a packaging issue. What may have happened is that a
recent distribution upgrade has updated your version of the SoapySDRPlay
plugin without updating also SDRPlay's driver. For example the latest
version of SoapySDRPlay3 requires v3.15 or later of the driver
(https://www.sdrplay.com/downloads/).

What was your previous and current version of th SoapySDRPlay plugin
and what driver are you using? (Note also that SoapySDRPlay3 requires
you to start the driver as a daemon process, usually via systemd,
whereas SoapySDRPlay2 does not.)

Chris

[Stephen Matthias]

I see that a number of drug dealers have infiltrated my forum-gqrx.  Is there any way that these drug dealer advertisements can be filtered out?

[Robin Gape]

Stephen,

if Google hasn’t already filtered a spam message out, the only obvious option is to view the mail on the web, and select the option to mark the email as spam or one of the other options. Other than that, marking mail as junk, if your mail client supports that option, is about the only option left to one as a subscriber.

If one is an owner, then it’s possible to set restrictions as to who can join the group. Probably it’s currently set to Public Access, but it’s also possible to set Approval Required, or Private Membership which means that the group can only be joined by an invitation from a group owner or administrator.

It’s frustrating, though it could be much worse than the experience on this group.

73,

Robin, G8DQX

[Richard Bown]

The alternative solution is simple, set up a mail filter to delete, look the domain  the bit after the @, most of it is coming from addresses in domains,you would never get mail from,  so filter on the domains,  that's what I do

Richard

Get BlueMail for Android