Announcement

Collapse
No announcement yet.

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

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

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

    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:
    pi@raspberrypi:~ $ 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:
    pi@raspberrypi:~ $ 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
    pi@raspberrypi:~ $ 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:
    pi@raspberrypi:~ $ sudo bash -c "$(wget -nv -O - https://raw.githubusercontent.com/wiedehopf/adsb-scripts/master/rtl_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 :-)

  • #2
    is the SDR connected directly to the RPi?
    if not, the USB extension is likely at fault.

    otherwise it might be a defective SDR.

    Comment

    Working...
    X