Mythdora 10.21 X64 Remote Wonder (one)

Hi,

I have just reinstalled with the latest mythdora, and everything went very well. I have it all working as it should, however my remote wonder remote no longer works. I selected it at install from the list of remotes.

I saw something saying that the lirc_atiusb driver has been removed from FC10, which explains it, but there must be a way for the remote to still work? the bug talks about using atilibusb mode of lirc but not sure how to do that.

There is also the suggestion of using ati_remote, if I use that it lets the arrow keys wrk, but can;t see how to make any of the other buttons work. I'm happy to use any method thats actually works.

Does anybody know how to make it work.

Regards

Ben

For now go and edit

For now go and edit /etc/sysconfig/lirc and amke the options read "--driver=atilibusb" or maybe it's -H atilibusb... and restart lirc service. See if irw is working then. This is something we're working on for an update to fix the config settings.

No joy yet

The command to add to the file is

when I do a ps I can see it running with the right option now :

[root@mythtv mythtv]# ps ax | grep lircd
2544 ? Ss 0:00 /usr/sbin/lircd --driver=atilibusb
3569 ? S 0:00 /usr/sbin/lircd --driver=atilibusb
[root@mythtv mythtv]

I also see in /var/log/messages this line, which looks good :-

Jan 12 21:47:43 mythtv lircd-0.8.4a[2544]: lircd(atilibusb) ready

The ati_remote module is not loaded, which I think is right

[root@mythtv mythtv]# lsmod | grep ati
[root@mythtv mythtv]

irw runs, but I get nothing when I press any of the remote buttons.

Regards

Ben

Try rebooting and then try

Try rebooting and then try again. You look to have two lircd processes going at the same time.

"Please ignore the man behind the curtain"
Dennis

"Please ignore the man behind the curtain"
Dennis

Got it working

Well Almost there.

Whilst irw output nothing, even after a reboot. I did find irrecord worked, so I have recorded a new config file that seems to work. Although it is giving 4 presses for every button press, so I need to slow that down a bit.

Ben

What remote was this for?

What remote was this for? And can you post your recently created lircd.conf here please?

You can adjust the repeat level in your ~/.lircrc so that myth doesn't interpret the multiple key presses.

Ryan

Sorted

Hi Ryan,

Thanks, I figured the repeat out, it was actually doing it 5 times, so I added delay 5 in the lircrc and all is well now.

I have the remote wonder as pictured here http://www.mythtv.org/wiki/index.php/Image:Remotewonder1.jpg and http://www.mythtv.org/wiki/index.php/Image:Remotewonder2.jpg I

Can't see how to attach a file, so will cut and paste it. I actually ended up with different button names, but they are consistent with my very original setup of mythtv, and so compatible with an lircrc file I had as a backup. Interestingly the lirc.conf file I used with this remote on MD5 is different from the recently recorded one, which again is different form the default lirc one for this remote. All very odd.

begin remote

name ati_remote_wonder
bits 16
eps 30
aeps 100

one 0 0
zero 0 0
pre_data_bits 8
pre_data 0x14
post_data_bits 16
post_data 0x0
gap 147995
toggle_bit_mask 0x0

begin codes
a 0xC500
b 0xC601
power 0xC702
tv 0xC803
dvd 0xC904
web 0xCA05
library 0xCB06
hand 0xCC07
mouse-up 0x3772
mouse-up-right 0x3A75
mouse-right 0x3671
mouse-down-right 0x3671
mouse-down 0x3873
mouse-down-left 0x3873
mouse-left 0x3570
mouse-up-left 0x3974
mouse-click-left 0x3D78
mouse-click-right 0x417C
vol-down 0xCE09
vol-up 0xCD08
mute 0xCF0A
channel-down 0xD10C
channel-up 0xD00B
1 0xD20D
2 0xD30E
3 0xD40F
4 0xD510
5 0xD611
6 0xD712
7 0xD813
8 0xD914
9 0xDA15
0 0xDC17
root-menu 0xDB16
setup-menu 0xDD18
c 0xDE19
d 0xF01B
up 0xDF1A
right 0xE41F
down 0xE722
left 0xE21D
ok 0xE31E
e 0xE621
f 0xE823
zoom 0xE520
timer 0xE11C
rew 0xE924
ffwd 0xEB26
play 0xEA25
stop 0xED28
pause 0xEE29
rec 0xEC27
end codes

end remote

lircrc

Thanks, I figured the repeat out, it was actually doing it 5 times, so I added delay 5 in the lircrc and all is well now.

Ben,

Would you mind posting your lircrc file? (I have the same part number as you do, so it must be correct!) I've been trying to fix this repeat issue, but no matter what I put in the lircrc file for repeat and delay, irw keeps on reporting 5 signals for every button press.

Just in case someone else can figure out what I'm doing wrong, here's my lircrc:


# Channel Up
begin
prog = mythtv
button = channel-up
delay=50
repeat=5
config = Up
end

# Channel Down
begin
prog = mythtv
button = channel-down
delay=50
repeat=5
config = Down
end

# General Left
begin
prog = mythtv
button = left
delay=50
repeat=5
config = Left
end

# General Right
begin
prog = mythtv
button = right
delay=50
repeat=5
config = Right
end

# LiveTV browse up channel
begin
prog = mythtv
button = channel-up
delay=50
repeat=5
config = Up
end

etc...

My lircd.conf file is the same as posted above by Ben, and here's my irw output:


[mythtv@mythfront ~]$ irw
00000014d00b0000 00 channel-up ati_remote_wonder
00000014d00b0000 01 channel-up ati_remote_wonder
00000014d00b0000 02 channel-up ati_remote_wonder
00000014d00b0000 03 channel-up ati_remote_wonder
00000014d00b0000 04 channel-up ati_remote_wonder
00000014cd080000 00 vol-up ati_remote_wonder
00000014cd080000 01 vol-up ati_remote_wonder
00000014cd080000 02 vol-up ati_remote_wonder
00000014cd080000 03 vol-up ati_remote_wonder
00000014cd080000 04 vol-up ati_remote_wonder
00000014ce090000 00 vol-down ati_remote_wonder
00000014ce090000 01 vol-down ati_remote_wonder
00000014ce090000 02 vol-down ati_remote_wonder
00000014ce090000 03 vol-down ati_remote_wonder
00000014ce090000 04 vol-down ati_remote_wonder
00000014d30e0000 00 2 ati_remote_wonder
00000014d30e0000 01 2 ati_remote_wonder
00000014d30e0000 02 2 ati_remote_wonder
00000014d30e0000 03 2 ati_remote_wonder
00000014d30e0000 04 2 ati_remote_wonder

I'm pressing the buttons as fast as I can!

Any help would be appreciated.

thanks!

The lircd.conf that comes

The lircd.conf that comes with MythDora is straight from the Wiki. What model number is your USB receiver? The one from the Wiki is 5000023600. I believe there are many versions of this which would make sense as to why it maynot work.

"Please ignore the man behind the curtain"
Dennis

"Please ignore the man behind the curtain"
Dennis

Model # 5000023600

d00dtv wrote:

The lircd.conf that comes with MythDora is straight from the Wiki. What model number is your USB receiver? The one from the Wiki is 5000023600. I believe there are many versions of this which would make sense as to why it maynot work.

"Please ignore the man behind the curtain"
Dennis

I have the model# you described and still no go. I am running 10.21 and have selected ATI remote wonder in the "infrared devices" section of the frontend and got some buttons working after I removed "ati_remote" from the blacklist (per the mythtv wiki), but still only a few buttons work. (I tried to assign the buttons via the frontend edit keys section but it would not recognize them)

I previously had tried the changes described above and nothing worked.

The only thing I can suggest

The only thing I can suggest is to do what was posted and use the atilibusb driver blacklisting the ati_remote module and create your own config file. OR continue to use what you have and create your own config using irrecord.

"Please ignore the man behind the curtain"
Dennis

"Please ignore the man behind the curtain"
Dennis

Its

Hmm,

I used a sticky pad to stick it at the top of the cabinet to get the range to work (the computer and cabinet are in the room next to the TV, so it has to work through the brick wall). So it's a bit hard to see what it is, but it looks like 5000016000.

It is identical to the picture in the wiki though, but I guess that means nothing as its what's inside the counts!

Regards

Ben

That's correct. And this

That's correct. And this issue will continue as ATI can't settle on one model. There are at least 4-5 that I know of.

"Please ignore the man behind the curtain"
Dennis

"Please ignore the man behind the curtain"
Dennis

Snapstream firefly

I'm having the same problem, but mine is a firefly RF unit. Worked great under MD5.
I've spent hours searching and trying different things, but no joy.

My model of receiver is R1000-1.

The thing that's strange is that when I go to edit /etc/sysconfig/lirc the file is there, but it is completely empty. I tried adding the "--driver=atilibusb" line to it but I get an error when restarting the lircd service: /etc/sysconfig/lirc: line 1: --driver=atilibusb: command not found

I was very surprised to find that the file /etc/lircd.conf contained a line saying that it was generated by lirc-0.7(lirc_atiusb) or something like that. I have since overwritten the file with the one from here -> http://www.mythtv.org/wiki/Snapstream_Firefly that is generated by lirc-0.8.4a(atilibusb).

Still when I run lsmod there is no entry for "lirc_atiusb" or for "atilibusb" as I've read in other posts should be the case.

This is a completely fresh installation of MD10.21. I choose all of the default options and chose my remote from the list of options in the browser-based setup. From everyone else's posts it's supposed to just work with the defaults so I was surprised that with the default install I was finding the older version in /etc/lircd.conf

I ran "yum upgrade" after the first run of mythtv and it all seemed to run fine. I got upgraded to .22 for mythtv but I still can not get anything for my remote. I changed the batteries in the remote so they are fresh but I get nothing when running irw and when I try irrecord I get
"irrecord: could not get file information for /dev/lirc
irrecord: default_init(): No such file or directory
irrecord: could not init hardware (lircd running ? --> close it, check permissions)"

Anyone have any thoughts?

Thank you so much! Obviously the WAF is very low right now.

Mike

What are the contents of

What are the contents of your /etc/sysconfig/lirc file?

I believe it should read something like this: "LIRCD_OPTIONS='-H atilibusb'"

You can also check to make atilibusb is compiled in (if yum upgrade changed your lirc version) at the commandline with lirc -H --help.

Ryan

My /etc/sysconfig/lirc file

My /etc/sysconfig/lirc file is completely empty.

I ran the lirc -H command and I got "bash: lirc: command not found"

Mike

Sorry, I realized it needs

Sorry, I realized it needs to be lircd for the command.

Here's what I got:

lircd -H --device=atilibusb
Driver `--device=atilibusb' not supported.
Supported drivers:
accent
alsa_usb
asusdh
atilibusb
audio
audio_alsa
bte
bw6130
commandir
creative
creative_infracd
default
devinput
dsp
dvico
ea65
i2cuser
irlink
irman
livedrive_midi
livedrive_seq
logitech
macmini
mp3anywhere
mplay
mouseremote
mouseremote_ps2
null
pcmak
pinsys
pixelview
samsung
sb0540
silitek
tira
udp
uirt2
uirt2_raw
usb_uirt_raw
usbx

Mike

Okay, obviously I don't know

Okay, obviously I don't know what I'm doing. Go easy on me. :)

I finally found the right syntax and here is the result:
"lircd -H atilibusb"
lircd: there seems to already be a lircd process with pid 2024
lircd: otherwise delete stale lockfile /var/run/lircd.pid

So I stopped the lircd with "/sbin/service lirc stop" and then ran "lircd -H atilibusb" and then I ran irw and it WORKS!!

So why wouldn't this work by default since I used all the default install options for MD10.21?

More importantly, where do I add this so that it autostarts and is running correctly?

Thank you so much!!! You are the best!!!!

Mike

When you did you install,

When you did you install, did you check the mythdora-updates repo to be active during the install? I think we made a fix for this after the release, and you'd have had to upgraded the mythdora rpm or checked it to update in the installer basically.

If you missed enabling mythdora-updates it wouldn't have had the proper fixes when you ran through the setup.

Also, you could have re-run the infrared device configuration from the mythdora-settings menus.

Ryan

Thanks for the reply Ryan.

Thanks for the reply Ryan. I was afraid to enable any other packages. When you say to enable the mythdora-updates you mean to check that additional repository during the install right?

I checked a few additional repositories the first time I installed and it said I had some conflicts or something and then I had to re-run the install from the beginning as it errored out with some kind of a bug message.

I want to be sure I've got it set up as stable as possible so if that's what I need to do then I will re-run the installation from the start and wipe everything out again.

Thanks again!

Mike

No. You don't need to wipe

No. You don't need to wipe anything. I was just asking if you did that step or not, which would explain why it didn't work the first time.

You should run this from the command line as root however:

yum upgrade mythdora

To upgrade to the stable mythdora rpm.

Ryan

Just to follow up for anyone

Just to follow up for anyone else going down the same road. I went ahead and reinstalled from scratch again and enabled the mythdora-updates package to see if the remote would work by default. It still did not work.

The key to getting it to work is to copy the updated /etc/lircd.conf file from this wiki page -> http://www.mythtv.org/wiki/Snapstream_Firefly

After copying that into the lircd.conf file then it did work without me having to add the "LIRCD_OPTIONS='-H atilibusb'" line to the /etc/sysconfig/lirc file. So choosing to enable the mythdora-updates repository must have allowed it to add that line, but somehow it does not enable the correct /etc/lircd.conf file to be included by default.

Thanks again for the help pisani. You guys are just incredible. :)

Mike

Which remote is it

Which remote is it exactly?

There is some variation in the remotes/receivers unfortunately. Is it the snapstream you chose out of the setup list when you configured mythdora or was it a remote wonder?

Ryan

In my case it is a

In my case it is a Snapstream firefly remote (Not the mini. It's the RF one)
I did choose the snapstream out of the setup list when I configured mythdora. It had the matching picture of my remote, but looks like the associated file is either an old version or maybe it's accidentally using the all-in-wonder remote.

Mike