LinHES Forums :: View topic - Hauppage PVR-150 model 1045 problem with R5C7

The Wiki says

Quote:

NOTE! While 0.4.5 is now available I do NOT recommend using it, as my testing has shown driver freezes on a simple channel change.

It would be hard to be more specific, I figured that was a serious enough pathology for anyone. ;-)

There is a simple patch which might improve your colors. See the call out in on the wiki page to a color saturation patch for the cx25840 driver. It'll add another 5 minutes to your driver rebuild and it gave me a fairly sharp improvement.

lirc_dev: IR Remote Control driver registered, at major 61
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.4.4 (tagged release) loading
ivtv: Linux version: 2.6.15-chw-2 SMP preempt 586 gcc-3.3
ivtv: In case of problems please include the debug info between
ivtv: the START INIT IVTV and END INIT IVTV lines, along with
ivtv: any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected WinTV PVR 150 card (cx23416 based)
ACPI: PCI Interrupt 0000:00:0c.0[A] -> GSI 16 (level, low) -> IRQ 18
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom: ivtv version
tveeprom: Hauppauge: model = 26132, rev = G1B2, serial# = 9519520
tveeprom: tuner = <unknown> (idx = 112, type = 4)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio processor = CX25841 (type = 23)
tveeprom: decoder processor = CX25841 (type = 1c)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
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]
cx25840 1-0044: ivtv driver
cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 1-0044: loaded v4l-cx25840.fw firmware (14264 bytes)
ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02050032
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)
tuner: type set to 50 (TCL 2002N) by ivtv i2c driver #0
ivtv0: Initialized WinTV PVR 150, card #0
ivtv: ==================== END INIT IVTV ====================
lirc_pvr150: chip found with RX and TX
ivtv0: i2c attach to card #0 ok [client=Hauppauge PVR150 IR RX, addr=71]
ivtv0: i2c attach to card #0 ok [client=Hauppauge PVR150 IR TX, addr=70]
lirc_dev: lirc_register_plugin: sample_rate: 0
lirc_pvr150: firmware of size 209327 loaded
lirc_pvr150: 575 codesets loaded
lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0

Author:	SunTzuTech [ Wed Jun 07, 2006 6:54 am ]
Post subject:	Hauppage PVR-150 model 1045 problem with R5C7
I picked up a Hauppage PVR-150 (model 1045) with the dogbone remote and IR blaster (I can't wait to get this working with my cable box). In the meantime, I have loaded R5C7 about a half dozen times (or more) trying to get my Knoppmyth box working. I am current on ivtv-0.4.5, and have been messing around with the config file in /etc/mythtv/modules/ivtv, using the CompilingIVTV and the ConfiguringthePVR150 how-to's in the wiki (among other things) Mostly, all I get is static, with sound on the channel (so I can listen to the channel, at least I can clue in to whether I have the right channel guide since my cable company has 3 different listing for std cable). The remote is working like a champ, and I'll test the irblaster once I get some picture to go along with the sound. I have tried the following options in modules/ivtv option ivtv tuner=50 option ivtv tuner=39 option ivtv tuner=43 plus a mismash of variations culled from various wiki's, forums and how-to's. I have not updated the firmware, because it appears that the latest firmware is in R5C7, as I have checksum'd the installed version and what's available for the PVR-150 and they're the same. Later versions of the PVR-250 firmware are not extractable using the ivtvfwextract.pl script, but I'm not sure that it makes a difference given another webpage I read on how hauppage released their firmware and the later versions of the PVR-250 are all the same. Only other update I've made is to load the latest NVIDIA 8176 driver. Ideas? I must have done about 2 dozen reboots last night trying to get this working. HW: Aopen dual PII board, with 1 PII-1Ghz, WD 250GB 7200rpm 8MB cache, NVidia (PNY) FX5500, Creative SB 5.1 Live, PVR-150 model 1045, Dlink G520 wifi (Atheros) card, Via USB 2.0/1394 card, Intel Pro/100 on motherboard. 1.5GB RAM

Author:	nickread [ Wed Jun 07, 2006 5:02 pm ]
Post subject:
Are you using the right frequency set? And once you have a channel with sound, have you tried fine tuning to find the picture?

Author:	tjc [ Wed Jun 07, 2006 6:29 pm ]
Post subject:	Re: Hauppage PVR-150 model 1045 problem with R5C7
SunTzuTech wrote: I am current on ivtv-0.4.5 As I said elswhere, I strongly recommend falling back to 0.4.4 following the directions on the wiki. SunTzuTech wrote: Mostly, all I get is static, with sound on the channel (so I can listen to the channel, at least I can clue in to whether I have the right channel guide since my cable company has 3 different listing for std cable). Sounds like a tuning issue. Most likely the wrong frequency set as nickread suggested. SunTzuTech wrote: I have tried the following options in modules/ivtv option ivtv tuner=50 : : This really shouldn't be necessary. It sounds like you're thrashing around trying various "solutions" without doing the diagnostics. First things first. Is the card being recognized? Is the firmware getting loaded? See this wiki page for directions on how to extract the critical information from the logs. http://www.knoppmythwiki.org/index.php?page=CheckingLogFiles Post it here so we can help you look at it and diagnose the problem. Once you understand a problem the solution is generally much easier. SunTzuTech wrote: it appears that the latest firmware is in R5C7 This was true until very recently, however they just switched to a beta version of the one of the bits (possibly the v4l-cx25840.fw). However this is unlikely to be your problem.

Author:	SunTzuTech [ Thu Jun 08, 2006 7:42 pm ]
Post subject:	Re: Hauppage PVR-150 model 1045 problem with R5C7
tjc wrote: SunTzuTech wrote: I am current on ivtv-0.4.5 As I said elswhere, I strongly recommend falling back to 0.4.4 following the directions on the wiki. There's an awful lot of stuff in the wiki for the PVR150. It's hard to make heads or tails of it. Lord knows that some of my problem was having the wrong decoder (instead of the one for PVR-150). tjc wrote: SunTzuTech wrote: Mostly, all I get is static, with sound on the channel (so I can listen to the channel, at least I can clue in to whether I have the right channel guide since my cable company has 3 different listing for std cable). Sounds like a tuning issue. Most likely the wrong frequency set as nickread suggested. SunTzuTech wrote: I have tried the following options in modules/ivtv option ivtv tuner=50 : : This really shouldn't be necessary. It sounds like you're thrashing around trying various "solutions" without doing the diagnostics. First things first. Is the card being recognized? Is the firmware getting loaded? As far as I can tell, it's getting loaded. I'll include the appropriate part of the logs at the bottom of this response tjc wrote: See this wiki page for directions on how to extract the critical information from the logs. http://www.knoppmythwiki.org/index.php?page=CheckingLogFiles Post it here so we can help you look at it and diagnose the problem. Once you understand a problem the solution is generally much easier. As a last resort, I managed to find someone who had the same tuner hw (since hauppage can't seem to make up it's mind which tuner hw it's going to use in the PVR-150), with options tuner 55 Which got me a fuzzy picture, and a lockup whenever I changed a channel. I'm running a PNY FX5500 to a Sun 18" Flat Panel LCD at 1280x1024. Not sure if I should go with a smaller resolution to get a better picture. I think it's time to just punt, and reinstall again. I think I've messed up too much stuff at this point, and I'd rather just go with stock + the latest nvidia drivers and go from there. tjc wrote: SunTzuTech wrote: it appears that the latest firmware is in R5C7 This was true until very recently, however they just switched to a beta version of the one of the bits (possibly the v4l-cx25840.fw). However this is unlikely to be your problem. here's the logs you requested: lirc_dev: IR Remote Control driver registered, at major 61 ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.4.5 (tagged release) loading ivtv: Linux version: 2.6.15-chw-2 SMP preempt 586 gcc-3.3 ivtv: In case of problems please include the debug info between ivtv: the START INIT IVTV and END INIT IVTV lines, along with ivtv: any module options, when mailing the ivtv-users mailinglist. ivtv0: Autodetected WinTV PVR 150 card (cx23416 based) ACPI: PCI Interrupt 0000:00:0c.0[A] -> GSI 16 (level, low) -> IRQ 18 ivtv0: Unreasonably low latency timer, setting to 64 (was 32) tveeprom: ivtv version tveeprom: Hauppauge: model = 26132, rev = G1B2, serial# = 9519520 tveeprom: tuner = TCL M2523_5N_E (idx = 112, type = 50) tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000) tveeprom: audio processor = CX25841 (type = 23) tveeprom: decoder processor = CX25841 (type = 1c) ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] 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] cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0) cx25840 1-0044: loaded v4l-cx25840.fw firmware (14264 bytes) ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44] wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b] ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0: Encoder revision: 0x02050032 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) tuner: type set to 55 (TCL 2002MB) by ivtv i2c driver #0 ivtv0: Initialized WinTV PVR 150, card #0 ivtv: ==================== END INIT IVTV ==================== lirc_pvr150: chip found with RX and TX ivtv0: i2c attach to card #0 ok [client=Hauppauge PVR150 IR RX, addr=71] ivtv0: i2c attach to card #0 ok [client=Hauppauge PVR150 IR TX, addr=70] lirc_dev: lirc_register_plugin: sample_rate: 0 lirc_pvr150: firmware of size 209327 loaded lirc_pvr150: 575 codesets loaded lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0 Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected VIA Apollo Pro 133 chipset agpgart: AGP aperture is 128M @ 0xe0000000 Thanks for the response

Author:	tjc [ Thu Jun 08, 2006 8:42 pm ]
Post subject:	Re: Hauppage PVR-150 model 1045 problem with R5C7
SunTzuTech wrote: Which got me a fuzzy picture, and a lockup whenever I changed a channel. Exactly the behaviour that I saw with 0.4.5 in my testing. SunTzuTech wrote: tveeprom: tuner = TCL M2523_5N_E (idx = 112, type = 50) Type 50 just like mine, although a later version. Code: tveeprom: tuner = TCL 2002N 5H (idx = 99, type = 50) The rest looks OK. If you haven't already reinstalled try steps 1-4 from the CompileIvtv procedure. It should only take about 5 minutes, especially since the tarball for 0.4.4 is already in /usr/src so you can skip the wget. Look to make sure the kernel source is unpacked, unpack 0.4.4 and go from there.

LinHES Forums http://forum.linhes.org/

Hauppage PVR-150 model 1045 problem with R5C7 http://forum.linhes.org/viewtopic.php?f=2&t=10392	Page 1 of 1

Author:	SunTzuTech [ Fri Jun 09, 2006 7:08 am ]
Post subject:	Re: Hauppage PVR-150 model 1045 problem with R5C7
tjc wrote: SunTzuTech wrote: Which got me a fuzzy picture, and a lockup whenever I changed a channel. Exactly the behaviour that I saw with 0.4.5 in my testing. A description of the problem you saw would have been useful in the wiki. I would have known exactly I couldn't use ivtv-0.4.5. tjc wrote: SunTzuTech wrote: tveeprom: tuner = TCL M2523_5N_E (idx = 112, type = 50) Type 50 just like mine, although a later version. Code: tveeprom: tuner = TCL 2002N 5H (idx = 99, type = 50) The rest looks OK. If you haven't already reinstalled I reinstalled and made one minor mod. I have everything working for a std cable, by commenting out in /etc/mythtv/moduels/ivtv options msp3400 once=1 and adding options ivtv tuner=50 The colors seem to be a little washed out, but everything is nice and crisp. I will test the ir blaster this wekeend with my digital cable. (Joy, I have modify my Zap2It lineup again) tjc wrote: try steps 1-4 from the CompileIvtv procedure. It should only take about 5 minutes, especially since the tarball for 0.4.4 is already in /usr/src so you can skip the wget. Look to make sure the kernel source is unpacked, unpack 0.4.4 and go from there. Appreciate your patience. I swear I've had this configuration before. This should be fun. I just scheduled about 50 hours of recording and once I got used to the interface, it was even easier. Time to get another PVR-150 from circuit city.

Author:	tjc [ Fri Jun 09, 2006 7:26 am ]
Post subject:
The Wiki says Quote: NOTE! While 0.4.5 is now available I do NOT recommend using it, as my testing has shown driver freezes on a simple channel change. It would be hard to be more specific, I figured that was a serious enough pathology for anyone. There is a simple patch which might improve your colors. See the call out in on the wiki page to a color saturation patch for the cx25840 driver. It'll add another 5 minutes to your driver rebuild and it gave me a fairly sharp improvement.

Author:	SunTzuTech [ Fri Jun 09, 2006 12:22 pm ]
Post subject:
tjc wrote: The Wiki says Quote: NOTE! While 0.4.5 is now available I do NOT recommend using it, as my testing has shown driver freezes on a simple channel change. It would be hard to be more specific, I figured that was a serious enough pathology for anyone. My fault. It was there. I spent two-three days with nothing but static, then got sound but static. After another day, I got a fuzzy screen and the lockup, but hadn't reread the wiki with that "statement". tjc wrote: There is a simple patch which might improve your colors. See the call out in on the wiki page to a color saturation patch for the cx25840 driver. It'll add another 5 minutes to your driver rebuild and it gave me a fairly sharp improvement. I'll give that a whirl tonight and report back. Thanks again for your patience. My frustration really got the best of me.

Author:	SunTzuTech [ Fri Jun 09, 2006 8:47 pm ]
Post subject:
tjc wrote: The Wiki says Quote: NOTE! While 0.4.5 is now available I do NOT recommend using it, as my testing has shown driver freezes on a simple channel change. It would be hard to be more specific, I figured that was a serious enough pathology for anyone. There is a simple patch which might improve your colors. See the call out in on the wiki page to a color saturation patch for the cx25840 driver. It'll add another 5 minutes to your driver rebuild and it gave me a fairly sharp improvement. It definitely looks a little better. Does it make any difference if I use 800x600, 1024x768 or 1280x1024 on my flat panel on the picture? Here's the logs. Does it look alright? Code: lirc_dev: IR Remote Control driver registered, at major 61 ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.4.4 (tagged release) loading ivtv: Linux version: 2.6.15-chw-2 SMP preempt 586 gcc-3.3 ivtv: In case of problems please include the debug info between ivtv: the START INIT IVTV and END INIT IVTV lines, along with ivtv: any module options, when mailing the ivtv-users mailinglist. ivtv0: Autodetected WinTV PVR 150 card (cx23416 based) ACPI: PCI Interrupt 0000:00:0c.0[A] -> GSI 16 (level, low) -> IRQ 18 ivtv0: Unreasonably low latency timer, setting to 64 (was 32) tveeprom: ivtv version tveeprom: Hauppauge: model = 26132, rev = G1B2, serial# = 9519520 tveeprom: tuner = <unknown> (idx = 112, type = 4) tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000) tveeprom: audio processor = CX25841 (type = 23) tveeprom: decoder processor = CX25841 (type = 1c) ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] 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] cx25840 1-0044: ivtv driver cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0) cx25840 1-0044: loaded v4l-cx25840.fw firmware (14264 bytes) ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44] wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b] ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0: Encoder revision: 0x02050032 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) tuner: type set to 50 (TCL 2002N) by ivtv i2c driver #0 ivtv0: Initialized WinTV PVR 150, card #0 ivtv: ==================== END INIT IVTV ==================== lirc_pvr150: chip found with RX and TX ivtv0: i2c attach to card #0 ok [client=Hauppauge PVR150 IR RX, addr=71] ivtv0: i2c attach to card #0 ok [client=Hauppauge PVR150 IR TX, addr=70] lirc_dev: lirc_register_plugin: sample_rate: 0 lirc_pvr150: firmware of size 209327 loaded lirc_pvr150: 575 codesets loaded lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0

Author:	tjc [ Sat Jun 10, 2006 12:00 am ]
Post subject:
SunTzuTech wrote: It definitely looks a little better. Does it make any difference if I use 800x600, 1024x768 or 1280x1024 on my flat panel on the picture? Beleive it or not I found that on my (old 27" tube) TV 640x480 actually looked better than 800x600 or any other resolution I tried. This probably had something to do with not causing scaling artifacts. For a flat panel it's native resolution is probably your best bet, but I don' t have any experience along those lines so that's just a SWAG. SunTzuTech wrote: Here's the logs. Does it look alright? : tveeprom: tuner = <unknown> (idx = 112, type = 4) : Well that unknown bit is a tad worrisome but so long as it's working... There is an 0.4.6 pre-release that I'm going to test tomorrow, but until I've fiddled with it it'd be premature to say anything more...

Author:	daphne444 [ Tue Aug 22, 2006 9:11 am ]
Post subject:
I have the same color washed-out problem that was described earlier (almost grayscale on a couple channels). However I cannot find the color saturation patch for the cx25840 driver in the wiki that was described. Does anyone have a pointer to where that may be. A simple search on color saturation does not seem to find it. Thanks

Author:	tjc [ Tue Aug 22, 2006 4:35 pm ]
Post subject:
Skip that and go straight to the 0.4.6 upgrade, it already includes all that. The CompileIvtv page on the wiki has been updated to that version. The TroubleShooting pages on the wiki have a lot more information.

Page 1 of 1	All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/