lircd doesn't work anymore - kernel 2.6.30
jf
I've completely reinstalled my broken gentoo, and almost anything seems to
work, except my realmagic remote control. I've already tried to emerge
lircd, then downloaded and install lircd 0.8.6, but I get always the same
answer "lircd: there's no hardware I can use and no peers are specified"
Before I broke the previous Gentoo, it worked perfectly, using /dev/ttyS0.
On the same PC, I run ubuntu, and the remote works well ( on /dev/ttyS0).
I've had a look on several docs, howtos and FAQ,as my system uses HAL, but
I've been unable to find an answer.
Any idea will be welcome.
thanks,
jf
AZ Nomad
Do you set LIRC_DEVICES in /etc/make.conf?
jf
> On Thu, 22 Oct 2009 00:01:31 +0200, jf <cest...@free.fr> wrote:
>>Hi u all :)
>>I've completely reinstalled my broken gentoo, and almost anything seems to
>>work, except my realmagic remote control.
>>thanks,
>>jf
>
> Do you set LIRC_DEVICES in /etc/make.conf?
no, I have read I should set INPUT_DEVICES="keyboard mouse lirc evdev"
but nothing about LIRC_DEVICES .What should I put there ?
jf
is it LIRC_DEVICES="devinput" ?
AZ Nomad
They are two seperate lines. INPUT_DEVICES is for X, LIRC_DEVICES is
for LIRC.
The name of the remote control device goes there. If you have it
blank, LIRC might default to installing everything. Do a
'emerge -pv lirc' to see what device(s) would be installed.
For example, on one of my systems I have a streamzap remote. The
device line is LIRC_DEVICES="streamzap". The actual kernel module
installed is lirc_streamzap. (the lirc package supplies the kernel
module)
jf
Thanks, I'll try that. But I know this remote doesn't need a kernel module.
The device driver is "pixelview".
jf
AZ Nomad
Driver == kernel module.
Try setting LIRC_DEVICES to pixelview_bt878, pixelview_pak, or pixelview_pro
jf
Yes, you are right, it says it doesn't need a "special kernel module" ;)
I set LIRC_DEVICES to pixelview, but it gave me the same answer, then I
tried with "devinput" and lirc says :
lircd: lircd(pixelview) ready
but if I launch vdr , it asks me to push a key, the remote answers ( I can
see the led on the receiver ), but vdr doesn't get it....
it"s not far, I'll get it ;)
regards,
jf
jf
I think it's now a matter of vdr config..
AZ Nomad
the /etc/lirc/lirc.conf setup may be returning button strings that vdr
doesn't recognize.
IE: you hit the rewind key; lirc returns "<<"; vdr then has to be
setup to interpret "<<" as rewind.
use the 'irw' command alone to test lirc w/out the vdr application.
jf
>
> use the 'irw' command alone to test lirc w/out the vdr application.
Again, I get nothing with irw :(
first try :
pcjf jf # /usr/local/sbin/lircd -n
lircd: lircd(realmagic) ready
lircd: accepted new client on /dev/lircd
lircd: readlink() failed for "/dev/lirc"
lircd: No such file or directory
lircd: could not create lock files
lircd: caught signal
Terminated
second try :
pcjf jf # /usr/local/sbin/lircd -n -d /dev/ttyS0
lircd: lircd(realmagic) ready
lircd: accepted new client on /dev/lircd
this time, when I run irw, I see the led flashing, but nothing on stdout
I'll try again tomorrow ;)
regards,
jf
AZ Nomad
>AZ Nomad wrote:
>>
>> use the 'irw' command alone to test lirc w/out the vdr application.
>Again, I get nothing with irw :(
use '/etc/init.d/lircd start' to start it
Have you googled for 'gentoo lirc' yet?
LIRC_DEVICES has to be pixelview_bt878. pixelview_pak, or pixelview_pro
setting it to an unknown value like 'pixelview' is the same as not
setting it as all.
/etc/init.d/lircd will load the kernel module, for example lirc_pixelview_bt878.
It'll create a device such as /dev/lirc0
/dev/ttyS0 is only for RS232 devices.
jf
> On Fri, 23 Oct 2009 01:42:06 +0200, jf <cest...@free.fr> wrote:
>>AZ Nomad wrote:
>>>
>>> use the 'irw' command alone to test lirc w/out the vdr application.
>
>>Again, I get nothing with irw :(
>
> use '/etc/init.d/lircd start' to start it
>
> Have you googled for 'gentoo lirc' yet?
>
Sure I have :)
> LIRC_DEVICES has to be pixelview_bt878. pixelview_pak, or pixelview_pro
>
> setting it to an unknown value like 'pixelview' is the same as not
> setting it as all.
why do they need to change things which work well !? ;)
>
> /etc/init.d/lircd will load the kernel module, for example
> lirc_pixelview_bt878. It'll create a device such as /dev/lirc0
>
> /dev/ttyS0 is only for RS232 devices.
my remote is a realmagic , the receiver is plugged on the serial port. And
that is the way I used it before, and also the way it works on the ubuntu
distro
jf
> my remote is a realmagic , the receiver is plugged on the serial port. And
> that is the way I used it before, and also the way it works on the ubuntu
> distro
I'm not far : now, when I run lircd, it says :
lircd: lircd(pixelview) ready, using /var/run/lirc/lircd
Then I run irw /var/run/lirc/lircd , and I get :
pcjf jf # irw /var/run/lirc/lircd
0000000018362d8b 00 1 REALmagic
0000000018362d8b 01 1 REALmagic
0000000018312c4b 00 2 REALmagic
0000000018312c4b 01 2 REALmagic
000000001831ac6b 00 3 REALmagic
000000001831ac6b 01 3 REALmagic
^C
when I press the 1,2,3 buttons :)
But vdr --rcu=/var/run/lirc/lircd can't is not accepted as a lircd client
I'll try to find some help in vdr groups.
Thanks again for your help :)
regards,
jf
jf
It's OK now : vdr --lirc=/var/run/lirc/lircd makes it work :)
AZ Nomad
Step 1 is working. Congratulations! The remote is operating and returning
codes.
The next step is to get the application to match.
The codes come from /etc/lirc/lircd.conf. That is where the the infrared
binary like 0x0007baf is equated to match a code like "1".
You have to either update the config file for your application to work with
what lircd is returning, or modify lircd (via /etc/lirc/lircd.conf) to match
what your application is expecting.