DVB-T adapter doesn't work on Vero 4k

I have the following DVB-T adapter attached to Vero 4k. The firmware is loaded correctly and I can select it via tvheadend configuration.

Bus 001 Device 003: ID 048d:9006 Integrated Technology Express, Inc. IT9135 BDA Afatech DVB-T HDTV Dongle

It worked on rbp2 running OSMC, but the scanning of the muxes on Vero 4k fails with this log:

2017-03-16 00:32:55.882 mpegts: 578MHz in IRIB - tuning on ITE 9135(9006) Generic_1 : DVB-T #0
2017-03-16 00:32:55.882 linuxdvb: ITE 9135(9006) Generic_1 : DVB-T #0 - DTV_CLEAR failed [e=Operation not supported]
2017-03-16 00:32:55.883 mpegts: 602MHz in IRIB - tuning on ITE 9135(9006) Generic_1 : DVB-T #0
2017-03-16 00:32:55.883 linuxdvb: ITE 9135(9006) Generic_1 : DVB-T #0 - DTV_CLEAR failed [e=Operation not supported]
2017-03-16 00:32:55.883 mpegts: 650MHz in IRIB - tuning on ITE 9135(9006) Generic_1 : DVB-T #0  
2017-03-16 00:32:55.883 linuxdvb: ITE 9135(9006) Generic_1 : DVB-T #0 - DTV_CLEAR failed [e=Operation not supported]

I tried to test it with dvbscan, so I stopped tvheadend service and ran it with my local file, but there was no output. So I tried i with w_scan and here is the output:

osmc@vero:~$ w_scan -c IR -C UTF-8 -f t -X
w_scan version 20130331 (compiled for DVB API 5.4)
using settings for IRAN, ISLAMIC REPUBLIC OF
Country identifier IR not defined. Using defaults.
scan type TERRESTRIAL, channellist 4
output format czap/tzap/szap/xine
output charset 'UTF-8'
Info: using DVB adapter auto detection.
    /dev/dvb/adapter0/frontend0 -> "ITE 9135(9006) Generic_1" doesnt support TERRESTRIAL -> SEARCH NEXT ONE.
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.

Sounds like the version of FW loaded in the tuner is not right.
If you search the internet, you can find different versions of ITE9135 FW.

I used to use an ITE9135 tuner for DVB-T, but it seemed to overheat sometimes.
It would be working fine all day, then I would get lots of strange errors. I often
spent many hours installing/re-installing/re-configuring … then I reckoned it was
just the tuner going faulty.

Now I use DVB-T Sundtek, and it works very, very well with TVHeadend.
We have it running all day with Digital Terrestrial radio, and then in the evenings
for TV Channels (in HD).

The tuner is connected to Vero 4K running OSMC with TVHeadend installed from the App store.

My advice: get the Sundtek tuner - it is well worth it.

Hope this helps.
Best regards,
Niall.

This exact same adapter worked for my over past 10 month 24/7 on RaspberryPi 2.

For now I use that rpb2 as a backend and vero 4k as frontend.

Same for me, rpi3 as the tvheadend server and working well.

Ok. I was using pi3 as backend TVH and swapped to Vero 4K. And it worked with no issues. Pi2 or pi3 work fine as TVH backend.

You could try copying the .fw file from the Pi2 onto the Vero4k. It could be that the firmware file shipped with Vero4k is not the right one for your ITE9135 tuner.

If you look at dmesg on the pi2, you should see the file name of the .fw file which is downloaded to the tuner.

I checked the firmware file in dmesg and they both load same file. I checked their md5sums and they are identical. Here is the dmesg after connecting dvb stick to vero 4k:

[46999.429208] usb 1-2: new high-speed USB device number 3 using xhci-hcd
[46999.573213] usb 1-2: New USB device found, idVendor=048d, idProduct=9006
[46999.573224] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[46999.573230] usb 1-2: Product: USB Deivce
[46999.573235] usb 1-2: Manufacturer: ITE Technologies, Inc.
[46999.595683] input: ITE Technologies, Inc. USB Deivce as /devices/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-2/1-2:1.1/0003:048D:9006.0003/input/input11
[46999.595892] hid-generic 0003:048D:9006.0003: input,hidraw2: USB HID v1.01 Keyboard [ITE Technologies, Inc. USB Deivce] on usb-xhci-hcd.0.auto-2/input1
[46999.614958] it913x: Chip Version=02 Chip Type=9135
[46999.616318] it913x: Remote HID mode NOT SUPPORTED
[46999.616660] it913x: Dual mode=0 Tuner Type=0
[46999.616663] it913x: Unknown tuner ID applying default 0x60
[46999.620228] usb 1-2: dvb_usb_v2: found a 'ITE 9135(9006) Generic' in cold state
[46999.639577] usb 1-2: dvb_usb_v2: downloading firmware from file 'dvb-usb-it9135-02.fw'
[46999.639906] it913x: FRM Starting Firmware Download
[46999.850506] it913x: FRM Firmware Download Completed - Resetting Device
[46999.890306] it913x: Chip Version=02 Chip Type=9135
[46999.890663] it913x: Firmware Version 52953344
[46999.969461] usb 1-2: dvb_usb_v2: found a 'ITE 9135(9006) Generic' in warm state
[46999.969681] usb 1-2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[46999.970004] DVB: registering new adapter (ITE 9135(9006) Generic)
[46999.980368] it913x-fe: ADF table value   :00
[46999.983445] it913x-fe: Crystal Frequency :12000000 Adc Frequency :20250000 ADC X2: 01
[47000.008566] it913x-fe: Tuner LNA type :60
[47000.248733] usb 1-2: DVB: registering adapter 0 frontend 0 (ITE 9135(9006) Generic_1)...
[47000.248919] usb 1-2: dvb_usb_v2: 'ITE 9135(9006) Generic' successfully initialized and connected
[47000.248976] usbcore: registered new interface driver dvb_usb_it913x

I thought the issue would be that there was no kernel module included that was suitable for this device. As firmware is loading and a adapter front end is being created, it looks like something different.

Stay tuned

1 Like

Agreed Sam. That was the issue as I saw it.

Me too.

How is the USB tuner connected to the Vero4K …?
Maybe there’s a communications issue between the tuner and the Vero4K.

My USB tuners are connected to Vero4K via a powered USB hub.
Same also when I was using RPi3 at TVH backend.
You could try that and see if there’s any improvement.

I found this

Issues with 9005 type devices.
Chip Version 2 on ID 048d:9135 does not tune (fixed from driver version 1.24).

here:
https://www.linuxtv.org/wiki/index.php/ITE_IT9135

Maybe you should try to get driver version 1.24 …?

Mine is a 048d:9006, not a 048d:9135.

Ok, but I think it’s worthwhile to try a different fw version, because the fw version you are using seems to be incompatible with Vero4k

Now i am “happy” vero4 owner and what dissapointment previosly i owned vero1 and all my 3 diferent dvb-t adapters are fully suported but with new vero4 none is supported.

lsusb
Bus 001 Device 005: ID 07ca:a867 AVerMedia Technologies, Inc. AVerTV DVB-T (A867)
Bus 001 Device 008: ID 2040:7070 Hauppauge Nova-T Stick 3
Bus 001 Device 007: ID 2252:1037
Bus 001 Device 009: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
Bus 001 Device 006: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 010: ID 0572:c688 Conexant Systems (Rockwell), Inc.
07ca:a867 AVerMedia Technologies, Inc. AVerTV DVB-T (A867) I see from tvheadend but impossible scan:
2017-05-02 22:31:12.171 mpegts: 578MHz in levira - tuning on Afatech AF9033 (DVB-T) : DVB-T #0
2017-05-02 22:31:12.171 linuxdvb: Afatech AF9033 (DVB-T) : DVB-T #0 - DTV_CLEAR failed [e=Operation not supported]
2017-05-02 22:31:12.171 mpegts: 514MHz in levira - tuning on Afatech AF9033 (DVB-T) : DVB-T #0
2017-05-02 22:31:12.171 linuxdvb: Afatech AF9033 (DVB-T) : DVB-T #0 - DTV_CLEAR failed [e=Operation not supported]
2017-05-02 22:31:12.171 mpegts: 522MHz in levira - tuning on Afatech AF9033 (DVB-T) : DVB-T #0

Hi there,

I appreciate your frustration.

Thanks for the output.

We’ll add support for your dongle in the next update. I’ll ping you when testing is available

Cheers,

Sam

Hi Niall which particular model of sundtek are you using? Tia Graham.

Hi Graham,

I have two Sundtek USB tuners:

For Terrestrial DVB-T/T2, this one:

For Satellite, DVB-S/S2 this one:
(actually, I have an earlier version … I think there’s a newer model now)

Best regards,
Niall.

hi Niall, the second option is the one I was looking at (and your right I think there is a newer model)…many thanks Graham.