Author
Topic: DVB Cards info needed for Templates (Read 58425 times)

We dont have a device template for the T500... cue Thom to give me a 'bashing' for not having one ;-)

...but we do have it working very well using our V4l package (PM me if any of you would like a copy...its DKMS based so will work correctly on 0710 or 0810...or indeed 0910 too ;-) )...and reliably in Myth now. The only issue we see is that if we reboot the T500's do not get in initialised properly from a 'warm' firmware boot. The solution is to do a shutdown, remove the power for 15 secs or so, then powerup and all is well. This is an irritation but compared to before when the T500 was so unstable it was unusable its very acceptable!

...So keep them comming and no one will go ignored just remember the info to post

DViCo FusionHDTV7 Dual Express - The lspci bits were already up on the wiki I created for this card. I ran the v4l2-ctl and added the output but soon realized that the analog inputs were likely from the usb tuner card I have plugged in (I'll post the info for it soon). The driver for this card does not support the analog inputs. http://wiki.linuxmce.org/index.php/DViCO_FusionHDTV7_Dual_Express

This card requires the xc5000 firmware. There are two versions that I have used, depending on which the kernel requests (1.1 or 1.6.114).

Replied as soon as I saw this post...I was away from the forums for a couple days. Keep up the good work.

ok there are new templates now in the CVS but some of you will need to install drivers and firmware, remember these templates might not be complete do to me not having the hardware to test, So feed back is welcomed and keep the cards coming as so we can get most of the common cards used into the 810 release.

that template has been in the sqlCVS, what you have to do is update your system via CVSopen webadminthen advance up at the topthen sqlCVS then updatecheck all and then nextand after update is done reloadit takes a little and another window will open say success !!

linuxmce@mythrouter:/lib/firmware$ md5sum dvb-fe-cx24116.fw dd8dfdfca6b72462d9db8032f78631c8 dvb-fe-cx24116.fw** went to fetch Firmware v1.20.79.0 linuxmce@mythrouter:/lib/firmware$ md5sum dvb-fe-cx24116.fw 417cafd3b10e207e1dba9a03ad63e405 dvb-fe-cx24116.fwDuring the previous couple of weeks I did a lot of test setup's in all kinds of ways. As stated earlier I have tried and tested both the standard v4l-dvb repositories at linuxtv.org as well as the s2-liplianin repository. At a certain point nothing would work any more.I am not a specialist in mercurial or git, but I did some searching and went back to some of the test installs.I found that hg parents gave me detailed info on the repository installed.

Struggeling to make vdr actually use it now. I mean, it does open the device (listed in lsof and I get device is busy when trying to scan for channels while vdr is running) but it says "no signal" when switching to TV on my orbiter.Any hints are welcome.

if you're getting device busy while vdr is running, that is why ... vdr is using the tuners, you have to stop it first so that scan can use them. check out the instructions on the wiki as this is explained.

I'm sorry, I did not make myself clear above.I was able to scan for channels after killing vdr-kbd and put the channels.conf to /etc/vdr/channels.conf (it contains a ton of channels and several more tons of scrambled channels)

After that I rebootet to make sure vdr is coming up normally (what, according to the logs it did).

But vdr from the orbiter insists to have "no signal".My mentioning of the device being busy above was meant to emphasize that vdr is in fact using the device (keeping it open and therefore restricting other apps from using it).