Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base -Powered By Ham CQ DX

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Solar
SFI 147
SN 162
A 10
K 1 Quiet
X-Ray C1.2
Wind 420.5 km/s
Aurora 1
Updated 16:30 UTC HamQSL · N0NBH
Day 80/40m Fair 30/20m Good 17/15m Good 12/10m Fair
Night 80/40m Good 30/20m Good 17/15m Good 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots
Select a band above to load spots
Ready — select a band to fetch live spots

SDRplay RSP1A Driver Issues with Latest GNU Radio 3.10

After upgrading to GNU Radio 3.10.7 on Debian 12, my SDRplay RSP1A is no longer being detected by GQRX or any gr-osmosdr applications. The device shows up in lsusb as '1df7:3010 SDRplay RSP1A' and the API 3.07 drivers install without errors.

However, when I run 'SoapySDRUtil --find', no SDRplay devices are enumerated. Downgrading to GNU Radio 3.9 resolves the issue, but I need the newer features in 3.10 for my weak-signal work.

Anyone successfully running RSP1A with the latest GNU Radio build? I'm wondering if this is a SoapySDR compatibility issue or something deeper in the driver stack.

  • Replies 2
  • Views 778
  • Created
  • Last Reply

Top Posters In This Topic

Most Helpful Posts

  • David Thompson
    David Thompson

    I hit this exact issue last month. The problem is SoapySDRPlay module wasn't recompiled against the new GNU Radio ABI. You need to rebuild it from source against GNU Radio 3.10 - the packaged version

Featured Replies

I hit this exact issue last month. The problem is SoapySDRPlay module wasn't recompiled against the new GNU Radio ABI. You need to rebuild it from source against GNU Radio 3.10 - the packaged version is still linked to 3.9 libraries.

Same problem here with my RSP2pro. I ended up building SoapySDRPlay from the GitHub master branch which has fixes for GNU Radio 3.10. Takes about 10 minutes to compile, then everything works perfectly. The Debian packages are indeed behind.

This is why I stick with the RSPdx - much better Linux support overall. But for your immediate problem, try installing the libsoapysdr0.8-module-sdrplay3 package instead of the regular one. That version has GNU Radio 3.10 compatibility.

  • Guest unlocked, unpinned, locked and pinned this topic
  • Guest locked, unlocked, unpinned and pinned this topic
  • Guest pinned, locked, unpinned and unlocked this topic

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.