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 Manu
