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

pvr 150 remote with multiple tuners
http://forum.linhes.org/viewtopic.php?f=2&t=11887
Page 1 of 1

Author:  andrewsw [ Thu Sep 28, 2006 6:20 pm ]
Post subject:  pvr 150 remote with multiple tuners

hey everybody,

I've got two pvr150 cards in my setup and can't get the remote to work on either one. I've googled around quite a bit and can't find my old resources.

basically, I had one pvr150 with remote working. I installed a second pvr150 and now I get no remote response. it doesn't answer to irw or anything. I'm sure there is something simple I'm missing, soif someone could point me in the right direction. also note that I do not get /dev/lirc0,1, only /dev/lirc and that maybe significant. I think I'm running r5b7.

thanks

Author:  tjc [ Thu Sep 28, 2006 9:43 pm ]
Post subject: 

Have you tried swapping the cards around, or plugging the sensor into the other card? Card order matters on the PCI bus, I don't remember if it's nearer to the CPU or further away that gets the lower ID, but when I added the second PVR card to my box my old PVR-250 suddenty became video1 instead of video0 as it had been. A quick slot swap fixed that.

Author:  andrewsw [ Fri Sep 29, 2006 10:53 am ]
Post subject: 

yeah, Im' familliar with that technique. Actually, I can identify the cards specifically as they get recognized because they have different revision numbers and the revision numbers show up in the ivtv portion of dmesg, so its easy to pick out the cards and know which one is which. I can't get any info out of either card for the remote... and I've only got one /dev/lirc, irw gets no response at all, so I'm wondering if there is some breakage in my dev and how its being linked up with the actual devices. I'm gonna spend some more time on it today and report back. IIRC, in the past, I've had to just strip it all out and start over from scratch and then it works. thanks for the help though.

Author:  bruce_s01 [ Fri Sep 29, 2006 6:37 pm ]
Post subject: 

Do you have the following?
Code:
~$ ls -l /dev/lirc*
crw-r--r--  1 root root 61, 0 Jun 22 05:25 /dev/lirc
crw-r--r--  1 root root 61, 1 Oct  1  2005 /dev/lirc1
srw-rw-rw-  1 root root     0 Sep 28 10:34 /dev/lircd
prw-r--r--  1 root root     0 Jul 30  2004 /dev/lircm


When using the Nova-T, the way I've found it to work was use dev/input driver, I don't know if the PVR150 works in the same way.
Have you tried the following at a command prompt?
Code:
cat /proc/bus/input/devices

If you see the Hauppauge cards, you may need to modify /etc/lirc/hardware.conf to use the dev/input driver for lirc. I found out about this here.

Regards
Bruce S.

Author:  andrewsw [ Sun Oct 01, 2006 9:08 pm ]
Post subject: 

Quote:
Do you have the following?
Code:
~$ ls -l /dev/lirc*
crw-r--r-- 1 root root 61, 0 Jun 22 05:25 /dev/lirc
crw-r--r-- 1 root root 61, 1 Oct 1 2005 /dev/lirc1
srw-rw-rw- 1 root root 0 Sep 28 10:34 /dev/lircd
prw-r--r-- 1 root root 0 Jul 30 2004 /dev/lircm


nope, just lirc, lircd and lircm. I've used the input driver in the past, but lost my config for it on the last update. I'll have to try and dig it out again. currently there are no hauppage cards in /dev/bus/input/devices. I seem to remember that being a problem before. In fact, now that I think about it, my PVR150 has never put up a /dev/input/event while my pvr350 did. I wonder what the difference is.

here is the pertinent parts of dmesg:

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 Link [APC4] enabled at IRQ 19
ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IR
Q 19
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom: ivtv version
tveeprom: Hauppauge: model = 26032, rev = C599, serial# = 8247262
tveeprom: tuner = TCL 2002N 5H (idx = 99, 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 2-0044: ivtv driver
cx25840 2-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 2-0044: loaded v4l-cx25840.fw firmware (14264 bytes)
ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
wm8775 2-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:  ======================  NEXT CARD  ======================
ivtv1: Autodetected WinTV PVR 150 card (cx23416 based)
ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC1] -> GSI 16 (level, high) -> IR
Q 20
ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom: ivtv version
tveeprom: Hauppauge: model = 26032, rev = C199, serial# = 8126031
tveeprom: tuner = TCL 2002N 5H (idx = 99, type = 50)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio processor = CX25841 (type = 23)
tveeprom: decoder processor = CX25841 (type = 1c)
ivtv1: i2c attach to card #1 ok [client=tveeprom, addr=50]
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #1
ivtv1: i2c attach to card #1 ok [client=(tuner unset), addr=61]
cx25840 3-0044: ivtv driver
cx25840 3-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #1)
eth0: no IPv6 routers present
cx25840 3-0044: loaded v4l-cx25840.fw firmware (14264 bytes)
ivtv1: i2c attach to card #1 ok [client=cx25840, addr=44]
wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #1)
ivtv1: i2c attach to card #1 ok [client=wm8775, addr=1b]
ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv1: Encoder revision: 0x02050032
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)
tuner: type set to 50 (TCL 2002N) by ivtv i2c driver #1
ivtv1: Initialized WinTV PVR 150, card #1
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
lirc_pvr150: chip found with RX and TX
ivtv1: i2c attach to card #1 ok [client=Hauppauge PVR150 IR RX, addr=71]
ivtv1: i2c attach to card #1 ok [client=Hauppauge PVR150 IR TX, addr=70]
lirc_dev: lirc_register_plugin: sample_rate: 0
lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0



The second detected card is my old one and it worked fine with the remote, though I had to do some now long forgotten tweaking. So either the new card is blocking the old one or something is broken... I've tried using irw and syslog shows:

Code:
Oct  1 20:03:55 mythtv lircd-0.8.0pre4-pvr150[2726]: accepted new client on /dev/lircd


but it doesn't produce any output. also properly shows removing the client on /dev/lircd.

I'm a little frustrated.

I'm thinking that since I'm behind a couple releases, I'll go ahead and upgrade before tackling this again. That way I'm starting with a clean slate. my record keeping is sub-par (as in non existant) so I can't recall what's been done. I have to reconstruct the history from what tarballs are lying around in /root. heh. Anyway, any input is appreciated before I plunge into the upgrade.

thanks.

A

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