RTL-SDR v3 adapter does not show in 'lsusb' after running "rtl_test -t"

Main forum to discuss RTL-SDR related topics.
Post Reply
Finn_McCool
Posts: 3
Joined: Tue May 05, 2020 3:00 pm

RTL-SDR v3 adapter does not show in 'lsusb' after running "rtl_test -t"

Post by Finn_McCool » Tue May 05, 2020 3:04 pm

Hi All,
Raspberry Pi4 4GB and RTl-SDR v3 dongle.

I have taken the FR24 raspberry Pi image and loaded my Pi4 and connected it the network all ok, but I am getting an issue where there is no data being captured. So I have been doing some basic fault finding and come up with the following:

Complete newbie to Raspberry Pi (but ok on Linux) but I have an issue where I run a 'watch' command e.g. 'watch lsusb' and can see updated status of my USB ports and they are looking correct for a directly connected dongle as follows:
[email protected]:~ $ watch lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


However, due to issues with the FR24 data capture I tried testing my dongle on a Windows machine and then on the Raspberry Pi4 machine. All looks ok on the Windows machine but when I run a 'rtl_test -t' command I get the following:
[email protected]:~ $ rtl_test -t
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001

Using device 0: Generic RTL2832U OEM
Detached kernel driver
Found Rafael Micro R820T tuner
r82xx_write: i2c wr failed=-1 reg=13 len=7
r82xx_write: i2c wr failed=-1 reg=0c len=1
r82xx_init: failed=-1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
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
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
r82xx_write: i2c wr failed=-1 reg=0a len=1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
WARNING: Failed to set sample rate.
No E4000 tuner found, aborting.
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
rtlsdr_write_reg failed with -1
Reattaching kernel driver failed!


Any further testing show that there is 'No supported Device available', and the 'watch lsusb' command shows the Dongle is no longer present
[email protected]:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


I now have to manually unplug the Dongle from the USB ports and re-insert the Dongle to get the adapter to re-appear again.

I found in another forum topic a modified rtl_test -t script which I also ran and the output of that is here:
[email protected]:~ $ sudo bash -c "$(wget -nv -O - https://raw.githubusercontent.com/wiede ... tl_test.sh)"
2020-05-05 15:11:59 URL:https://raw.githubusercontent.com/wi...er/rtl_test.sh [2136/2136] -> "-" [1]
-----
Lost samples in the first 2 seconds after starting the test are common and not a problem!
Starting 30 second rtl_test, standby!
-----
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001

Using device 0: Generic RTL2832U OEM
Detached kernel driver
Found Rafael Micro R820T tuner
r82xx_write: i2c wr failed=-1 reg=13 len=7
r82xx_write: i2c wr failed=-1 reg=0c len=1
r82xx_init: failed=-1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
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
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
r82xx_write: i2c wr failed=-1 reg=0a len=1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
WARNING: Failed to set sample rate.
rtlsdr_demod_write_reg failed with -1
rtlsdr_demod_read_reg failed with -1
rtlsdr_write_reg failed with -1
rtlsdr_write_reg failed with -1

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...
Allocating 15 zero-copy buffers
cb transfer status: 1, canceling...

Library error -5, exiting...
Reattaching kernel driver failed!
-------
Test finished!
More than 2 lost samples per million or other errors probably mean the receiver isn't working correctly.
Try another power supply before condemning the receiver though!
-------
-------
No undervoltage detected, looking fine!
If the dongle is not directly plugged into the Raspberry Pi, lack of power/voltage could still be an issue.
Even without detected undervoltage a better power supply can often improve reception!
For optimum performance i would recommend the Official Raspberry Pi power supply.
-------

The dongle once again dissappears from the 'lsusb' list and will once again need a manually eject and re-insert back into the USB ports again.

Are the above errors pointing to a power supply issue or a driver problem somewhere on the Raspberry - any hints greatly received :-)

laurentp
Posts: 8
Joined: Tue Mar 24, 2020 12:26 pm

Re: RTL-SDR v3 adapter does not show in 'lsusb' after running "rtl_test -t"

Post by laurentp » Tue May 05, 2020 9:16 pm

"...Are the above errors pointing to a power supply issue..."

Ok, stupid(?) question: what is power capacity of PS You use? In A. Same (at least) as "official"?
I don't know RPi, I have OrangePi PC+ and there suggested PS is quite big: [email protected] So I got one, it is working stable (don't used DVB on that), also I use 12v->5V 3A switching regulator, working fine too. And there are forum threads about issues caused by bad PS and uSD cards.

Finn_McCool
Posts: 3
Joined: Tue May 05, 2020 3:00 pm

Re: RTL-SDR v3 adapter does not show in 'lsusb' after running "rtl_test -t"

Post by Finn_McCool » Wed May 06, 2020 7:21 am

I am using a Power supply I got from Amazon which was not directly badged as an 'official' Raspberry Power Supply but is rated output is 5v and 3000 mA. I have sinced purchased an external powered USB hub and will try to connect the USB3.0 hub to the Raspberry and the RTL-SDR dongle into the hub and try again. (Also an official Raspberry Power Supply is also on the way ;) )

tim_rtd
Posts: 154
Joined: Fri Jun 30, 2017 11:34 am

Re: RTL-SDR v3 adapter does not show in 'lsusb' after running "rtl_test -t"

Post by tim_rtd » Wed May 06, 2020 1:48 pm

You said your using the V3 dongle. Don't use the -t switch..just rtl_test. Won't solve reg problem.
lsusb stuff....... I suspect you haven't done the blacklisting part of the easy setup guide.
Powered usb3 hub is your best shot. I have a pi4 and running 3 V3's on the usb3 hub.

Finn_McCool
Posts: 3
Joined: Tue May 05, 2020 3:00 pm

Re: RTL-SDR v3 adapter does not show in 'lsusb' after running "rtl_test -t"

Post by Finn_McCool » Tue May 12, 2020 7:59 am

Thanks for all your hints etc... I think I have found the issue! I purchased a counterfeit item from eBay without knowing, but subsequently found pictures showing the FONT print on the dongle wasn't correct, and also the motherboard inside was an orange color instead of green plus the end plates were secured with 4 screws instead of 2. I have now found a UK recommended supplier of the official dongle and one is on its way.

Post Reply