[mythtv-users] What replaces irw when using atilibusb for the remote receiver?
jarod at wilsonet.com
Tue May 11 03:40:14 UTC 2010
On Mon, May 10, 2010 at 9:02 PM, Don Brett <dlbrett at zoominternet.net> wrote:
> Jarod Wilson wrote:
>> On Sun, May 9, 2010 at 4:41 PM, Don Brett <dlbrett at zoominternet.net>
>>> I'm using the remote control from an ATI Tv Wonder 650 (but not the
>>> board). I would like to map the buttons for it (ati theater remote), but
>>> irw doesn't give me any output. Is there a different program to use? Or,
>>> there a trick to getting irw to work?
>>> Oh, by the way, I get these messages in /var/log/messages; but the remote
>>> control mostly works in mythdora-12....should I be concerned?
>>> May 7 11:48:42 nick lircd-0.8.6: lircd(atilibusb) ready, using
>>> May 7 11:48:43 nick lircd-0.8.6: accepted new client on
>>> May 7 11:48:43 nick lircd-0.8.6: couldn't find a compatible USB
>>> May 7 11:48:43 nick lircd-0.8.6: Failed to initialize hardware
>> Its probably an input layer remote, not an atilibusb remote. atilibusb
>> is for the remote wonder RF remotes. lirc can be configured to use
>> input layer devices though, and irw works just fine with them.
> Right, I figured out the thing about RF just after posting the
> question....it's definitely an IR remote. I'm not sure what you mean by
> input layer, but I assume I will need to select a different driver. From
> the MythDora-12 settings I tried several different selections, but they all
> gave me errors similar to the following:
> May 10 20:46:57 nick kernel: lirc_dev: IR Remote Control driver registered,
> major 249
> May 10 20:46:57 nick kernel: lirc_mceusb: Windows Media Center Edition USB
> IR Transceiver driver for LIRC 1.90
> May 10 20:46:57 nick kernel: lirc_mceusb: Daniel Melander <lirc at rajidae.se>,
> Martin Blatter <martin_a_blatter at yahoo.com>, Dan Conti <dconti at acm.wwu.edu>
> May 10 20:46:57 nick kernel: usbcore: registered new interface driver
> May 10 20:47:00 nick lircd-0.8.6: lircd(default) ready, using
> May 10 20:47:20 nick lircd-0.8.6: accepted new client on
> May 10 20:47:20 nick lircd-0.8.6: could not get file information for
> May 10 20:47:20 nick lircd-0.8.6: default_init(): No such file or
> May 10 20:47:20 nick lircd-0.8.6: Failed to initialize hardware
> May 10 20:47:23 nick lircd-0.8.6: accepted new client on
Not sure if there's a menu item you can select for that thing or not.
But basically, its a receiver that ties into the linux kernel's input
subsystem, and creates a device /dev/input/eventX for the remote, and
delivers keypresses to the system as if they were keyboard keys a la a
multimedia keyboard, more or less. You can use such devices with lirc
by telling lircd to use the devinput userspace driver instead of the
default driver (lirc kernel driver), and for device, pointing lircd at
/dev/input/eventX for the device (or more appropriately, as X may
change, at the symlink to /dev/input/eventX that should land in
> I also noticed the database was hosed, with dozens of these errors in
> 100509 22:53:21 [ERROR] /usr/libexec/mysqld: Incorrect key file for table
> './mythconverg/program.MYI'; try to repair it
> 100510 20:52:26 [ERROR] /usr/libexec/mysqld: Table './mythconverg/people' is
> marked as crashed and should be repaired
> 100510 20:52:29 [ERROR] /usr/libexec/mysqld: Table './mythconverg/program'
> is marked as crashed and should be repaired
> So, are the lircd errors a result of a corrupt database, or are they
> separate issues?
Separate issues. Definitely repair your db, but yeah, its not related.
> If separate, how do I create the proper information for
See above. :) There is no /dev/lirc0 for this device type.
jarod at wilsonet.com
More information about the mythtv-users