[linux-dvb] Partially resolved HDTV5 lite and Twinhan DST together + dst module question

GFarris gfarris at pacbell.net
Thu Oct 13 05:11:14 CEST 2005

Thanks for the response.  Unfortunately that didn't fix it.
I tried both on the same line:
bttv card=0x71 i2c_hw=1 card=0x87 i2c_hw=0
That locked up!
Then I tried:
bttv card=0x71 i2c_hw=1
bttv card=0x87 i2c_hw=0
That didn't lock up, but the analog tuner still doesn't work right.
When I do channel up or down in kdetv, tvtime or xawtv, the indicator changes, but the channel doesn't actually change.
Just to be sure, I removed the DST card and analog worked fine again.
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.
I should mention that I am writing these lines in the kernel-2.6 file in /etc/modules.autoload.d.
It shouldn't matter, but just in case----
Greg Farris
Mike Krufky wrote:

> Manu Abraham wrote:
>> GFarris wrote:
>>> I finally was able to get my computer to boot without locking up 
>>> while both the HDTV5 lite and the Twinhan DST (MOT) are installed by 
>>> switching pci slots with each other, and then doing:
>>> bttv i2c_hw=1 card=0x71
>>> dvb-bt8xx
>>> dst
>>> However, now analog doesn't work with any of the usual programs. If 
>>> I re-scan, it only finds the channels it was last tuned to. If I 
>>> pull out the Twinhan, then analog works again. Weird.
>> Probably it was writing to the dst (i2c) instead of the HDTV5. It 
>> should not be writing to the DST, the DST tunes properly in that case ?
>> probably Michael Krufky can comment on the HDTV5, since he was 
>> working on the HDTV5 lite. Michael any thoughts ?
>>> Also, I'd rather have the lite as the first card so I don't have to 
>>> specify the card # since I use it more than the Twinhan.
>>> Anyway, I don't understand how dst by itself, or with dvb-bt8xx can 
>>> work, since the Twinhan always barfs without the i2c_hw=1 parm.
> Hmm... Looks like the Twinhan barfs without the i2c_hw=1 parm, but in 
> my experience FusionHDTV5 Lite barfs WITH the i2c_hw=1 parm.
> I'm not sure what i2c_hw=1 does, nor did I do any research on it. 
> What I do know, is that modprobing dvb-bt8xx alone is enough to get 
> FusionHDTV5 Lite to work. (dvb-bt8xx will automatically load up bt878 
> and bttv modules)

i2c_hw=1 causes bttv to use Hardware I2C instead of S/W based 
Bitbanging. I think the HDTV5 uses S/W I2C

> Maybe the proper fix to make these cards work together would be to 
> cause FusionHDTV5 Lite to ignore the i2c_hw=1 parm. Manu, what do you 
> think?

I think individually it can be called as card=0x68/0x71 i2c_hw=1 
card=0x87 i2c_hw=0
Maybe Greg could try that addition and try it like that and see how it 
goes .. ?

ie modprobe bttv card=0x68/0x71 i2c_hw=1 card=0x87 i2c_hw=0


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.linuxtv.org/pipermail/linux-dvb/attachments/20051012/c5ae9e38/attachment-0001.htm

More information about the linux-dvb mailing list