[mythtv-users] What replaces irw when using atilibusb for the remote receiver?

[Don Brett]

Jarod Wilson wrote:
> On Sun, May 9, 2010 at 4:41 PM, Don Brett <dlbrett at zoominternet.net> wrote:
>   
>> I'm using the remote control from an ATI Tv Wonder 650 (but not the capture
>> 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, is
>> 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[4056]: lircd(atilibusb) ready, using
>> /var/run/lirc/lircd
>> May 7 11:48:43 nick lircd-0.8.6[4056]: accepted new client on
>> /var/run/lirc/lircd
>> May 7 11:48:43 nick lircd-0.8.6[4056]: couldn't find a compatible USB device
>> May 7 11:48:43 nick lircd-0.8.6[4056]: 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 
lirc_mceusb
May 10 20:47:00 nick lircd-0.8.6[1531]: lircd(default) ready, using 
/var/run/lirc/lircd
May 10 20:47:20 nick lircd-0.8.6[1531]: accepted new client on 
/var/run/lirc/lircd
May 10 20:47:20 nick lircd-0.8.6[1531]: could not get file information 
for /dev/lirc0
May 10 20:47:20 nick lircd-0.8.6[1531]: default_init(): No such file or 
directory
May 10 20:47:20 nick lircd-0.8.6[1531]: Failed to initialize hardware
May 10 20:47:23 nick lircd-0.8.6[1531]: accepted new client on 
/var/run/lirc/lircd

I also noticed the database was hosed, with dozens of these errors in 
/var/log/mysqld.log


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?  If separate, how do I create the proper information 
for /dev/lirc0?