ERROR: Sorry - i couldn't get any working frequency/transponder Nothing to scan!

Help and Support Raspberry Pi
1

hi,

I am having troubles with this dvb-t usb stick: http://www.conceptronic.net/es/download_list.php?stype=1&back=2&productid=291

On windows 10 on another computer it works perfectly, but I cannot manage to work in raspberry pi 2 model B.

The usb stick is recognised and I can scan frequencies with w_scan command, but I am getting the error mentioned in the topic.

The tutorial im following is this one:

In my case kernel version is 4.1.5-1-osmc.

Could someone help me please? I am desperated. I will answer your questions immediately because I need to solve this problem.

Many thanks

2

try here

https://discourse.osmc.tv/t/dvb-t-dongle-not-working-after-2015-08-03-update

3

I have done:

apt-get install rbp2-image-3.18.13-1-osmc --reinstall

and now uname -r says that I am at 3.18.13-1-osmc, so OK.

But when I use:

sudo w_scan -c ES > channels.conf

the answer is:

w_scan version 20130331 (compiled for DVB API 5.4)
using settings for SPAIN
DVB aerial
DVB-T Europe
scan type TERRESTRIAL, channellist 4
output format vdr-2.0
WARNING: could not guess your codepage. Falling back to ‘UTF-8’
output charset ‘UTF-8’, use -C to override
Info: using DVB adapter auto detection.
main:3228: FATAL: ***** NO USEABLE TERRESTRIAL CARD FOUND. *****
Please check wether dvb driver is loaded and
verify that no dvb application (i.e. vdr) is running.

I assure there is not any vdr running, and the answer to dmesg is:

dmesg | grep dvb
[ 4.913670] usb 1-1.2.1: dvb_usb_v2: found a ‘Dexatek DK DVB-T Dongle’ in warm state
[ 5.002906] dvb_usb_rtl28xxu: probe of 1-1.2.1:1.0 failed with error -32
[ 5.003551] usbcore: registered new interface driver dvb_usb_rtl28xxu

What should I do now?

Many Thanks.

4

is the tuner plugged in to the pi or a hub? I assume you powered everything down and didn’t just do a reboot?

5

The tuner is connected to a usb hub, not to the pi. And yes, I powered everything down, and up again. The answer is the same, seems to be a problem with the driver, or firmware.

How could I know?

Thanks.

6

sorry I couldn’t be more help, just going by what I experienced. For me disconnecting power from the pi and the hub, and then reconnecting them, fixed it. Must be a different issue, hopefully someone else can help you