First of all kudos to Cecil and his team for work the done on R5D1. This release allowed me to watch encrypted DVB-S streams using a CAM and my Canal Digitaal subscription. I have been struggling with this for months now and never got it to work. This release proved it is indeed possible. Many thanks!

Now, being the inquisitive mind that I am (plus I'd finally like to know why I didn't get it to work), I'd like some insight in how this setup differs from what I have been trying.

What I have learnt in the past is that the DVB support for MythTV is partly (mostly?) kernel based and partly MythTV based. As of now I haven't really figured out yet. Perhaps the dvb-utils (szap et al) are also required for full DVB support.

The KNC1 DVB-S adapter (rev2) I have been using requires kernel > 2.6.15. Luckily R5D1 comes with 2.6.17 (vanilla - based on the release notes) so the adapter was recognised immediately. Unfortunately when I took the kernel-sources tarball from my R5D1 setup to my FC4 test rig, it compiled just fine, yielded a working kernel, allowed for channel scanning in MythTV, but gave no channel locks in LiveTV. Anyone knows if the kernel has special patches (besides the ones mentioned in the release notes)?

From the release notes and a previous post about compiling MythTV:

http://www.mysettopbox.tv/phpBB2/viewtopic.php?t=9042

I already gathered that the mythtv-0.19-fixes branch is used for compiling MythTV. I have compiled this source many times now with different -dvb-path= options, but so far all attempts (including a recompile with the include files of the 2.6.17-chw-8 kernel sources) have failed to access the CAM properly. Based on the .diff files in the /usr/src/mythtv/source directory, mythtv is compiled with -dvb-path=/usr/include (amongst others). The files there generally come from the debian package linux-kernel-headers. This doesn't seem to be installed on R5D1. Anyone know where these include files come from?

Lastly I'm curious where the dvb-utils binaries come from. They don't seem to come from a .deb package. Anyone have an idea?

Please help me in trying to understand how dvb support is added to KnoppMyth R5D1. I have been struggling for months now. Finding that this setup works is very rewarding, but also made me more curious where I went wrong in trying myself.

If someone has answers to the questions above or the interaction between MythTV and the kernel (and dvb-utils) wrt DVB operations, please share!

Source. I'd suggest asking your query on the MythTV mailing list...

_________________
cesman

When the source is open, the possibilities are endless!

No, they are just a way of testing the kernel's DVB drivers. The MythTV application is a client that opens the drivers thw same way szap does.

I suspect the CAM support isn't working? Does it need extra firmware on that machine?


Try http://www.linuxtv.org/hg (now called dvb-apps, not dvb-utils?)

_________________
| Nigel Pearson, nigel.pearson.au@gmail.com
| "Things you own end up owning you" - Tyler, Fight Club

Thanks Nigel for your time. The lack of CAM support is the most likely culprit, however I don't really see how to add it. Having the same kernel sources didn't solve the issue. The firmware is certaintly something to look at. I can't remember seeing references to firmware requirements for this hardware on the linuxtv wiki, but I'll give it a try.

Perhaps another question you might happen to know: If MythTV is just a DVB client, then during the compile it needs to be "taught" DVB by pointing it to the right DVB header files (--dvb-path= option in ./configure). What header files do you usually use? The ones in /usr/include, the ones supplied with the sources of the running kernel, the ones supplied with the hg v4l-dvb sources or the ones supplied with dvb-utils sources? I think by now I have tried all, but I can't really make out which one should be used.

So far there have been too many variables and too little time to try all permutations. All help in deciphering this is mostly appreciated.

Did you check that you were using the same kernel configuration? e.g. do both /proc/config.gz files match?

Another thing to check would be the kernel output. Do 'dmesg >dmesg.log' on both machines and compare them line by line. That may reveal a load order dependency, or a missing module, et c.



Since KnoppMyth R5A9, I have just used /usr/include.

I would check that your kernel build did actually install the headers in /usr/include. If it doesn't, then maybe you need to also do something like 'make headers_install'

_________________
| Nigel Pearson, nigel.pearson.au@gmail.com
| "Things you own end up owning you" - Tyler, Fight Club

Thanks again. I will use these pointers when I find more time to do some testing.