Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[vdr] HELP: VDR-1.3.15 does not work with a budget card (SkyStar2)
Dear VDR users and developers,
I did extensive testing, and the only conclusion, that's left, is, that
there is a problem with budget cards or in particular with the TechniSat
SkyStar 2 when using VDR.
I already posted some messages, but I did not get any replies, so I wonder
if this is a problem with my particular setup, of if noone is using a
SkyStar2 in such a mixed setup.
My latest test is with 2 FF cards (2x Hauppauge WinTV Nexus-S) and one
SkyStar2, so
device 1 = FF
device 2 = FF
device 3 = budget SkyStar2
A simple channellist mod for trying the use of all three cards:
Das Erste;ARD:11836:hC34:S19.2E:27500:101:102=deu:104:1:28106:1:1101:0
Bayerisches FS;ARD:11836:hC34:S19.2E:27500:201:202=deu:204:2:28107:1:1101:0
NDR FS MV;ARD:12109:hC34:S19.2E:27500:2401:2402=deu:2404:3:28224:1:1073:0
Now starting VDR and viewing the logfile while zapping from channel one to
three:
----- snip -----
Nov 13 00:13:56 avmaster vdr[12249]: VDR version 1.3.15 started
Nov 13 00:13:56 avmaster vdr[12249]: loading plugin:
/usr/lib/vdr/libvdr-remote.so
Nov 13 00:13:56 avmaster su(pam_unix)[12247]: session closed for user vdr
Nov 13 00:13:56 avmaster vdr[12249]: loading /etc/vdr/setup.conf
Nov 13 00:13:56 avmaster vdr[12249]: loading /etc/vdr/sources.conf
Nov 13 00:13:56 avmaster vdr[12249]: loading /etc/vdr/diseqc.conf
Nov 13 00:13:56 avmaster vdr[12249]: loading /etc/vdr/channels.conf
Nov 13 00:13:56 avmaster vdr[12249]: loading /etc/vdr/commands.conf
Nov 13 00:13:56 avmaster vdr[12249]: loading /etc/vdr/svdrphosts.conf
Nov 13 00:13:56 avmaster vdr[12249]: loading /etc/vdr/ca.conf
Nov 13 00:13:56 avmaster vdr[12249]: loading /etc/vdr/remote.conf
Nov 13 00:13:56 avmaster vdr[12249]: loading /etc/vdr/keymacros.conf
Nov 13 00:13:56 avmaster vdr[12249]: reading EPG data from /var/vdr/epg.data
Nov 13 00:13:56 avmaster vdr[12249]: probing /dev/dvb/adapter0/frontend0
Nov 13 00:13:56 avmaster vdr[12249]: probing /dev/dvb/adapter1/frontend0
Nov 13 00:13:56 avmaster vdr[12249]: tuner on device 1 thread started
(pid=12249, tid=-1210537040)
Nov 13 00:13:56 avmaster vdr[12249]: Section handler thread started
(pid=12249, tid=-1218929744)
Nov 13 00:13:56 avmaster vdr[12249]: probing /dev/dvb/adapter2/frontend0
Nov 13 00:13:56 avmaster vdr[12249]: tuner on device 2 thread started
(pid=12249, tid=-1227322448)
Nov 13 00:13:56 avmaster vdr[12249]: Section handler thread started
(pid=12249, tid=-1235715152)
Nov 13 00:13:56 avmaster vdr[12249]: probing /dev/dvb/adapter3/frontend0
Nov 13 00:13:56 avmaster vdr[12249]: found 3 video devices
Nov 13 00:13:56 avmaster vdr[12249]: initializing plugin: remote (0.3.2):
Remote control
Nov 13 00:13:56 avmaster vdr[12249]: setting primary device to 1
Nov 13 00:13:56 avmaster vdr[12249]: SVDRP listening on port 2001
Nov 13 00:13:56 avmaster vdr[12249]: starting plugin: remote
Nov 13 00:13:56 avmaster vdr[12249]: remote: using '/dev/input/event2'
Nov 13 00:13:56 avmaster vdr[12249]: remote-event2: autorepeat supported
Nov 13 00:13:56 avmaster vdr[12249]: remote-event2: exclusive access granted
Nov 13 00:13:56 avmaster vdr[12249]: loading
/etc/vdr/themes/sttng-default.theme
Nov 13 00:13:56 avmaster vdr[12249]: remote control remote-event2 - keys known
Nov 13 00:13:56 avmaster vdr[12249]: switching to channel 1
Nov 13 00:13:56 avmaster vdr[12249]: tuner on device 3 thread started
(pid=12249, tid=-1244107856)
Nov 13 00:13:56 avmaster vdr[12249]: Section handler thread started
(pid=12249, tid=-1252500560)
Nov 13 00:13:57 avmaster vdr[12249]: channel 11 (BR-alpha) event 00:00
'Tanz meines Lebens' status 4
Nov 13 00:13:57 avmaster vdr[12249]: channel 13 (Phoenix) event 00:00 'Im
Dialog' status 4
Nov 13 00:13:57 avmaster vdr[12249]: channel 12 (SÜDWEST BW) event 00:00
'Literatur im Foyer' status 4
Nov 13 00:13:57 avmaster vdr[12249]: channel 2 (Bayerisches FS) event 00:10
'Rundschau-Nacht' status 4
Nov 13 00:13:57 avmaster vdr[12249]: channel 10 (WDR Köln) event 23:30
'WDR-dok' status 4
Nov 13 00:13:57 avmaster vdr[12249]: channel 1 (Das Erste) event 22:45
'Chain of Command - Helden sterben nie' status 4
Nov 13 00:13:58 avmaster vdr[12249]: channel 17 (arte) event 23:50
'Wunderwaffe Westkonzert' status 4
Nov 13 00:13:58 avmaster vdr[12249]: channel 9 (SR Fernsehen Südwest) event
00:00 'Literatur im Foyer' status 4
Nov 13 00:13:58 avmaster vdr[12249]: channel 8 (hr-fernsehen) event 00:00
'strassen stars' status 4
Nov 13 00:13:59 avmaster vdr[12249]: switching to channel 2
Nov 13 00:13:59 avmaster vdr[12249]: transfer thread started (pid=12249,
tid=-1273750608)
Nov 13 00:13:59 avmaster vdr[12249]: receiver on device 2 thread started
(pid=12249, tid=-1282143312)
Nov 13 00:13:59 avmaster vdr[12249]: TS buffer on device 2 thread started
(pid=12249, tid=-1292637264)
Nov 13 00:14:03 avmaster vdr[12249]: switching to channel 3
Nov 13 00:14:03 avmaster vdr[12249]: transfer thread ended (pid=12249,
tid=-1273750608)
Nov 13 00:14:03 avmaster vdr[12249]: TS buffer on device 2 thread ended
(pid=12249, tid=-1292637264)
Nov 13 00:14:03 avmaster vdr[12249]: buffer stats: 51888 (2%) used
Nov 13 00:14:03 avmaster vdr[12249]: receiver on device 2 thread ended
(pid=12249, tid=-1282143312)
Nov 13 00:14:03 avmaster vdr[12249]: buffer stats: 52264 (1%) used
Nov 13 00:14:04 avmaster vdr[12249]: changing pids of channel 1103 from
901+901:902:204 to 201+201:202:204
Nov 13 00:14:08 avmaster vdr[12249]: ERROR: device 3 has no lock, can't
attach receiver!
Nov 13 00:14:08 avmaster vdr[12249]: transfer thread started (pid=12249,
tid=-1282143312)
Nov 13 00:14:17 avmaster vdr[12249]: caught signal 15
Nov 13 00:14:17 avmaster vdr[12249]: transfer thread ended (pid=12249,
tid=-1282143312)
Nov 13 00:14:17 avmaster vdr[12249]: buffer stats: 0 (0%) used
Nov 13 00:14:17 avmaster vdr[12249]: saved setup to /etc/vdr/setup.conf
Nov 13 00:14:17 avmaster vdr[12249]: tuner on device 1 thread ended
(pid=12249, tid=-1210537040)
Nov 13 00:14:17 avmaster vdr[12249]: Section handler thread ended
(pid=12249, tid=-1218929744)
Nov 13 00:14:17 avmaster vdr[12249]: tuner on device 2 thread ended
(pid=12249, tid=-1227322448)
Nov 13 00:14:17 avmaster vdr[12249]: Section handler thread ended
(pid=12249, tid=-1235715152)
Nov 13 00:14:17 avmaster vdr[12249]: tuner on device 3 thread ended
(pid=12249, tid=-1244107856)
Nov 13 00:14:18 avmaster vdr[12249]: Section handler thread ended
(pid=12249, tid=-1252500560)
Nov 13 00:14:18 avmaster vdr[12249]: stopping plugin: remote
Nov 13 00:14:18 avmaster vdr[12249]: =====================
Nov 13 00:14:18 avmaster vdr[12249]: EPG bugfix statistics
Nov 13 00:14:18 avmaster vdr[12249]: =====================
Nov 13 00:14:18 avmaster vdr[12249]: IF SOMEBODY WHO IS IN CHARGE OF THE
EPG DATA FOR ONE OF THE LISTED
Nov 13 00:14:18 avmaster vdr[12249]: CHANNELS READS THIS: PLEASE TAKE A
LOOK AT THE FUNCTION cEvent::FixEpgBugs()
Nov 13 00:14:18 avmaster vdr[12249]: IN VDR/epg.c TO LEARN WHAT'S WRONG
WITH YOUR DATA, AND FIX IT!
Nov 13 00:14:18 avmaster vdr[12249]: =====================
Nov 13 00:14:18 avmaster vdr[12249]: Fix Hits Channels
Nov 13 00:14:18 avmaster vdr[12249]: 0 73 Bayerisches FS, SÜDWEST BW,
Phoenix, rbb Brandenburg, BR-alpha, Das Erste, WDR Köln, ...
Nov 13 00:14:18 avmaster vdr[12249]: 2 62 Bayerisches FS, SÜDWEST BW,
Phoenix, rbb Brandenburg, BR-alpha, Das Erste, WDR Köln, ...
Nov 13 00:14:18 avmaster vdr[12249]: 3 47 KiKa
Nov 13 00:14:18 avmaster vdr[12249]: 4 5 SÜDWEST BW, SR Fernsehen
Südwest
Nov 13 00:14:18 avmaster vdr[12249]: 6 288 SÜDWEST BW, Bayerisches FS,
WDR Münster, Das Erste, NDR FS MV, arte, WDR Köln, ...
Nov 13 00:14:18 avmaster vdr[12249]: 7 1 KiKa
Nov 13 00:14:18 avmaster vdr[12249]: =====================
Nov 13 00:14:18 avmaster vdr[12249]: exiting
----- snip -----
It does not matter if the budget card is device 2 or 3, my former test were
with only one FF + the SkyStar2.
All my system, kernel, config, drivers and access to all three cards are
OK. I can use "scan" and "szap" on all three devices without any problem
and with positiv FE_SIGNAL_LOCK, the SkyStar2 is working just fine, even
with accessing AstraHD (I checked the picture output with mplayer several
times, so it is not only about feedback from the various programs in the
console).
So everything seems to work, but nevertheless VDR simply can not access the
SkyStar2, it always leeds to this "ERROR: device X has no lock, can't
attach receiver!".
I really would appreciate some input on that matter, it simply is driving
me crazy! There is no possible explaination, that it's about the kernel,
the use of NPTL, the use of any kernel-config, or something else concering
my system, because otherwise all the rest would not work that well. VDR
1.3.15 is confirmed to work fine with NPTL enabled and a recent 2.6.9
kernel, I also can confirm this, when it comes down to FF cards, but it's
now about my budget SkyStar2.
Is there anything special to consider, when using a budget card??? I did
not find any setting, that would specify something explicitely for a budget
card.
I found a patch on vdr-portal.de concerning the tuner-lock-timeout, but
that one did not change anything.
I'm lost, I spent much too much time in tracking down that problem, and I
am not a single step further to the goal. FF cards work fine, even when
having more than one in my machine, but the budget SkyStar2 simply does not
want to work with my VDR setup. No need to ask about additional plugins
that may cause problem, there are none, I'm just using plain VDR 1.3.15 +
remote-plugin.
Please someone with the knowledge take a look at my case. All the former
test-results are enclosed.
Date: Thu, 11 Nov 2004 12:00:58 +0100
To: vdr@linuxtv.org
From: post <post@mhr.at>
Subject: VDR-1.3.15 has a problem with one FF + one budget card
Dear VDR users and developers,
It seems there is a problem with the actual VDR version, as it can not
access my budget card. I have a Nexus-S as device 1, and the TechniSat
Skystar2 as device 2.
VDR simply can not access device 2, all I get is "ERROR: device 2 has no
lock, can't attach receiver!".
I already did extensive testing, and my latest tries brought up, that my
hardwaresetup is indeed working fine, and that it is not a
system-configuration or driver problem. The latest test was:
szap -a 0 -r -n 1
mplayer -cache 4096 - < /dev/dvb/adapter0/dvr0
and
szap -a 1 -r -n 1
mplayer -cache 4096 - < /dev/dvb/adapter1/dvr0
which both brought up the signal in mplayer.
So I can scan for channels, and I can watch a signal on both cards, but
VDR always reports "ERROR: device 2 has no lock, can't attach receiver!",
and I have no idea, what else to try, and what the problem could be.
It's just plain VDR 1.3.15 without any additional plugins (except the
remote-plugin), my VDR_OPTS are "aio analogtv doubleepg hdtv
instant-replay jumpplay submenu" for the patches, that get added by the
genoo ebuild.
Someone please have a look, I really don't know what to do now, my only
option would be to swap the SkyStar2 against a second FF (but that only
would be the last possibility, if no solution should be found, and if it
should work fine with a second FF one).
Below is all the information, gathered until now.
Date: Thu, 11 Nov 2004 08:24:59 +0100
To: vdr@linuxtv.org
From: post <post@mhr.at>
Subject: HELP NEEDED: SkyStar2 budget card driving me crazy!
Dear VDR users and developers,
This thread was taken over from the linux-dvb mailing list (former
subject: FE_REFACTURING: skystar2: no data), because I not so sure any
more, that my problem has something to do with the dvb-kernel driver at all.
It's about a setup with kernel 2.6.9, dvb-kernel from actual CVS, one FF
card + one budget card (+ one analog card for use with the anlog plugin),
and VDR 1.3.15 (until now only with the remote-plugin).
> I don't really know, if my problem has to do with that matter at all,
but I
> can access my SkyStar2 without problem, when I use the "scan" utility
from
> the dvb-apps package. But as soon as I try to pause a live-event in
VDR, it
> tells:
>
> vdr[11272]: switching device 2 to channel 1
> vdr[11272]: timer 1 (1 1901-2201 '@TITLE EPISODE') start
> vdr[11272]: Title: 'Get the Clip' Subtitle: '(null)'
> vdr[11272]: record /avdata/vdr/@Get_the_Clip__/2004-11-10.19:01.10.01.rec
> vdr[11272]: creating directory
> /avdata/vdr/@Get_the_Clip__/2004-11-10.19:01.10.01.rec
> vdr[11272]: recording to
> '/avdata/vdr/@Get_the_Clip__/2004-11-10.19:01.10.01.rec/001.vdr'
> vdr[11272]: ERROR: device 2 has no lock, can't attach receiver!
> vdr[11272]: buffer stats: 0 (0%) used
> vdr[11272]: replay (null)
> rc-scripts: Failed to stop vdr.
>
> (device 1 is a FF, device 2 is the SkyStar2)
This is so weird. Formerly I thought, it was working with the dvb-kernel
that came with sources 2.6.8.1 and 2.6.9, but it wasn't either (don't
know what happened, but looks like that test with pausing a live-signal
not always swaped over to device 2, and as long as VDR only accessed
device 1 everthing seemed to be working, but VDR completele gets messed
up and performs an emergency exit if there is no lock to a device)
.
I always get that "ERROR: device 2 has no lock, can't attach receiver",
regardless of the used linux kernel and dvb-kernel version.
This is really driving me insane. I did serveral tests, but I am really
not sure what else to take a look at. I don't think it's a problem with
VDR, because otherwise others would have experienced the same problem as
well, and there is nothing to configure for that use of one FF + one
budget card. This is the actual situation:
I use now kernel 2.6.9 with the dvb-kernel from CVS (just by updating
with "cvs update -dP" without any tag).
This is the dmesg output during boot:
----- snip -----
saa7146: register extension 'dvb'.
ACPI: PCI interrupt 0000:01:07.0[A] -> GSI 19 (level, high) -> IRQ 209
saa7146: found saa7146 @ mem f92a0000 (revision 1, irq 209) (0x13c2,0x0003).
DVB: registering new adapter (Technotrend/Hauppauge WinTV Nexus-S rev2.X).
adapter has MAC addr = 00:d0:5c:23:6c:82
dvb-ttpci: gpioirq unknown type=0 len=0
dvb-ttpci: info @ card 0: firm f0240009, rtsl b0250018, vid 71010068, app
8000261c
dvb-ttpci: firmware @ card 0 supports CI link layer interface
dvb-ttpci: Crystal audio DAC @ card 0 detected
saa7146_vv: saa7146 (0): registered device video0 [v4l2]
DVB: registering frontend 0 (ST STV0299 DVB-S)...
dvb-ttpci: found av7110-0.
ACPI: PCI interrupt 0000:01:09.0[A] -> GSI 17 (level, high) -> IRQ 217
drivers/media/dvb/b2c2/skystar2.c: FlexCopII(rev.130) chip found
drivers/media/dvb/b2c2/skystar2.c: the chip has 6 hardware filters
DVB: registering new adapter (SkyStar2).
DVB: registering frontend 1 (ST STV0299 DVB-S)...
bttv: driver version 0.9.15 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
ACPI: PCI interrupt 0000:01:0a.0[A] -> GSI 16 (level, high) -> IRQ 201
bttv0: Bt878 (rev 2) at 0000:01:0a.0, irq: 201, latency: 32, mmio: 0xd8000000
bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
bttv0: using: Hauppauge (bt878) [card=10,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=00ffffdb [init]
bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
bttv0: Hauppauge eeprom: model=61324, tuner=Philips FI1216 MK2 (5), radio=no
bttv0: using tuner=5
bttv0: i2c: checking for MSP34xx @ 0x80... found
msp3400: Ignoring new-style parameters in presence of obsolete ones
msp34xx: init: chip=MSP3410D-B4 +nicam +simple
msp3410: daemon started
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
tvaudio: Ignoring new-style parameters in presence of obsolete ones
tvaudio: TV audio decoder + audio/video mux driver
tvaudio: known chips:
tda9840,tda9873h,tda9874h/a,tda9850,tda9855,tea6300,tea6420,tda8425,pic16c54
(PV951),ta8874z
tuner: Ignoring new-style parameters in presence of obsolete ones
tuner: chip found at addr 0xc2 i2c-bus bt878 #0 [sw]
tuner: type set to 5 (Philips PAL_BG (FI1216 and compatibles)) by bt878
#0 [sw]
bttv0: registered device video1
bttv0: registered device vbi0
bttv0: PLL: 28636363 => 35468950 .. ok
r8169: eth0: link up
i2c_adapter i2c-3: nForce2 SMBus adapter at 0x5000
i2c_adapter i2c-4: nForce2 SMBus adapter at 0x5500
flexcop_i2c_func
----- snip -----
device 1 = Hauppauge WinTV Nexus-S + CI-Slot-Adapter 545
device 2 = TechniSat SkyStar2
(device 3 = Hauppauge WinTV analog card -> this one will be used with the
VDR analog plugin)
This is the lsmod output:
----- snip -----
Module Size Used by
fglrx 222908 7
eeprom 6496 0
w83l785ts 6236 0
asb100 19612 0
i2c_sensor 2944 3 eeprom,w83l785ts,asb100
i2c_nforce2 4992 0
tuner 18020 0
tvaudio 19744 0
msp3400 20584 0
bttv 140108 0
i2c_algo_bit 7880 1 bttv
btcx_risc 3656 1 bttv
skystar2 25284 0
mt352 4676 1 skystar2
dvb_ttpci 78604 0
saa7146_vv 43520 1 dvb_ttpci
video_buf 16388 2 bttv,saa7146_vv
saa7146 14436 2 dvb_ttpci,saa7146_vv
ves1820 4932 1 dvb_ttpci
tda8083 4996 1 dvb_ttpci
stv0297 7744 1 dvb_ttpci
sp8870 6220 1 dvb_ttpci
ves1x93 5764 1 dvb_ttpci
ttpci_eeprom 2112 1 dvb_ttpci
nvidia_agp 5404 1
agpgart 26280 2 nvidia_agp
evdev 6848 0
snd_intel8x0 26984 0
snd_ac97_codec 62736 1 snd_intel8x0
snd_mpu401_uart 5632 1 snd_intel8x0
snd_rawmidi 19236 1 snd_mpu401_uart
snd_seq_oss 29760 0
snd_seq_midi_event 5952 1 snd_seq_oss
snd_seq 46032 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 6152 3 snd_rawmidi,snd_seq_oss,snd_seq
snd_pcm_oss 45480 0
snd_pcm 80392 2 snd_intel8x0,snd_pcm_oss
snd_timer 20100 2 snd_seq,snd_pcm
snd_page_alloc 7240 2 snd_intel8x0,snd_pcm
snd_mixer_oss 16128 1 snd_pcm_oss
snd 44900 11
snd_intel8x0,snd_ac97_codec,snd_mpu401_uart,snd_rawmidi,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore 7008 1 snd
stv0299 8772 2 skystar2,dvb_ttpci
i2c_core 18384 20
eeprom,w83l785ts,asb100,i2c_sensor,i2c_nforce2,tuner,tvaudio,msp3400,bttv,i2c_algo_bit,skystar2,mt352,dvb_ttpci,ves1820,tda8083,stv0297,sp8870,ves1x93,ttpci_eeprom,stv0299
----- snip -----
I can use the "scan" utility on both devices without any problem
I can use "szap" without any problem. The result looks like follows:
szap test on Hauppauge WinTV Nexus-S (device 1):
----- snip -----
root # szap -a 0 -n 86
reading channels from file '/root/.szap/channels.conf'
zapping to 86 'VIVA;VIVA Fernsehen GmbH & Co. KG':
sat 0, frequency = 12669 MHz V, symbolrate 22000000, vpid = 0x0135, apid
= 0x0136
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 03 | signal 9814 | snr 7d16 | ber 0000ff30 | unc 00000000 |
status 1f | signal adc1 | snr e5e6 | ber 00003400 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal adc0 | snr e5ec | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal aefd | snr e5e0 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal af00 | snr e607 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal af00 | snr e5e9 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal adca | snr e5e0 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
----- snip -----
szap test on TechniSat SkyStar2 (device 2):
----- snip -----
root # szap -a 1 -n 86
reading channels from file '/root/.szap/channels.conf'
zapping to 86 'VIVA;VIVA Fernsehen GmbH & Co. KG':
sat 0, frequency = 12669 MHz V, symbolrate 22000000, vpid = 0x0135, apid
= 0x0136
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
status 03 | signal a403 | snr 7608 | ber 0000537f | unc 00000000 |
status 1f | signal bbec | snr e30d | ber 00000124 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal bd5b | snr e35e | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal bccf | snr e33a | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal bddf | snr e31f | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal bdbd | snr e307 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ba8d | snr e30a | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
----- snip -----
From what is shown here, I would say, everything is working, but due to
my setup I only ever managed to get a picture shown from the FF card. I
have installed VDR 1.3.15 and kvdr (which just accesses the v4l
interface of the FF card), so I can see a picture on my monitor when the
FF card is tuned to a channel. But I don't know how to perform a test to
get a picture on screen from the SkyStar2 without VDR.
I have mplayer compiled with the dvb extension, but for some reason I can
not get it to work with one of the dvb cards as input, because it always
complains about "dvb configuration emtpy, exit" (I've copied over a
channel.conf in szap format, but I couldn't find any hint about a "dvb
configuration" in the mplayer documents):
----- snip -----
$ mplayer dvb://1@
MPlayer 1.0pre4-3.3.4 (C) 2000-2004 MPlayer Team
CPU: Advanced Micro Devices Athlon MP/XP/XP-M Barton 2757 MHz (Family: 6,
Stepping: 0)
Detected cache-line size is 64 bytes
CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 0
Kompiliert für x86 CPU mit folgenden Erweiterungen: MMX MMX2 3DNow
3DNowEx SSE
Reading config file /usr/share/mplayer/mplayer.conf
Reading config file /home/master/.mplayer/config
Reading /home/master/.mplayer/codecs.conf: Can't open
'/home/master/.mplayer/codecs.conf': Datei oder Verzeichnis nicht gefunden
Reading /usr/share/mplayer/codecs.conf: 66 audio & 176 video codecs
font: can't open file: /home/master/.mplayer/font/font.desc
Font /usr/share/mplayer/font/font.desc loaded successfully! (206 chars)
Verwende Linux Hardware RTC-Timing (1024Hz)
Can't open input config file /home/master/.mplayer/input.conf: Datei oder
Verzeichnis nicht gefunden
Input config file /usr/share/mplayer/input.conf parsed: 53 binds
Spiele dvb://1@
DVB CONFIGURATION IS EMPTY, exit
Failed to open dvb://1@
Beende... (Ende der Datei)
----- snip -----
(I know this it OT, but maybe someone can give me some advice, how to fix
that to be able to test my setup with another software than VDR)
I really totally lost here at the moment. I didn't want to fiddle arround
that much. I only want to use VDR with some plugins on that machine, and
I thought I can set this box up within a few days, but now I am already
playing arround for more than a week, and I still have no clue how to
solve that problem with "ERROR: device 2 has no lock, can't attach receiver"
--
Sincerely,
Master One
Home |
Main Index |
Thread Index