Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] Re: FE_REFACTURING: skystar2: no data



At 22:12 10.11.2004, you wrote:

The change was stv0299. Is your card using this frontend?
Yes.

> 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)
>
Sorry, I don't use vdr very often, so, I cannot tell whether this is a vdr
problem or not.
I'll check vdr with my - now working - ss2.6B tomorrow.
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".

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 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.

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