[mythtv-users] lirc Problems Configuring ATI Remote Wonder to Work on Fedora 10

[Thomas Fjellstrom]

On February 13, 2009, Mache Creeger wrote:
> At 10:12 AM 2/13/2009, Nick Morrott wrote:
> >On 13/02/2009, Mache Creeger <mache at creeger.com> wrote:
> > > I have problems getting my ATI Remote Wonder I/II to work on my myth
> > > 0.21 frontend running on Fedora 10.
> > >
> > >  I use the same ~/.lircrc and /etc/lircd.conf configuration in my other
> > > two FEs (one Fedora 8 and the other Fedora 9) so I do not believe that
> > > is the problem. Looking at /var/log/messages do see that there is
> >
> > confusion between
> >
> > > /dev/lirc and /dev/lircd causing a failure to initialize the hardware
> > > (see "could not get file information for /dev/lirc").
> > >
> > >  I have tried numerous experiments with /etc/sysconfig/lirc and
> > > /etc/udev/rules.d/lirc.rules with no success. Any ideas?
> > >
> > >  -- Mache Creeger
> > >
> > >  # uname -r
> > >  2.6.27.12-170.2.5.fc10.x86_64
> > >
> > >  # rpm -qa | grep mythtv-frontend
> > >  mythtv-frontend-0.21-201.fc10.x86_64
> > >
> > >  # rpm -qa | grep lirc
> > >  lirc-0.8.4a-1.fc10.x86_64
> > >  lirc-libs-0.8.4a-1.fc10.x86_64
> > >  lirc-devices-0.8-4.fc10.noarch
> > >
> > >  # cat /var/log/messages  | grep lirc
> > >  Feb 13 09:16:25 DEN lircd-0.8.4a[2339]: removed client
> > >  Feb 13 09:16:27 DEN lircd-0.8.4a[2339]: caught signal
> > >  Feb 13 09:17:21 DEN lircd-0.8.4a[2330]: lircd(default) ready
> > >  Feb 13 09:18:08 DEN lircd-0.8.4a[2330]: accepted new client on
> > > /dev/lircd Feb 13 09:18:08 DEN lircd-0.8.4a[2330]: could not get file
> > > information for /dev/lirc
> > >  Feb 13 09:18:08 DEN lircd-0.8.4a[2330]: default_init(): No such file
> > > or directory
> > >  Feb 13 09:18:08 DEN lircd-0.8.4a[2330]: Failed to initialize hardware
> > >
> > >  # more /etc/modprobe.conf
> > >  # nvidia kernel module
> > >  alias char-major-195 nvidia-180_22
> > >  alias nvidia nvidia-180_22
> > >
> > >  # lsmod |grep lirc
> > >  #
> >
> >Your LIRC modules do not appear to be loaded, hence the missing /dev/lirc.
> >
> >Have you tried modprobing them?
> >
> >Nick
>
> # modprobe atilibusb
> FATAL: Module atilibusb not found.
>
> # cat /var/log/messages |grep lirc
> Feb 13 10:56:56 DEN lircd-0.8.4a[2326]: removed client
> Feb 13 10:56:58 DEN lircd-0.8.4a[2326]: caught signal
> Feb 13 10:57:49 DEN lircd-0.8.4a[2326]: lircd(atilibusb) ready
> Feb 13 10:58:40 DEN lircd-0.8.4a[2326]: accepted new client on /dev/lircd
>
> # more /etc/sysconfig/lirc
> # Note: in addition to these parameters, you need to have working    -*- sh
> -*- # configuration file for lircd (and lircmd if enabled).
>
> # Options to lircd(8).  Typically, this will be empty, as which driver to
> use # should be specified using the LIRC_DRIVER variable below.
> LIRCD_OPTIONS=""
> # The infrared receiver (and/or transmitter) driver to be used by lircd(8),
> # similar to passing "-H driver" to lircd(8).
> # Run "/usr/sbin/lircd -H help" to get a listing of supported drivers.
> LIRC_DRIVER="atilibusb"
>
> # Which lirc device will be used by lircd(8).
> # This is the same as passing "-d device" to lircd.
> # An empty value will use the default /dev/lirc device.
> LIRC_DEVICE=""
>
> # If "yes", the init script will try to start lircmd(8) too.
> ENABLE_LIRCMD="no"
>
> # Options to lircmd(8).
> LIRCMD_OPTIONS=""
>
> # lsmod |grep ati
> #
>
> # /usr/sbin/lircd -H help
> Driver `help' not supported.
> Supported drivers:
>          accent
>          alsa_usb
>          asusdh
>          atilibusb
>
> -- Mache

I'm not sure it helps, but I have a classic ATI Remote, and use the 
lirc_atiusb driver.

Works fairly well, but it seems to not like most brands of batteries, it 
almost seems like it starts loosing signal strength a few weeks after changing 
the batteries.

-- 
Thomas Fjellstrom
tfjellstrom at shaw.ca