Hi,
I uploaded the seventh version of the SpAn(=Spectrum Analyzer)-plugin
and the ninth version of the LCR(=Least Cost Routing)-plugin.
They can be found at http://lcr.vdr-developer.org/
Changelog LCR:
2008-08-13: Version 0.0.9
- switched to gettext; therefore vdr >= 1.5.7 is required.
- added italian language (thanks to Diego Pierotto for the translation).
Changelog SpAn:
2008-08-13: Version 0.0.7
- Cleaned up the translation.
- switched to gettext; therefore vdr >= 1.5.7 is required.…
[View More]
- added italian language (thanks to Diego Pierotto for the translation).
Kindly
Christian Leuschen
[View Less]
Hello all.
I've done some more debugging with both the dvb modules and vdr in debug mode.
So far my only clue is that sometime during normal operation, the link gets
reinitialised (dvb_ca_en50221_link_init) which finally fails with a timeout
from dvb_ca_en50221_wait_if_status. After that, everything is dead until I
restart vdr.
I have attached the debug output. I hope that at least now someone can please
point me into the right direction or maybe even has a idea what the problem
might …
[View More]be and how one could fix it.
Thanks a lot in advance.
Best regards,
Matthias Dahl
PS. Sorry for posting this both on the vdr and dvb list but I am still not
sure if this a dvb or vdr problem.
[View Less]
Hello!
I'm not living in an area where Digita transmits this channel via dvb-t, so I was
wondering if there are other .fi users who could record/dump some minutes of
this channel and upload it somewhere so we others could check the quality
etc :)
http://www.digita.fi/digita_dokumentti.asp?path=1840;3793;1973;9850;10653
-- Pasi
I receive 138 KU and I can use TT3200 to scan the following symbolrate:
12302 V 30000(DVB-S) 12401 V 22425(DVB-S) 12430 V 22425(DVB-S)
12490 V 21600(DVB-S) 12537 V 41250(DVB-S) 12646 V 22425(DVB-S)
But I can't scan the following symbolrate:
12354 V 43000(DVB-S) 12460 V 21600(DVB-S2) 12598 V 43000(DVB-S)
12720 V 43000(DVB-S)
If the symbolrate>=43000 or DVB-S2,the TT3200 can’t scan them?
I make and make install the recently multiproto.
My VDR:VDR1.7.0+H.264+xinelibputout+multiproto.…
[View More]
Who can tell me what I should do?
_________________________________________________________________
用手机MSN聊天写邮件看空间,无限沟通,分享精彩!
http://mobile.msn.com.cn/
[View Less]
Hello guys,
I have Fedora 9 with lastest kernel. I have Skystar 2 DVB PCI card rev 2.8.
As this revision is using FlexCopII DVB i needed to recompile v4l dvb
modules. I have downloaded lastest v4l using mercurial.
Now my Skystar 2 works fine with Fedora 9 . I am using Kaffeine , which
works fine.
My problem is :
I am trying to compile vdr-1.7.0 from source, when i will do "make" i will
get this error :
[root@home vdr-1.7.0]# make
In file included from audio.c:12:
dvbdevice.h:19:2: error: #…
[View More]error VDR requires Linux DVB driver API version
3.3!
In file included from dvbdevice.c:10:
dvbdevice.h:19:2: error: #error VDR requires Linux DVB driver API version
3.3!
In file included from dvbosd.c:15:
dvbdevice.h:19:2: error: #error VDR requires Linux DVB driver API version
3.3!
In file included from eitscan.c:13:
dvbdevice.h:19:2: error: #error VDR requires Linux DVB driver API version
3.3!
font.c:14:10: error: #include expects "FILENAME" or <FILENAME>
In file included from vdr.c:45:
dvbdevice.h:19:2: error: #error VDR requires Linux DVB driver API version
3.3!
make: *** Deleting file `.dependencies'
g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD
-DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE
-DVIDEODIR=\"/video\" -DCONFDIR=\"/video\" -DPLUGINDIR=\"./PLUGINS/lib\"
-DLOCDIR=\"./locale\" -I/usr/include/freetype2
-I/usr/src/v4l-dvb/linux/include audio.c
In file included from audio.c:12:
dvbdevice.h:19:2: error: #error VDR requires Linux DVB driver API version
3.3!
In file included from audio.c:12:
dvbdevice.h:38: error: 'dvbfe_delsys' does not name a type
make: *** [audio.o] Error 1
As i mentioned before, i had to recompile v4l-dvb modules, location is
/usr/src/v4l-dvb/.
I have edited Make.config and uncommented :
### The directory environment:
DVBDIR = /usr/src/v4l-dvb/linux
Which seems to me correct right?
Please point me to result.
Thanks in advance!
David
[View Less]
Hello all.
I am resending the following message because I didn't get any response so far
and in addition I am putting it on cc' to the vdr devel list. I'd look into
this issue myself, yet I don't have the necessary time to dive into the DVB
tree. So please, if anyone knows how to debug this or has any hint where the
problem could be located... I'd be more than grateful to hear about it.
By the way, just today after a few minutes of uptime with vdr 1.7.0, I got
those (increased the CAM …
[View More]check interval to 5 seconds btw):
vdr: [3280] ERROR: can't write to CI adapter on device 0: Input/output error
vdr: [3280] ERROR: can't write to CI adapter on device 0: Invalid argument
And the CAM stopped working until I restarted vdr. In one forum post someone
reported about similar problems with MythTV, so it's becoming more and more
likely that this is indeed a problem within the dvb tree. And if it's a SMP
problem, it should get fixed because multicore systems will be everywhere
pretty soon.
Thanks again.
----------------------------------------------------------------------------------
Hello all.
After minutes or hours or days of running vdr 1.4.7, I get the following
messages in my syslog:
dvb_ca adapter 0: CAM tried to send a buffer larger than the ecount size!
dvb_ca adapter 0: DVB CAM link initialisation failed :(
When running vdr 1.6.x, the problems are even more frequent/worse and I get
those:
dvb_ca adapter 0: CAM tried to send a buffer larger than the link buffer
size (192 > 128)!
vdr: [3140] ERROR: can't write to CI adapter on device 0: Input/output error
dvb_ca adapter 0: CAM tried to send a buffer larger than the ecount size!
dvb_ca adapter 0: DVB CAM link initialisation failed :(
The result is always the same, the CAM stops decrypting and I have to restart
vdr. After a lot of searching around, I've learnt that I am not the only one
with those problems and they seem to be related to multi core systems. I read
that pining vdr down to one CPU core might help... and indeed it did.
This cannot be a hardware related issue because...
1) meanwhile I switched from a NForce 590 SLI to a X48 chipset and thus also
from an AMD64 X2 5600+ (Winchester) to an Intel Core2Duo E8400 (Wolfdale)
2) I swapped my KNC One DVB-C Plus for a new one
And the problems persist.
I've already written a report to the vdr list which was unfortunately ignored
and besides it looks more like a dvb issue itself.
I was unable to test the kernel with nosmp or similar (which was reported by
others to work just fine) because I need this machine to work on.
I've attached detailed informations about my system and I'd be more than happy
to help fix this once and for all, so one can savely rely on vdr again.
Last but not least, I am using a AlphaCrypt Light module with 3.15 firmware.
Thanks a lot in advance for every help.
Best regards,
Matthias Dahl
[View Less]
I can't scan HD channel with TT3200 in VDR
multiproto+VDR-1.7.0+H.264+xineliboutput
138 KU
TT3200+VDR:
scan play
12302 V 30000(DVB-S) ok ok
12354 V 43000(DVB-S) ok no
12401 V 22425(DVB-S) ok ok
12430 V 22425(DVB-S) ok ok
12460 V 21600(DVB-S2) no no
12490 V 21600(DVB-S) ok ok
12537 V 41250(DVB-S) ok ok
12598 V 43000(DVB-S) ok no
12646 V 22425(DVB-S) ok ok
12720 V 43000(DVB-S) ok no
…
[View More]SS2+VDR:
scan play
12302 V 30000(DVB-S) ok ok
12354 V 43000(DVB-S) ok ok
12401 V 22425(DVB-S) ok ok
12430 V 22425(DVB-S) ok ok
12460 V 21600(DVB-S2) no no
12490 V 21600(DVB-S) ok ok
12537 V 41250(DVB-S) ok ok
12598 V 43000(DVB-S) ok ok
12646 V 22425(DVB-S) ok ok
12720 V 43000(DVB-S) ok ok
TT3200+DVB Viewer:
scan play
12302 V 30000(DVB-S) ok ok
12354 V 43000(DVB-S) ok ok
12401 V 22425(DVB-S) ok ok
12430 V 22425(DVB-S) ok ok
12460 V 21600(DVB-S2) ok ok
12490 V 21600(DVB-S) ok ok
12537 V 41250(DVB-S) ok ok
12598 V 43000(DVB-S) ok ok
12646 V 22425(DVB-S) ok ok
12720 V 43000(DVB-S) ok ok
TT3200+VDR、SS2+VDR、TT3200+DVB Viewer tested in the same PC.
Who can tell me what I should do? thank you!
_________________________________________________________________
MSN 中文网,最新时尚生活资讯,白领聚集门户。
http://cn.msn.com
[View Less]
I can't scan HD channel with TT3200 in VDRmultiproto+VDR-1.7.0+H.264+xineliboutput
138 KU
TT3200+VDR:
scan play12302 V 30000(DVB-S) ok ok 12354 V 43000(DVB-S) ok no12401 V 22425(DVB-S) ok ok12430 V 22425(DVB-S) ok ok12460 V 21600(DVB-S2) no no12490 V 21600(DVB-S) ok ok12537 V 41250(DVB-S) ok ok12598 V 43000(DVB-S) ok no12646 V 22425(DVB-S) ok ok12720 V 43000(DVB-S) ok no
SS2+VDR:
scan …
[View More]play12302 V 30000(DVB-S) ok ok 12354 V 43000(DVB-S) ok ok12401 V 22425(DVB-S) ok ok12430 V 22425(DVB-S) ok ok12460 V 21600(DVB-S2) no no12490 V 21600(DVB-S) ok ok12537 V 41250(DVB-S) ok ok12598 V 43000(DVB-S) ok ok12646 V 22425(DVB-S) ok ok12720 V 43000(DVB-S) ok ok
TT3200+DVB Viewer:
scan play12302 V 30000(DVB-S) ok ok 12354 V 43000(DVB-S) ok ok12401 V 22425(DVB-S) ok ok12430 V 22425(DVB-S) ok ok12460 V 21600(DVB-S2) ok ok12490 V 21600(DVB-S) ok ok12537 V 41250(DVB-S) ok ok12598 V 43000(DVB-S) ok ok12646 V 22425(DVB-S) ok ok12720 V 43000(DVB-S) ok ok
TT3200+VDR、SS2+VDR、TT3200+DVB Viewer tested in the same PC.
Who can tell me what I should do? thank you!
_________________________________________________________________
看MSN史诗巨片,票选人气角色,赢取PSP等诸多好礼!
http://im.msn.cn/
[View Less]
Upgraded to Debian Sid and Kernel 2.6.26
Multiproto fails once again.
What's up duck ?
----
lassehome:/usr/src/multiproto# make
make -C /usr/src/multiproto/v4l
make[1]: Entering directory `/usr/src/multiproto/v4l'
creating symbolic links...
Kernel build directory is /lib/modules/2.6.26-1-686/build
make -C /lib/modules/2.6.26-1-686/build SUBDIRS=/usr/src/multiproto/v4l
modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
CC [M] /usr/src/multiproto/v4l/cx25840-core.o
In …
[View More]file included from /usr/src/multiproto/v4l/cx25840-core.c:42:
/usr/src/multiproto/v4l/../linux/include/media/v4l2-i2c-drv-legacy.h: In
function 'v4l2_i2c_drv_init':
/usr/src/multiproto/v4l/../linux/include/media/v4l2-i2c-drv-legacy.h:197: warning: assignment
from incompatible pointer type
/usr/src/multiproto/v4l/cx25840-core.c: At top level:
/usr/src/multiproto/v4l/cx25840-core.c:71: error: conflicting type
qualifiers for 'addr_data'
/usr/src/multiproto/v4l/../linux/include/media/v4l2-i2c-drv-legacy.h:41:
error: previous declaration of 'addr_data' was here
make[3]: *** [/usr/src/multiproto/v4l/cx25840-core.o] Error 1
make[2]: *** [_module_/usr/src/multiproto/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/usr/src/multiproto/v4l'
make: *** [all] Error 2
----
[View Less]
you must patch the multiproto with fix-jdelvare-i2c-i2c-constify-client-address-data.patch.
download the fix-jdelvare-i2c-i2c-constify-client-address-data.patch and copyt to /multiproto/linux
then patch it.
_________________________________________________________________
MSN 中文网,最新时尚生活资讯,白领聚集门户。
http://cn.msn.com