78 replies to this topic

[pieterg]

I think we should cooperate to create a usbtunerhelper module in kernel space, it might operate better.

it will be more optimal, but it requires a new interface to the drivers, instead of the current vtuner interface.
the data has to be written to /dev/misc/vtuner devicenodes, and that has to be done from userspace, so there is no other way.

And on the usb tunerdriver side, there is not generic way to get hold of the dvb data. So that would require an individual patch for each device, instead of a single hook in the dvbcore.

[malakudi]

I think we should cooperate to create a usbtunerhelper module in kernel space, it might operate better.

it will be more optimal, but it requires a new interface to the drivers, instead of the current vtuner interface.
the data has to be written to /dev/misc/vtuner devicenodes, and that has to be done from userspace, so there is no other way.

And on the usb tunerdriver side, there is not generic way to get hold of the dvb data. So that would require an individual patch for each device, instead of a single hook in the dvbcore.

The "accelerated vtuner interface" that was reported in the changelog of some of the latest dm8xx drivers, what exactly accelerates?

[pieterg]

They probably improved zapping speed or so.
The interface itself looks the same, still userspace.

[Plineo]

Hi malakudi

I have an Avermedia Volar HD Pro (a835), I managed to compile v4l-dvb from SIFTeam in Openpli, but unfortunately my stick doesn't work. Have you tried one of these sticks with your compilation??

[malakudi]

Hi malakudi

I have an Avermedia Volar HD Pro (a835), I managed to compile v4l-dvb from SIFTeam in Openpli, but unfortunately my stick doesn't work. Have you tried one of these sticks with your compilation??

This is an af9035/tda18218 stick and it should work with current drivers, though I haven't been able to test it.

Try installing following packages:
v4l-dvb-module-dvb-usb-af9035
v4l-dvb-module-af9033
v4l-dvb-module-tua9001
v4l-dvb-module-tda18218
v4l-dvb-module-mxl5007t
v4l-dvb-module-dvb-usb
v4l-dvb-firmware

then reboot and check if it works.

[jblimon]

For af9015 chipsets, you need following ipk files:

v4l-dvb-module-af9013
v4l-dvb-module-dvb-pll
v4l-dvb-module-dvb-usb
v4l-dvb-module-dvb-usb-af9015
v4l-dvb-module-mc44s803
v4l-dvb-module-mt2060
v4l-dvb-module-mxl5005s
v4l-dvb-module-mxl5007t
v4l-dvb-module-qt1010
v4l-dvb-module-tda18218
v4l-dvb-module-tda18271

[highlight=#ebeff9]hello friend

[/highlight][highlight=#ffffff]I installed those packages you indicate, but not my USB tuner [/highlight]any side.

[highlight=#ffffff]How is it done? [/highlight]
[highlight=#ffffff]
[/highlight]
[highlight=#ffffff][/highlight][highlight=#ffffff]thanks and regards[/highlight]

[Plineo]

Thanks Malakudi, I have tried those packets but no luck!!

I had to dowload the firmware dvb-usb-af9035-01.fw since it is not delivered with firmware packet. If I reboot with the stick plugged:

dvb-usb (please define a log prefix): tuner ID:10 not supported, please report!
usbcore: registered new driver dvb_usb_af9035

then if I unplug and plug the stick again:

dvb-usb: found a 'Avermedia AverTV Volar HD Team Bob/Chip (A825/A835/B835)' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-af9035-01.fw'
dvb-usb (please define a log prefix): command:24 failed:17
dvb-usb (please define a log prefix): firmware download failed:-5
dvb_usb_af9035: probe of 2-1:1.0 failed with error -5

any ideas??

[Bobsilvio]

@plineo
open your pen dvb-t and indentify 3 chip. Write name..
1) af9035
2) af9033
3) ??? (tuner chip)

[Plineo]

@bobsilvio

There are two main chips:

AF9035B -> processor
TDA18218HN -> tuner

[robertut]

How about EC168 chipset? E3C:E3C EC168
Like this one, very cheap: http://global.ebay.c...0535477463/item
It works great under Win32 and x64 environment.

Which drivers do I need to install in OpenPLi for it to work?

[rwijnberg]

the driver package enigma2-plugin-drivers-dvb-usb-dib0700 - 1.0-r0
is completely broken. It is unusable.
full with symbol errors (compiled against the wrong kernel?)

v4l-dvb-module-dib0070 - 0.0+hg20100904-r6.5
v4l-dvb-module-dib0090 - 0.0+hg20100904-r6.5
v4l-dvb-module-dib3000mb - 0.0+hg20100904-r6.5
v4l-dvb-module-dib3000mc - 0.0+hg20100904-r6.5
v4l-dvb-module-dib7000m - 0.0+hg20100904-r6.5
v4l-dvb-module-dib7000p - 0.0+hg20100904-r6.5
v4l-dvb-module-dib8000 - 0.0+hg20100904-r6.5
v4l-dvb-module-dibx000-common - 0.0+hg20100904-r6.5
v4l-dvb-module-dvb-usb-dib0700 - 0.0+hg20100904-r6.5
v4l-dvb-module-dvb-usb-dibusb-common - 0.0+hg20100904-r6.5
v4l-dvb-module-dvb-usb-dibusb-mb - 0.0+hg20100904-r6.5
v4l-dvb-module-dvb-usb-dibusb-mc - 0.0+hg20100904-r6.5

[pieterg]

no, the package does not contain anything, so it is not built against the wrong kernel.
It's a meta package, but the list of dependencies is incomplete since the previous v4l update.
So it is only a cosmetic inconvenience, you need to install the deps yourself.

[rwijnberg]

no, the package does not contain anything, so it is not built against the wrong kernel.
It's a meta package, but the list of dependencies is incomplete since the previous v4l update.
So it is only a cosmetic inconvenience, you need to install the deps yourself.

I know, but what I mean is that the modules are broken.
Replacing the modules with the r6.3 release fixes the problem.
Output of dmesg shortly after loading the modules lists lots of symbol errors.

[pieterg]

missing symbols = module dependencies you failed to install/load. I don't think it is actually broken.

[rwijnberg]

missing symbols = module dependencies you failed to install/load. I don't think it is actually broken.

I disagree.

The meta package (enigma2-plugin-drivers-dvb-usb-dib0700) also installs the following modules automatically:
v4l-dvb-module-dib0070 - 0.0+hg20100904-r6.5
v4l-dvb-module-dib0090 - 0.0+hg20100904-r6.5
v4l-dvb-module-dib3000mb - 0.0+hg20100904-r6.5
v4l-dvb-module-dib3000mc - 0.0+hg20100904-r6.5
v4l-dvb-module-dib7000m - 0.0+hg20100904-r6.5
v4l-dvb-module-dib7000p - 0.0+hg20100904-r6.5
v4l-dvb-module-dib8000 - 0.0+hg20100904-r6.5
v4l-dvb-module-dibx000-common - 0.0+hg20100904-r6.5
v4l-dvb-module-dvb-usb-dib0700 - 0.0+hg20100904-r6.5
v4l-dvb-module-dvb-usb-dibusb-common - 0.0+hg20100904-r6.5
v4l-dvb-module-dvb-usb-dibusb-mb - 0.0+hg20100904-r6.5
v4l-dvb-module-dvb-usb-dibusb-mc - 0.0+hg20100904-r6.5

There is *NOTHING* extra I have to install to make my DVB-T usb stick working.

After loading above mentioned modules, output of dmesg shows the following:
dvb_usb_dib0700: Unknown symbol mt2266_attach
dvb_usb_dib0700: Unknown symbol xc2028_attach
dvb_usb_dib0700: Unknown symbol mxl5007t_attach
dvb_usb_dib0700: Unknown symbol xc5000_attach
dvb_usb_dib0700: Unknown symbol s5h1411_attach
dvb_usb_dib0700: Unknown symbol mt2060_attach
dvb_usb_dib0700: Unknown symbol lgdt3305_attach
dvb_usb_dibusb_common: Unknown symbol dvb_pll_attach
dvb_usb_dibusb_common: Unknown symbol mt2060_attach
dvb_usb_dibusb_mb: Unknown symbol dibusb_pid_filter_ctrl
dvb_usb_dibusb_mb: Unknown symbol dibusb_i2c_algo
dvb_usb_dibusb_mb: Unknown symbol dibusb2_0_streaming_ctrl
dvb_usb_dibusb_mb: Unknown symbol dvb_pll_attach
dvb_usb_dibusb_mb: Unknown symbol dibusb_streaming_ctrl
dvb_usb_dibusb_mb: Unknown symbol dibusb_power_ctrl
dvb_usb_dibusb_mb: Unknown symbol ir_codes_dibusb_table
dvb_usb_dibusb_mb: Unknown symbol dibusb2_0_power_ctrl
dvb_usb_dibusb_mb: Unknown symbol dibusb_pid_filter
dvb_usb_dibusb_mb: Unknown symbol dibusb_rc_query
dvb_usb_dibusb_common: Unknown symbol dvb_pll_attach
dvb_usb_dibusb_common: Unknown symbol mt2060_attach
dvb_usb_dibusb_mc: Unknown symbol dibusb_pid_filter_ctrl
dvb_usb_dibusb_mc: Unknown symbol dibusb_i2c_algo
dvb_usb_dibusb_mc: Unknown symbol dibusb2_0_streaming_ctrl
dvb_usb_dibusb_mc: Unknown symbol dibusb_dib3000mc_tuner_attach
dvb_usb_dibusb_mc: Unknown symbol dibusb_dib3000mc_frontend_attach
dvb_usb_dibusb_mc: Unknown symbol ir_codes_dibusb_table
dvb_usb_dibusb_mc: Unknown symbol dibusb2_0_power_ctrl
dvb_usb_dibusb_mc: Unknown symbol dibusb_pid_filter
dvb_usb_dibusb_mc: Unknown symbol dibusb_rc_query
dvb_usb_dibusb_common: Unknown symbol dvb_pll_attach
dvb_usb_dibusb_common: Unknown symbol mt2060_attach

Is it broken or not?

[pieterg]

well, to start with, you are obviously missing some mt2x6x modules, so it seems.

[rwijnberg]

well, to start with, you are obviously missing some mt2x6x modules, so it seems.

It worked before with the modules with release number r6.3
My DVB-T stick uses the dib0700 chipset.
If I replace module dvb-usb-dib0700.ko version r6.5 with the 6.3 version (from my second box) everything works fine. I'm missing nothing.

I'll stop this discussion.

[littlesat]

I just follow this... but even I do currently not understand what you exactly did.

As far I understand it is working no with the 6.3 ko and 6.3 v4l modules

But what was your start???

[malakudi]

Newer drivers have more dependencies. Just install the missing dependencies manually. It is already mentioned which packages are needed for dib0700, in this thread.

[hemertje]

Newer drivers have more dependencies. Just install the missing dependencies manually. It is already mentioned which packages are needed for dib0700, in this thread.

so we must add these dependencies in our buildenvironment so our users dont have to install manual these drivers.