4 Note on SDRPlay RSP1 on Linux

f4exb edited this page 2020-06-24 16:59:14 +02:00

Most distributions will load the msi2500 driver by default that will come in the way of the direct access that SDRangel makes with libmirisdr (and libusb). Thus you will see the SDRPlay in the list of devices and you will be able to select it but it will fail at start time.

Look at dmesg to see if your system has loaded device drivers for the SDR module. They are incompatible with the binary-only driver. Relevant output:

  [20084.148384] msi2500 3-2:1.0: Registered as swradio0
  [20084.148386] msi2500 3-2:1.0: SDR API is still slightly experimental and functionality changes may follow

In this case, edit /etc/modprobe.d/blacklist.conf and add:

  blacklist sdr_msi3101
  blacklist msi001
  blacklist msi2500

Then, unplug the SDRPlay, remove the offending modules and restart the module loading service (or whatever loads the modules on your Linux distribution):

  sudo rmmod msi001 msi2500
  sudo systemctl restart systemd-modules-load.service

These are the same actions as for Pothos that are detailed here

• Home
• Quick start
• Quick start legacy (v6)
  • Main Window
  • Spectrum
• Hardware requirements
• High DPI displays
• Compile in Linux
• Compile in Windows
• Compile in MacOS
• History and major releases
• Audio related
  • Notes on Pulseaudio setup
  • Audio management
  • Networking audio
  • WSJT X
  • Decoding Morse from audio
  • Text to speech
• Plugins
  • Channel plugins with special conditions
  • Channel Rx plugins
  • Channel Tx plugins
  • Channel MIMO plugins
  • Plugins for special devices
  • Device Rx plugins
  • Device Tx plugins
  • Device MIMO plugins
  • Feature plugins
  • Notes
    • SDRPlay RSP1 on Linux
    • Soapy Remote
    • SDRPlay and SoapySDR (obsolete)
• Advanced
  • Developers notes
• Server and API
  • SDRangel server
  • Web (http) REST API
  • Reverse API