On 6/18/07, Michael Krufky <mkrufky@xxxxxxxxxxx> wrote:
Jake,
Jake Thompson wrote:
> Hi All,
> Hope I have finally landed in the right place, and I apologize ahead of
> time
> if this has already been covered, but my attempts to find the answer in the
> archive has not worked yet.
This is the right place.
> I have a KWorld ATSC-110 that I use to record QAM256 streams in mythtv. I
> have FC6 x86_64 and kernel 2.6.20-1.2952.fc6 currently.
>
> I have can no longer tune any of my channels, I get a singal strength that
> bounces all over the place and never gets a lock.
Are there any error / warning messages in dmesg when you experience these problems?
> On the 2.6.20-1.2933.fc6 kernel it works like a charm and always has, if I
> rill back to the previous kernel it will continue to work.
>
> On the channels that I should be receiving, the signal strength bounces
> around, on channels that I should not be getting it just stays steady at
> 99%. On the older kernel it did not bounce around at all.
>
> I just downloaded the latest version from CVS, but that has not solved the
> problem either.
We dont use cvs anymore... Try the latest modules from mercurial --
http://linuxtv.org/hg/v4l-dvb ... howto @ http://linuxtv.org/repo
> Here is some output:
Is the following output from a GOOD configuration? ...or is this the problem
configuration? It all looks fine to me.
> dmesg:
> saa7133[0]: found at 0000:01: 07.0, rev: 240, irq: 17, latency: 32, mmio:
> 0xfdfff000
> saa7133[0]: subsystem: 17de:7350, board: Kworld ATSC110
> [card=90,autodetected]
> saa7133[0]: board init: gpio is 100
> saa7133[0]: i2c eeprom 00: de 17 50 73 ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: registered device video1 [v4l2]
> saa7133[0]: registered device vbi1
> nxt200x: NXT2004 Detected
> DVB: registering new adapter (saa7133[0])
> DVB: registering frontend 0 (Nextwave NXT200X VSB/QAM frontend)...
> nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
> nxt2004: Waiting for firmware upload(2)...
> nxt2004: Firmware upload complete
>
>
> lsmode | grep saa
> saa7134_dvb 25484 0
> dvb_pll 25348 2 saa7134_dvb
> saa7134 148564 1 saa7134_dvb
> ir_kbd_i2c 18576 1 saa7134
> video_buf_dvb 15748 1 saa7134_dvb
> tda1004x 24068 1 saa7134_dvb
> video_buf 35204 6 saa7134_dvb,saa7134,video_buf
> _dvb,cx8800,cx88xx,bttv
> ir_common 45572 4 saa7134,ir_kbd_i2c,cx88xx,bttv
> compat_ioctl32 17152 3 saa7134,cx8800,bttv
> videodev 36864 5 saa7134,cx8800,cx88xx,bttv,ivtv
> v4l2_common 28288 11
> saa7134,cx8800,cx88xx,bttv,compat_ioctl32,wm8775,cx25840,tuner,ivtv,cx2341x,videodev
>
> v4l1_compat 20356 4 saa7134,bttv,ivtv,videodev
> i2c_core 32833 18
> nxt200x,saa7134_dvb,dvb_pll,saa7134,ir_kbd_i2c,tda1004x,i2c_ec,cx88xx,bttv,lirc_i2c,wm8775,cx25840,tuner,ivtv,i2c_algo_bit,tveeprom,i2c_nforce2,nvidia
^^^ and we see here that i2c-core is being used as a module, so that rules out
the i2c-compiled as static bug that markus solved recently.
> Any help would be greatly appreciated. Not too sure how to troubleshoot
> this.
Try mercurial. If that doesnt work, then I need to see dmesg during a bad
configuration where nothing works.
Good Luck,
Michael Krufky
_______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
