ons, 30.04.2003 kl. 15.23 skrev Gerd Knorr: > Stian Jordet <liste@xxxxxxxxx> writes: > > > > What do you get with "audio_debug=1" ? > > > > It is quite hard to capture anything useful, since it doesn't happen > > everytime. But here is a log with some failed, and some succesful > > carrier detection. Hope this helps. > > > saa7134[0]/audio: scanning 5.500 MHz => dc is 7389 [1911/-5478] > > saa7134[0]/audio: scanning 6.000 MHz => dc is 3644 [-327/3317] > > saa7134[0]/audio: scanning 6.500 MHz => dc is 237 [-3/-240] > > saa7134[0]/audio: audio carrier scan failed, using 5.500 MHz [last detected] > > Which one is the correct carrier? 5.5 MHz? I don't know 100% sure, but I'm willing to bet some money on 5.5 MHz, because I used to hardcode 5500Hz in saa7134-tvaudio.c, and then it worked everytime. > > saa7134[0]/audio: scanning 5.500 MHz => dc is 258 [918/1176] > > saa7134[0]/audio: scanning 6.000 MHz => dc is 9053 [-1451/7602] > > saa7134[0]/audio: scanning 6.500 MHz => dc is 10 [132/142] > > saa7134[0]/audio: found PAL main sound carrier @ 6.000 MHz [9053/258] > > Or 6.0 MHz? Or different for different stations? Don't think it's different for different stations. See above. > Does it become better if you increase one or both of the delay defines > (SCAN_*_DELAY in saa7134-tvaudio.c)? No.. If there was any difference, it was to the worse, it seems. But as I said, it worked fine at the time of 2.5.65 (don't remember the date, but I have that kernel-image and modules still, and they work perfect). Best regards, Stian
