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)
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.
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
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
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... ^^)
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:
cd /usr/src
sudo apt-get install mercurial
sudo hg clone http://jusst.de/hg/mantis
cd mantis
sudo make
sudo make install
sudo rebootThe 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...
cirion,
we are welcoming patches that will enable those two things in 0810.
rgds
Oliver
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
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/
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 ^^
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
Quote from: mannheim on January 15, 2009, 10:09:08 PMsudo 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.
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 :D
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
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.
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
hi again.
the jusst.de mantis driver doesn't install at all. compiling and make install runs well without interrupt or error messages. however, after reboot the card is only in lspci, no modules loaded or no dmesg output.
due to "Kernel 2.6.28 released on 24.12.2008 works with the mantis driver in the s2-liplianin repository." i wasted several days now.
installing with the s2api mantis driver the card starts, dmesg output is there and i can watch tv :D
though with some little picture errors.
so now what? the s2api in the standard lmce kernel (2.6.24 iirc ?) ? i don't understand this...
hope anybody could bring me light into the darkness :D
greetings
mannheim
If you really want to know what's happening, google it...
But in short, It was a big fight, that lasted for years, and then in the end a group went together and made S2API.
S2API is the new standard for DVB and it is included in the latest kernel.
Installing the S2API driver from s2-liplianin repository works fine in older kernels, but this does not mean that the software you want to use the card with supports S2API.
Since you now are using LinuxMCE and it is using versions of VDR and Kaffeine that has no S2API support, you cannot use S2API drivers. For now there is no stable version of VDR or Kaffeine that has support for S2API. For now, forget S2API and use the Mantis driver.
You could be the one that makes the support for S2API in LinuxMCE...
ok, but why then did a have a life tv signal withhin lmce / vdr ? ... thats the point i don't understand.
i even could change channels without a crash...
i've found a patch for s2-api support for vdr 1.7 ... is it possible to implement the 1.7 into lmce?
thx
Quote from: mannheim on February 02, 2009, 05:37:29 PMi've found a patch for s2-api support for vdr 1.7 ... is it possible to implement the 1.7 into LinuxMCE?
Hmm... Am I talking to a Wall here?!?
Did you even read THIS thread?
All the answers to that question is in this tread....
Please read it again... There are 2 pages now...
i'm sorry cirion, but maybe i just understood not everything? comes that to your mind or is linux now a days self-explaining?
i'll try my best to get that damn thing running and your style like i'm so clever so you idiot lern to read doesn't really help.
ok, in conclusion: kernel is too old for s2-api,ok ... therefor also no need in upgrading vdr to 1,7, right? but why then do the s2 api drivers work (with little picture failures) in standard lmce 0710?
i've read in the wiki about upgrading the kernel. should i give it a try, and when yes, to which version might be the possibly best one?
thx for your time.
Quote from: mannheim on February 02, 2009, 10:44:58 PMi'm sorry cirion, but maybe i just understood not everything? comes that to your mind or is linux now a days self-explaining? i'll try my best to get that damn thing running and your style like i'm so clever so you idiot lern to read doesn't really help.
Hehe... READ AGAIN! What I'm trying to say by READ AGAIN! is exactly that. You did not read this thread again did you? I'm going to help you find what I was pointing at...
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...
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/
Quote from: mannheim on February 02, 2009, 10:44:58 PMok, in conclusion: kernel is too old for s2-api,ok ... therefor also no need in upgrading vdr to 1,7, right? but why then do the s2 api drivers work (with little picture failures) in standard LinuxMCE 0710?
i've read in the wiki about upgrading the kernel. should i give it a try, and when yes, to which version might be the possibly best one?
I'm not shure the Kernel is too old... If you installed S2API, and the newer scan tools Scan and Szap, you can try scanning a new Channels.conf. If that works, there is nothing wrong with the kernel used in 7.10.
What remains the problem, is the lack of support for S2API in VDR and Kaffeine. And Oliver wrote a reply to my post (yes in this thread):
Quote from: posde 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 LinuxMCE VDR version, even though we provide one. Right now you can, after installing the LinuxMCE 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 LinuxMCE 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
What this means is that in LMCE 7.10, if you are not developing a new version of VDR for LinuxMCE you will not be able to get VDR 1.7 running. And by not having the correct VDR version to patch, you will not be able to patch it correctly either. The LMCE 7.10 VDR version is based on the VDR 1.6 stable release, and the developers that made that integration will not use the next version of VDR before it is released as a stable.
The next part gets better.... LMCE 8.10 according to Oliver, will let you use whatever version of VDR you want, probably because the new VDR integration does not use the VDR source itself, but is talking to whatever VDR version is installed.
Now this is why I ask you to either use the Mantis driver for having TV now in LMCE 7.10 or wait for LMCE 8.10 when this might be sorted. You could try using LMCE 8.10, but there is no support for the Alpha version and I'm not having much luck with it yet. I have not yet come to the point where I am trying VDR in 8.10. First I have to sort my resolution problems and figure out how to find my RAID.
ok that made thinks a bit more clear. though i still don't understand why than the s2-lipliani driver works for me in normale lmce 0710 environment?
btw, i tried to install the multiproto mantis in 2 different systems with lmce. the result was no dmesg output at all.
will give 0810 a try...
btw i recommend sw-raid in linux though you have a real raid controller like rocketraid or sth.
thx,
mannheim
The driver works, since you have compiled and installed it for 7.10. But the software (VDR or Mythtv) does not know about this driver, since it is using a new API called S2API. This API was released 1 month ago in the latest linux kernel. VDR and Mythtv supports Multiproto wich is the API that the Mantis driver uses. If you want to know more about why Multiproto never got integrated in the kernel you will have to google it.
The Raid I am using is SW raid from 7.10. And sadly it is not detected in 8.10. I can browse it in KDE....
But right now I'm installing a fresh 8.10 so it might work...
hi again...
if someone has the same problem here a info how the card really works in my case.
first install the mantis driver, reboot.
than install the s2-liplianin driver, reboot.
tadaa... dmesg | grep -i dvb brings the correct output. channel scanning works. and live tv in lmce with vdr works, too ... all without cam module, didn't tested that because our provider don't scrambles the channels. (except of pay-tv of course)
if someone has a explanation for that behaviour i would be glad to know that ... or maybe some improvement suggestions ... :)
so long,
mannheim