Annotation of dvb-kernel/README.bt8xx, revision 1.8
1.4 hunold 1: How to get the Nebula, PCTV and Twinhan DST cards working
2: =========================================================
1.1 holger 3:
1.6 hunold 4: This class of cards has a bt878a as the PCI interface, and require the
5: bttv driver.
1.2 honan 6:
1.6 hunold 7: Please pay close attention to the warning about the bttv module options
8: below for the DST card.
1.2 honan 9:
1.8 ! hunold 10: 1) Loading Modules
1.4 hunold 11: ==================
1.1 holger 12:
1.6 hunold 13: In general you need to load the bttv driver, which will handle the gpio
14: and i2c communication for us. Next you need the common dvb-bt8xx device
15: driver and one frontend driver.
16:
17: The bttv driver will HANG YOUR SYSTEM IF YOU DO NOT SPECIFY THE
18: COORECT CARD ID! A list of possible card ids can be found inside
1.7 hunold 19: "bttv-cards.c" inside the bttv driver package.
1.1 holger 20:
1.2 honan 21: Pay attention to failures to load these frontends.
22: (E.g. dmesg, /var/log/messages).
1.3 honan 23:
1.8 ! hunold 24: 2a) Nebula / Pinnacle PCTV
1.4 hunold 25: --------------------------
26:
27: $ modprobe bttv i2c_hw=1 card=0x68
28: $ modprobe dvb-bt8xx
29:
30: For Nebula cards use the "nxt6000" frontend driver:
31: $ modprobe nxt6000
32:
33: For Pinnacle PCTV cards use the "cx24110" frontend driver:
34: $ modprobe cx24110
35:
1.8 ! hunold 36: 2b) TwinHan
1.4 hunold 37: -----------
38:
39: $ modprobe bttv i2c_hw=1 card=0x71
40: $ modprobe dvb-bt8xx
41: $ modprobe dst
1.3 honan 42:
1.6 hunold 43: The value 0x71 will override the PCI type detection for dvb-bt8xx,
1.7 hunold 44: which is necessary for TwinHan cards.
1.6 hunold 45:
46: If you're having an older card (blue color circuit) and card=0x71 locks
47: your machine, try using 0x68, too. If that does not work, ask on the
48: mailing list.
1.3 honan 49:
1.6 hunold 50: The DST module takes a couple of useful parameters, in case the dst
51: drivers fails to detect your type of card correctly.
1.3 honan 52:
53: dst_type takes values 0 (satellite), 1 (terrestial TV), 2 (cable).
54:
55: dst_type_flags takes bit combined values:
56: 1 = new tuner type packets. You can use this if your card is detected
57: and you have debug and you continually see the tuner packets not
58: working (make sure not a basic problem like dish alignment etc.)
59:
60: 2 = TS 204. If your card tunes OK, but the picture is terrible, seemingly
61: breaking up in one half continually, and crc fails a lot, then
62: this is worth a try (or trying to turn off)
63:
64: 4 = has symdiv. Some cards, mostly without new tuner packets, require
65: a symbol division algorithm. Doesn't apply to terrestial TV.
66:
67: You can also specify a value to have the autodetected values turned off
68: (e.g. 0). The autodected values are determined bythe cards 'response
69: string' which you can see in your logs e.g.
70:
71: dst_check_ci: recognize DST-MOT
72:
73: or
74:
75: dst_check_ci: unable to recognize DSTXCI or STXCI
LinuxTV legacy CVS <linuxtv.org/cvs>