Hi all,
I have compiled and installed rtl-sdr on CentOS 6 following instructions. Everything compiles without errors, but: - when I run rtl_test I get the following errors: 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 Found Rafael Micro R820T tuner Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
Info: This tool will continuously read from the device, and report if samples get lost. If you observe no further output, everything is fine.
Reading samples in async mode... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling...
Library error 0, exiting...
If I run rtl_tcp I get the following errors when the client tries to connect: Found 1 device(s). Found Rafael Micro R820T tuner Using ezcap USB 2.0 DVB-T/DAB/FM dongle Tuned to 100000000 Hz. listening... Use the device argument 'rtl_tcp=192.168.33.99:8767' in OsmoSDR (gr-osmosdr) source to receive samples in GRC and control rtl_tcp parameters (frequency, gain, ...). client accepted! set freq 145000000 cb transfer status: 5, canceling... cb transfer status: 5, canceling... rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 set sample rate 1024000 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 set freq correction 4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 worker cond timeout Signal caught, exiting! comm recv bye Signal caught, exiting! all threads dead.. listening...
The same client connects without errors to another rtl_tcp instance on a Windows 7 computer, with the same module.
Any help is greatly appreciated.
Thanks, Dan
This message looks coming from libusb. Maybe you check that lib source to understand what error code 5 stands for....
Have you tried to run app as root ? Le 6 oct. 2013 22:34, "Dan" yo3ggx@gmail.com a écrit :
Hi all,
I have compiled and installed rtl-sdr on CentOS 6 following instructions. Everything compiles without errors, but:
- when I run rtl_test I get the following errors:
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 Found Rafael Micro R820T tuner Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
Info: This tool will continuously read from the device, and report if samples get lost. If you observe no further output, everything is fine.
Reading samples in async mode... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling...
Library error 0, exiting...
If I run rtl_tcp I get the following errors when the client tries to connect: Found 1 device(s). Found Rafael Micro R820T tuner Using ezcap USB 2.0 DVB-T/DAB/FM dongle Tuned to 100000000 Hz. listening... Use the device argument 'rtl_tcp=192.168.33.99:8767' in OsmoSDR (gr-osmosdr) source to receive samples in GRC and control rtl_tcp parameters (frequency, gain, ...). client accepted! set freq 145000000 cb transfer status: 5, canceling... cb transfer status: 5, canceling... rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 set sample rate 1024000 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 set freq correction 4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 worker cond timeout Signal caught, exiting! comm recv bye Signal caught, exiting! all threads dead.. listening...
The same client connects without errors to another rtl_tcp instance on a Windows 7 computer, with the same module.
Any help is greatly appreciated.
Thanks, Dan
Hi,
I have tried to install rtlsdr for 64bit using a different procedure, from here: http://www.trinityos.com/HAM/CentosDigitalModes/hampacketizing-centos.html#4... with the same resuit.
I really don't now what to do ....
Best regards, Dan
On 10/6/2013 11:37 PM, Sylvain AZARIAN wrote:
This message looks coming from libusb. Maybe you check that lib source to understand what error code 5 stands for....
Have you tried to run app as root ?
Le 6 oct. 2013 22:34, "Dan" <yo3ggx@gmail.com mailto:yo3ggx@gmail.com> a écrit :
Hi all, I have compiled and installed rtl-sdr on CentOS 6 following instructions. Everything compiles without errors, but: - when I run rtl_test I get the following errors: 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 Found Rafael Micro R820T tuner Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6 Info: This tool will continuously read from the device, and report if samples get lost. If you observe no further output, everything is fine. Reading samples in async mode... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... Library error 0, exiting... If I run rtl_tcp I get the following errors when the client tries to connect: Found 1 device(s). Found Rafael Micro R820T tuner Using ezcap USB 2.0 DVB-T/DAB/FM dongle Tuned to 100000000 Hz. listening... Use the device argument 'rtl_tcp=192.168.33.99:8767 <http://192.168.33.99:8767>' in OsmoSDR (gr-osmosdr) source to receive samples in GRC and control rtl_tcp parameters (frequency, gain, ...). client accepted! set freq 145000000 cb transfer status: 5, canceling... cb transfer status: 5, canceling... rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 set sample rate 1024000 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 set freq correction 4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 worker cond timeout Signal caught, exiting! comm recv bye Signal caught, exiting! all threads dead.. listening... The same client connects without errors to another rtl_tcp instance on a Windows 7 computer, with the same module. Any help is greatly appreciated. Thanks, Dan
I really don't now what to do ....
You're using CentOS. This is an enterprise Linux system, designed for running servers. This means the software is chosen because it is known to be stable, so it is usually missing the latest features.
As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in August 2010. This is over three years old! A *lot* of bug fixes and improvements happen in three years.
The problem you are experiencing has likely been fixed at some point within this time, so your solutions are to install a newer libusb version, or better yet, switch to a Linux distro that is more suited to this kind of work. CentOS is great if you want to run a database server, but not so good if you want to experiment with the very latest gadgets!
Cheers, Adam.
On Fri, 11 Oct 2013 06:47:54 +1000 Adam Nielsen a.nielsen@shikadi.net wrote:
As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in August 2010. This is over three years old! A *lot* of bug fixes and improvements happen in three years.
Age has nothing to do with it. The libusb 1 existed when RHEL 6 was composed, but users weren't clamouring for it, so it didn't make the cut. AFAIK it's missing from EPEL too.
My suggestion would be to grab an old libusb1 RPM and rebuild it. It should be trivial and the result is installable alongside the old libusub. http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/14/Fedor...
-- Pete
forget rpm, just install libusb by downloading the tarball at http://www.libusb.org/ configure make make install
just my two cents
On Thu, Oct 10, 2013 at 4:58 PM, Pete Zaitcev zaitcev@kotori.zaitcev.uswrote:
On Fri, 11 Oct 2013 06:47:54 +1000 Adam Nielsen a.nielsen@shikadi.net wrote:
As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in August 2010. This is over three years old! A *lot* of bug fixes and improvements happen in three years.
Age has nothing to do with it. The libusb 1 existed when RHEL 6 was composed, but users weren't clamouring for it, so it didn't make the cut. AFAIK it's missing from EPEL too.
My suggestion would be to grab an old libusb1 RPM and rebuild it. It should be trivial and the result is installable alongside the old libusub.
http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/14/Fedor...
-- Pete
As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in August 2010. This is over three years old! A *lot* of bug fixes and improvements happen in three years.
Age has nothing to do with it.
So you're saying no useful work was done on libusb in three years? Granted I haven't looked at the commit history but it seems a bit unlikely.
My suggestion would be to grab an old libusb1 RPM and rebuild it. It should be trivial and the result is installable alongside the old libusub.
I'm not sure how rebuilding a version of libusb that doesn't work will help...
Cheers, Adam.
What he's saying is CENTOS uses libusb.0.1.12, upgrade to libusb1.0.
On Thu, Oct 10, 2013 at 5:19 PM, Adam Nielsen a.nielsen@shikadi.net wrote:
As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in August 2010. This is over three years old! A *lot* of bug fixes and improvements happen in three years.
Age has nothing to do with it.
So you're saying no useful work was done on libusb in three years? Granted I haven't looked at the commit history but it seems a bit unlikely.
My suggestion would be to grab an old libusb1 RPM and rebuild it. It should be trivial and the result is installable alongside the old libusub.
I'm not sure how rebuilding a version of libusb that doesn't work will help...
Cheers, Adam.
Mahmoud Lababidi wrote:
forget rpm, just install libusb by downloading the tarball at http://www.libusb.org/ configure make make install
just my two cents
I'd recommend avoiding the libusbx tarball which has been linked from there and instead getting the http://git.libusb.org/libusb.git code.
Adam Nielsen wrote:
As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in August 2010. This is over three years old! A *lot* of bug fixes and improvements happen in three years.
Age has nothing to do with it.
So you're saying no useful work was done on libusb in three years?
It's complicated, but yes libusb.git code hasn't changed in about a year. I expect it to work reliably, and indeed one or two bugs have been fixed since the 1.0.9 release. (Before you say it, no, I can not simply make a 1.0.10 release. As I wrote, it is complicated. If you'd like to help out feel free to let me know and I'll explain until your ears fall off.. :)
Granted I haven't looked at the commit history but it seems a bit unlikely.
Please do look into the facts (it's very easy) rather than speculating.
Thanks
//Peter
Hi all,
On 10/11/2013 7:15 AM, Peter Stuge wrote:
Mahmoud Lababidi wrote:
forget rpm, just install libusb by downloading the tarball at http://www.libusb.org/ configure make make install
just my two cents
I'd recommend avoiding the libusbx tarball which has been linked from there and instead getting the http://git.libusb.org/libusb.git code.
I have tried to compile both the one from www.libusb.org and the one from git. After recompiling rtl-sdr with the new libraries the errors are the same....
Any other hints?
Thank you, Dan
Adam Nielsen wrote:
As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in August 2010. This is over three years old! A *lot* of bug fixes and improvements happen in three years.
Age has nothing to do with it.
So you're saying no useful work was done on libusb in three years?
It's complicated, but yes libusb.git code hasn't changed in about a year. I expect it to work reliably, and indeed one or two bugs have been fixed since the 1.0.9 release. (Before you say it, no, I can not simply make a 1.0.10 release. As I wrote, it is complicated. If you'd like to help out feel free to let me know and I'll explain until your ears fall off.. :)
Granted I haven't looked at the commit history but it seems a bit unlikely.
Please do look into the facts (it's very easy) rather than speculating.
Thanks
//Peter
Dan wrote:
I'd recommend avoiding the libusbx tarball which has been linked from there and instead getting the http://git.libusb.org/libusb.git code.
I have tried to compile both the one from www.libusb.org and the one from git. After recompiling rtl-sdr with the new libraries the errors are the same....
Did you make sure that the rtl-sdr programs are in fact also using the new libraries, as opposed to what is installed by CentOS which is what will be used by default, when running them?
Any other hints?
Only to use the latest kernel code.
If you see the problem with the latest kernel (from Linus' git - the latest packaged by CentOS is irrelevant) and using code from git.libusb.org/libusb.git by way of e.g. LD_LIBRARY_PATH then I would be interested in seeing a libusb debug log. See http://libusb.org/wiki/debug for a copypaste-able instruction on how to generate one. Thanks!
//Peter
Hi Peter,
On 10/11/2013 7:46 PM, Peter Stuge wrote:
Dan wrote:
I'd recommend avoiding the libusbx tarball which has been linked from there and instead getting the http://git.libusb.org/libusb.git code.
I have tried to compile both the one from www.libusb.org and the one from git. After recompiling rtl-sdr with the new libraries the errors are the same....
Did you make sure that the rtl-sdr programs are in fact also using the new libraries, as opposed to what is installed by CentOS which is what will be used by default, when running them?
Before this I've fully uninstalled the previous version and set the environment variables: LIBUSB_LIBS and LIBUSB_CFLAGS before running ./configure for rtl-sdr
Dan
On Fri, 11 Oct 2013 20:27:57 +0300 Dan yo3ggx@gmail.com wrote:
LIBUSB_LIBS and LIBUSB_CFLAGS before running ./configure for rtl-sdr
That's a bit indirect. The best way is to run ldd ./myapp
I continue to maintain that all this advice about installing "latest" without knowing what's up is not likely to work. The stock libusb1 rpm from Koji works just fine, I would not even bother rebuilding it, just pull off an F14 repo.
Find what the problem is by running strace ./rtl-sdr and matching ioctls to the code.
-- Pete
Dan wrote:
Any other hints?
Only to use the latest kernel code.
I cannot change the kernel on the system I intend to use the dongle, as it provides other services which cannot be interrupted..
I can understand that you can not upgrade kernel on the final system, but it would be very helpful if you could test on a separate system, with similar hardware, with a new kernel, to see if the problem persists.
Did you make sure that the rtl-sdr programs are in fact also using the new libraries, as opposed to what is installed by CentOS which is what will be used by default, when running them?
Before this I've fully uninstalled the previous version and set the environment variables: LIBUSB_LIBS and LIBUSB_CFLAGS before running ./configure for rtl-sdr
That sounds good. It is important that you have uninstalled the version provided by the CentOS package.
Pete Zaitcev wrote:
LIBUSB_LIBS and LIBUSB_CFLAGS before running ./configure for rtl-sdr
That's a bit indirect. The best way is to run ldd ./myapp
ldd is a good way to see what libraries will actually be loaded by a given program. If indeed the CentOS package has been uninstalled then ldd should confirm that the correct library file is being loaded.
I continue to maintain that all this advice about installing "latest" without knowing what's up is not likely to work.
It's not about what will likely make things work, it's about doing debugging with the current state of the code, so that I know that I haven't already fixed the problem in libusb.git and so that I know exactly what code is being used when the error occurs.
The stock libusb1 rpm from Koji works just fine, I would not even bother rebuilding it, just pull off an F14 repo.
Since there are commits in libusb.git which are not included in those binaries it is significantly more helpful to use the git code for testing.
Find what the problem is by running strace ./rtl-sdr and matching ioctls to the code.
Please don't do that, it is not helpful. Please focus on creating a debug log as described on http://libusb.org/wiki/debug since that's very useful for those of us who know the libusb code.
Thanks
//Peter
Hi Peter,
On 10/12/2013 10:34 AM, Peter Stuge wrote:
I can understand that you can not upgrade kernel on the final system, but it would be very helpful if you could test on a separate system, with similar hardware, with a new kernel, to see if the problem persists.
As I don't have a similar system with Linux (but I have a similar one with Windows where the rtlsdr library works perfect), I intend to install it on a virtual machine on the same hardware just to see if I still get the same errors. Is this a good ideea? What Linux version do you recommend to try with?
ldd is a good way to see what libraries will actually be loaded by a given program. If indeed the CentOS package has been uninstalled then ldd should confirm that the correct library file is being loaded.
When I try 'ldd -v rtl_test' I get the message "not a dynamic executable"
Find what the problem is by running strace ./rtl-sdr and matching ioctls to the code.
Please don't do that, it is not helpful. Please focus on creating a debug log as described on http://libusb.org/wiki/debug since that's very useful for those of us who know the libusb code.
I'll do it.
Thanks
//Peter
Thanks, Dan
Hi,
I've done the following: - uninstall CentOS distribution libusb1 and libusb1-devel - download the latest libusb1 from git: http://git.libusb.org/libusb.git - automake.sh - make - make install - use the latest rtlsdr code from git - set the env variables as follows: export LIBUSB_LIBS="-L/usr/local/lib -lusb-1.0" export LIBUSB_LIBS="-L/usr/local/lib" - ./configure - make - make install Trying to run rtl_test I get a lot of debug messages. The full answer can be seen here: http://www.yo3ggx.ro/rtlsdr/rtltest.txt
Thanks Dan
On 10/12/2013 10:34 AM, Peter Stuge wrote:
Dan wrote:
Any other hints?
Only to use the latest kernel code.
I cannot change the kernel on the system I intend to use the dongle, as it provides other services which cannot be interrupted..
I can understand that you can not upgrade kernel on the final system, but it would be very helpful if you could test on a separate system, with similar hardware, with a new kernel, to see if the problem persists.
Did you make sure that the rtl-sdr programs are in fact also using the new libraries, as opposed to what is installed by CentOS which is what will be used by default, when running them?
Before this I've fully uninstalled the previous version and set the environment variables: LIBUSB_LIBS and LIBUSB_CFLAGS before running ./configure for rtl-sdr
That sounds good. It is important that you have uninstalled the version provided by the CentOS package.
Pete Zaitcev wrote:
LIBUSB_LIBS and LIBUSB_CFLAGS before running ./configure for rtl-sdr
That's a bit indirect. The best way is to run ldd ./myapp
ldd is a good way to see what libraries will actually be loaded by a given program. If indeed the CentOS package has been uninstalled then ldd should confirm that the correct library file is being loaded.
I continue to maintain that all this advice about installing "latest" without knowing what's up is not likely to work.
It's not about what will likely make things work, it's about doing debugging with the current state of the code, so that I know that I haven't already fixed the problem in libusb.git and so that I know exactly what code is being used when the error occurs.
The stock libusb1 rpm from Koji works just fine, I would not even bother rebuilding it, just pull off an F14 repo.
Since there are commits in libusb.git which are not included in those binaries it is significantly more helpful to use the git code for testing.
Find what the problem is by running strace ./rtl-sdr and matching ioctls to the code.
Please don't do that, it is not helpful. Please focus on creating a debug log as described on http://libusb.org/wiki/debug since that's very useful for those of us who know the libusb code.
Thanks
//Peter
Dan wrote:
Hi,
I've done the following:
- uninstall CentOS distribution libusb1 and libusb1-devel
- download the latest libusb1 from git: http://git.libusb.org/libusb.git
- automake.sh
- make
- make install
- use the latest rtlsdr code from git
- set the env variables as follows: export LIBUSB_LIBS="-L/usr/local/lib -lusb-1.0" export LIBUSB_LIBS="-L/usr/local/lib"
- ./configure
- make
- make install
Trying to run rtl_test I get a lot of debug messages. The full answer can be seen here: http://www.yo3ggx.ro/rtlsdr/rtltest.txt
Thanks! I'll take a look at this and get back to you.
//Peter
Hi Peter,
On 10/13/2013 9:21 AM, Peter Stuge wrote:
Dan wrote:
Hi,
I've done the following:
- uninstall CentOS distribution libusb1 and libusb1-devel
- download the latest libusb1 from git: http://git.libusb.org/libusb.git
- automake.sh
- make
- make install
- use the latest rtlsdr code from git
- set the env variables as follows: export LIBUSB_LIBS="-L/usr/local/lib -lusb-1.0" export LIBUSB_LIBS="-L/usr/local/lib"
- ./configure
- make
- make install
Trying to run rtl_test I get a lot of debug messages. The full answer can be seen here: http://www.yo3ggx.ro/rtlsdr/rtltest.txt
Thanks! I'll take a look at this and get back to you.
By the way... I've done nothing specific to generate this debug info. Is this the default build option in git code?
//Peter
Many thanks, Dan
Hi Pete,
On 10/12/2013 12:52 AM, Pete Zaitcev wrote:
On Fri, 11 Oct 2013 20:27:57 +0300 Dan yo3ggx@gmail.com wrote:
LIBUSB_LIBS and LIBUSB_CFLAGS before running ./configure for rtl-sdr
That's a bit indirect. The best way is to run ldd ./myapp
I continue to maintain that all this advice about installing "latest" without knowing what's up is not likely to work. The stock libusb1 rpm from Koji works just fine, I would not even bother rebuilding it, just pull off an F14 repo.
The version of libusb1 in F14 is 1.0.8-1, but in CentOS 6.2 is newer (1.0.9-0.6.rc1). I think now that I have another issue as I have tested with several libusb1-devel libraries, but without uninstalling original libusb1 from CentOS because of multiple dependencies.
Find what the problem is by running strace ./rtl-sdr and matching ioctls to the code.
I need to read as I'm not familiar with this...
-- Pete
Thank you, Dan
Hi Peter,
On 10/12/2013 12:52 AM, Pete Zaitcev wrote:
I continue to maintain that all this advice about installing "latest" without knowing what's up is not likely to work. The stock libusb1 rpm from Koji works just fine, I would not even bother rebuilding it, just pull off an F14 repo.
I have tried to install both libusb1 and usb1-devel from F14 repo. The problem remain the same.
Hi,
On 10/11/2013 7:46 PM, Peter Stuge wrote:
Any other hints?
Only to use the latest kernel code.
I cannot change the kernel on the system I intend to use the dongle, as it provides other services which cannot be interrupted..
If you see the problem with the latest kernel (from Linus' git - the latest packaged by CentOS is irrelevant) and using code from git.libusb.org/libusb.git by way of e.g. LD_LIBRARY_PATH then I would be interested in seeing a libusb debug log. See http://libusb.org/wiki/debug for a copypaste-able instruction on how to generate one. Thanks!
I will try to generate a debug log to see...
Thanks, Dan
//Peter
Hi Adam,
On 10/10/2013 11:47 PM, Adam Nielsen wrote:
I really don't now what to do ....
You're using CentOS. This is an enterprise Linux system, designed for running servers. This means the software is chosen because it is known to be stable, so it is usually missing the latest features.
As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in August 2010. This is over three years old! A *lot* of bug fixes and improvements happen in three years.
I have the following libusv1 libraries installed: libusb1-1.0.9-0.6.rc1.el6.i686 libusb1-1.0.9-0.6.rc1.el6.x86_64
The problem you are experiencing has likely been fixed at some point within this time, so your solutions are to install a newer libusb version, or better yet, switch to a Linux distro that is more suited to this kind of work. CentOS is great if you want to run a database server, but not so good if you want to experiment with the very latest gadgets!
I will try to build a newer version of the library.
Cheers, Adam.
Thank you, Dan
-
Adam Nielsen -
Dan -
Mahmoud Lababidi -
Pete Zaitcev -
Peter Stuge -
Sylvain AZARIAN