Re: Twinhan cab-ci problem in Fedora Core 5

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

 



I finally got some time to work with my myth-computer during the
holidays. This time it is installed with fedora core 6.

As Raido suggested, it seems there is a confilict between the Cinergy
400 card (SAA7134) and the Twinhan cab-ci (VP2031A, dst) card.
I am not very good at device drivers, so there are probably some faults
in the theories below. Please apologize!

When the computer boots up, the SAA7134 module is autoloaded, and with
it the module ir-kbd-i2c. This seems to be in the way for the dst_probe
procedure. I think that is why the dmesg contains the line:

i2c IR (Hauppauge): unknown key: key=0x3f raw=0x3fff down=1

when dst_probe writes through the I2C bus.

After removing the Cinergy card, it is possible to load the dvb-bt8xx
module correctly.

Also, the commands:

rmmod saa7134
rmmod ir-kbd-i2c
modprobe dst verbose=4
modprobe dst_ca verbose=4
modprobe dvb-bt8xx
modprobe saa7134

... with both cards installed seems to do the trick.

The dmesg for this is:

---------------------------------------------
DVB: registering new adapter (bttv0).
dst(0) dst_comm_init: Initializing DST.
dst(0) dst_gpio_outb: mask=[ffffffff], enbb=[0001], outhigh=[0000]
dst(0) rdc_reset_state: Resetting state machine
dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0000]
dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002]
writing [ 00 06 00 00 00 00 00 fa ]
dst(0) dst_gpio_outb: mask=[ffffffff], enbb=[0000], outhigh=[0000]
dst(0) read_dst: reply is 0xff
dst(0) dst_wait_dst_ready: dst wait ready after 1
dst(0) read_dst: reply is 0x0
 0x44 0x43 0x54 0x2d 0x43 0x49 0x6c
dst(0) dst_gpio_outb: mask=[ffffffff], enbb=[0000], outhigh=[0000]
dst(0) dst_get_device_id: Recognise [DCT-CI]
dst(0) dst_type_print: DST type: cable
DST type flags : 0x1000 VLF 0x8 firmware version = 1 0x10 firmware
version = 2
dst(0) dst_comm_init: Initializing DST.
dst(0) dst_gpio_outb: mask=[ffffffff], enbb=[0001], outhigh=[0000]
dst(0) rdc_reset_state: Resetting state machine
dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0000]
dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002]
writing [ 00 0a 00 00 00 00 00 f6 ]
dst(0) dst_gpio_outb: mask=[ffffffff], enbb=[0000], outhigh=[0000]
dst(0) read_dst: reply is 0xff
dst(0) dst_wait_dst_ready: dst wait ready after 0
dst(0) read_dst: reply is 0x0
 0x8 0xca 0x10 0x17 0x19 0x29 0xc5
dst(0) dst_get_mac: MAC Address=[00:08:ca:17:19:00]
dst(0) dst_get_tuner_info: DST TYpe = MULTI FE
dst(0) dst_comm_init: Initializing DST.
dst(0) dst_gpio_outb: mask=[ffffffff], enbb=[0001], outhigh=[0000]
dst(0) rdc_reset_state: Resetting state machine
dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0000]
dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002]
writing [ 00 13 00 00 00 00 00 ed ]
dst(0) dst_gpio_outb: mask=[ffffffff], enbb=[0000], outhigh=[0000]
dst(0) read_dst: reply is 0xff
dst(0) dst_wait_dst_ready: dst wait ready after 0
dst(0) read_dst: reply is 0xbc
 0x1 0x0 0x0 0x0 0x0 0x0 0x43
dst(0) dst_get_tuner_info: DST type has TS=188
dst(0) dst_get_tuner_info: DST has Daughterboard
dst_ca_attach: registering DST-CA device
DVB: registering frontend 0 (DST DVB-C)...
input: i2c IR (Hauppauge) as /class/input/input5
ir-kbd-i2c: i2c IR (Hauppauge) detected at i2c-0/0-001a/ir0 [bt878 #0
[hw]]
saa7130/34: v4l2 driver version 0.2.14 loaded
saa7134[0]: found at 0000:00:0c.0, rev: 1, irq: 21, latency: 32, mmio:
0xcfffbc00
saa7134[0]: subsystem: 153b:1142, board: Terratec Cinergy 400 TV
[card=8,autodetected]
saa7134[0]: board init: gpio is 50000
input: saa7134 IR (Terratec Cinergy 40 as /class/input/input6
tuner 1-0060: All bytes are equal. It is not a TEA5767
tuner 1-0060: chip found @ 0xc0 (saa7134[0])
tuner 1-0060: type set to 5 (Philips PAL_BG (FI1216 and compatibles))
saa7134[0]: i2c eeprom 00: 3b 15 42 11 ff ff ff ff ff ff ff ff ff ff ff
ff
saa7134[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff
saa7134[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff
saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff
saa7134[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff
saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff
saa7134[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff
saa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff
saa7134[0]: registered device video0 [v4l2]
saa7134[0]: registered device vbi0
---------------------------------------------
It seems that ir-kbd-i2 also here binds to bt878 (which should to be on
the Twinhan card). Both cards have remotes, though I only use one of
them (the Cinergy one).
I have not yet tested if any of the cards work, I guess that will be
next.

Is there a more elegant way to solve this than unloading and reloading
modules? Maybe some install or options lines in modprobe.conf?

I have also tested these two cards on an a-bit kv8 pro motherboard (VIA
K8T800 Pro chipset, socket 754, Athlon64 3400+, fedora core 5 64-bit).
That did not make any significant difference.

BR
Svante




_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

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

  Powered by Linux