[linux-dvb] Problems using two devices (ff & budget)

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

 



Hello,
first I'd like to excuse me for bothering linux-dvb and vdr mailing
list... I don't know where the problem is related to.

Yesterday I upgraded my vdr system into a two dvb-s devices system.
First it all seems to work. But in the evening I realized that recording
is not possible.

In the logs I found:
Aug 28 17:53:42 cinema vdr[5733]: timer 6 (7 1656-1810 'Wissen Extrem:
Monster Maschinen') stop
Aug 28 17:53:42 cinema vdr[5733]: timer 6 (7 1656-1810 'Wissen Extrem:
Monster Maschinen') start
Aug 28 17:53:42 cinema vdr[5733]: record
/video/Wissen_Extrem:_Monster_Maschinen/2005-08-28.16:56.50.99.rec

---------------------------------------------
dmesg shows the following using the b2c2-flexcop-pci module of kernel
2.6.12.5 I just compiled and I am using:
during initialization:
b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip unloaded
successfully
b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded
successfully
flexcop-pci: will use the HW PID filter.
flexcop-pci: card revision 1
ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [LNKD] -> GSI 10 (level,
low) -> IRQ 10
DVB: registering new adapter (FlexCop Digital TV device).
b2c2-flexcop: MAC address = 00:d0:d7:03:22:17
b2c2-flexcop: i2c master_xfer failed
b2c2-flexcop: i2c master_xfer failed
b2c2-flexcop: i2c master_xfer failed
mt352_read_register: readreg error (reg=127, ret==-121)
b2c2-flexcop: i2c master_xfer failed
i2c_readbytes: i2c read error (addr 0a, err == -121)
b2c2-flexcop: i2c master_xfer failed
stv0297_readreg: readreg error (reg == 0x80, ret == -22)
b2c2-flexcop: found the vp310 (aka mt312) at i2c address: 0x0e
DVB: registering frontend 1 (Zarlink VP310 DVB-S)...
b2c2-flexcop: initialization of 'SkyStar 2 DVB-S (old version)' at the
'PCI' bus controlled by a 'FlexCopII' complete

an a lot of
b2c2-flexcop: i2c master_xfer failed
messages!

---------------------------------------------

dmesg shows the following using the skystar2 module of kernel 2.6.12.5 I
just compiled and I also tried:
during initialization:
ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [LNKD] -> GSI 10 (level,
low) -> IRQ 10
drivers/media/dvb/b2c2/skystar2.c: FlexCopII(rev.130) chip found
drivers/media/dvb/b2c2/skystar2.c: the chip has 6 hardware filters
driver_initialize MAC address = 00:d0:d7:03:22:17:00:00
DVB: registering new adapter (SkyStar2).
i2c_readbytes: i2c read error (addr 0a, err == -121)
mt352_read_register: readreg error (reg=127, ret==-121)
DVB: registering frontend 1 (Zarlink VP310 DVB-S)...


The first dvb device is of course the Hauppauge Nexus 2.1 (DVB-S) which
is the primary device.
PrimaryDVB = 1
PrimaryLimit = 0 (and tried with 51 (because of DefaultPriority = 50))

The secound device is a Skystar 2 (Rev. 2.3 with flexcop II)

I don't know what to do.
Is kernel 2.6.12.5 equipped with a recent dvb driver version?

I read about problems using the skystar device but that should have been
solved - suggestions?

Greetings,

Ingo Seeberg


## PLEASE USE ENCRYPTION AND/OR YOUR SIGNATURE FOR ANY MESSAGE ##
------------------------------------------------------
PGP public key

http://www.et-inf.fho-emden.de/~iseebe/iseebe_pub.asc
------------------------------------------------------



[Index of Archives]     [Linux Media]     [Video 4 Linux]     [Asterisk]     [Samba]     [Xorg]     [Xfree86]     [Linux USB]

  Powered by Linux