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

Non-MCE PVR-150/ivtv and R5B7
http://forum.linhes.org/viewtopic.php?f=6&t=9068		 Page 1 of 1
Author:  numbski [ Sat Mar 18, 2006 9:14 pm ]
Post subject:  Non-MCE PVR-150/ivtv and R5B7
(Mods, if you could move this to Tier-2, thanks!)

Seems I got in a hurry and made this post in the wrong forum earlier:

I was of the impression that ivtv was updated and therefore the PVR-150 would work "out of the box" as it were.

No such luck it seems. I had originally gotten this to work with an all-software card, but the framerate sucked. Couldn't even get the install to complete due to known issues with ivtv prior to R5B7.

Ran the install today, installed without a hitch, and I was presented with 10 (!!!) available inputs, all on video0 (the rest of /dev/video* give "could not probe inputs):

Composite 0-4
Tuner0
S-Video 0-3

I'm using a DirecTV tuner box with composite video out into the RCA composite in on the PVR-150. I've tried all of the input combinations on /dev/video0, and get black and white static on all of them. It's rather frustrating. I'd like to kow which input is the composite input so that I can at least stop flipping around like a maniac trying to find the right one. You'd figure it would be composite 0, but I can't be certain.

I was a bit concerned that the ivtv driver seemed to pick up the card as a PVR-250 at first, but apparently this is normal?

I would suspect you'd want what's being dumped into /var/log/messages re: ivtv. Here you go:

Code:
Mar 18 14:58:38 livingroom kernel: ivtv:  ==================== START INIT IVTV ====================
Mar 18 14:58:38 livingroom kernel: ivtv:  version 0.4.3 (tagged release) loadingMar 18 14:58:38 livingroom kernel: ivtv:  Linux version: 2.6.15-chw-2 SMP preempt 586 gcc-3.3
Mar 18 14:58:38 livingroom kernel: ivtv:  In case of problems please include the debug info between
Mar 18 14:58:38 livingroom kernel: ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
Mar 18 14:58:38 livingroom kernel: ivtv:  any module options, when mailing the ivtv-users mailinglist.
Mar 18 14:58:38 livingroom kernel: ivtv0: Autodetected WinTV PVR 250 card (cx23416 based)
Mar 18 14:58:38 livingroom kernel: ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
Mar 18 14:58:38 livingroom kernel: tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
Mar 18 14:58:38 livingroom kernel: ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
Mar 18 14:58:38 livingroom kernel: cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
Mar 18 14:58:42 livingroom kernel: ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
Mar 18 14:58:42 livingroom kernel: wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
Mar 18 14:58:42 livingroom kernel: ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
Mar 18 14:58:42 livingroom kernel: ivtv0 warning: i2c client addr: 0x21 not found for command 0x8004646b!
Mar 18 14:58:43 livingroom kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
Mar 18 14:58:43 livingroom kernel: ivtv0: Encoder revision: 0x02050032
Mar 18 14:58:43 livingroom kernel: ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
Mar 18 14:58:43 livingroom kernel: ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
Mar 18 14:58:43 livingroom kernel: ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
Mar 18 14:58:43 livingroom kernel: ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
Mar 18 14:58:43 livingroom kernel: ivtv0 warning: i2c client addr: 0x21 not found for command 0x40085618!
Mar 18 14:58:43 livingroom kernel: ivtv0 warning: i2c client addr: 0x21 not found for command 0xc0045627!
Mar 18 14:58:43 livingroom kernel: ivtv0 warning: i2c client addr: 0x40 not found for command 0x40086d11!
Mar 18 14:58:43 livingroom kernel: ivtv0 warning: i2c client addr: 0x40 not found for command 0x80287610!
Mar 18 14:58:43 livingroom kernel: ivtv0 warning: i2c client addr: 0x40 not found for command 0x40287611!
Mar 18 14:58:43 livingroom kernel: ivtv0 warning: i2c client addr: 0x40 not found for command 0x40085618!
Mar 18 14:58:43 livingroom kernel: ivtv0 warning: i2c client addr: 0x21 not found for command 0x40085618!
Mar 18 14:58:43 livingroom kernel: ivtv0 warning: i2c client addr: 0x40 not found for command 0x80287610!
Mar 18 14:58:43 livingroom kernel: ivtv0 warning: i2c client addr: 0x40 not found for command 0x40287611!
Mar 18 14:58:43 livingroom kernel: ivtv0 warning: i2c client addr: 0x21 not found for command 0x40045613!
Mar 18 14:58:43 livingroom kernel: ivtv0 warning: i2c client addr: 0x40 not found for command 0x402c5639!
Mar 18 14:58:43 livingroom kernel: ivtv0 warning: i2c client addr: 0x21 not found for command 0x40045612!
Mar 18 14:58:43 livingroom kernel: ivtv0 warning: i2c client addr: 0x40 not found for command 0x80287610!
Mar 18 14:58:43 livingroom kernel: ivtv0 warning: i2c client addr: 0x40 not found for command 0x40287611!
Mar 18 14:58:44 livingroom kernel: ivtv0: Initialized WinTV PVR 250, card #0
Mar 18 14:58:44 livingroom kernel: ivtv:  ====================  END INIT IVTV  ====================
Mar 18 14:58:44 livingroom kernel: ivtv0: i2c attach to card #0 ok [client=Hauppauge PVR150 IR RX, addr=71]
Mar 18 14:58:44 livingroom kernel: ivtv0: i2c attach to card #0 ok [client=Hauppauge PVR150 IR TX, addr=70]
Mar 18 14:58:47 livingroom kernel: ivtv0 warning: i2c client addr: 0x40 not found for command 0x80287610!


As you can see, there is a metric ton of ic2 client addr errors. I'm not sure what's causing that either. :(

Yes, I have a good video source. Plugged directy to the tv is great, plugged to the pvr-150, nothing. Inputs on the back going from edge connector outward are coax, female s-video, female rca, female 1/8" minijack labeled "Line In", female 1/8" minijack labled "IR".

I hate asking for help, but um...help?

Also, I get bad output from ivtvctl -I:

Code:
root@livingroom:~# ivtvctl -I
check SAA7115 input signal
ioctl: Input detect failed (cannot read SAA regs)
ioctl: Input detect failed (cannot read SAA regs)


That should tell me where to find my video signal, should it not?
Author:  numbski [ Sat Mar 18, 2006 9:22 pm ]
Post subject: 
Man...I really don't want to have to recompile ivtv, but based on the below, I may have to:

http://www.digitaldescent.net/wordpress/index.php?p=413

Look familiar to anyone? This is the output I get from lspci -v:

Code:
0000:02:04.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
        Subsystem: Hauppauge computer works Inc.: Unknown device 0003
        Flags: bus master, medium devsel, latency 64, IRQ 20
        Memory at f8000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [44] Power Management version 2
Author:  numbski [ Sat Mar 18, 2006 9:34 pm ]
Post subject: 
Yup, that was the problem.

I've submitted a bug to the devs:

http://ivtvdriver.org/trac/ticket/88

In the meantime, this is the workaround (for those who run into my problem):

Open a terminal.
su -
cd
wget "http://dl.ivtvdriver.org/ivtv/archive/0.4.x/ivtv-0.4.3.tar.gz"
tar xvzf ivtv-0.4.3.tar.gz
cd ivtv-0.4.3/
(make the edits suggested in the blog entry above to ivtv-cards.c)
make
make install
reboot

Now my only issue is that the picture is ugly as sin. Not sure what would cause that though. It's like there's 3 or 4 horizontal bars that are jittering the picture back and forth. This is not present when video is run directly to the television.

(Update: that was just a bad RCA cable. Bizarre. As I said, striaght to the TV was no issue, but going to the Myth box, ugly picture. Replace the cable, clean picture. Go fig...)
Author:  tjc [ Sat Mar 18, 2006 10:24 pm ]
Post subject: 
Dude, not only does R5B7 already comes with 0.4.3, but there are already instructions on the Wiki for reinstalling it if you need to for some other reason...
http://www.knoppmythwiki.org/index.php?page=CompileIvtv

Unless they've reused a version number (and the ivtv folks are smarter than that) what you done should be a no-op.
Author:  numbski [ Sun Mar 19, 2006 12:04 am ]
Post subject: 
The problem is there there's a bug still present in 0.4.3, and that my PVR-150 was being mis-detected as a PVR-250. Thus the bug regport, and the explanation here in case someone else comes across the issue. Without digging deep, I could have scrambled forever and never figured this one out. I got lucky and someone else had found the bug, but for whatever reason, that person never reported it, and only fixed it on their install and posted the fix on their blog.

Sorry, didn't mean to give the impression of wasted time. I assure you, this was a non-trivial fix.

EDIT: I noticed I left out a step, which would have made you think this was a noop. You actually have to make the change to ivtv-cards.c prior to make. That's what causes the issue...the device id is listed under pvr-250 instead of pvr-150. Once you move the device entry and compile, life is good.
Author:  Beldak [ Sun Mar 19, 2006 7:00 pm ]
Post subject: 
Having the same problem here with PVR-150. Install goes fine, but no TV (worked find in R30.X).

Will try this bugfix and see if that works.
Author:  cecil [ Sun Mar 19, 2006 7:11 pm ]
Post subject:  Re: Non-MCE PVR-150/ivtv and R5B7
numbski wrote:
(Mods, if you could move this to Tier-2, thanks!)
Why? First off, this doesn't even belong in KnoppMyth -> Installation. Other than the 150, you don't ever talk about the rest of your hardware. I should pipe this to /dev/null....
Author:  numbski [ Sun Mar 19, 2006 9:06 pm ]
Post subject: 
Erm? My apologies...I've obviously come off horribly wrong here. I thought I would recount my experiences with the latest release (R5B7) so that others that have the issue would find the solution when running a search.

I had such a rough experience getting the install to go that I thought I would be able to save future such problems by documenting it (in fact I thought this was the purpose of the forum!), so in the spirit of being helpful, here is what I have:

Compaq Evo (sorry, not model number...) P4 1.7Ghz
394 MB of RAM
20GB Hard Drive (for testing)
Using the on-board video running to a Philips 23PF9966 LCD HD TV via the VGA port. Piping the DirecTV Hughes receiver using Composite0 into the PVR-150. I did, in fact find that Composite0 was the correct input for the RCA jack, and in fact once you rebuild ivtv with the bugfix I posted, the number of inputs comes way down from 10 to 4. Much more reasonable to guess upon.

So...yeah, hope that helps. Out of curiousity though...why the hostility? I'm just trying to help others out.
Author:  cyates [ Tue Mar 21, 2006 11:45 am ]
Post subject: 
numbski, I too had this issue.

Dell Optiplex Gx110, PVR-150.

The 150 was being detected as a 250. If I shut the PC down for at least 30 seconds (didn't have to remove the power cord, just shutdown -h now) then when it was powered back on things were fine.

lspci -v returns the card as:
Subsystem: Hauppauge computer works Inc.: Unknown device 8003

Without the 30 second power off then:
Subsystem: Hauppauge computer works Inc.: Unknown device 0003

I havn't tried the ivtv patch (things are working now :D ) but I'd guess that too may fix things without the 30 second power off.

BTW, I didn't have this issue with R5A30.
Author:  jparchem [ Wed Mar 22, 2006 5:24 pm ]
Post subject: 
Thanks Numbski for taking the time to share this fix with the rest of us 150 owners. I appreciate it.
Author:  tjc [ Wed Mar 22, 2006 6:45 pm ]
Post subject: 
BTW - I posted draft directions for doing this over here: http://mysettopbox.tv/phpBB2/viewtopic.php?t=9065 Has anyone followed/verified them? If they're good, I can turn that context diff into a real patch and add it to the R5B7 fixup list.
Author:  nbdwt73 [ Thu Mar 23, 2006 4:28 pm ]
Post subject: 
Thanks numbski - I had the same problem and could not figure it out... Yes tjc, I tried it on two machine and verified that it works. I even tried moving the cards (pvr150 and pvr250) around (different pci slots) and all checked out.
Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/