I believe that if the device was recognized by the kernel, the device node would be created like it has been created for the mouse or keyboard, without any modifications in the UDEV rules.

Also, have you tried to build LIRC with support for each of the usb drivers and try if one of these work with your remote?

It seems that I cannot be much of a help here, because I do not own a similar device, so I can only write hypothetically about a possible solution. This thread:
http://www.linuxquestions.org/questions/showthread.php?t=234259
seems to deal with a similar problem, so, if I were you, I’d ask them for some info.

From what I understood: the first and absolutely essential step is to make sure that kernel creates an input device for receiver but in my case no such think happens.

In /etc/udev/rules.d/udev.rules there is line:
KERNEL=”hiddev*”, NAME=”usb/%k”

So (based on what is in logs previously posted) there should be a device:
/dev/usb/hiddev0
created but only
usbdev5.2
is created.

I also tried with following lines but with no success
KERNEL=”hiddev*”, NAME=”usb/hiddev%n”
DRIVER=”hiddev*”, NAME=”usb/hiddev%n”

I use Slackware 10.2 with 2.6.14.5 selfcompiled kernel.
proc, sys, usbdevfs are mounted

Do you have any idea what might be wrong?

For example:

begin
prog = irexec
button = 0
button = 3
config = amarok /path/to/playlist3
repeat = 0
end
.
.
begin
prog = irexec
button = 2
button = 1
config = amarok /path/to/playlist21
repeat = 0
end


This means that you have to define as many configurations in the .lircrc file as the number of your playlists. This does not seem convenient though.

I tried to create a configuration in which, if you press a button from 0-9, it exports and appends the respective number in a system variable and then by pressing button “play” for example it would execute the command amarok /path/to/playlist$KeySequence and unset the variable. This did not work. It seems that exporting variables with irexec does not work or I am missing something here… I’ll look into it again at some later time, because it’s a very interesting issue.

In this comment you mention that you have already tried to create a button sequence by placing two button= entries in each configuration. I do not understand why this does not work. Maybe there is something wrong with lircd.conf file or maybe you have to increase the repeat= value for each button configuration.

One more thing. In the above article I mention nothing about key sequencies. This should be corrected.

Thanks for your feedback. :-)

I already tried to play with delays, but without success. In fact it is not at all application related. What I try to do is simply to send a two (or more) keystroke sequence.
In other words : How do I tell lirc to interpret a ‘1′ followed by a ‘5′ as 15 instead of 1 followed by 5 ?

thanks,

Serge

I do not currently use amarok, so I do not fully understand your issue. Anyway, for application specific information I think you should refer to its documentaion or to a relevant forum or mailing list.

Thanks for this info.
I installed Lirc on a fedora 4. It works well, but I still have a problem.
I am looking to launch playlist in Amarok. From 1 to 9 I have no problem, but I can’ get it work behind that.
Do you have any idea how I could do that ?
I saw something with two “button” lines in lircrc, but from the moment i press the first one, it start that playlist. I need some delay between the keystrokes, ut don’t find how to do it.

Many thanks,

Serge

Sometimes getting things to work is a lot of pain, but I can assure you that finally they DO work. :-) I don’t know if the following info helps you, but I’ll write it anyway.

First of all, I would recommend checking if your remote control registers as an input device. You can do a:
# cat /proc/bus/input/devices
And see if there is any reference there. If you are lucky and your remote registers as an input device (much like as a mouse or keyboard) you can try a different approach to set the button mappings. You will not need LIRC at all. I cannot help with that as I have no such experience, but I think you have to edit xorg.conf for the buttons.
On the other hand, if you do want to use LIRC with this input device, you can. LIRC can read from the input device using the --driver=/dev/input (I have no experience either on this, so someone else has to confirm that it’s right). Have a look at these two bttv FAQ questions: http://linux.bytesex.org/v4l2/faq.html#ir They are not specific to bttv.

I did some research, but I could not find any info about this remote. From the kernel messages, I believe that it registers itself as an input device.

In the case you need to know which kernel config options are enabled in the fedora kernel, I can post it or send it to you. As for finding out which driver to compile LIRC with, I do not know any other way apart from comparing the names of the hardware. A last thing would be to compile LIRC trying each one of the listed USB drivers (http://www.lirc.org/html/table.html#@hw-usb) and see if anyone works.

Here are some links you may want to try:
http://www.linuxquestions.org/questions/showthread.php?t=234259
http://undergroundcircus.net/ben/ir501d.html

All the best,
Raoul

In my opinion the most important step is the selection of necessary driver.

I have:

TRUST – Multimedia Remote Control NB-5100p
http://www.trust.com/products/product.aspx?artnr=14272

known also as:
Formosa 21/ eDio 21

USB Receivers : IR-507
http://www.edio21.com/prod_ir507.asp
+
IR Multi Remote Controller: RC102
http://www.edio21.com/prod_rc102.asp

This is what kernel logs in to messages file when I plug in USB receiver:
Dec 31 13:16:07 andres-slack kernel: usb 5-1: new low speed USB device
using uhci_hcd and address 3
Dec 31 13:16:08 andres-slack kernel: input: USB HID v1.10 Device
[Formosa Industrial Computin Formosa RC102-809 USB Remot] on
usb-0000:00:10.3-1

The device seems to not be supported under lirc but as the same device can have different commercial names you can never be sure beforehand.

What I was missing badly in lirc documentation as well as in your tutorial was answer to some basic questions like e.g.:
- Whether any of IrDA stack from kernel need to be compiled in order to have lirc working?
- Is there any easy way to find out which driver would I need apart from looking for name match?
- Is there any generic driver in lirc that I can use as a first step to find out if it works with my hardware?

I looked through many places to find answers and apparently the answer to all questions is NO.

If I knew it before it might have helped me to save a lot of time, because I wouldn’t have to read all the documentation when my device was not supported.

Since irrecord is a LIRC client, it requires that the daemon (lircd) is up and running. An /etc/lircd.conf is not needed to be in place in order to use irrecord. The file that will be generated is the new lircd.conf for your remote control.

Its a good tutorial, and i have been itching to get remote configured for my latop, hopefully my remote works with lirc, btw is there any documentation specifying on how to figure out codes for a remote that is not supported ?

thanks for the walkthro