I have updated my gnuradio installation via pybombs today.
Gqrx is no longer working with my RTL-SDR dongle. The gui loads, but the
moment when I start the receiver it works for about a second and then it
crashes with:
rtlsdr_read_async returned with -5
Segmentation fault (core dumped)
I tried different sample rates, but I cannot get it work. To be on the
safe side I rebuilt gr-iqbal and gr-osmosdr and then gqrx, but that does
not fix it. Other applications (gr-air-modes) work well with the new
build and do not crash.
Here is a complete dump of a session:
mark@orion:~/apps/gnuradio/3.7$ gqrx
linux; GNU C++ version 4.6.3; Boost_105300; UHD_003.007.000-1-ga8caec5f
gr-osmosdr v0.1.0-78-g1e8b45d0 (0.1.1git) gnuradio
v3.7.4git-35-g1092e685
built-in source types: file osmosdr fcd rtl rtl_tcp uhd hackrf rfspace
airspy
Using Volk machine: sse4_a_64_orc
gr-osmosdr v0.1.0-78-g1e8b45d0 (0.1.1git) gnuradio
v3.7.4git-35-g1092e685
built-in source types: file osmosdr fcd rtl rtl_tcp uhd hackrf rfspace
airspy
Using device #0 Realtek RTL2838UHIDIR SN: 00000013
Found Rafael Micro R820T tuner
Exact sample rate is: 1500000.014901 Hz
rtlsdr_read_async returned with -5
Segmentation fault (core dumped)
tnx for any help,
Mark
On Fri, Mar 21, 2014 at 12:20 PM, M Dammer [email protected] wrote:
build and do not crash.
built-in source types: file osmosdr fcd rtl rtl_tcp uhd hackrf rfspace
airspy
Using device #0 Realtek RTL2838UHIDIR SN: 00000013
Found Rafael Micro R820T tuner
Exact sample rate is: 1500000.014901 Hz
rtlsdr_read_async returned with -5
Segmentation fault (core dumped)
tnx for any help,
Mark
Mark,
Updated from what previous version?
What’s your system (OS, processor)?
Tom
I updated from a gnuradio 3.7.3 git version (before 3.7.3 was officially
released). I updated the pybombs recipes via git before the update.
“Pybombs update” removed all updateable gnuradio stuff and installed it
new as expected.
I can actually confirm the problem now on two machines. Both running
XUbuntu 12.04 64bit. One with an Intel core 2 due and the other with an
AMD “APU” processor. I usually had no problems running gnuradio, gqrx
and other related applications on both machines.
Can you explain what that rtlsdr_read_async… message means ?
Mark
On 03/21/2014 12:41 PM, M Dammer wrote:
Mark
That message is coming from the rtl-sdr driver code, which is seeing an
error return from a libusb read transaction. Which means there’s
something
wrong in the USB communications path between your PC and the dongle.
–
Marcus L.
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
I cannot see anything being wrong with USB. I tried different Kernels,
different Dongles and they all fail. However booting my live DVD and
starting gqrx (32bit) works.
It looks like some incompatibility between the latest gqrx and my
systems 
Mark
This does not work. GQRX depends on gr-osmosdr and wont compile without
it.
Make sure you have the latest version of rtl-sdr library and gr-osmosdr.
There was a change somewhere and if you have one version more recent
than the other, it can cause issue. So rebuild librtlsdr , then
rebuild gr-osmosdr to use it, then rebuild gqrx.
I remember having this issue as well on my computer. I think there is
some
incompatibility with running gqrx and having gr-osmosdr installed. What
I
did was simply uninstall gr-osmosdr to run gqrx then reinstall it when I
need to use gnuradio with the rtlsdr source. I haven’t had time to debug
further though.
Just updated everything and now both can coexist. I must’ve been running
some old package somewhere.
On Fri, Mar 21, 2014 at 9:51 PM, Sylvain M. [email protected]
wrote:
Make sure you have the latest version of rtl-sdr library and gr-osmosdr.
There was a change somewhere and if you have one version more recent
than the other, it can cause issue. So rebuild librtlsdr , then
rebuild gr-osmosdr to use it, then rebuild gqrx.
Indeed, I have just updated all my packages using pybombs and gqrx
runs fine with rtlsdr.
Alex
I updated and I still have the problem. Checking my syslog brought me to
the following error:
[ 7568.643970] gqrx[9018]: segfault at 7f82cb540ab8 ip 00007f7e89a1b646
sp 00007f7e5affcc70 error 4 in libusb-1.0.so.0.1.0[7f7e89a12000+11000]
and googling this brought me to the following Debian bug report where
someone explicitly mentions a similar problem with a funcube dongle pro
and qthid on Ubuntu 12.04 AMD64 systems:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658136
Well, I think its time for the two yearly reinstall of the systems when
the next LTS is coming out…
Mark