kernel requirements for lirc (/dev/input/...)

[crawler]

Dear Sundtek Support Team,

I'm using a SkyTV Ultimate on a Cubietruck (Debian Wheezy, Kernel 3.19.4) with VDR and lirc.
My problem is, that the IR-Device of the stick isn't being recognized by the system:

Code: [Auswählen]

/opt/bin/getinput.sh
waiting 5 seconds...
ls: cannot access /event*: No such file or directory
The event structure is enabled in kernel config, first it was compiled as a module, now it is fixed, but that doesn't change the fact, that there is no entry in /dev/input/event...
I can get output from the IR-device doing a

Code: [Auswählen]

cat /dev/mediainput0, but I can't use /dev/mediainput0 with lirc/devinput config.

I want to be able to run a shutdown script using irexec, but since there's no entry in /dev/input/..., it can't be accessed by lirc.

Please help.

[Sundtek]

you will need the "uinput" module to have it work as devinput device.

cat /proc/bus/input/devices should give you a hint which device it is.

[crawler]

Hi,

thanks for the hint, I enabled the uniput module and now it's getting recognized as

Code: [Auswählen]

/opt/bin/getinput.sh
waiting 5 seconds...
Sundtek IR Event: /dev/input/event0
and dmesg|grep input gives me

Code: [Auswählen]

dmesg|grep input
[    9.461560] input: Sundtek Ltd. Remote Control as /devices/virtual/input/input0
[    9.462040] evbug: Connected device: input0 (Sundtek Ltd. Remote Control at unknown)
but following the instructions at your lirc howto page doesn't get the remote working, irw gives me no output.

This is my hardware.conf:

Code: [Auswählen]

# /etc/lirc/hardware.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS=""

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD=false

#Don't start irexec, even if a good config file seems to exist.
#START_IREXEC=false

#Try to load appropriate kernel modules
LOAD_MODULES=true

# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="devinput"
# usually /dev/lirc0 is the correct setting for systems using udev
DEVICE="/dev/input/event0"
MODULES=""

# Default configuration files for your hardware if any
LIRCD_CONF=""
LIRCMD_CONF=""
I've got the "big" remote control, so I copied the sundtek_vcr_remote.conf to /etc/lirc/lircd.conf and did a

Code: [Auswählen]

/opt/bin/mediaclient --updaterc=1 -d /dev/mediainput0
Updating remote control layout
done
dpkg-reconfigure lirc doesn't give me a configuration menu (ncurses-dev installed), so I edited the hardware.conf manually.

Starting lirc I get

Code: [Auswählen]

May 25 12:00:04 localhost lircd-0.9.0-pre1[2566]: lircd(devinput) ready, using /var/run/lirc/lircd
May 25 12:00:04 localhost lircd-0.9.0-pre1[2566]: accepted new client on /var/run/lirc/lircd
May 25 12:00:04 localhost lircd-0.9.0-pre1[2566]: initializing '/dev/input/event0'
May 25 12:00:04 localhost kernel: [   47.743886] input: Sundtek Ltd. Remote Control (lircd bypass) as /devices/virtual/input/input3
May 25 12:00:04 localhost kernel: [   47.745543] evbug: Connected device: input3 (Sundtek Ltd. Remote Control (lircd bypass) at unknown)
irw gives me not output at all.

What can I do ?

[Sundtek]

The big (square like) remote control should be 3

updaterc=3

We also had trouble to get lirc work last time, however without lirc the keys just work fine.


So first try to stop lirc, push the numbers - and if they show up on the console devinput is configured correctly on your side. The rest depends on the lirc setup.



this shows which value updaterc should have.

[crawler]

Hi,

Code: [Auswählen]

/etc/init.d/lirc stop
[ ok ] Stopping execution daemon: irexec:.
[ ok ] Stopping remote control daemon(s): LIRC:.
root@cubietruck:~# /opt/bin/mediaclient --updaterc=3 -d /dev/mediainput0
Updating remote control layout
done
Doing a

Code: [Auswählen]

cat /dev/input/event0gives me

Code: [Auswählen]

�cUҎ��cUҎ�cU����cU���cUt���cUt��cU����cU���cU7^��cU7^�cU�^��cU�^while pushing buttons at the rc.

Stopping vdr and starting lirc, irw gives me nothing:

Code: [Auswählen]

/etc/init.d/vdr stop
Stopping Linux Video Disk Recorder: vdr.
root@cubietruck:~# irw
connect: Connection refused
root@cubietruck:~# /etc/init.d/lirc start
[ ok ] Loading LIRC modules:.
[ ok ] Starting remote control daemon(s) : LIRC :.
[ ok ] Starting execution daemon: irexec:.
root@cubietruck:~# irw
 
BUT::
Stopping vdr and lirc, then pressing buttons at the rc gives me:

Code: [Auswählen]

May 25 13:36:42 localhost kernel: [  172.053463] evbug: Event. Dev: input0, Type: 1, Code: 116, Value: 1
May 25 13:36:42 localhost kernel: [  172.053483] evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
May 25 13:36:42 localhost kernel: [  172.053601] evbug: Event. Dev: input0, Type: 1, Code: 116, Value: 0
May 25 13:36:42 localhost kernel: [  172.053610] evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
May 25 13:36:42 localhost kernel: [  172.211109] evbug: Event. Dev: input0, Type: 1, Code: 116, Value: 1
May 25 13:36:42 localhost kernel: [  172.211126] evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
May 25 13:36:42 localhost kernel: [  172.211212] evbug: Event. Dev: input0, Type: 1, Code: 116, Value: 0
May 25 13:36:42 localhost kernel: [  172.211221] evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
May 25 13:36:42 localhost kernel: [  172.236751] evbug: Event. Dev: input0, Type: 1, Code: 116, Value: 1
May 25 13:36:42 localhost kernel: [  172.236768] evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
May 25 13:36:42 localhost kernel: [  172.236851] evbug: Event. Dev: input0, Type: 1, Code: 116, Value: 0
May 25 13:36:42 localhost kernel: [  172.236860] evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
So the rc seems to be working in some way, but what am I missing in the lirc configuration ?

[crawler]

Hi,

I've got the answer:

The default configuration file provided by your company seems to be faulty in the way that there is a 0x00000000000 entry after every code mapping.

This seems to confuse lirc. I deleted these second entries and everything worked just fine.

[Sundtek]

We generated that file with lirc ... that would more or less just show some weird behavior of Lirc or at least the lirc version it was generated with.

Thanks for the feedback we will check that closer within the next days.