<DIV>Thanks for the response. Unfortunately that didn't fix it.</DIV>
<DIV> </DIV>
<DIV>I tried both on the same line:</DIV>
<DIV>bttv card=0x71 i2c_hw=1 card=0x87 i2c_hw=0<BR>That locked up!</DIV>
<DIV> </DIV>
<DIV>Then I tried:</DIV>
<DIV>bttv card=0x71 i2c_hw=1</DIV>
<DIV>bttv card=0x87 i2c_hw=0</DIV>
<DIV>dvb-bt8xx</DIV>
<DIV>dst</DIV>
<DIV>That didn't lock up, but the analog tuner still doesn't work right.</DIV>
<DIV>When I do channel up or down in kdetv, tvtime or xawtv, the indicator changes, but the channel doesn't actually change.</DIV>
<DIV> </DIV>
<DIV>Just to be sure, I removed the DST card and analog worked fine again.</DIV>
<DIV> </DIV>
<DIV>Note--sometimes when I start analog mode, I see a green screen. I am able to get a picture back by doing azap on an 8VSB channel! If I azap a QAM256 channel, the picture goes green again. I don't know if this has anything to do with my problem, but it's something to look at anyway.</DIV>
<DIV> </DIV>
<DIV>I should mention that I am writing these lines in the kernel-2.6 file in /etc/modules.autoload.d.</DIV>
<DIV>It shouldn't matter, but just in case----</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Greg Farris</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Mike Krufky wrote:<BR><BR>> Manu Abraham wrote:<BR>><BR>>> GFarris wrote:<BR>>><BR>>>> I finally was able to get my computer to boot without locking up <BR>>>> while both the HDTV5 lite and the Twinhan DST (MOT) are installed by <BR>>>> switching pci slots with each other, and then doing:<BR>>>> bttv i2c_hw=1 card=0x71<BR>>>> dvb-bt8xx<BR>>>> dst<BR>>>> <BR>>>> However, now analog doesn't work with any of the usual programs. If <BR>>>> I re-scan, it only finds the channels it was last tuned to. If I <BR>>>> pull out the Twinhan, then analog works again. Weird.<BR>>><BR>>><BR>>> Probably it was writing to the dst (i2c) instead of the HDTV5. It <BR>>> should not be writing to the DST, the DST tunes properly in that case ?<BR>>> probably Michael Krufky can comment on the HDTV5, since he was <BR>>> working on the HDTV5 lite. Michael any
thoughts ?<BR>>><BR>>>> Also, I'd rather have the lite as the first card so I don't have to <BR>>>> specify the card # since I use it more than the Twinhan.<BR>>>> <BR>>>> Anyway, I don't understand how dst by itself, or with dvb-bt8xx can <BR>>>> work, since the Twinhan always barfs without the i2c_hw=1 parm.<BR>>><BR>>><BR>> Hmm... Looks like the Twinhan barfs without the i2c_hw=1 parm, but in <BR>> my experience FusionHDTV5 Lite barfs WITH the i2c_hw=1 parm.<BR>><BR>> I'm not sure what i2c_hw=1 does, nor did I do any research on it. <BR>> What I do know, is that modprobing dvb-bt8xx alone is enough to get <BR>> FusionHDTV5 Lite to work. (dvb-bt8xx will automatically load up bt878 <BR>> and bttv modules)<BR><BR><BR>i2c_hw=1 causes bttv to use Hardware I2C instead of S/W based <BR>Bitbanging. I think the HDTV5 uses S/W I2C<BR><BR>><BR>> Maybe the proper fix to make these cards work together
would be to <BR>> cause FusionHDTV5 Lite to ignore the i2c_hw=1 parm. Manu, what do you <BR>> think?<BR>><BR><BR>I think individually it can be called as card=0x68/0x71 i2c_hw=1 <BR>card=0x87 i2c_hw=0<BR>Maybe Greg could try that addition and try it like that and see how it <BR>goes .. ?<BR><BR>ie modprobe bttv card=0x68/0x71 i2c_hw=1 card=0x87 i2c_hw=0<BR><BR>Manu<BR><BR><BR></DIV>