<html>
<body>
<font size=3>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? <br><br>
-- Mache Creeger<br><br>
Apr 6 10:31:35 digit kernel: lirc_dev: IR Remote Control driver
registered, at major 61<br>
Apr 6 10:31:35 digit kernel: lirc_atiusb: USB remote driver for
LIRC v0.5<br>
Apr 6 10:31:35 digit kernel: lirc_atiusb: Paul Miller
<pmiller9@users.sourceforge.net><br>
Apr 6 10:31:35 digit kernel: lirc_dev: lirc_register_plugin:
sample_rate: 0<br>
Apr 6 10:31:35 digit kernel: lirc_atiusb[2]: X10 Wireless
Technology Inc USB Receiver on usb1:2<br>
Apr 6 10:31:35 digit kernel: usbcore: registered new driver
lirc_atiusb<br>
Apr 6 10:31:50 digit lircd-0.8.1-CVS[2579]: lircd(userspace)
ready<br>
Apr 6 10:32:32 digit lircd-0.8.1-CVS[2579]: accepted new client on
/dev/lircd<br>
Apr 6 10:32:32 digit kernel: lirc_atiusb[2]: data received ff
(ep=0x81 length=1)<br>
Apr 6 10:33:22 digit kernel: lirc_atiusb[2]: data received 14 d6 11
f0 (ep=0x81 length=4)<br>
Apr 6 10:33:23 digit kernel: lirc_atiusb[2]: data received 14 d5 10
f0 (ep=0x81 length=4)<br>
Apr 6 10:33:24 digit kernel: lirc_atiusb[2]: data received 14 d7 12
f0 (ep=0x81 length=4)<br>
Apr 6 10:33:24 digit kernel: lirc_atiusb[2]: data received 14 d5 10
f0 (ep=0x81 length=4)<br>
Apr 6 10:33:24 digit kernel: lirc_atiusb[2]: data received 14 d7 12
f0 (ep=0x81 length=4)<br>
Apr 6 10:33:24 digit kernel: lirc_atiusb[2]: data received 14 d5 10
f0 (ep=0x81 length=4)<br>
Apr 6 10:33:24 digit kernel: lirc_atiusb[2]: data received 14 d7 12
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:03 digit kernel: lirc_atiusb[2]: data received 14 c8 03
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 35 70
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 39 74
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 39 74
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 35 70
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 36 71
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 3b 76
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 36 71
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 35 70
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 39 74
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:07 digit kernel: lirc_atiusb[2]: data received 14 39 74
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:08 digit kernel: lirc_atiusb[2]: data received 14 38 73
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:08 digit kernel: lirc_atiusb[2]: data received 14 3b 76
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:08 digit kernel: lirc_atiusb[2]: data received 14 38 73
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:08 digit kernel: lirc_atiusb[2]: data received 14 37 72
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:08 digit kernel: lirc_atiusb[2]: data received 14 38 73
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:08 digit kernel: lirc_atiusb[2]: data received 14 3b 76
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:09 digit kernel: lirc_atiusb[2]: data received 14 e2 1d
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:10 digit kernel: lirc_atiusb[2]: data received 14 e3 1e
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:10 digit kernel: lirc_atiusb[2]: data received 14 e4 1f
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:10 digit kernel: lirc_atiusb[2]: data received 14 df 1a
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:11 digit kernel: lirc_atiusb[2]: data received 14 e7 22
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:11 digit kernel: lirc_atiusb[2]: data received 14 e3 1e
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:11 digit kernel: lirc_atiusb[2]: data received 14 e4 1f
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:11 digit kernel: lirc_atiusb[2]: data received 14 e2 1d
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:13 digit kernel: lirc_atiusb[2]: data received 14 ea 25
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:14 digit kernel: lirc_atiusb[2]: data received 14 c8 03
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:15 digit kernel: lirc_atiusb[2]: data received 14 c9 04
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:15 digit kernel: lirc_atiusb[2]: data received 14 ca 05
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:17 digit kernel: lirc_atiusb[2]: data received 14 41 7c
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:17 digit kernel: lirc_atiusb[2]: data received 14 42 7d
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:18 digit kernel: lirc_atiusb[2]: data received 14 35 70
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:18 digit kernel: lirc_atiusb[2]: data received 14 3c 77
f0 (ep=0x81 length=4)<br>
Apr 6 10:34:18 digit kernel: lirc_atiusb[2]: data received 14 35 70
f0 (ep=0x81 length=4)<br><br>
At 10:06 AM 4/6/2006, Mache Creeger wrote:<br>
<blockquote type=cite class=cite cite="">Thanks, I will give it a
shot. <br><br>
-- Mache Creeger<br><br>
At 08:21 AM 4/6/2006, you wrote:<br>
<blockquote type=cite class=cite cite="">On 4/5/06, <b>Mache Creeger</b>
<<a href="mailto:mache@creeger.com">mache@creeger.com</a>> wrote:
<dl>
<dd>I am at a loss. The only issue I can see is when I press
buttons on
<dd>the remote, the light on the ATI USB dongle does not blink. It
stays
<dd>continually lit.<br>
<dd>I have read the wiki at
<dd><a href="http://www.mythtv.org/wiki/index.php/ATI_Remote_Wonder_II">
http://www.mythtv.org/wiki/index.php/ATI_Remote_Wonder_II</a> and have
<dd>set everything up the way they have stated.<br>
<dd>When I run irw it just sits there, does not return any status, and
<dd>does not return to a new prompt. I get nothing, even when I
push
<dd>buttons on the remote control unit.<br>
<dd>Everything seems to be in place. Here is a listing off of
dmesg.<br>
<dd># dmesg | grep lirc
<dd>lirc_dev: IR Remote Control driver registered, at major 61
<dd>lirc_atiusb: USB remote driver for LIRC v0.5
<dd>lirc_atiusb: Paul Miller
<<a href="mailto:pmiller9@users.sourceforge.net">
pmiller9@users.sourceforge.net</a>>
<dd>lirc_dev: lirc_register_plugin: sample_rate: 0
<dd>lirc_atiusb[2]: X10 Wireless Technology Inc USB Receiver on usb1:2
<dd>usbcore: registered new driver lirc_atiusb<br>
<dd>The daemon is running...<br>
<dd># /etc/rc.d/init.d/lircd status
<dd>lircd (pid 4269) is running...<br>
<dd>/etc/lircd.conf was copied off of the wiki<br>
<dd>~mythtv/.mythtv/lircrc was also copied off of the wiki <br>
<dd># modprobe lirc_atiusb
<dd>#
<dd>Comes right back with no status<br>
<dd># rpm -q lirc
<dd>lirc-0.8.1-cvs20060325_57.rhfc4.at<br>
<dd># rpm -q lirc-kmdl-2.6.16-1.2069_FC4
<dd>lirc-kmdl-2.6.16-1.2069_FC4-0.8.1-cvs20060325_57.rhfc4.at <br>
<dd># ls -l /dev/ | grep lirc
<dd>lrwxrwxrwx 1 root
root 5 Apr 5 02:49 lirc
-> lirc0
<dd>crw-rw-rw- 1 root root 61, 0
Apr 5 02:49 lirc0
<dd>srw-rw-rw- 1 root
root 0 Apr 5 12:38
lircd<br>
<dd># uname -r
<dd>2.6.16-1.2069_FC4<br>
<dd>Any ideas?<br><br>
</dl><br>
You might try adding the following line to the file,
/etc/modprobe.conf,<br>
(or equivalent file if you are not using Fedora Core):<br><br>
options lirc_atiusb debug=1<br><br>
Then, you can watch the file, /var/log/messages, to see if button
presses<br>
on the ATI Remote Wonder II result in any messages added to the log
file.<br><br>
Small disclaimer: I use the ATI Remote Wonder (not the
"II" version).<br><br>
For more information you can search the archive at<br><br>
<a href="http://www.gossamer-threads.com/lists/mythtv/users">
www.gossamer-threads.com/lists/mythtv/users</a><br><br>
for the string, "HOWTO multiple" for more<br>
information on setting up the ATI Remote Wonder.<br><br>
-- <br>
MM</font></blockquote></blockquote></body>
</html>