I am trying to get a MythTV setup working with a DViCO FusionHDTV7 Dual Express using Mythbuntu 8.10 and I have been able to generate a channels.conf file using the latest v4l-dvb source code and the scan utility that comes with the dvb-utils in Mythbuntu (the dvbscan utility in latest dvb-apps source code give me the error "Unable to query frontend status"). I am also able to watch channels using mplayer, but the the problem is that MythTV does not identify any channels. I am able to watch channels using MythTV, but I have to manually enter the channel data since the tuning is not working. The belief is that the signal strength and SNR output must be incorrect and that is causing the problem with MythTV. I would like to help get this fixed, so others don't have the problems that I have run into, so what can I do to help get the signal strength and SNR outputs working? If it's helpful, I have attached an example output using azap with one of the channels that I can watch with mplayer: using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 503028615 Hz video pid 0x0011, audio pid 0x0014 status 01 | signal e000 | snr e450 | ber 00000000 | unc 00000000 | status 1f | signal 00ff | snr 00ff | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal 00ff | snr 00ff | ber 00000ab7 | unc 00000ab7 | FE_HAS_LOCK status 1f | signal 00fa | snr 00fa | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal 00fa | snr 00fa | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal 00fa | snr 00fa | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal 00fa | snr 00fa | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal 00fa | snr 00fa | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal 00fa | snr 00fa | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1f | signal 00fa | snr 00fa | ber 00000000 | unc 00000000 | FE_HAS_LOCK Thanks, Dave -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
