Author Topic: Terratec C PCI HD DVB-C Card in PCI-X Slot using LinuxMCE 0710 (Read 17605 times)

mannheim · « **on:** January 13, 2009, 09:42:13 pm »

Hi Together,

i tried to solve my problem with the help of the irc channels, but without success.

Heres the Situation:
The Card was installed with s2-liplianin
( http://www.linuxtv.org/wiki/index.php/TerraTec_Cinergy_C_DVB-C ) and dmesg posts:

[ 101.667604] found a VP-2040 PCI DVB-C device on (0a:01.0),
[ 101.670427] DVB: registering new adapter (Mantis dvb adapter)
[ 102.189326] mantis_frontend_init (0): Probing for CU1216 (DVB-C)
[ 102.192819] mantis_frontend_init (0): found Philips CU1216 DVB-C frontend (TDA10023) @ 0x0c
[ 102.192823] mantis_frontend_init (0): Mantis DVB-C Philips CU1216 frontend attach success
[ 102.192829] DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)...

scanning with "w_scan -fc -o4 > channels.conf" delivers channels.conf , which i used with in VDR.

Now i get a picture starting TV in the Lmce UI. But it's totally green and purple and with about 0.005 fps

I tried another slot in the server without any difference. The Hardware is a HP ProLiant DL580 G2 Server.
Btw MythTV didn't do anything.

I hope someone can help me. Pleaaaasssseeeeee!!!

Greetings from germany, mannheim

I have a Syslog, too:
^{Jan 13 19:30:46 dcerouter vdr: [7974] caught signal 15
Jan 13 19:30:46 dcerouter vdr: [7974] stopping plugin: xineliboutput
Jan 13 19:30:46 dcerouter vdr: [7974] [xine..put] cXinelibDevice::StopDevice(): Stopping device ...
Jan 13 19:30:46 dcerouter vdr: [13387] transfer thread ended (pid=7974, tid=13387)
Jan 13 19:30:46 dcerouter vdr: [7974] cTS2PES got 0 TS errors, 18 TS continuity errors
Jan 13 19:30:46 dcerouter vdr: [7974] cTS2PES got 0 TS errors, 2 TS continuity errors
Jan 13 19:30:46 dcerouter vdr: [7974] cTS2PES got 0 TS errors, 2 TS continuity errors
Jan 13 19:30:46 dcerouter vdr: [7974] buffer stats: 134796 (6%) used
Jan 13 19:30:47 dcerouter vdr: [13389] TS buffer on device 1 thread ended (pid=7974, tid=13389)
Jan 13 19:30:47 dcerouter vdr: [13388] buffer stats: 99828 (4%) used
Jan 13 19:30:47 dcerouter vdr: [13388] receiver on device 1 thread ended (pid=7974, tid=13388)
Jan 13 19:30:47 dcerouter vdr: [8415] Remote decoder/display server (cXinelibServer) thread ended (pid=7974, tid=8415)
Jan 13 19:30:47 dcerouter vdr: [7974] stopping plugin: control
Jan 13 19:30:47 dcerouter vdr: [7974] [xine..put] cXinelibOsdProvider: shutting down !
Jan 13 19:30:47 dcerouter vdr: [7974] saved setup to /var/lib/vdr/setup.conf
Jan 13 19:30:47 dcerouter vdr: [8412] section handler thread ended (pid=7974, tid=8412)
Jan 13 19:30:47 dcerouter kernel: [ 1638.183055] mantis stop feed and dma
Jan 13 19:30:47 dcerouter vdr: [8411] tuner on device 1 thread ended (pid=7974, tid=8411)
Jan 13 19:30:47 dcerouter vdr: [8289] CI adapter on device 0 thread ended (pid=7974, tid=8289)
Jan 13 19:30:47 dcerouter vdr: [7974] [xine..put] cXinelibDevice::StopDevice(): Stopping device ...
Jan 13 19:30:47 dcerouter vdr: [7974] deleting plugin: xineliboutput
Jan 13 19:30:47 dcerouter vdr: [7974] deleting plugin: control
Jan 13 19:30:47 dcerouter vdr: [8414] [control] gateways thread ended (pid=7974)
Jan 13 19:30:47 dcerouter vdr: [7974] max. latency time 1 seconds
Jan 13 19:30:47 dcerouter vdr: [7974] exiting, exit code 0
Jan 13 19:30:51 dcerouter vdr: [25109] cTimeMs: using monotonic clock (resolution is 1 ns)
Jan 13 19:30:52 dcerouter vdr: [25131] cTimeMs: using monotonic clock (resolution is 1 ns)
Jan 13 19:30:52 dcerouter vdr: [25134] cTimeMs: using monotonic clock (resolution is 1 ns)
Jan 13 19:30:52 dcerouter vdr: [25159] cTimeMs: using monotonic clock (resolution is 1 ns)
Jan 13 19:30:52 dcerouter vdr: [25159] LMCEVDR version 1.6.0 started
Jan 13 19:30:52 dcerouter vdr: [25159] switched to user 'vdr'
Jan 13 19:30:52 dcerouter vdr: [25159] codeset is 'UTF-8' - known
Jan 13 19:30:52 dcerouter vdr: [25159] found 23 locales in /usr/share/locale
Jan 13 19:30:52 dcerouter vdr: [25159] loading plugin: /usr/lib/vdr/plugins/libvdr-control.so.1.6.0
Jan 13 19:30:52 dcerouter vdr: [25159] loading plugin: /usr/lib/vdr/plugins/libvdr-xineliboutput.so.1.6.0
Jan 13 19:30:52 dcerouter vdr: [25159] loading /var/lib/vdr/setup.conf
Jan 13 19:30:52 dcerouter vdr: [25159] [xine..put] Skipping configuration entry Frontend=none (overridden in command line)
Jan 13 19:30:52 dcerouter vdr: [25159] ERROR: unknown config parameter: xineliboutput.OSD.SpuAutoSelect = 1
Jan 13 19:30:52 dcerouter vdr: [25159] ERROR: unknown config parameter: xineliboutput.OSD.SpuLang0 = en
Jan 13 19:30:52 dcerouter vdr: [25159] ERROR: unknown config parameter: xineliboutput.OSD.SpuLang1 = Af
Jan 13 19:30:52 dcerouter vdr: [25159] ERROR: unknown config parameter: xineliboutput.OSD.SpuLang2 = dee
Jan 13 19:30:52 dcerouter vdr: [25159] ERROR: unknown config parameter: xineliboutput.OSD.SpuLang3 =
Jan 13 19:30:52 dcerouter vdr: [25159] loading /var/lib/vdr/sources.conf
Jan 13 19:30:52 dcerouter vdr: [25159] loading /var/lib/vdr/diseqc.conf
Jan 13 19:30:52 dcerouter vdr: [25159] loading /var/lib/vdr/channels.conf
Jan 13 19:30:52 dcerouter vdr: [25159] loading /var/lib/vdr/timers.conf
Jan 13 19:30:52 dcerouter vdr: [25159] loading /var/lib/vdr/svdrphosts.conf
Jan 13 19:30:52 dcerouter vdr: [25159] loading /var/lib/vdr/remote.conf
Jan 13 19:30:52 dcerouter vdr: [25159] loading /var/lib/vdr/keymacros.conf
Jan 13 19:30:52 dcerouter vdr: [25159] reading EPG data from /home/public/data/VDRTV/video/epg.data
Jan 13 19:30:52 dcerouter vdr: [25161] video directory scanner thread started (pid=25159, tid=25161)
Jan 13 19:30:52 dcerouter vdr: [25162] video directory scanner thread started (pid=25159, tid=25162)
Jan 13 19:30:52 dcerouter vdr: [25161] video directory scanner thread ended (pid=25159, tid=25161)
Jan 13 19:30:52 dcerouter vdr: [25162] video directory scanner thread ended (pid=25159, tid=25162)
Jan 13 19:30:52 dcerouter vdr: [25159] probing /dev/dvb/adapter0/frontend0
Jan 13 19:30:52 dcerouter vdr: [25164] CI adapter on device 0 thread started (pid=25159, tid=25164)
Jan 13 19:30:52 dcerouter vdr: [25159] found 1 video device
Jan 13 19:30:52 dcerouter vdr: [25159] initializing plugin: control (0.0.2a): Control VDR over terminal or telnet
Jan 13 19:30:52 dcerouter vdr: [25159] initializing plugin: xineliboutput (1.0.0~rc2-cvs-LMCE0710-8): LMCEVDRoutput based on X11/xine-lib output plugin
Jan 13 19:30:52 dcerouter vdr: [25159] [xine..put] cTimePts: clock_gettime(CLOCK_MONOTONIC): clock resolution 0 us
Jan 13 19:30:52 dcerouter vdr: [25159] [xine..put] cTimePts: using monotonic clock
Jan 13 19:30:52 dcerouter vdr: [25159] [xine..put] cTimePts: clock_gettime(CLOCK_MONOTONIC): clock resolution 0 us
Jan 13 19:30:52 dcerouter vdr: [25159] [xine..put] cTimePts: using monotonic clock
Jan 13 19:30:52 dcerouter vdr: [25159] [xine..put] RTP SSRC: 0x3d25714e
Jan 13 19:30:52 dcerouter vdr: [25159] setting primary device to 2
Jan 13 19:30:52 dcerouter vdr: [25159] assuming manual start of VDR
Jan 13 19:30:52 dcerouter vdr: [25159] SVDRP listening on port 2001
Jan 13 19:30:52 dcerouter vdr: [25159] setting current skin to "classic"
Jan 13 19:30:52 dcerouter vdr: [25159] loading /var/lib/vdr/themes/classic-default.theme
Jan 13 19:30:52 dcerouter vdr: [25159] starting plugin: control
Jan 13 19:30:52 dcerouter vdr: [25166] tuner on device 1 thread started (pid=25159, tid=25166)
Jan 13 19:30:52 dcerouter vdr: [25167] section handler thread started (pid=25159, tid=25167)
Jan 13 19:30:52 dcerouter vdr: [25168] ERROR (thread.c,224): Permission denied
Jan 13 19:30:52 dcerouter vdr: [25169] [control] gateways thread started (pid=25159)
Jan 13 19:30:52 dcerouter vdr: [25169] [control] socket opened
Jan 13 19:30:52 dcerouter vdr: [25159] starting plugin: xineliboutput
Jan 13 19:30:52 dcerouter vdr: [25170] Remote decoder/display server (cXinelibServer) thread started (pid=25159, tid=25170)
Jan 13 19:30:52 dcerouter vdr: [25170] ERROR (thread.c,224): Permission denied
Jan 13 19:30:52 dcerouter vdr: [25170] [xine..put] cXinelibServer: Can't set priority to SCHED_RR 2 [1,99]
Jan 13 19:30:52 dcerouter vdr: [25170] [xine..put] Listening on port 37890
Jan 13 19:30:52 dcerouter vdr: [25170] [xine..put] Listening for UDP broadcasts on port 37890
Jan 13 19:30:52 dcerouter vdr: [25159] [xine..put] cXinelibDevice::StartDevice(): Device started
Jan 13 19:30:52 dcerouter vdr: [25159] ERROR: /dev/lircd: No such file or directory
Jan 13 19:30:52 dcerouter vdr: [25159] ERROR: remote control LIRC not ready!
Jan 13 19:30:54 dcerouter vdr: [25164] CAM 1: no module present
Jan 13 19:30:54 dcerouter vdr: [25159] switching to channel 1
Jan 13 19:30:54 dcerouter vdr: [25159] setting watchdog timer to 60 seconds
Jan 13 19:30:54 dcerouter kernel: [ 1644.834669] mantis start feed & dma
Jan 13 19:30:54 dcerouter vdr: [25187] receiver on device 1 thread started (pid=25159, tid=25187)
Jan 13 19:30:54 dcerouter vdr: [25188] TS buffer on device 1 thread started (pid=25159, tid=25188)
Jan 13 19:30:54 dcerouter vdr: [25186] transfer thread started (pid=25159, tid=25186)
Jan 13 19:30:54 dcerouter vdr: [25186] [xine..put] Detected video size 720x576
Jan 13 19:30:54 dcerouter vdr: [25186] setting audio track to 1 (0)
Jan 13 19:30:54 dcerouter vdr: [25186] cAudioRepacker(0xC0): skipped 392 bytes to sync on next audio frame
Jan 13 19:30:55 dcerouter vdr: [25186] PES packet shortened to 4440 bytes (expected: 4624 bytes)
Jan 13 19:31:00 dcerouter vdr: [25159] max. latency time 1 seconds
Jan 13 19:33:01 dcerouter /USR/SBIN/CRON[25838]: (root) CMD (bash -c '/usr/pluto/bin/DiskSpaceMonitor.sh &>/dev/null')
Jan 13 19:33:52 dcerouter vdr: [25186] cDolbyRepacker: skipped 1352 bytes to sync on next AC3 frame
Jan 13 19:33:52 dcerouter vdr: [25186] PES packet shortened to 12120 bytes (expected: 12304 bytes)
Jan 13 19:33:58 dcerouter vdr: [25186] cAudioRepacker(0xC0): skipped 392 bytes to sync on next audio frame
Jan 13 19:33:58 dcerouter vdr: [25186] PES packet shortened to 4440 bytes (expected: 4624 bytes)}

mannheim · « **Reply #1 on:** January 13, 2009, 11:18:06 pm »

Edit:
I just tested to watch TV with a pxe booted notebook with the result that the pictures weren't green or purple at all. So this might be a channels.conf issue.
Will check the vdr-wiki again. Maybe someone have a dvb-c channels.conf manual for me?

Greetings from germany, mannheim.

Ps: i replied my own post because of the mobile browser capabilitites.

mannheim · « **Reply #2 on:** January 14, 2009, 05:02:42 pm »

update:

i made a new kind of working channels.conf
if i test the card with kaffein it finds also some channels and if i watch tv i got maybe 3 or 4 frames and than the picture freezes.

please help. please!!

it's really frustrating...

mannheim

Marie.O · « **Reply #3 on:** January 14, 2009, 11:19:22 pm »

mannheim,

I would take this issue to the linuxtv, dvb or vdr mailing list/forum.

The card is not supported out of the box with lmce, and we currently awfully short on people, especially people with DVB knowledge.

rgds
Oliver

mannheim · « **Reply #4 on:** January 15, 2009, 02:36:35 am »

thx for answer oliver,

i work my through v4l at the moment (recommendation from hari), which seems quite good information

don't ask me why i started there so late, i just didn't had the project right on my focus ^^

i hope i will find a way ... and write it in the wiki

sl,
mannheim
(i know, stupid nickname... ^^)

cirion · « **Reply #5 on:** January 15, 2009, 02:35:42 pm »

Quote from: mannheim on January 13, 2009, 09:42:13 pm

Heres the Situation:
The Card was installed with s2-liplianin

Yes that is your problem! That driver is for S2API.

If you read the same Wiki you would have found this:
"Kernel 2.6.28 released on 24.12.2008 works with the mantis driver in the s2-liplianin repository."

LinuxMCE is not at that kernel yet... So for now you have to use multiproto mantis driver for your card.
A few lines down in the same wiki:

Code: [Select]

cd /usr/src
sudo apt-get install mercurial
sudo hg clone http://jusst.de/hg/mantis  
cd mantis
sudo make
sudo make install
sudo reboot

The VDR and MythTV versions in LinuxMCE support multiproto, but there is no support for S2API.

I'm hoping this will change in 8.10, but since Kubuntu 8.10 still does not use Kernel 2.6.28, it might not come in LMCE 8.10.

I only have 2 things I want in LMCE810, and that is VDPAU and S2API support...

Marie.O · « **Reply #6 on:** January 15, 2009, 05:02:07 pm »

cirion,

we are welcoming patches that will enable those two things in 0810.

rgds
Oliver

mannheim · « **Reply #7 on:** January 15, 2009, 07:06:00 pm »

hi.

thx for the answer. i'll try the other driver.

the point is in the linuxtv.org/wiki there is a recommendation i thought for the s2api version ... maybe misunderstood, but it isn't also that clearly mentioned.

however...
i will write patches and contribute in 0810 if i can learn to do so in the next months ... will see

mannheim

cirion · « **Reply #8 on:** January 15, 2009, 09:10:45 pm »

I guess, the biggest problem is that VDR and MythTV for LMCE is the stable releases, and the patches are made for the developer versions...

Here is the patch for VDR 1.70:
http://www.linuxtv.org/pipermail/vdr/2008-October/018061.html

Here is 2 Wikis for S2API and MythTV:
http://dolot.kipdola.com/index.php?title=Install_S2API
http://dolot.kipdola.com/index.php?title=Install_MythTV

S2API is already supported in the latest kernel 2.6.28, and for those cards that made it into the first release, work out of the box. I do not know when Kubuntu will get this kernel.

To see what cards made it, and a bit more info on S2API read this wiki:
http://www.linuxtv.org/wiki/index.php/S2API

VDPAU support from Nvidia requires the lates driver for Linux:
http://www.nvidia.com/object/linux_display_ia32_180.22.html

Then Xine, Mplayer, VLC, Mythtv and VDR needs to support it...
I found a guide for VDR 1.70 with VDPAU:
http://blog.mymediasystem.net/avchd/vdr-xine-with-vdpa/

mannheim · « **Reply #9 on:** January 15, 2009, 10:09:08 pm »

i installed the mantis driver now ... my first goal at all is a LinuxMCE 0710 in "productive environment"

so, i can record dvb stream to harddisc via dvbstream but vdr isn't working within LinuxMCE. i guess the channels.conf is the problem.

i created init data via w_scan an than:

sudo scan -o vdr -e 6 ini_tuning_data.txt > channels.conf

the result is only a black screen in vdr or the "no signal"-signal ...

edit: i just want to get the "standard" lmce 0710 running. not anything outside the normal ways or something. i only thought to myself if that doesn't work i'm not willing to just give up... however, just wanna watch TV with my MDs ^^

Marie.O · « **Reply #10 on:** January 15, 2009, 11:35:41 pm »

Quote from: cirion on January 15, 2009, 09:10:45 pm

I guess, the biggest problem is that VDR and MythTV for LMCE is the stable releases, and the patches are made for the developer versions...

yes. But the interesting part is, with 0810 you will no longer need a special lmce VDR version, even though we provide one. Right now you can, after installing the lmce VDR, go and install any other VDR version you like.

If you want to provide some ready made packages for us to include in the lmce distribution, we will gladly accept those. Unfortunately, right now, I don't think we have the man power, to go after these patches ourselfs.

rgds
Oliver

cirion · « **Reply #11 on:** January 29, 2009, 01:52:43 am »

Quote from: mannheim on January 15, 2009, 10:09:08 pm

sudo scan -o vdr -e 6 ini_tuning_data.txt > channels.conf

the result is only a black screen in vdr or the "no signal"-signal ...

edit: i just want to get the "standard" LinuxMCE 0710 running. not anything outside the normal ways or something. i only thought to myself if that doesn't work i'm not willing to just give up... however, just wanna watch TV with my MDs ^^

What did you do with the channels.conf file?
Did you upload it in the webadmin?
Does it contain anything?

Are you using the CI adapter? Are you using FTA channels, or encrypted channels?

This card does work in standard LMCE 07.10 with the Mantis driver.
The card has to be in the Core for it to work.
Install mantis driver, reboot, stop vdr, scan a channels.conf then upload it to the webadmin and reboot.
FTA channels should then work on the Core.

Next would be to get the MD's working. That requires updating VDR, so get it working on the Core first.

mannheim · « **Reply #12 on:** January 30, 2009, 02:11:53 pm »

Hi again.

the situation now is even worse. after the last reinstallation of the system i don't have any dmesg output anymore. i reinstalled it several times

however, i try my luck with that on the v4l mailing list, maybe theres a version issue of the mantis driver.

the last time, cirion, i used the follow:
uploaded the channels.conf via webadmin, yes. and yes, it contained something. looked also in proper syntax compared "by watching" to the channels.conf seen in the wiki.
no ci module and only FTA (non encrypted i guess) channels. our provider don't encrypt in general.

however, will go back to that point if i get the card itself again in the system. lspci btw shows up the card.

greetings
mannheim

cirion · « **Reply #13 on:** January 30, 2009, 03:06:16 pm »

As you can see, the Mantis driver changed the last few days. That could have broken something...
http://jusst.de/hg/mantis

Try an earlier version.

mannheim · « **Reply #14 on:** January 30, 2009, 03:13:18 pm »

yes, i'm only not sure how to get them.

for example i see "manifest" for a version 3 weeks ago. that should be eventually better.

however do i:

sudo hg clone http://jusst.de/hg/mantis/file/3c897a20ff8b
sudo make
sudo make install

?

thx

News: