[mythtv-users] Problem with PVR-350 + LG TAPE tuner

Mike Burr mburr at pointdx.com
Mon Nov 8 18:31:45 UTC 2004 

Actually, I've got things working! The solution: apt-get dist-upgrade 
and a 2.6.8 kernel. I have no idea which of the hundreds of packages 
and/or kernel upgrades made the difference, but It's definitely fixed. 
Previously, my uptime record (for the video) was probably 12 hours. I'm 
beyond 72 hours now without a hitch. Lucky me.

For anyone with a Debian system and one of these cards: Let me know if 
you need help, I've managed to get things working without having to 
un-Debianize my machine hardly at all (just gotta look for those 
sources). It's nice not to have too many of those unaccounted-for 
binaries floating around.

sschaefer1 at woh.rr.com wrote:
> (This response pertains to kernel version 2.4.26 or 2.4.27 only.)
> 
> Sorry for not posting my information sooner. When I had gotten around to it originally, I had seen that there was a new patch for the 2.4.27 kernel, on whomever's website that was/don't remember.
> 
> Here is my the manually patched tuner.c and tuner.h files for 2.4.26 (should work fine for 2.4.27), that includes the new tuner type 47.
> 
> http://www.schaefer.dhcp.biz/tuner.c
> http://www.schaefer.dhcp.biz/tuner.h
> 
> Not that I care what version you use, but I'm here to say that ivtv-0.1.9 works flawlessly with my Hauppauge WinTV PVR 350 card. It has a the newer tuner type 47 so I had to patch the tuner module in the kernel AND in the bttv driver code, since it also has a copy of the tuner module. If you don't and it doesn't support type 47, and you use/install the bttv driver it will overwrite your patched tuner.o.
> 
> I use bttv-0.7.107 driver, so if you use bttv-0.9+ then you might be careful about the patch, I'm guessing that the bttv-0.9+'s tuner module is a little more recent than the kernel's (2.4.26/27's).
> 
> I manually edited the tuner.c/.h files, deleted tuner.o (with in the kernel tree), went back to the root of the kernel tree and executed "make modules;make modules_install", but keep in mind that the kernel I use is from this same source kernel tree... so my source tree configuration is in sync with my compiled kernel... if you have not compiled your own kernel then you might be in for some extra work.  I noticed a short discussion on "cloneconfig", personally never used it, but it sounds like it'd save you some time. I don't know for sure, but I don't think the tuner.o cares about the kernel's configuration (symbols and stuff) so you may be able to get away with just executing "make modules" and then copying the tuner.o into the proper /lib/modules/ location.
> 
> Feel free to contact me if you have questions or if I've confused you.
>    sschaefer1 at woh.rr.com
> 
> ----- Original Message -----
> From: mburr at pointdx.com
> Date: Saturday, November 6, 2004 0:38 am
> Subject: Re: [mythtv-users] Problem with PVR-350 + LG TAPE tuner
> 
> 
>>Quoting "Michael T. Dean" <mtdean at thirdcontact.com>:
>>
>>>mburr at pointdx.com wrote:
>>>
>>>
>>>>Quoting sschaefer1 at woh.rr.com:
>>>> 
>>>>
>>>>
>>>>>I recently purchased/installed/setup a Hauppauge WinTV PVR 350 
>>
>>(US/NTSC).> >>I'm running Slackware 10, Linux kernel 2.4.26, 
>>patched with video for
>>
>>>linux
>>>
>>>>>2.
>>>>>I had to further patch the tuner.h and tuner.c to know about 
>>
>>the type 47
>>
>>>>>(TUNER_LG_NTSC_TAPE).
>>>>>
>>>>>Let me know if you want instructions or more info.
>>>>>   
>>>>>
>>>>
>>>>Sure. That'd be great. I'm desperate at this point. I've had a 
>>
>>tough time
>>
>>>>locating the above mentioned patches.
>>>>
>>>
>>>I think Mike got things working, but for those searching the 
>>
>>lists, 
>>
>>>tuner patches are available at
>>>http://67.18.1.101/~ckennedy/ivtv/new_tuners/
>>
>>Unfortunately, I've still got some major stability problems. I do 
>>have all the
>>expected channels (presumabably I'd have 62+ if I had cable). 
>>Sound and
>>hardware
>>decoding work. But The card refuses to work for more than a couple 
>>of hours
>>without choking.
>>
>>I get a bunch of barf like this when it dies
>>=================
>>Nov  6 00:22:32 mythtv kernel: ivtv: IRQ: IVTV_IRQ_DEC_DMA_ERR 
>>intr 1
>>Nov  6 00:22:32 mythtv kernel: ivtv: DMA Registers State: xfer: 
>>0x00000000,state: 0x00000013 dec_addr: 0x00000000 enc_addr: 
>>0x18e7c000 control: 0x00000003
>>Nov  6 00:22:32 mythtv kernel: ivtv: DMA DEC Buffers:
>>Nov  6 00:22:32 mythtv kernel:  0x00000000:0x00000000:0x00000000
>>Nov  6 00:22:32 mythtv kernel: ivtv: DMA ENC Buffers:
>>Nov  6 00:22:32 mythtv kernel:  0x001186c0:0x18e44000:0x00004000
>>Nov  6 00:22:32 mythtv kernel:  0x0011c6c0:0x18e40000:0x80004000
>>Nov  6 00:22:32 mythtv kernel:  0x000feec0:0x18e68000:0x80004000
>>Nov  6 00:22:32 mythtv kernel:  0x000e9700:0x18aa0000:0x80004000
>>Nov  6 00:22:32 mythtv kernel:  0x000ed700:0x18c20000:0x80004000
>>Nov  6 00:22:32 mythtv kernel:  0x000f1700:0x18d70000:0x00004000
>>Nov  6 00:22:32 mythtv kernel:  0x000f5700:0x18d6c000:0x00004000
>>Nov  6 00:22:32 mythtv kernel:  0x000f9700:0x18d68000:0x00004000
>>Nov  6 00:22:32 mythtv kernel: ivtv: IRQ: IVTV_IRQ_DEC_DMA_ERR 
>>intr 2
>>Nov  6 00:22:32 mythtv kernel: ivtv: DMA Registers State: xfer: 
>>0x00000000,state: 0x00000003 dec_addr: 0x00000000 enc_addr: 
>>0x18e7c000 control: 0x00000003
>>Nov  6 00:22:32 mythtv kernel: ivtv: DMA DEC Buffers:
>>Nov  6 00:22:32 mythtv kernel:  0x00000000:0x00000000:0x00000000
>>Nov  6 00:22:32 mythtv kernel: ivtv: DMA ENC Buffers:
>>Nov  6 00:22:32 mythtv kernel:  0x001186c0:0x18e44000:0x00004000
>>Nov  6 00:22:32 mythtv kernel:  0x0011c6c0:0x18e40000:0x80004000
>>Nov  6 00:22:32 mythtv kernel:  0x000feec0:0x18e68000:0x80004000
>>Nov  6 00:22:32 mythtv kernel:  0x000e9700:0x18aa0000:0x80004000
>>Nov  6 00:22:32 mythtv kernel:  0x000ed700:0x18c20000:0x80004000
>>Nov  6 00:22:32 mythtv kernel:  0x000f1700:0x18d70000:0x00004000
>>Nov  6 00:22:32 mythtv kernel:  0x000f5700:0x18d6c000:0x00004000
>>Nov  6 00:22:32 mythtv kernel:  0x000f9700:0x18d68000:0x00004000
>>Nov  6 00:22:32 mythtv kernel: ivtv: Checking FW at 197611 jiffies
>>=================
>>
>>I've gone to a lot of trouble to simplify my hardware environment 
>>(disablethings, etc.) I've disabled my second CPU (yes it is an 
>>SMP box). I've been
>>trying to do some research before whining some more, but I don't 
>>think it can
>>be
>>said that I've got it "working" :-( 
>>
>>FYI, my environment:
>>
>>Dell Precision 420
>>Duel PIII 933Mhz (one currently disabled)
>>1GB ECC RAM
>>Intel PIIX4 Ultra 66 Chipset (1 disk, OS)
>>Ultra100 TX2 Chipset (3 disks, mythtv data. Currently only one 
>>disk in use)
>>Debian "Unstable"
>>2.4.27-1-386 Stock kernel package (Was 2.4.27-1-686-smp)
>>ivtv-0.2.0-pre2l
>>Just about every piece of on-board hardware disabled
>>SoundBlaster "Live" PCI sound card
>>
>>If you have any ideas and/or debugging tips, I'm all ears. I'll 
>>gladly write
>>some docs dealing with all of this stuff when I get everything 
>>fixed, if
>>there's
>>any interest...
>>
>>Thanks.
>>-Mike.
>>_______________________________________________
>>mythtv-users mailing list
>>mythtv-users at mythtv.org
>>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

More information about the mythtv-users mailing list