Glad to know I'm not the only one having this problem. I saw the thread from John Williams about something similar, although his description was that he was getting static, and in his logs he was having problems with the eeprom module not loading correctly, which I've looked for and do not have. I only have one tveeprom module and according to the logs it's loading correctly.
It is exactly as Richard describes where I can specify a channel to tune to and it gets it close enough so that if I'm watching carefully I can kinda see what the program on is between the flipping and vertical bars, and indeed it's the channel I specified. I always thought that the frequencies were a good guess for the card since they might be slightly different for each person and it was the job of the hardware tuner to take that guess and get to the closest good frequency, which it apparently isn't doing. Even manually passing frequencies to it using ptune.pl seems to get the exact same result unless I pass it a value far enough away from the correct frequency to get complete static. It's almost as if the tuner is homing in on the correct frequency plus an offset, so it never gets tuned in correctly. I'm going to try the card in a windows box tonight to see if it is indeed hardware related, but somehow I'm doubting that since it worked fine before and all I did was move it between two boxes. I'll also take some pictures of it during the move so that we can see if we're talking about the same card. -Kevin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Houser Sent: Monday, February 14, 2005 5:31 PM To: [email protected] Subject: Re: [ivtv-devel] Older PVR-250 card not tuning properly Not just you, I also have the same issue on an older 250 with tuner type 2. I had a camera on order to send in some pictures of the card per a request on this list, but just finally got it. I had been suspecting something physically happened to my card in the time it was unused, but your post definately makes me think it's something that changed in the driver now. My next window to get the card out of that machine is tonight. I'll get off my butt and send in the pictures and the rest of the debug info ASAP tonight. Btw, I bet your tuner mostly follows the stations correctly if you give it a shot. Ie., 46 is 46, just slightly scrambled, etc. This wouldn't likely happen if your card was using the wrong frequency standard (at least not on a good sample). Kevin Ulmes wrote: >I'm having a bit of trouble getting my PVR-250 card to work, or more >precisely tune correctly. The symptoms are that I can insert all the >drivers (ivtv, tuner, without any errors, however when I use mplayer to >view /dev/video0 I get what looks like a scrambled TV station (i.e. not >quite B&W static, but a really fuzzy image with bars that jumps all >over the place, and looks like a really badly tuned TV station). This >is a card from almost >2 years ago, so I'm pretty sure it's not that I have a new tuner that >isn't supported (that and it worked a while ago). > >I'm running gentoo (2004.3), using kernel 2.6.9-gentoo-r6 (preempt), >with an older PVR-250 card (Tuner type=2 according to the ivtv module's detection. >I've also tried setting the tuner type manually to 39 in case I had the >newer LG tuner with no luck) on an Athlon 2600+, using an nForce2 chipset. > >Here's what I've tried to no success already: >1. I figured I was using the wrong frequency tables and switched >between us-cable, us-cable-hrc, and even tried us-bcast just to make >sure (BTW I'm in Baltimore Maryland using Comcast standard cable as my >source) with no success. I was using the ptune-ui.pl script to do this >while watching video in mplayer. > >2. I tried using different versions of the driver. I started out with >0.2.0_rc3 from the gentoo portage tree, then switched back to >0.1.10-pre2-ck71d, and am now running 0.3.1z (although the ivtv kernel >log says it's 0.3.1y). All load correctly and have no errors as far as >I can see (well other than not working :). > >3. I've checked that the video source is good by doing the testing with >a TV plugged into the same source as the PVR-250 card is, and the TV is >able to tune properly. > >4. I've tried various versions of the firmware all to no avail. > >Next in the list to try is switching back to a 2.4.x kernel, but before >I do that I figured I'd post here and see if anyone could quickly point >out something I'm doing wrong. I've had this card working about a year >and a half ago in an older PII running slackware and a 2.4.x kernel, so >I'm pretty sure the hardware is good. I've included the kernel log >messages below, as well as an lsmod, and the firmware versions I'm >using. Any help would be appreciated :) > >-Kevin Ulmes > >MD5 hashes of the firmware I'm using: >305dba74bbe5905447add8883f3ecb68 ivtv-fw-dec.bin >ab75947ef1b086e26f9b08e628baa02e ivtv-fw-enc.bin > >Kernel Log: >Linux video capture interface: v1.00 >tuner: Ignoring new-style parameters in presence of obsolete ones >ivtv: Unknown parameter `mpg_buffers' >ivtv: ==================== START INIT IVTV ==================== >ivtv: version 0.3.1 (y) loading >ivtv: Linux version: 2.6.9-gentoo-r6 preempt K7 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. >ivtv: Autodetected WinTV PVR 250 card >ivtv: Found an iTVC16 based chip >ACPI: PCI interrupt 0000:01:07.0[A] -> GSI 5 (level, low) -> IRQ 5 >ivtv: Unreasonably low latency timer, setting to 64 (was 32) >ivtv: XXX PCI device: 0x01e0 vendor: 0x10de >msp34xx: ivtv version >msp34xx: init: chip=MSP3435G-B6, has NICAM support, simple (D) mode, >simpler >(G) no-thread mode >msp34xx: $Id$ compiled on: Dec 11 2004 23:34:39 >ivtv: i2c attach [client=MSP3435G-B6,ok] >saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005) >saa7115: detecting saa7115 client on address 0x42 >saa7115: writing init values >ivtv: i2c attach [client=saa7115[0],ok] >saa7115: status: (1E) 0x48, (1F) 0xc0 >tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 >ivtv: i2c attach [client=(tuner unset),ok] >tveeprom: Hauppauge: model = 32031, rev = B210, serial# = 6196441 >tveeprom: tuner = Philips FI1236 MK2 (idx = 10, type = 2) >tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000) >tveeprom: audio_processor = MSP3435 (type = 10) >ivtv: i2c attach [client=tveeprom[0],ok] >ivtv: Tuner Type 2, Tuner formats 0x00001000, Radio: yes, Model >0x00892450, Revision 0x00000000 >ivtv: NTSC tuner detected >ivtv: Radio detected >ivtv: Encoder revision: 0x02040011 >ivtv: Configuring WinTV PVR 250 card with 5 streams >ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes >total >ivtv: Registered v4l2 device, streamtype 0 minor 0 >ivtv: Create DMA stream 1 >ivtv: Registered v4l2 device, streamtype 1 minor 32 >ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total >ivtv: Registered v4l2 device, streamtype 2 minor 224 >ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes >total >ivtv: Registered v4l2 device, streamtype 3 minor 24 >ivtv: Create stream 4 >ivtv: Registered v4l2 device, streamtype 4 minor 64 >ivtv: Setting Tuner 2 >tuner: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles)) by >ivtv i2c driver #0 >saa7115: decoder set input (4) >saa7115: now setting Composite input >ivtv: Setting audio matrix to input 3, output 1 >ivtv: Switching standard to NTSC. >ivtv: ivtv_enc_thread: pid = 6723, itv = 0xe1991820 >saa7115: decoder set norm NTSC >saa7115: set audio: 0x01 >ivtv: Initialized WinTV PVR 250, card #0 >ivtv: ==================== END INIT IVTV ==================== > >Lsmod: >Module Size Used by >bttv 145356 0 >video_buf 17156 1 bttv >firmware_class 7808 1 bttv >v4l2_common 5120 1 bttv >btcx_risc 3976 1 bttv >lirc_i2c 6916 0 >lirc_dev 10892 2 lirc_i2c >tveeprom 11060 0 >ivtv 806660 1 >tuner 18852 0 >saa7115 11416 0 >msp3400 26168 0 >i2c_algo_bit 8584 2 bttv,ivtv >i2c_core 19216 7 >bttv,lirc_i2c,tveeprom,tuner,saa7115,msp3400,i2c_algo_bit >videodev 7552 2 bttv,ivtv >snd_pcm_oss 48552 0 >snd_mixer_oss 17792 1 snd_pcm_oss >snd_seq_oss 31744 0 >snd_seq_midi_event 6400 1 snd_seq_oss >snd_seq 49424 4 snd_seq_oss,snd_seq_midi_event >usbcore 102116 1 >snd_intel8x0 29900 0 >snd_ac97_codec 68816 1 snd_intel8x0 >snd_pcm 84872 2 snd_pcm_oss,snd_intel8x0 >snd_timer 21380 2 snd_seq,snd_pcm >snd_page_alloc 7688 2 snd_intel8x0,snd_pcm >gameport 3712 1 snd_intel8x0 >snd_mpu401_uart 6272 1 snd_intel8x0 >snd_rawmidi 20260 1 snd_mpu401_uart >snd_seq_device 6536 3 snd_seq_oss,snd_seq,snd_rawmidi >snd 47716 11 >snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_intel8x0,snd_ac97_cod >ec,sn d_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device >forcedeth 14848 0 > > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide Read honest & candid >reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >_______________________________________________ >ivtv-devel mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/ivtv-devel > > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
