[mythtv-users] Hauppauge Lirc setup and new mythtv install

[Jarod Wilson]

On Mon, Sep 20, 2010 at 8:13 PM, Brian White <bjwhite at columbus.rr.com> wrote:
> Jarod,
> Regarding initscripts,  I have been starting lircd from the command line
> with "lircd -n " and then running "irw" in another console session.

Okay, in that particular case, hardware.conf has absolutely no effect
on anything.

> I have
> also tried the fedora 13 package /etc/rc.d/init.d/lirc script with the same
> results.

Its also not used at all by the Fedora initscript. So I'd just nuke
that hardware.conf file, its not doing you any good. :) (the Fedora
initscript does look for config values in /etc/sysconfig/lirc though).

> It does not appear to bind to the hardware.

Its not the initscript having trouble, its the lirc_i2c kernel module.

> One thing I don't fully understand about the f13 packages, I don't see a
> kernel module package.   Do those need to be built from the source?   I'm
> assuming they're necessary.

The Fedora kernel has the lirc drivers patched in already.


> If it helps, I did get the remote to sort of work using the dev/input and
> ir_kbd_i2c setup.   When I "modprobe ir_kbd_i2c ", the following appears in
> dmesg:
> input: i2c IR (Hauppauge WinTV PVR-150 as /devices/virtual/input/input4
> Creating IR device irrcv0
> ir-kbd-i2c: i2c IR (Hauppauge WinTV PVR-150 detected at i2c-0/0-0071/ir0
> [ivtv i2c driver #0]

Ah, okay, well, that's a bit of progress...if ir-kbd-i2c is binding,
then I swear lirc_i2c ought to be able to. Unless...

> I can actually half-way navigate mythtv using a select few buttons on the
> remote, but it's not really usable that way.
> when I instead   modprobe lirc_i2c , all I get is
>   lirc_dev: IR Remote Control driver registered, major 250
> with no hardware bind.

If ir-kbd-i2c is already bound, it definitely won't bind.

> The PVR-150 does have a blaster adapter on the IR cord.   I assume that
> means RX and TX.

Ah. Yeah. Okay, yeah, lirc_i2c isn't going to bind to this thing. You
have a device with i2c device id ir_rx_z8f0811_haup, which lirc_i2c
won't bind to these days. Only lirc_zilog (and ir-kbd-i2c) are set up
to bind to that i2c device id.

> I haven't used this PVR-150 for IR capabilities for a couple of years, so
> that's why I'm a little behind on its configuration.    I used to always
> compile my own vanilla kernels and the recompile lirc without problem.
> With this new machine, I'm trying to avoid a custom kernel, but I'm not
> opposed to compiling the lirc stuff each time a kernel update comes down the
> pipeline.
> Is there a full-blown tarball package download for the lirc_zilog, or is it
> just in .diff patch form?   I did some searching yesterday and didn't have
> luck finding it.   I will search some more because I know you're a busy guy.

You already have it on your system. :) lirc_zilog is provided in the
Fedora kernels. You just need to acquire the firmware.

http://wilsonet.com/?p=40 specifically covers using lirc_zilog with
the hdpvr, but its mostly applicable to your card as well (start at
"Either way, you still need a firmware image," and continue from
there). Reliability issues mentioned w/the hdpvr aren't relevant for
your card (so far as I know), fwiw. :)


-- 
Jarod Wilson
jarod at wilsonet.com