Menu
▾
▴
Re: ati remote wonder 2 and mythtv
|
From: Tyler F. <ty...@li...> - 2005-02-22 04:18:55
|
Hi Paul,
Good news and bad news. I did as you instructed and experimented for a
few hours tonight. Here are my findings:
1) Apparently I was doing something wrong, or number 3 below was
getting me while I was doing my testing, because by following your
instructions I was able to get irw to respond to the keys I entered in
the config with irrecord. Very good news.
2) Pushing the Aux1-4 buttons or the PC button (also a "mode switch"
button) did not affect irw's ability to successfully capture the
buttons that I had recorded in irrecord, even on a different mode.
Also good news.
3) However--this is the bad news--when I reboot, the config file no
longer works and I have to generate an entirely new one. I repeated
this and would be happy to repeat it as many times as you'd like to
confirm it's consistent.
Any ideas what would be causing it to change each time? Below are
three config files, all of which work in irw after I create them and
reload lircd, but then don't work at all after a reboot.
Given this slightly-different problem, please let me know what you
think and what would be useful from the syslog debug output and I'll be
sure to send it your way.
Thanks.
-Tyler
begin remote
name full.conf
bits 16
eps 30
aeps 100
one 0 0
zero 0 0
pre_data_bits 8
pre_data 0x0
post_data_bits 16
post_data 0x6666
gap 203929
min_repeat 7
toggle_bit 0
begin codes
up 0x0258
down 0x0259
left 0x025A
right 0x025B
ok 0x025C
play 0x022C
end codes
end remote
begin remote
name after_reboot.conf
bits 40
eps 30
aeps 100
one 0 0
zero 0 0
gap 203947
toggle_bit 0
begin codes
ok 0x00025C2F6B
left 0x00025A2F6B
right 0x00025B2F6B
up 0x0002582F6B
down 0x0002592F6B
play 0x00022C2F6B
end codes
end remote
begin remote
name /root/after_reboot2.conf
bits 8
eps 30
aeps 100
one 0 0
zero 0 0
pre_data_bits 16
pre_data 0x2
post_data_bits 16
post_data 0x10
gap 203946
toggle_bit 0
begin codes
ok 0x5C
up 0x58
down 0x59
left 0x5A
right 0x5B
play 0x2C
end codes
end remote
On Feb 20, 2005, at 10:17 AM, Paul Miller wrote:
> Hi Tyler,
>
> I believe the ATI RW II has Aux1-4 buttons at the top of the remote
> which change the output value of all the other buttons -- ie, they
> select the mode. The default behavior is to squash the mode bits
> from the output such that the buttons act as expected. Perhaps you
> have a newer model than the user who assisted me with adding support
> for this remote. (I don't have a RW II).
>
> Anyhow, try this
>
> 1) load the module with debug=1
> 2) run irrecord to create a simple config file (without pressing aux
> buttons)
> 3) run ircd
> 4) run irw and see if the buttons you recorded appear
> 5) press different aux buttons and see if irw still works
> 6) send me the debug output with your comments of what actually
> happened.
>
> You could also try experimenting with the emit_modekeys parameter
> (type modinfo lirc_atiusb.ko for details).
>
> -Paul
>
> On Saturday 19 February 2005 3:20 pm, Tyler Forsythe wrote:
>> I've tried searching the archives & google and can't find my
>> answer. I'll be brief. I'm running MythTV on Slack 10 and lirc
>> version "lircd 0.7.1-CVS".
>>
>> The applicable section from dmesg:
>>
>> lirc_dev: IR Remote Control driver registered, at major 61
>>
>> lirc_atiusb: USB remote driver for LIRC v0.4
>> lirc_atiusb: Paul Miller <pmi...@us...>
>> usb.c: registered new driver lirc_atiusb
>> lirc_dev: lirc_register_plugin:sample_rate: 0
>> lirc_atiusb[5]: on usb2:5
>>
>> I finally got lirc to seem to function after putting this in my
>> rc.local file (previously I didn't have a lirc0 in dev, which
>> seemed to be causing the daemon to fail) :
>>
>> ln -s /dev/lirc /dev/lirc0 ;
>>
>> And then this manually as it's not working in rc.local for some
>> reason:
>>
>> lircd -d /dev/lirc0 /etc/lircd.conf ;
>>
>> With that, I can use irrecord to record a new config file, which
>> was a huge step because for the longest time I couldn't get lirc to
>> do anything to confirm it saw the remote besides what was in dmesg,
>> much less give any sort of output on button press. Does it matter
>> that everytime I run irrecord the gap length is determined to be
>> different? That seems to raise a flag in my mind as a big problem.
>> Also, as a result of this, each config file I produce for the same
>> keys have different values.
>>
>> So, I moved the config file I created using irrecord into /etc as
>> /etc/lircd.conf. Reboot just to make sure it all loads in
>> correctly. Start MythTV and it responds to nothing from the remote.
>> I even tried it without rebooting by killing the daemon and
>> swapping in a newly-generated config file and restarting the
>> daemon. I looked to make sure I had the buttons named the same in
>> lircd.conf as in ~/.mythtv/lircrc and am pretty sure I have them
>> right. At the end of this message I have included two partial
>> config files I created. Could it be an issue with MythTV not
>> looking for it? I compiled it long ago and may have left off a
>> lirc option if that's required. However, I don't see anything
>> about that in the myth docs. I've also tried running "irxevent
>> ~/.mythtv/lircrc" and starting MythTV, but with no remote success.
>>
>> Running irw prints nothing when keys are pressed. A snippet of
>> /var/log/lircd (the second line is when irw is run, third is when
>> it's closed with control-c) :
>>
>> Feb 19 15:21:59 Bart lircd 0.7.1-CVS: lircd(atiusb) ready
>> Feb 19 15:47:52 Bart lircd 0.7.1-CVS: accepted new client on
>> /dev/lircd Feb 19 15:48:00 Bart lircd 0.7.1-CVS: removed client
>>
>> Any ideas? Thank you for your time.
>>
>> -Tyler Forsythe
>>
>>
>> first:
>>
>> name ATI_REMOTE_WONDER_II
>> bits 40
>> eps 30
>> aeps 100
>>
>> one 0 0
>> zero 0 0
>> gap 203975
>> toggle_bit 0
>>
>>
>> begin codes
>> a 0x0002786373
>> b 0x0002796373
>> c 0x00027A6373
>> d 0x00027B6373
>> e 0x00027C6373
>> f 0x00027D6373
>> vol+ 0x0002106373
>> vol- 0x0002116373
>> chan+ 0x0002206373
>> chan- 0x0002216373
>> mute 0x00020D6373
>> 1 0x0002016373
>> 2 0x0002026373
>> 3 0x0002036373
>> 4 0x0002046373
>> 5 0x0002056373
>> 6 0x0002066373
>> 7 0x0002076373
>> 8 0x0002086373
>> 9 0x0002096373
>> 0 0x0002006373
>> up 0x0002586373
>> down 0x0002596373
>> left 0x00025A6373
>> right 0x00025B6373
>> play 0x00022C6373
>> stop 0x0002316373
>> record 0x0002376373
>> end codes
>>
>> end remote
>>
>>
>>
>>
>> begin remote
>>
>> name second_rwii
>> bits 8
>> eps 30
>> aeps 100
>>
>> one 0 0
>> zero 0 0
>> pre_data_bits 16
>> pre_data 0x2
>> post_data_bits 16
>> post_data 0x0
>> gap 203954
>> toggle_bit 0
>>
>>
>> begin codes
>> left 0x5A
>> right 0x5B
>> up 0x58
>> down 0x59
>> play 0x2C
>> stop 0x31
>> record 0x37
>> vol+ 0x10
>> vol- 0x11
>> chan+ 0x20
>> chan- 0x21
>> mute 0x0D
>> a 0x78
>> b 0x79
>> c 0x7A
>> d 0x7B
>> e 0x7C
>> f 0x7D
>> ok 0x5C
>> 1 0x01
>> 2 0x02
>> 3 0x03
>> end codes
>>
>> end remote
>>
>>
>>
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real
>> users. Discover which products truly live up to the hype. Start
>> reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>
|