vtuner sources

[__jata__]

I have wrote a slightly modified version - now it contains a patch for 'relaxed' tuner-group assignment. It means, if you define a tuner group, for example:

Code: Select all

vtuner -f s2:1

It tries to connect only to a tuner from the group '0'. But if it fails, then after timeout it releases the assignment and continues with seeking about any available tuner on any available Nessie in the network, as like as no tuner group (and no fixed IP of Nessie) was defined at the command line. (the original code waits forever in such situation). The patch is ugly but it works..
This property might be disabled by the undef of

Code: Select all

USE_FALLBACK="1"

in the ebuild (and 'ebuild .... digest', of course), then the patch is skipped and it uses of the original code only. It works only in the version 9999.
Hope, it helps.
And, btw, it works nicely even under gentoo-3.2.1 kernel

[hop]

I have wrote a slightly modified version - now it contains a patch for 'relaxed' tuner-group assignment. It means, if you define a tuner group, for example:

Code: Select all

vtuner -f s2:1

It tries to connect only to a tuner from the group '0'. But if it fails, then after timeout it releases the assignment and continues with seeking about any available tuner on any available Nessie in the network, as like as no tuner group (and no fixed IP of Nessie) was defined at the command line. (the original code waits forever in such situation). The patch is ugly but it works..

Not so much ugly. Someone simply don't like goto (like me )

Anyway, it is nice feature, thanks. I only would like to see it settable by command line switch.

This property might be disabled by the undef of

Code: Select all

USE_FALLBACK="1"

in the ebuild (and 'ebuild .... digest', of course), then the patch is skipped and it uses of the original code only. It works only in the version 9999.
Hope, it helps.
And, btw, it works nicely even under gentoo-3.2.1 kernel

Nice to hear. Thanks.

Honza

[__jata__]

I do not like 'goto' as well.. and yes, to have it as the command line option would be nice. I used the simplest modification just because I did not want to fiddle with the original code too much; any complicated patch might be difficult to remove or adapt, when the original code is changed (and this is happening with very alive projects quite often).
But if you like this idea, please, rewrite it and include into the repo .. the strategy is clear.
Thx..

[hop]

FYI, linux 3.3 comes with really HUGE changes inside DVB core subsystem.

Until all get stabilized, we have supporting it only partly - I made a fixed source file you can download from here:
http://code.google.com/p/vtuner/issues/detail?id=18

Honza

[__jata__]

Yeah, I would strongly recommend to wait with upgrade from 3.2.x to 3.3.0 and stay with the current functional kernel.
- besides of the DVB-API changes there is regression in PCIE susbystem and kernel can Oops on certain MB (I have hit this on GA Z68 MB on one PC).
- vdr, even the newest (1.7.26) does not work with 3.3.0, at least for me. It does not die, just stops without a chance to access the OSD and waits in this frozen state until killed. Not only with Nessie, with HVR4000 also and not only with eHD, but vdr-xine/VDPAU suffers by the same problem. Might be I have something wrong in the kernel, but I rather do not think so.
But if there is somebody, who is really desperade, I have already prepared ebuild, covering the 3.3.0-gentoo as well. Send me PM, if yoy want to try, but personally, I will wait until these troubles are solved.

[__jata__]

So, ok, I made small step forward. There is really something seriously wrong with the DVB subsystem in the 3.3.0 kernel. The current situation:
- SDTV channels mostly work (Nessie or HVR4000/vdr or kaffeine)
- HDTV channels mostly do not work (Nessie or HVR4000/vdr)
- switching of polarisation (V->H or H->V) works sometimes on certain channels
- switching of transponder with the same polarisation may or may not work
Failure of command gives the next message in the vdr.log:

Code: Select all

log-2012-03-22-05:12:56:Mar 22 06:09:10 [vdr] [21281] ERROR: frontend 0/0: Nepřípustný argument
log-2012-03-22-05:12:56:Mar 22 06:09:26 [vdr] [21281] ERROR: frontend 0/0: Nepřípustný argument
log-2012-03-22-05:12:56:Mar 22 06:09:45 [vdr] [21281] ERROR: frontend 0/0: Nepřípustný argument
log-2012-03-22-05:12:56:Mar 22 06:10:08 [vdr] [21281] ERROR: frontend 0/0: Nepřípustný argument
log-2012-03-22-05:12:56:Mar 22 06:12:03 [vdr] [21281] ERROR: frontend 0/0: Nepřípustný argument
log-2012-03-22-05:12:56:Mar 22 06:12:25 [vdr] [21281] ERROR: frontend 0/0: Nepřípustný argument
log-2012-03-22-05:12:56:Mar 22 06:12:32 [vdr] [21281] ERROR: frontend 0/0: Nepřípustný argument
log-2012-03-22-05:12:56:Mar 22 06:12:42 [vdr] [21281] ERROR: frontend 0/0: Nepřípustný argument


(translation: ERROR: frontend 0/0: Invalid argument).
And the uncertain result of the tuning at the given channel was the reason, why I was not able to warm-up vdr previously...
Nevertheless, enclosed is the vtuner-ebuild, just for brave men and experiments. It still can be used with elder kernels, proxyfe patch is used only when kernel-3.3.N is found.

[ales]

As everyone can see in above paragraphs it should be problematic to use kernel 3.3.0 and above. We recomended to use kernel max version 3.2.11 - __jata__ reported in 3.2.12 are some problem s with PCIe - dvb subsystem itself should not be affected but ....

[__jata__]

Kernel 3.4.0-gentoo and the vtunerc.ko, produced by the ebuild from 22.3.2012 (i.e. - the patch http://code.google.com/p/vtuner/issues/detail?id=18 has been applied):
- SDTV channels work, if DVB-S
- HDTV channels do not work at all (Message: 'Channel not available'), SDTV channels in S2 do not work as well (the same message).
So under 3.4.0-kernel it is 'DVB-S only' system..... so the last fully functional system is based on the 3.2.16 kernel (under gentoo). Everything above 3.2.16 suffers by some troubles.

[hop]

Version 1.3 of vtuner kernel driver was just released in repository.

This is a major fix for compilation on kernels >= 3.3.0, which are using internal DVB API 5.5

Please reopen the issue #18 on vtuner homepage if it not fixed the issue for you.

/Honza

[__jata__]

If you are using kernels >3.7.0, maybe the next patch has to be applied (in the 'driver' tree):

Code: Select all

--- Makefile.orig       2013-02-07 13:09:14.903314119 +0100
+++ Makefile    2013-02-07 13:09:31.158134414 +0100
@@ -11,6 +11,7 @@
 obj-$(CONFIG_DVB_VTUNERC) += vtunerc.o
 
 ccflags-y += -Idrivers/media/dvb/dvb-core
+ccflags-y += -Idrivers/media/dvb-core
 ccflags-y += -Idrivers/media/dvb/frontends
 ccflags-y += -Idrivers/media/common/tuners
 ccflags-y += -Iinclude


At least for gentoo-sources-3.7.x kernels, the vtunerc.ko compilation fails otherwise.