101 replies to this topic

[andriup]

Hi everybody

My enigma starts normally, but USB tuner DVB-T (URZ0085 on chipset IT9135) is not visible in the enigma2 after installing drivers.
My tuner Solo 2, soft Open Pli. Kernel 3.3.6

[ims]

Vu Solo2... USB DVB - Evolve Mars ( 048d:9006) , installed kernel module for it913x, firmware for it913x, but nothing added there in tuners.

Only on start E2 I can see:

 

Input device "ITE Technologies, Inc. USB Deivce" is a keyboard  

[Gennar1]

Vu Solo2... USB DVB - Evolve Mars ( 048d:9006) , installed kernel module for it913x, firmware for it913x, but nothing added there in tuners.

Only on start E2 I can see:

 

Input device "ITE Technologies, Inc. USB Deivce" is a keyboard  

 

Make sure you have installed also the kernel module kernel-module-it913x-fe in addition to the obvious kernel-module-dvb-usb-it913x.

[ims]

Thanks, I will try it tomorrow.

[ims]

Still no success. When is pluged DVB-USB Evolve Mars dongle into vu solo2 (without installed drivers), then is visible with "lsusb" as

 

Bus 01 Device 003: ID: 048d:9006
 

 

After reboot box there is missing. There could be problem...

Edited by ims, 16 April 2013 - 09:24.

[Gennar1]

Can you post a dmesg?

[ims]

I will try it, I am making it all via telnet on remote box...

 

Edit: here is

Attached Files

•  dmesg.log   13.48KB   15 downloads

[ims]

I think, there is some problem ( when I am trying modprobe dvb-usb-it913x ).

it913x: Chip Version=02 Chip Type=9135
it913x: Firmware Version 52887808
it913x: Remote HID mode NOT SUPPORTED
it913x: Dual mode=0 Tuner Type=0
it913x: Unknown tuner ID applying default 0x60
usb 1-1: dvb_usb_v2: found a 'ITE 9135(9006) Generic' in warm state
usb 1-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
DVB: registering new adapter (ITE 9135(9006) Generic)
it913x-fe: ADF table value      :00
usb 1-1: dvb_usb_v2: 2nd usb_bulk_msg() failed=-145
usb 1-1: dvb_usb_v2: 2nd usb_bulk_msg() failed=-145
usb 1-1: dvb_usb_v2: 2nd usb_bulk_msg() failed=-145
usb 1-1: dvb_usb_v2: 2nd usb_bulk_msg() failed=-145
usb 1-1: dvb_usb_v2: 2nd usb_bulk_msg() failed=-145
usb 1-1: dvb_usb_v2: 2nd usb_bulk_msg() failed=-145
it913x-fe: Crystal Frequency :12000000 Adc Frequency :20250000 ADC X2: 01
usb 1-1: dvb_usb_v2: 'ITE 9135(9006) Generic' error while loading driver (-19)
usb 1-1: dvb_usb_v2: 'ITE 9135(9006) Generic' successfully deinitialized and disconnected
[LCD]: unknown cmd 0x1015
FE tune
usbcore: deregistering interface driver dvb_usb_it913x

[Gennar1]

I think, there is some problem ( when I am trying modprobe dvb-usb-it913x ).

it913x: Chip Version=02 Chip Type=9135
it913x: Firmware Version 52887808
it913x: Remote HID mode NOT SUPPORTED
it913x: Dual mode=0 Tuner Type=0
it913x: Unknown tuner ID applying default 0x60
usb 1-1: dvb_usb_v2: found a 'ITE 9135(9006) Generic' in warm state
usb 1-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
DVB: registering new adapter (ITE 9135(9006) Generic)
it913x-fe: ADF table value      :00
usb 1-1: dvb_usb_v2: 2nd usb_bulk_msg() failed=-145
usb 1-1: dvb_usb_v2: 2nd usb_bulk_msg() failed=-145
usb 1-1: dvb_usb_v2: 2nd usb_bulk_msg() failed=-145
usb 1-1: dvb_usb_v2: 2nd usb_bulk_msg() failed=-145
usb 1-1: dvb_usb_v2: 2nd usb_bulk_msg() failed=-145
usb 1-1: dvb_usb_v2: 2nd usb_bulk_msg() failed=-145
it913x-fe: Crystal Frequency :12000000 Adc Frequency :20250000 ADC X2: 01
usb 1-1: dvb_usb_v2: 'ITE 9135(9006) Generic' error while loading driver (-19)
usb 1-1: dvb_usb_v2: 'ITE 9135(9006) Generic' successfully deinitialized and disconnected
[LCD]: unknown cmd 0x1015
FE tune
usbcore: deregistering interface driver dvb_usb_it913x

 

You can try to change the firmware parameter with modprobe:

modprobe dvb-usb-it913x firmware=1
 

 

 

and eventually firmware=2, firmware=3.

[ims]

I think, I tried all this ( for 9006 it should be 2.fw). I think, it was same. I must load it always manualy, because after reboot is not more usb-stick in lsusb list.

When try with "loaded" module, enigma is finishing in "no idle".

 

I think, better will be try it under ultimo (or xp1000) personaly and know, if is stick ok.

Edited by ims, 16 April 2013 - 19:22.

[ims]

Still problem, that after reboot is not USB-stick detected. When I put it to box and reload modules :

root@vusolo2:~# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0002
Bus 003 Device 001: ID 1d6b:0002
Bus 004 Device 001: ID 1d6b:0002
Bus 005 Device 001: ID 1d6b:0001
Bus 006 Device 001: ID 1d6b:0001
Bus 007 Device 001: ID 1d6b:0001
Bus 008 Device 001: ID 1d6b:0001
Bus 001 Device 003: ID 048d:9006
root@vusolo2:~# lsmod
Module                  Size  Used by
it913x_fe              30661  1 
ipv6                  311826  12 
dvb_usb_it913x          9196  0 
dvb_usb_v2             13716  1 dvb_usb_it913x
fpga_directc           57649  0 
brcmfb                  1238  2 
dvb_bcm7356         11704403  34 fpga_directc,brcmfb

Now i have not problem in dmesg. But when I am run enigma2 and saw on debug, it finishing on:

 

---- opening lame channel db
reading services (version 4)
loaded 8751 services
linking adapter1/frontend0 to vtuner0
scanning for frontends..
opening frontend 0
close frontend 0
opening frontend 1
close frontend 1
opening frontend 2
main thread is non-idle! display spinner!
no spinner DC!
main thread is non-idle! display spinner!
no spinner DC!
main thread is non-idle! display spinner!
no spinner DC!
main thread is non-idle! display spinner!
no spinner DC!
...
...
...

[ims]

I tried this USB stick on Vu ultimo (I found, that there is not drivers) and after reboot it is still visible with lsusb.

On XP1000, where are drivers for this stick it works well.  Only on Solo2 is problem. With/without drivers it does not exist in USB after reboot box more.

[Dimitrij]

In my opinion, the problem with close frontend

[sypo]

Usb tuner dvb-t it913x stops booting tuner (again ) on Linux Kernel 3.8.7

[petar258]

same on ET5000 and i am surprised that i can not download version of drivers for previous kernel - 3.6.0, which worked ok

 

Usb tuner dvb-t it913x stops booting tuner (again ) on Linux Kernel 3.8.7

[macnuts]

Looks like a USB issue:

ehci-brcm ehci-brcm.0: force halt; handshake b0480314 00004000 00000000 -> -145
ehci-brcm ehci-brcm.0: HC died; cleaning up
usb 1-2: USB disconnect, device number 3
dvb-usb: error while stopping stream.

I recently updated the IT913x patch with a few changes from the official driver mantainer.
If you had no problem with the previous version of the driver, we can revert the latest changes and wait for a fix from the mantainer.

 

 I have that kind of error on my Vu+Duo2. Have you solved it on et box? If so can that patch be ported back to kernel 3.3.8 for Vu+Duo?

I have a 9006 ver 1 chipset and it is affected by the "Issues with 9006 Chip version 1 devices resetting USB controller" but that issue info is outdated maybe.

 

Regards.

[athoik]

@macnuts,

OE-A has already integrate the following patches for linux-vuplus-3.3.8

it913x-backports-from-kernel-3.4.patch
it913x-backports-from-kernel-3.5.patch
it913x-fix-bulk-read-write-retry-loop.patch
it913x-switch-off-PID-filter-by-default.patch

So you can build kernel module by adding those patches and see if it fixes problems.

        file://it913x-backports-from-kernel-3.4.patch \
        file://it913x-backports-from-kernel-3.5.patch \
        file://it913x-switch-off-PID-filter-by-default.patch \
        file://it913x-fix-bulk-read-write-retry-loop.patch \

Then you can send those to OpenPLi also, so other users will benefit.

[macnuts]

I can see those files in:

meta-openpli/recipies-linux/linux/linux-vuplus-3.3.8

and they are listed in:

meta-openpli/recipies-linux/linux/linux-vuplus-3.3.8.inc

and that include file is required by:

linux-vuplus-3.3.8.bb

so I think those patches are integrated with openpli. If not, please name the file to modify.

 

Regards.

[athoik]

No, you are right patches are in. So you need to check changelog and see if there is a fix on latest kernel.

[macnuts]

Thank you athoik for your guidance.

 

I've found first candidate and I am going to check it now.

 

Few questions about applying patch to kernel:

1. I got the code with: bitbake -c devshell linux-vuduo2 but there is no git for this linux of course, so I initialized one for easy patch creation. But the commit path in the patch file will be out of sync. Does it matter for bitbake?

2. Will it be enough to increase PR_INC in the linux-vuplus-3.3.8.inc file each time I update the patch? (linux-vuplus-3.3.8.inc is where I am going to add patch file to SRC_URI).

 

Regards.