OSMOSDR source_c creation failure in op25

Status
Not open for further replies.

FrostWizard4

Member
Joined
Aug 9, 2019
Messages
10
I am fully aware of THIS post and i have followed it multiple times, however whenever i reinstall op25 with ./install.sh i get the same error over and over again:
Code:
osmosdr source_c creation failure
Traceback (most recent call last):
  File "./rx.py", line 921, in <module>
    rx = rx_main()
  File "./rx.py", line 835, in __init__
    self.tb = p25_rx_block(self.options)
  File "./rx.py", line 123, in __init__
    gain_names = self.src.get_gain_names()
AttributeError: 'NoneType' object has no attribute 'get_gain_names'
should i just wipe linux?
(Im using windows 10 as my primary driver but i have a separate partition for linux with ~ 30 GB)
 
Last edited:

boatbod

Member
Joined
Mar 3, 2007
Messages
3,339
Location
Talbot Co, MD
No wipe, we need to find out what's going on otherwise it will keep happening.

Start with the RTL dongle unplugged, execute a "dmesg" command, save the output, plug in the dongle and then re-run the same dmesg command. The additional information which appears the second time should relate to the kernel detecting and loading drivers for the rtl device.

With the dongle plugged in, execute a 'lsusb' command and see ifL device is recognized.

Assuming the device is appearing in the lsusb listing, chances are it needs to be blacklisted properly. Post the debug info from above and we'll see where to go next.
 

FrostWizard4

Member
Joined
Aug 9, 2019
Messages
10
here are all 3 files saved from the terminal output,
help is dmesg without RTL-SDR
helpsdr is with RTL-SDR
lsusb is, lsusb obviously.
 

Attachments

  • help.txt
    60 KB · Views: 6
  • helpsdr.txt
    60.3 KB · Views: 4
  • lsusb.txt
    583 bytes · Views: 4

boatbod

Member
Joined
Mar 3, 2007
Messages
3,339
Location
Talbot Co, MD
The RTL device is being recognized by the kernel, so the probability is that it's not blacklisted correctly.

As superuser, make a text file named /etc/modprobe.d/blacklist-rtl.conf
Code:
blacklist dvb_usb_rtl28xxu
blacklist rtl2832
blacklist rtl2830
blacklist rtl2838

If you already have a file in that location with a similar name, make sure it has the same contents as above.
Reboot and try op25 again.
 

FrostWizard4

Member
Joined
Aug 9, 2019
Messages
10
I opened the file and found exactly what you put,
Code:
blacklist dvb_usb_rtl28xxu
blacklist rtl2832
blacklist rtl2830
blacklist rtl2838
 

FrostWizard4

Member
Joined
Aug 9, 2019
Messages
10
I also used rm to remove op25, reinstalled and got the same error
When i setup op25 on my friends RaspPi he needed 198 updates but it worked
I think the updates made your code fail.
 

boatbod

Member
Joined
Mar 3, 2007
Messages
3,339
Location
Talbot Co, MD
What happens if you run the command "osmocom_fft"?

Please report output of:

apt list --installed | grep rtl
apt list --installed | grep osmo
 

FrostWizard4

Member
Joined
Aug 9, 2019
Messages
10
Osmocom_fft reported with:
Code:
Traceback (most recent call last):
  File "/usr/bin/osmocom_fft", line 33, in <module>
    import osmosdr
  File "/usr/lib/python2.7/dist-packages/osmosdr/__init__.py", line 26, in <module>
    from osmosdr_swig import *
  File "/usr/lib/python2.7/dist-packages/osmosdr/osmosdr_swig.py", line 17, in <module>
    _osmosdr_swig = swig_import_helper()
  File "/usr/lib/python2.7/dist-packages/osmosdr/osmosdr_swig.py", line 16, in swig_import_helper
    return importlib.import_module('_osmosdr_swig')
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
ImportError: No module named _osmosdr_swig

| grep rtl reported with:
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
and..
Code:
librtlsdr-dev/bionic,now 0.6.0-myriadrf1~bionic amd64 [installed]
librtlsdr0/bionic,now 0.6.0-myriadrf1~bionic amd64 [installed,automatic]
python3-reportlab/bionic,bionic,now 3.4.0-3build1 all [installed]
python3-reportlab-accel/bionic,now 3.4.0-3build1 amd64 [installed]
rtl-sdr/bionic,now 0.6.0-myriadrf1~bionic amd64 [installed,automatic]
soapysdr0.6-module-rtlsdr/bionic,now 0.2.4-1 amd64 [installed,automatic]

| grep osmo reported:
Code:
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

gr-osmosdr/bionic,now 0.1.4.127-myriadrf1~bionic amd64 [installed]
libgnuradio-osmosdr0.1.4/bionic,now 0.1.4-14build1 amd64 [installed,upgradable to: 0.1.4.127-myriadrf1~bionic]
libosmosdr0/bionic,now 0.1.8.effcaa7-7 amd64 [installed,automatic]
soapyosmo-common0.6/bionic,now 0.2.5-1build1 amd64 [installed,automatic]
soapysdr0.6-module-osmosdr/bionic,now 0.2.5-1build1 amd64 [installed,automatic]
 

FrostWizard4

Member
Joined
Aug 9, 2019
Messages
10
Code:
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

swig/bionic,now 3.0.12-1 amd64 [installed]
swig3.0/bionic,now 3.0.12-1 amd64 [installed,automatic]
 
S

simpilo

Guest
Why does it keeps saying the warning?
I used the same command boatbod mentioned and I got the same results you had.

swig:
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

swig3.0/stable,now 3.0.12-2 i386 [installed,automatic]
swig/stable,now 3.0.12-2 i386 [installed]

rtl:
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

librtlsdr-dev/stable,now 0.6-1 i386 [installed]
librtlsdr0/stable,now 0.6-1 i386 [installed,automatic]
python3-reportlab-accel/stable,now 3.5.13-1 i386 [installed,automatic]
python3-reportlab/stable,now 3.5.13-1 all [installed,automatic]
rtl-sdr/stable,now 0.6-1 i386 [installed,automatic]
soapysdr0.6-module-rtlsdr/stable,now 0.2.5-1 i386 [installed,automatic]

osmo:
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

gr-osmosdr/stable,now 0.1.4-14+b10 i386 [installed]
libgnuradio-osmosdr0.1.4/stable,now 0.1.4-14+b10 i386 [installed,automatic]
libosmosdr0/stable,now 0.1.8.effcaa7-7+b1 i386 [installed,automatic]
soapyosmo-common0.6/stable,now 0.2.5-1+b12 i386 [installed,automatic]
soapysdr0.6-module-osmosdr/stable,now 0.2.5-1+b12 i386 [installed,automatic]

Looks like APT isn't well used in scripts. Reference apt gives “Unstable CLI Interface” warning

I wouldn't worry about it. My copy of OP25 installed fine. (after 200000000 attempts before I switched to a more Debian based distro).
 

boatbod

Member
Joined
Mar 3, 2007
Messages
3,339
Location
Talbot Co, MD
Sorry for the delay in responding.

The curious thing is that your rtl driver appears to be installed and the dongle is correctly blacklisted in the kernel. The swig package is installed, but you are getting errors when you try to start either osmocom_fft or rx.py. Can you re-run rx.py and post the command line you used along with the complete log for it trying to start. I'd also be interested in whatever text has appeared on the terminal window when rx.py exits.
 
Status
Not open for further replies.
Top