SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have bought a ATI Remote Wonder remote and try to get it running on my 13.37 box.
First I recognized that the device works out of the box with the ati_remote kernel module, which is not a lirc module, and unfortunately not all buttons have a function.
Then I tried to run it with lirc (0.9.0 from SBo).
So I blacklisted the ati_remote module to prevent it from loading and created the device /var/run/lirc because the slackbuild doesn't.
I started lircd with one of the sample lircd.confs for the ati remote. But I don't get anything with irw.
After that I tried the other possibility, with loading a driver from the command line. So I first unloaded the kernel modules lirc_atiusb and lirc_dev. Then I startet lircd with option -H atilibusb and a sample lircd.conf for atilibusb.
Now I got something with irw.
Can anyone tell me what's the problem with using the lirc kernel modules? Why I don't get any output with irw?
Any links to GOOD and EASY tutorials, how to set up lirc are welcome.
PS: So far, I don't really look through the documentation of lirc. Is it really this complicated and complex, or is it me?
With the statement "unfortunately not all buttons have a function" I meant, that some buttons are not detected (or assigned) when using the ati_remote kernel module, which is not a lirc module, but a usb input device module, that detects the remote as a kind of keyboard, or so. I'm not sure, but I read something about the ability to assign keys in a Xmodmap file and I don't know if this is the better way to configure my remote than with lirc.
I'm aware that I have to assign functions to buttons in a config file. But I still don't really know how the config files work together (if they do at all). Like in other tutorials which are based on a ununtu system, your lirc config files are in an "lirc"-directory in etc and there is a file called hardware.conf. In the slackware lirc(0.9.0) package from slackbuils.org, the config files are directly in etc and there is no hardware.conf.
Nevertheless, as I wrote, I get output with irw, when using the driver atilibusb. I just didn't get it managed to control a application because I don't know exactly how to edit all the config files to get it working at the moment. But hopefully I will find out :-)
One of my questions is, why doesn't it work with the lirc modules lirc_dev and lirc_atiusb but with the driver atilibusb, because it should as far as I read.
My actual understanding of the config files is:
- lircd.conf -> there I just assign a name to the remote itself and to each button with the according code
- lircrc -> there I have to assign the functions to the buttons with the button names from lircd.conf
Please tell me if I'm wrong.
The next is, when I want to control xbmc with it, I read that I have to configure a file called Lircmap.xml. Do I still need to put the functions in lircrc then or is everything done in Lircmap.xml then?
So, as you can see, for me it's not exatly clear where I have to edit what.
And the fact, that it doesn't work with the lirc modules also bothers me.
For documentation, you are absolutely right. For me it could also be more detailed, i.e. the description of some options.
Lirc may be a powerful tool and for sure it's good that it is there, but for me it's a mess to configure it, even to figure out how to configure it the right way.
I googled a lot, but didn't find an easy to use tutorial or documentation for me.
But maybe I looked at the wrong places.
if you use the ati_remote kernel module along with irw, do you get a response for all of the keys on the remote ?
They might not be mapped, but can you see anything ? If so, just remap your own config file, or as you say, use Xmodmap.
Also, try modinfo ati_remote : it may have tips for you.
Yes you need a good conf file for the lirc for this remote. I had a working one, but at the end of it all, I decided to use the kernel built in module. I found it better to have the mouse/keyboard emulation combo then app specific bindings. It had to meet spouse approval, and she really did not like have to toggle for music, then toggle for a video player then toggle for ...
It got annoying really fast. Using the kernel module I do not have a working OK button. But the checkmark key on this remote emulates the enter key.
As another person stated, betweek xbindkeys and xmodmap I have a nice set up that I'm quite happy with.
Would be great if you would provide me your config files, so that I at least can get an idea how to configure it with xbindkeys and xmodmap.
I also already thought if lirc is really, what I want. The fact that it behaves the same in all applications, when it works as an generic USB input device is a plus and the configuration is less comlicated then with lirc. Most buttons work out of the box. Just plug in and it's directly usable.
But I'm not sure at the moment, if I shouldn't give lirc a try anyhow, and if it's just to have a comparison, which fits better the needs.
At the moment, I think I will stick with the USB input device mode, because of a lack of time, that I would need to get it running with lirc.