hi, below you find the debug output my tt 2.3 premium works with qam256 - so it should not be a cable or wallplug problem marco ves1820: Detected Chip Version 0x7a ves1820: pwm=0x64 ves1820: Verbose Status: ves1820: VAFC 3 ves1820: VAGC 0xff ves1820: PWMREF 0x13 ves1820: MSE 0x56 ves1820: BER-RANGE 0 ves1820: Verbose Status: ves1820: VAFC -18 ves1820: VAGC 0xff ves1820: PWMREF 0x13 ves1820: MSE 0x58 ves1820: BER-RANGE 1 ves1820: Verbose Status: ves1820: VAFC 3 ves1820: VAGC 0xce ves1820: PWMREF 0x13 ves1820: MSE 0x16 ves1820: BER-RANGE 1 ves1820: AFC (3) -20215Hz ves1820: Verbose Status: ves1820: VAFC 3 ves1820: VAGC 0xff ves1820: PWMREF 0x13 ves1820: MSE 0x16 ves1820: BER-RANGE 1 ves1820: Verbose Status: ves1820: VAFC 3 ves1820: VAGC 0xff ves1820: PWMREF 0x13 ves1820: MSE 0x16 ves1820: BER-RANGE 1 ves1820: Verbose Status: ves1820: VAFC 3 ves1820: VAGC 0xff ves1820: PWMREF 0x13 ves1820: MSE 0x17 ves1820: BER-RANGE 1 ves1820: Verbose Status: ves1820: VAFC 3 ves1820: VAGC 0xff ves1820: PWMREF 0x13 ves1820: MSE 0x15 ves1820: BER-RANGE 1 ves1820: Verbose Status: ves1820: VAFC 3 ves1820: VAGC 0xff ves1820: PWMREF 0x13 ves1820: MSE 0x17 ves1820: BER-RANGE 1 ves1820: Verbose Status: ves1820: VAFC 3 ves1820: VAGC 0xff ves1820: PWMREF 0x13 ves1820: MSE 0x15 ves1820: BER-RANGE 0 On Wed, 2 Aug 2006, thomas schorpp wrote: > Marco Skambraks wrote: > > hi, > > I tried your patch with TT dvb-c 2.1 premium and the latest firmware 2623 > > kernel 2.6.13 and almost the latest dvb/v4l drivers > > my cable-provider is iesy (hessen) > > frq = 121mhz qam256 > > for NTV and some of the other private-channels > > the patch has no effect I've still several drop-outs > > if I watch a channel with qam256 modulation > > > > maybe I can support you with some debug output > > just tell me which data is important to improve the qam256 support in > > ves1820 > > > > marco > > > > On Wed, 2 Aug 2006, thomas schorpp wrote: > > > > > > patch is for developers and debugging only. > but I am interested in Your syslog output like this: > > Aug 2 21:49:00 tom1 kernel: ves1820: Verbose Status: > Aug 2 21:49:00 tom1 kernel: ves1820: VAFC -3 > Aug 2 21:49:00 tom1 kernel: ves1820: VAGC 0xff > Aug 2 21:49:00 tom1 kernel: ves1820: AGCCONF 0x13 > Aug 2 21:49:00 tom1 kernel: ves1820: AGCREF 0x13 > Aug 2 21:49:00 tom1 kernel: ves1820: PWMREF 0x13 > Aug 2 21:49:00 tom1 kernel: ves1820: MSE 0x16 > Aug 2 21:49:00 tom1 kernel: ves1820: BER-RANGE 0 > > maybe youve got a old wallplug with ~120MHz trap... > the qam256 problem is mainly frequency independend. > > > > > patch contains correction for viterbi monitor flag, wrong SYNC > > > register bit > > > used before in ves1820.c(?). > > > cant use hg head - doesnt build dvb-ttpci.ko dont know why, yet. > > > > > > y > > > tom > > > > > > > > > <schorpp> lo > > > <schorpp> I am on the qam256 problems with some FF cards dvb > > _______________________________________________ > > linux-dvb@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > -------------------------------------------------- AMMEC - Accessible Multimedia Entertainment Center http://www.ammec.de Email: Marco Skambraks <marco@xxxxxxxx> _______________________________________________ linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
