| LinHES Forums http://forums.linhes.org/ |
|
| Trying to get PVR150 IR Blaster to wrk (wrkng aftr reinstal) http://forums.linhes.org/viewtopic.php?f=2&t=17229 |
Page 1 of 1 |
| Author: | poflynn [ Sat Nov 10, 2007 10:18 pm ] |
| Post subject: | Trying to get PVR150 IR Blaster to wrk (wrkng aftr reinstal) |
Hi All, I went out today and bought a brand new Hauppauge 150 (non-MCE). FYI Circuit City nationwide is dumping these cards for $60 as they are no longer going to carry them. Anyway, to get this blaster to work with my AT&T u-verse I tried following these directions http://www.blushingpenguin.com/mark/blog/?p=24 I know the codeset for my STB are the 0_130_ codes. I am running R5F27, the one 150 tuner card, no other IR receivers or blasters. I actually installed R5F27 w/o the card in place and added the card today. Here's what worked: Download, make & configure lirc-0.8.3-CVS-pvr150.tar.bz2 Download & copy firmware to /usr/lib/hotplug/firmware (do I need to symlink this to /lib/modules?) Quote: modprobe lirc_dev debug=1 && modprobe lirc_pvr150 debug=1 Did not return any msgs, errors or otherwise. But when I look in /var/log/syslog this is all I get: Quote: Nov 10 18:31:29 mbe kernel: lirc_dev: IR Remote Control driver registered, at major 61 as opposed to the 8 or so "PVR150" type msgs quoted in the link above. Needless to say my IR blaster doesn't work. I haven't actually hooked the card up to my STB yet, it's no good unless I get the blaster to work, so I'm not certain if the card works although it looks good to me from the syslog below. Any help would be massively appreciated. Thanks! Other details below: Elsewhere in syslog I get: Quote: Nov 10 18:21:57 mbe kernel: ivtv: Start initialization, version 1.1.0 Nov 10 18:21:57 mbe kernel: ivtv0: Initializing card #0 Nov 10 18:21:57 mbe kernel: ivtv0: Autodetected Hauppauge card (cx23416 based) Nov 10 18:21:57 mbe kernel: ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 18 (level, low) -> IRQ 18 Nov 10 18:21:57 mbe kernel: tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) Nov 10 18:21:57 mbe kernel: tveeprom 0-0050: Hauppauge model 26152, rev E5B2, serial# 10276667 Nov 10 18:21:57 mbe kernel: tveeprom 0-0050: tuner model is TCL M2523_5N_E (idx 112, type 50) Nov 10 18:21:57 mbe kernel: tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08) Nov 10 18:21:57 mbe kernel: tveeprom 0-0050: audio processor is CX25843 (idx 37) Nov 10 18:21:57 mbe kernel: tveeprom 0-0050: decoder processor is CX25843 (idx 30) Nov 10 18:21:57 mbe kernel: tveeprom 0-0050: has no radio, has IR receiver, has IR transmitter Nov 10 18:21:57 mbe kernel: ivtv0: Autodetected Hauppauge WinTV PVR-150 Nov 10 18:21:57 mbe kernel: ivtv0: Reopen i2c bus for IR-blaster support Nov 10 18:21:57 mbe kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled Nov 10 18:21:57 mbe kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Nov 10 18:21:57 mbe kernel: serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A Nov 10 18:21:57 mbe kernel: 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Nov 10 18:21:57 mbe kernel: 00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A Nov 10 18:21:57 mbe kernel: parport: PnPBIOS parport detected. Nov 10 18:21:57 mbe kernel: parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA] Nov 10 18:21:57 mbe kernel: tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) Nov 10 18:21:57 mbe kernel: cx25840 0-0044: cx25843-24 found @ 0x88 (ivtv i2c driver #0) Nov 10 18:21:57 mbe kernel: wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0) Nov 10 18:21:57 mbe kernel: tuner-simple 0-0061: type set to 50 (TCL 2002N) Nov 10 18:21:57 mbe kernel: tuner 0-0061: type set to TCL 2002N Nov 10 18:21:57 mbe kernel: ivtv0: Registered device video0 for encoder MPG (4096 kB) Nov 10 18:21:57 mbe kernel: ivtv0: Registered device video32 for encoder YUV (2048 kB) Nov 10 18:21:57 mbe kernel: ivtv0: Registered device vbi0 for encoder VBI (1024 kB) Nov 10 18:21:57 mbe kernel: ivtv0: Registered device video24 for encoder PCM (320 kB) Nov 10 18:21:57 mbe kernel: ivtv0: Initialized card #0: Hauppauge WinTV PVR-150 Nov 10 18:21:57 mbe kernel: ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 17 (level, low) -> IRQ 19 Nov 10 18:21:57 mbe kernel: PCI: Setting latency timer of device 0000:00:1f.5 to 64 Nov 10 18:21:57 mbe kernel: ivtv: End initialization I have a "lircd" in /dev after I run "lircd" on the cmd line (lircd is not set to auto-start) /etc/lirc/hardware.conf looks like: Quote: # /etc/lirc/hardware.conf
# # Arguments which will be used when launching lircd LIRCD_ARGS="" #Don't start lircmd even if there seems to be a good config file START_LIRCMD=false #Try to load appropriate kernel modules LOAD_MODULES=true # Run "lircd --driver=help" for a list of supported drivers. DRIVER="default" # If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc/0 will be # automatically used instead DEVICE="/dev/lirc0" MODULES="lirc_dev lirc_pvr150" (note that the above file references "/dev/lirc0" which doesn't exist. I changed it to "lircd" but it didn't make a difference so I changed it back). /etc/modules does not contain any "lirc" references. |
|
| Author: | poflynn [ Sun Nov 11, 2007 10:45 pm ] |
| Post subject: | Working |
Well, I figured it would be quicker to re-install everything from scratch so I did just that and now it's all peachy.... As an FYI the firmware at the link below is newer than what shipped with R5F27 and contained (very approximately) 80 more codesets than the one that ships with KM. Also, the lircd.conf in that link also has the equivalent longer list than what ships with KM. As it turns out my STB was not in the one that shipped with KM but it was in the one below. http://www.blushingpenguin.com/mark/blog/?p=19 |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|