[mythtv-users] Not Working: ATI Remote Wonder II and Lirc

Mache Creeger mache at creeger.com
Thu Apr 6 17:37:27 UTC 2006


The RF link on the ATI RW remote seems to be working.  However, I do 
not get any movement from the mythfrontend screen.  Where can I look 
next to find out what is broken?

-- Mache Creeger

Apr  6 10:31:35 digit kernel: lirc_dev: IR Remote Control driver 
registered, at major 61
Apr  6 10:31:35 digit kernel: lirc_atiusb: USB remote driver for LIRC v0.5
Apr  6 10:31:35 digit kernel: lirc_atiusb: Paul Miller 
<pmiller9 at users.sourceforge.net>
Apr  6 10:31:35 digit kernel: lirc_dev: lirc_register_plugin: sample_rate: 0
Apr  6 10:31:35 digit kernel: lirc_atiusb[2]: X10 Wireless Technology 
Inc USB Receiver on usb1:2
Apr  6 10:31:35 digit kernel: usbcore: registered new driver lirc_atiusb
Apr  6 10:31:50 digit lircd-0.8.1-CVS[2579]: lircd(userspace) ready
Apr  6 10:32:32 digit lircd-0.8.1-CVS[2579]: accepted new client on /dev/lircd
Apr  6 10:32:32 digit kernel: lirc_atiusb[2]: data received 
ff  (ep=0x81 length=1)
Apr  6 10:33:22 digit kernel: lirc_atiusb[2]: data received 14 d6 11 
f0  (ep=0x81 length=4)
Apr  6 10:33:23 digit kernel: lirc_atiusb[2]: data received 14 d5 10 
f0  (ep=0x81 length=4)
Apr  6 10:33:24 digit kernel: lirc_atiusb[2]: data received 14 d7 12 
f0  (ep=0x81 length=4)
Apr  6 10:33:24 digit kernel: lirc_atiusb[2]: data received 14 d5 10 
f0  (ep=0x81 length=4)
Apr  6 10:33:24 digit kernel: lirc_atiusb[2]: data received 14 d7 12 
f0  (ep=0x81 length=4)
Apr  6 10:33:24 digit kernel: lirc_atiusb[2]: data received 14 d5 10 
f0  (ep=0x81 length=4)
Apr  6 10:33:24 digit kernel: lirc_atiusb[2]: data received 14 d7 12 
f0  (ep=0x81 length=4)
Apr  6 10:34:03 digit kernel: lirc_atiusb[2]: data received 14 c8 03 
f0  (ep=0x81 length=4)
Apr  6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 35 70 
f0  (ep=0x81 length=4)
Apr  6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 39 74 
f0  (ep=0x81 length=4)
Apr  6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 39 74 
f0  (ep=0x81 length=4)
Apr  6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 35 70 
f0  (ep=0x81 length=4)
Apr  6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 36 71 
f0  (ep=0x81 length=4)
Apr  6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 3b 76 
f0  (ep=0x81 length=4)
Apr  6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 36 71 
f0  (ep=0x81 length=4)
Apr  6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 35 70 
f0  (ep=0x81 length=4)
Apr  6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 39 74 
f0  (ep=0x81 length=4)
Apr  6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 39 74 
f0  (ep=0x81 length=4)
Apr  6 10:34:08 digit kernel: lirc_atiusb[2]: data received 14 38 73 
f0  (ep=0x81 length=4)
Apr  6 10:34:08 digit kernel: lirc_atiusb[2]: data received 14 3b 76 
f0  (ep=0x81 length=4)
Apr  6 10:34:08 digit kernel: lirc_atiusb[2]: data received 14 38 73 
f0  (ep=0x81 length=4)
Apr  6 10:34:08 digit kernel: lirc_atiusb[2]: data received 14 37 72 
f0  (ep=0x81 length=4)
Apr  6 10:34:08 digit kernel: lirc_atiusb[2]: data received 14 38 73 
f0  (ep=0x81 length=4)
Apr  6 10:34:08 digit kernel: lirc_atiusb[2]: data received 14 3b 76 
f0  (ep=0x81 length=4)
Apr  6 10:34:09 digit kernel: lirc_atiusb[2]: data received 14 e2 1d 
f0  (ep=0x81 length=4)
Apr  6 10:34:10 digit kernel: lirc_atiusb[2]: data received 14 e3 1e 
f0  (ep=0x81 length=4)
Apr  6 10:34:10 digit kernel: lirc_atiusb[2]: data received 14 e4 1f 
f0  (ep=0x81 length=4)
Apr  6 10:34:10 digit kernel: lirc_atiusb[2]: data received 14 df 1a 
f0  (ep=0x81 length=4)
Apr  6 10:34:11 digit kernel: lirc_atiusb[2]: data received 14 e7 22 
f0  (ep=0x81 length=4)
Apr  6 10:34:11 digit kernel: lirc_atiusb[2]: data received 14 e3 1e 
f0  (ep=0x81 length=4)
Apr  6 10:34:11 digit kernel: lirc_atiusb[2]: data received 14 e4 1f 
f0  (ep=0x81 length=4)
Apr  6 10:34:11 digit kernel: lirc_atiusb[2]: data received 14 e2 1d 
f0  (ep=0x81 length=4)
Apr  6 10:34:13 digit kernel: lirc_atiusb[2]: data received 14 ea 25 
f0  (ep=0x81 length=4)
Apr  6 10:34:14 digit kernel: lirc_atiusb[2]: data received 14 c8 03 
f0  (ep=0x81 length=4)
Apr  6 10:34:15 digit kernel: lirc_atiusb[2]: data received 14 c9 04 
f0  (ep=0x81 length=4)
Apr  6 10:34:15 digit kernel: lirc_atiusb[2]: data received 14 ca 05 
f0  (ep=0x81 length=4)
Apr  6 10:34:17 digit kernel: lirc_atiusb[2]: data received 14 41 7c 
f0  (ep=0x81 length=4)
Apr  6 10:34:17 digit kernel: lirc_atiusb[2]: data received 14 42 7d 
f0  (ep=0x81 length=4)
Apr  6 10:34:18 digit kernel: lirc_atiusb[2]: data received 14 35 70 
f0  (ep=0x81 length=4)
Apr  6 10:34:18 digit kernel: lirc_atiusb[2]: data received 14 3c 77 
f0  (ep=0x81 length=4)
Apr  6 10:34:18 digit kernel: lirc_atiusb[2]: data received 14 35 70 
f0  (ep=0x81 length=4)

At 10:06 AM 4/6/2006, Mache Creeger wrote:
>Thanks, I will give it a shot.
>
>-- Mache Creeger
>
>At 08:21 AM 4/6/2006, you wrote:
>>On 4/5/06, Mache Creeger 
>><<mailto:mache at creeger.com>mache at creeger.com> wrote:
>>I am at a loss.  The only issue I can see is when I press buttons on
>>the remote, the light on the ATI USB dongle does not blink.  It stays
>>continually lit.
>>I have read the wiki at
>><http://www.mythtv.org/wiki/index.php/ATI_Remote_Wonder_II>http://www.mythtv.org/wiki/index.php/ATI_Remote_Wonder_II 
>>and have
>>set everything up the way they have stated.
>>When I run irw it just sits there, does not return any status, and
>>does not return to a new prompt.  I get nothing, even when I push
>>buttons on the remote control unit.
>>Everything seems to be in place.  Here is a listing off of dmesg.
>># dmesg | grep lirc
>>lirc_dev: IR Remote Control driver registered, at major 61
>>lirc_atiusb: USB remote driver for LIRC v0.5
>>lirc_atiusb: Paul Miller 
>><<mailto:pmiller9 at users.sourceforge.net>pmiller9 at users.sourceforge.net>
>>lirc_dev: lirc_register_plugin: sample_rate: 0
>>lirc_atiusb[2]: X10 Wireless Technology Inc USB Receiver on usb1:2
>>usbcore: registered new driver lirc_atiusb
>>The daemon is running...
>># /etc/rc.d/init.d/lircd status
>>lircd (pid 4269) is running...
>>/etc/lircd.conf was copied off of the wiki
>>~mythtv/.mythtv/lircrc was also copied off of the wiki
>># modprobe lirc_atiusb
>>#
>>Comes right back with no status
>># rpm -q lirc
>>lirc-0.8.1-cvs20060325_57.rhfc4.at
>># rpm -q lirc-kmdl-2.6.16-1.2069_FC4
>>lirc-kmdl-2.6.16-1.2069_FC4-0.8.1-cvs20060325_57.rhfc4.at
>># ls -l /dev/ | grep lirc
>>lrwxrwxrwx  1 root   root        5 Apr  5 02:49 lirc -> lirc0
>>crw-rw-rw-  1 root   root  61,   0 Apr  5 02:49 lirc0
>>srw-rw-rw-  1 root   root        0 Apr  5 12:38 lircd
>># uname -r
>>2.6.16-1.2069_FC4
>>Any ideas?
>>
>>
>>You might try adding the following line to the file, /etc/modprobe.conf,
>>(or equivalent file if you are not using Fedora Core):
>>
>>options lirc_atiusb debug=1
>>
>>Then, you can watch the file, /var/log/messages, to see if button presses
>>on the ATI Remote Wonder II result in any messages added to the log file.
>>
>>Small disclaimer:  I use the ATI Remote Wonder (not the "II" version).
>>
>>For more information you can search the archive at
>>
>> 
>><http://www.gossamer-threads.com/lists/mythtv/users>www.gossamer-threads.com/lists/mythtv/users
>>
>>for the string, "HOWTO multiple" for more
>>information on setting up the ATI Remote Wonder.
>>
>>--
>>MM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20060406/65fb0382/attachment.htm 


More information about the mythtv-users mailing list