Title: Converted from Rich Text
I think it would more be an issue with some hardware in your pc or the mainboard itself generating frequencies disturbing this channel. If the machines are at different locations, it might also be a portable phone or wireless transmitter that is causing interference. DECT phones always transmit continously, even if you are not talking on them actualy
 
________________ Original message ________________
Subject: Re: [ivtv-users] bad reception on only one channel. Help!
Author: "scott" <[EMAIL PROTECTED]>
Date: 16th January 2006 10:29:17
 
tried some more stuff tonight in attempt to get to the bottom of this thing. here's what i know:

- tried removing 2nd tuner (pvr-250) from system. now using only pvr-350 w/ tv-out. no change in ch. 9 reception
- tried disabling pvr-350 hw mpeg decode, no change.
- tried disabling pvt-350 tv-out and used computer monitor instead. still no change.

finally, i took my pvr-250 and threw it in my windows box. after loading windows drivers and apps, viola! ch. 9 comes in loud and clear. i am forced to conclude from these finding that i have an ivtv driver issue. could it be that i need to use a different tuner type? tveeprom reports tuner type 2 (see below), but could it be wrong? any ideas?

--scott
----- Original Message ----
Date: Thu, 12 Jan 2006 19:32:13 -0800 (PST)
From: scott <[EMAIL PROTECTED]>
Subject: [ivtv-users] bad reception on only one channel. Help!
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"

I'm having a single-channel reception problem, and am hoping some genius out there might have some suggestions on how I could resolve it.
I have a dual tuner system with a pvr-250 and a 350 running KnoppMyth, and am using the 350's tv-out. All channels come in fine except channel 9, which just happens to be NBC. I can't live without scrubs, so I'd like to get this resolved. If I can do that, i can cancel my tivo service and move over to mythtv permanently!

Channel 9 is getting some "rainbow" colored interference that spans the range from annoying to uwatchable. A pic of the problemcan be found here. It happens all over the screen, although my photo only captured part of it in that instant.

here's what I know already:
- signal strength from the cable line in to my apartment is very strong
- Tivo and my TV do not exhibit the problem
- both tuners (250 and 350) exhibit the problem
- both tuners are the same type (type 2)
here's what I've tried already, with no luck:
- replace all splitters, cables
- run direct line from primary cable drop to a single pvr tuner input
- tried mythbox at a friend's house
- upgrade mythtv
- upgrade ivtv driver
- fine-tune reception from setup
- run extra ground lines from mythbox to various places
- isolate mythbox chassis ground (i know i know, its dangerous)
- searched ivtv-dev forum (no luck)
- searched mythtv users/dev forums (no luck)

here are my system specs:
KnoppMyth R5A26 (Knoppix based)
Athlon XP 2200+
Soyo K7VME Motherboard (KM400 chipset)
512 megs RAM
200 Gb Seagate baracude IV 7200 RPM HD
PVR-250, PVR-350
250-watt microATX seasonic power supply

Anyone have any ideas? I can usually figure these things out, but I'm stumped on this one... thanks.

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.4.0 (tagged release) loading
ivtv: Linux version: 2.6.13.2-chw-3 SMP preempt 586 gcc-3.3
ivtv: In case of problems please include the debug info
ivtv: between the START INIT IVTV and END INIT IVTV lines when
ivtv: mailing the ivtv-devel mailinglist.
ivtv0: Autodetected WinTV PVR 350 card (iTVC15 based)
ACPI: PCI Interrupt 0000:00:08.0[A] -> GSI 16 (level, low) -> IRQ 18
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
msp34xx: ivtv version
msp34xx: init: chip=MSP3448W-A2, has NICAM support, simpler (G) no-thread mode
msp34xx: $Id$ compiled on: Oct 9 2005 22:52:16
ivtv0: i2c attach to card #0 ok [client=MSP3448W-A2, addr=40]
saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21]
tveeprom: ivtv version
tveeprom: Hauppauge: model = 48132, rev = J323, serial# = 7112712
tveeprom: tuner = Philips FM1236 (idx = 23, type = 2)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio processor = MSP4448 (type = 1b)
tveeprom: decoder processor = SAA7115 (type = 13)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
saa7127 0-0044: saa7127 found @ 0x88 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=saa7127, addr=44]
ivtv0: loading /lib/modules/ivtv-fw-enc.bin
ivtv0: loading /lib/modules/ivtv-fw-dec.bin
ivtv0: Encoder revision: 0x02040011
ivtv0: Decoder revision: 0x02020023
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
ivtv0: Create encoder radio stream
ivtv0: Allocate DMA decoder MPEG stream: 16 x 65536 buffers (1024KB total)
ivtv0: Allocate DMA decoder VBI stream: 512 x 2048 buffers (1024KB total)
ivtv0: Create decoder VOUT stream
ivtv0: Allocate DMA decoder YUV stream: 24 x 43200 buffers (1024KB total)
ivtv0: loading /lib/modules/ivtv_init_mpeg.bin
tuner: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles)) by ivtv i2c driver #0
ivtv0: Initialized WinTV PVR 350, card #0
ivtv: ====================== NEXT CARD ======================
ivtv1: Autodetected WinTV PVR 250 card (iTVC16 based)
ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 17 (level, low) -> IRQ 19
ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #1
ivtv1: i2c attach to card #1 ok [client=(tuner unset), addr=61]
msp34xx: ivtv version
msp34xx: init: chip=MSP3435G-B6, has NICAM support, simpler (G) no-thread mode
msp34xx: $Id$ compiled on: Oct 9 2005 22:52:16
ivtv1: i2c attach to card #1 ok [client=MSP3435G-B6, addr=40]
saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c driver #1)
ivtv1: i2c attach to card #1 ok [client=saa7115, addr=21]
tveeprom: ivtv version
tveeprom: Hauppauge: model = 32031, rev = B110, serial# = 6151093
tveeprom: tuner = Philips FI1236 MK2 (idx = 10, type = 2)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio processor = MSP3435 (type = a)
tveeprom: decoder processor = SAA7115 (type = 13)
ivtv1: i2c attach to card #1 ok [client=tveeprom, addr=50]
ivtv1: loading /lib/modules/ivtv-fw-enc.bin
ivtv1: Encoder revision: 0x02040011
ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv1: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv1: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv1: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles)) by ivtv i2c driver #1
ivtv1: Initialized WinTV PVR 250, card #1
ivtv: ==================== END INIT IVTV ====================


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ivtvdriver.org/pipermail/ivtv-users/attachments/20060113/3e3c4680/attachment.html

------------------------------

_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users




_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to