Brian, Okay yeah its looking like quite probably that the codec chip is set wrong. Fortunately its fairly easy to check this. All you have to do is in the config line change CODEC_SAA7111 to be CODEC_SAA7113. The SAA7113 driver module provides slightly more debug than the SAA7111 because its not quite as mature, but this is to our advantage in this case. When you run xawtv now and look at the system log you should get a line that appears as follows: Jan 12 13:32:56 puny kernel: saa7113: attaching SAA7113 at 0x4a The important part of this line is the address given at the end of the line, in this case 0x4a. This is the standard address for the SAA7113. It also has an alternate possibility of 0x48, but I would not expect it to be on this address. The unfortunate thing here is that 0x48 is the standard address for the SAA7111, and this can cause some confusion. So if the SAA7113 driver does attach to 0x4a, then you definately have the SAA7113 chip. In which case it should just be a case of tracking down the right tuner chip. If that doesn't work, we may have to look more closely at determining exactly what chips are in your WinTV Cheers, Cameron
