Author |
Message |
dwvcfii
|
Posted: Sun Mar 19, 2006 9:21 pm |
|
Joined: Sun Nov 27, 2005 5:02 pm
Posts: 3
|
I have the RF output of my STB connected to the tuner input of my PVR150. This configuration has been working nicely since R5A26 came out.
I performed a fresh (overwrite) installation of R5B7 on top of my existing working system and now find that my PVR150 receives only video static and distorted audio. The scan during installation process found channel 3, and I remembered to preset the tuner to channel 3. The fact that I have audio and it disappears when I pull the tuner input confirms that the basic sanity of my setup is fine. It's just that the PVR150 can't seem to "lock" to a good signal.
After some tweaking and no luck fixing the problem I gave up and installed 30.2. That works. So something in R5B7 has affected the ability of my < 1 year old PVR150 to receive video.
While I'm no stranger to linux, I'm relatively new to video applications on linux, so I don't really know how to troubleshoot this effectively. Any ideas? Could this be some signal level issue related to new firmware introduced in R5B7? Any obvious stuff to look at? Is there any signal debugging data produced by the PVR150 I can look at?
Thanks,
-Doug
|
|
Top |
|
 |
tjc
|
Posted: Sun Mar 19, 2006 10:10 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Try upgrading just the ivtv driver on top of that 30.2 install. See the instructions at http://www.knoppmythwiki.org/index.php?page=CompileIvtv Don't miss the last paragraph!
BTW - Did you do an auto install or and auto upgrade? Sounds like the former at first glance, but the symptoms match an upgrade without dropping an recreating the tuner card definitions in mythtv-setup.
R5B7and the ivtv 0.4.3 drivers it uses haven't given me any grief with my PVR-150.
|
|
Top |
|
 |
cesman
|
Posted: Mon Mar 20, 2006 2:16 am |
|
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location:
Fontana, Ca
|
tjc wrote: R5B7and the ivtv 0.4.3 drivers it uses haven't given me any grief with my PVR-150. Works fine here as well...
_________________ cesman
When the source is open, the possibilities are endless!
|
|
Top |
|
 |
dwvcfii
|
Posted: Mon Mar 20, 2006 8:42 am |
|
Joined: Sun Nov 27, 2005 5:02 pm
Posts: 3
|
That's the strange thing. This is something I'd expect of an upgrade, but I did a clean Auto Install precisely to avoid this kind of issue. Oh well.
This is clearly a software / pvr150 firmware problem (in other words, it's not like I zapped my card in some way) since the hardware works on R5A22, A26, and 30.2.
I'll reinstall 30.2 one more time (which should work) and try to install ivtv 0.4.3 on top of that to see if that produces the same result as B7.
Thanks for the help.
-Doug
|
|
Top |
|
 |
Dinki
|
Posted: Mon Mar 20, 2006 12:11 pm |
|
Joined: Fri Dec 26, 2003 2:25 pm
Posts: 244
|
I think I'm having a similar problem with my PVR150 and the tuner not being set. It is very similar to the problem that I had in this thread:
http://mysettopbox.tv/phpBB2/viewtopic.php?t=8902
but the fix I found does not work in R5B7 . I'm really at a loss on what to do now. Looks like I might have to go back down to 30.2 to get my system functional again.
Here's my grepped ivtv from dmesg:
Code: ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.4.3 (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) ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] tuner 1-0061: chip found @ 0xc2 (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) 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) ivtv0: Initialized WinTV PVR 150, card #0 ivtv: ====================== NEXT CARD ====================== ivtv1: Autodetected AVerMedia M179 card (cx23415 based) ivtv1: i2c attach to card #1 ok [client=tveeprom, addr=50] tuner 2-0060: chip found @ 0xc0 (ivtv i2c driver #1) ivtv1: i2c attach to card #1 ok [client=(tuner unset), addr=60] saa7115 2-0021: saa7114 found @ 0x42 (ivtv i2c driver #1) ivtv1: i2c attach to card #1 ok [client=saa7114, addr=21] ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv1: loaded v4l-cx2341x-dec.fw firmware (262144 bytes) ivtv1: Encoder revision: 0x02050032 ivtv1: Decoder revision: 0x02020023 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) ivtv1: Initialized AVerMedia M179, card #1 ivtv: ==================== END INIT IVTV ==================== 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_pvr150: ivtv i2c driver #1: no devices found
any reason why adding: /etc/modprobe.d/ivtv Code: # Options for ivtv module options ivtv tuner=50,2
Wouldn't work like in 30.2?
|
|
Top |
|
 |
Dinki
|
Posted: Mon Mar 20, 2006 3:54 pm |
|
Joined: Fri Dec 26, 2003 2:25 pm
Posts: 244
|
I went back to version 30.2 and the above fix worked as it did before. Something in r5b7 is messing with my ivtv 
|
|
Top |
|
 |
Xsecrets
|
Posted: Mon Mar 20, 2006 4:30 pm |
|
Joined: Mon Oct 06, 2003 10:38 am
Posts: 4978
Location:
Nashville, TN
|
Dinki wrote: I went back to version 30.2 and the above fix worked as it did before. Something in r5b7 is messing with my ivtv 
well I don't know if I'd call it messing with ivtv. It does however have a newer version of ivtv. perhaps this is an issue for the ivtv development list.
_________________ Have a question search the forum and have a look at the KnoppMythWiki.
Xsecrets
|
|
Top |
|
 |
Dinki
|
Posted: Mon Mar 20, 2006 5:59 pm |
|
Joined: Fri Dec 26, 2003 2:25 pm
Posts: 244
|
Hmm. Wasn't trying to be insulting. I have version 0.4.3 working fine under 30.2 but can't get it to work under r5b7 following the same steps I used for 30.2 . Perhaps it is the wrong assumption that it is something in r5b7 that is causing me grief, but I can't really narrow it down to anything else.
|
|
Top |
|
 |
tkoster
|
Posted: Mon Mar 20, 2006 9:32 pm |
|
Joined: Mon Apr 04, 2005 10:50 am
Posts: 120
|
Which video setting are you selecting in mythtv-setup? When I first set mine up, I used video0 as that is the first that pops up and also the one I used in previous editions. However, the change in the ivtv drivers seem to have bumped my 350 up to video1. Once I switched to that I got livetv again.
However, I'm still trying to figure out why the 350 won't record.
|
|
Top |
|
 |
tjc
|
Posted: Mon Mar 20, 2006 10:53 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Dinki, I'm somewhat concerned about the order of your module loads, most people have to pull the ivtv line out of /etc/modules to avoid problems with the firmware not loading, this means that the ivtv stuff doesn't appear in dmesg.
Can you use the sed command shown on the wiki CheckingLogFiles page to make sure we're not misisng critical bits from the logs? I've tried to discourage people from using the grep shortcut for exactly this reason...
Also try this:
Code: grep ivtv /etc/modules
Oh and check the firmware md5sums as shown on the CompileIvtv page.
|
|
Top |
|
 |
numbski
|
Posted: Mon Mar 20, 2006 10:58 pm |
|
Joined: Wed Feb 22, 2006 8:08 pm
Posts: 28
|
|
Top |
|
 |
Dinki
|
Posted: Tue Mar 21, 2006 10:22 am |
|
Joined: Fri Dec 26, 2003 2:25 pm
Posts: 244
|
tjc, as always, thank you for your time in responding. Unfortunately I've already switched back to 30.2 and may take the route of upgrading from source to avoid the hardware issues I'm running up against. It just seems odd that using the same version of IVTV and the same steps in patching the firmware, updating the config files produces a different result. I can say that the checksums did match though.
I guess my patience hasn't been all that great lately, but I suppose having a newborn in the house can change the priorities of things. 
|
|
Top |
|
 |
tjc
|
Posted: Tue Mar 21, 2006 7:35 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
It looks like the kernel in R5B7 moved forward from v4l1 to v4l2. You can't even build the ivtv 0.4.0 driver which uses the v4l1 API against it anymore. This could be part of the issue. Oddly both of my cards (PVR-250 and PVR-150) are behaving just fine... 
|
|
Top |
|
 |
Dinki
|
Posted: Tue Mar 21, 2006 9:04 pm |
|
Joined: Fri Dec 26, 2003 2:25 pm
Posts: 244
|
Hmm. Don't really understand the ramifications. I guess it's best that I don't try to move to r5b7 then, right?
|
|
Top |
|
 |