[mythtv-users] Trouble w/ Hauppauge HD-PVR & IR transmitter

[Mike Perkins]

On 31/01/16 03:45, Rob wrote:
> So I've been able to get video capture to work w/ my HD-PVR, but I'm unable
> to issue any channel-change commands.  I'm not seeing any glaring error
> messages with trying to initialize the device, but irsend can't seem to
> find it....  /dev/lirc0 doesn't exist, but I'm getting the feeling that
> pointing to the underlying event should resolve this glitch.
>
> $ dmesg
> ...
> [    2.637962] IR NEC protocol handler initialized
> [    2.638022] IR RC5(x/sz) protocol handler initialized
> [    2.638077] IR RC6 protocol handler initialized
> [    2.638132] IR JVC protocol handler initialized
> [    2.638187] IR Sony protocol handler initialized
> [    2.638243] IR SANYO protocol handler initialized
> [    2.638298] IR Sharp protocol handler initialized
> [    2.638353] IR MCE Keyboard/mouse protocol handler initialized
> [    2.638410] IR XMP protocol handler initialized
> [    2.638507] usbcore: registered new interface driver hdpvr
> [    2.638803] device-mapper: ioctl: 4.28.0-ioctl (2014-09-17) initialised:
> dm-devel at redhat.com
> ...
> [    3.112902] usb 3-3: New USB device found, idVendor=2040, idProduct=4903
> [    3.112965] usb 3-3: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [    3.113021] usb 3-3: Product: Hauppauge HD PVR
> [    3.113075] usb 3-3: Manufacturer: AMBA
> [    3.113128] usb 3-3: SerialNumber: 00A7233D
> [    3.131266] hdpvr 3-3:1.0: firmware version 0x17 dated Jul 27 2011
> 05:11:32
> [    3.131328] hdpvr 3-3:1.0: untested firmware, the driver might not work.
> ...
> [    3.645186] Registered IR keymap rc-hauppauge
> [    3.645364] input: i2c IR (HD-PVR) as /devices/virtual/rc/rc0/input3
> [    3.645477] rc0: i2c IR (HD-PVR) as /devices/virtual/rc/rc0
> [    3.645531] ir-kbd-i2c: i2c IR (HD-PVR) detected at i2c-0/0-0071/ir0
> [Hauppage HD PVR I2C]
> ...
> [  111.338965] lirc_dev: IR Remote Control driver registered, major 248
> [  111.341677] lirc_zilog: module is from the staging directory, the
> quality is unknown, you have been warned.
> [  111.341926] lirc_zilog: Zilog/Hauppauge IR driver initializing
> [  111.343103] lirc_zilog: probing IR Tx on Hauppage HD PVR I2C (i2c-0)
> [  111.343299] lirc_zilog: probe of IR Tx on Hauppage HD PVR I2C (i2c-0)
> done. Waiting on IR Rx.
> [  111.343303] lirc_zilog: probe of IR Tx on Hauppage HD PVR I2C (i2c-0)
> done
> [  111.343348] lirc_zilog: initialization complete
>
> $ ls -L /dev
> ...
> crw------- 1 root root   10, 232 Jan 30 22:20 kvm
> srw-rw-rw- 1 root root         0 Jan 30 22:20 log
> ...
>
> $ cat /proc/bus/input/devices
> ...
> I: Bus=0018 Vendor=0000 Product=0000 Version=0000
> N: Name="i2c IR (HD-PVR)"
> P: Phys=i2c-0/0-0071/ir0
> S: Sysfs=/devices/virtual/rc/rc0/input3
> U: Uniq=
> H: Handlers=kbd event3
> B: PROP=0
> B: EV=100013
> B: KEY=10afc312 214201700000000 0 118000 41a800004801 9e16c000000000
> 10000ffc
> B: MSC=10
>
>
>>> Attempting to issue a command:
> $ irsend SEND_ONCE blaster 0_130_KEY_POWER
> irsend: command failed: SEND_ONCE blaster 0_130_KEY_POWER
> irsend: hardware does not support sending
>
>>> LIRC's interpretation of the command:
> $ lircd -n -d /dev/input/event3 /etc/lirc/lircd.conf
> lircd-0.9.0[4396]: lircd(default) ready, using /var/run/lirc/lircd
> lircd-0.9.0[4396]: accepted new client on /var/run/lirc/lircd
> lircd-0.9.0[4396]: could not get hardware features
> lircd-0.9.0[4396]: this device driver does not support the LIRC ioctl
> interface
> lircd-0.9.0[4396]: did you mean to use the devinput driver instead of the
> default driver?
> lircd-0.9.0[4396]: Failed to initialize hardware
> lircd-0.9.0[4396]: error processing command: SEND_ONCE blaster
> 0_130_KEY_POWER
> lircd-0.9.0[4396]: hardware does not support sending
> lircd-0.9.0[4396]: removed client
>
I'm assuming you have a UDEV rule which associates 'blaster' with /dev/input/event3?

-- 

Mike Perkins