I’m almost there at last! Is this a permission issue?
I notice that there aren’t any USB devices listed under /dev. Should
there be?
Using device #0: ezcap USB 2.0 DVB-T/DAB/FM dongle
usb_open error -3
Traceback (most recent call last):
File “./simple_fm_rcv.py”, line 949, in
tb = simple_fm_rcv(devid=options.devid, volume=options.volume,
rdsfile=options.rdsfile, gain=options.gain, freq=options.freq,
xmlport=options.xmlport, arate=options.arate, mute=options.mute,
ftune=options.ftune, ant=options.ant, subdev=options.subdev,
ahw=options.ahw, deemph=options.deemph, prenames=options.prenames,
prefreqs=options.prefreqs)
File “./simple_fm_rcv.py”, line 402, in init
self.osmosdr_source_c_0 = osmosdr.source_c( args=“nchan=” + str(1)
" " + devid )
File
“/usr/local/lib/python2.7/site-packages/osmosdr/osmosdr_swig.py”, line
431, in source_c
return _osmosdr_swig.source_c(args)
RuntimeError: Failed to open rtlsdr device.
Try running the test program that comes with one of the libraries [can’t
remember which one OTTOMH] as yourself and as root. That should answer
the permissions question.
Try running the test program that comes with one of the libraries [can’t
remember which one OTTOMH] as yourself and as root. That should answer
the permissions question.
Thanks Alex,
As me, I receive an open usb error and as root I receive a can’t find
librtlsdr.so.0 error. The library is in /usr/local/lib.
How might I set the usb permission?
[phil@localhost src (master)]$ rtl_test -t
Found 1 device(s):
0: ezcap USB 2.0 DVB-T/DAB/FM dongle
Using device 0: ezcap USB 2.0 DVB-T/DAB/FM dongle
usb_open error -3
Failed to open rtlsdr device #0.
[phil@localhost src (master)]$ su
Password:
[root@localhost src (master)]# rtl_test -t
rtl_test: error while loading shared libraries: librtlsdr.so.0: cannot
open shared object file: No such file or directory
[root@localhost src (master)]#
In case it’s not obvious, the hex numbers are the VID/PID of the USB
device. You can see these for connected USB devices with lsusb. The MODE
parameter determines the permissions, in this case RW for everybody.
Once the rules are created, reload udev and reinsert the device.
To be precise, reloading a service [usually] results in it re-reading
its config without restarting it. Restarting it, stops it and starts it.
Restarting udev will achieve the same end result in this case as
reloading it. With some more heavyweight services [eg squid, apache] a
reload is a lot quicker and less disruptive than a restart.
In case it’s not obvious, the hex numbers are the VID/PID of the USB
device. You can see these for connected USB devices with lsusb. The MODE
parameter determines the permissions, in this case RW for everybody.
Once the rules are created, reload udev and reinsert the device.
Thanks again Alex,
By “reload udev” do you mean restart udevd?
–
Regards,
Phil
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.