2011-07-08, 12:45
Hello again,
using the old lirc modules wasn't a dead end at all, there was just a change in the ir-codes I can't explain, since everything (except the kernel) is almost the same. I stil got output with cat /dev/lirc0 | xxd so I tried other lircd.conf files
The following should not keep any suprises, but maybe someone find's it usefull anyways.
What I did:
blacklist the new event modules for rc devices in /etc/modprobe.d/blacklist-rc.conf:
I also was used to hide the usb device from usbhid, but since there are other drivers for that device in the kernel, it's not necessary anymore, but if someone is using an older kernel without those event rc modules it might be usefull to create a file /etc/modprobe.d/usbhid-imon.conf with the following (maybe you have to adjust your usb-id, use lsusb -v):
next pass the right module options to lirc_imon in /etc/modprobe.d/lirc_imon.conf (the display_type 1 is vfd, ir_protocol 1 is RC-6):
install lirc:
in the package setup I chose
the resulting hardware.conf:
the lircd.conf I used:
By the way: Does anyone know why irrecord does not work with the imon devices?
Now I installed the old modules:
now a fast:
With the old lirc_imon driver lcdproc works without problems, no stall of xbmc to loss of contact to the display, as you can observe in syslog after a while.
using the old lirc modules wasn't a dead end at all, there was just a change in the ir-codes I can't explain, since everything (except the kernel) is almost the same. I stil got output with cat /dev/lirc0 | xxd so I tried other lircd.conf files
The following should not keep any suprises, but maybe someone find's it usefull anyways.
What I did:
blacklist the new event modules for rc devices in /etc/modprobe.d/blacklist-rc.conf:
Quote:blacklist rc_core
blacklist rc_imon_pad
blacklist imon
blacklist ir_lirc_codec
blacklist ir_sony_decoder
blacklist ir_jvc_decoder
blacklist ir_rc6_decoder
blacklist ir_rc5_decoder
blacklist ir_nec_decoder
I also was used to hide the usb device from usbhid, but since there are other drivers for that device in the kernel, it's not necessary anymore, but if someone is using an older kernel without those event rc modules it might be usefull to create a file /etc/modprobe.d/usbhid-imon.conf with the following (maybe you have to adjust your usb-id, use lsusb -v):
Quote:options usbhid quirks=0x15c2:0x0036:0x0004
next pass the right module options to lirc_imon in /etc/modprobe.d/lirc_imon.conf (the display_type 1 is vfd, ir_protocol 1 is RC-6):
Quote:options lirc_imon display_type=1 ir_protocol=1
install lirc:
Quote:aptitude install lirc
in the package setup I chose
Quote:Remote Control configuration: Soundgraph iMON IR/LCD
IR transmitter, if present: None
the resulting hardware.conf:
Quote:# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Soundgraph iMON IR/LCD"
REMOTE_MODULES="lirc_dev lirc_imon"
REMOTE_DRIVER=""
REMOTE_DEVICE="/dev/lirc0"
REMOTE_SOCKET=""
# I don't know why a cfg file is given here, I think it's ignored
# maye its used if /etc/lirc/lircd.conf doesn't exist
REMOTE_LIRCD_CONF="imon/lircd.conf.imon"
REMOTE_LIRCD_ARGS=""
#Chosen IR Transmitter
TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_SOCKET=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""
#Enable lircd
START_LIRCD="true"
#Don't start lircmd even if there seems to be a good config file
START_LIRCMD="false"
#Try to load appropriate kernel modules
LOAD_MODULES="true"
# Default configuration files for your hardware if any
LIRCMD_CONF=""
#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"
the lircd.conf I used:
Quote:begin remoteThe first codes are the ones I used to get from my remote, the second set are the codes I get now and I don't have a clue why the changed. As you can see: They're almost the same, except the trailing 00002ae or 00000000 at the end.
name OrigenAE_via_iMON
bits 64
eps 30
aeps 100
one 0 0
zero 0 0
gap 139998
ignore_mask 0x0000800000000fff
min_repeat 1
toggle_bit 0
begin codes
KEY_POWER 0x800f040c000002ae
KEY_STOP 0x800f8419000002ae
KEY_RECORD 0x800f0417000002ae
KEY_PAUSE 0x800f8418000002ae
KEY_PLAY 0x800f0416000002ae
KEY_REWIND 0x800f8415000002ae
KEY_FASTFORWARD 0x800f0414000002ae
KEY_PREVIOUS 0x800f841b000002ae
KEY_NEXT 0x800f041a000002ae
KEY_BACK 0x0200002a00000000
KEY_INFO 0x800f040f000002ae
KEY_UP 0x0200005200000000
KEY_LEFT 0x0200005000000000
KEY_OK 0x0200002800000000 # OK -- same code as KEY_ENTER
KEY_RIGHT 0x0200004f00000000
KEY_DOWN 0x0200005100000000
KEY_VOLUMEUP 0x800f0410000002ae
KEY_VOLUMEDOWN 0x800f8411000002ae
KEY_MENU 0x800f040d000002ae # Big ugly windows logo
KEY_CHANNELUP 0x800f0412000002ae
KEY_CHANNELDOWN 0x800f8413000002ae
KEY_MUTE 0x800f840e000002ae
KEY_PVR 0x800f0448000002ae
KEY_DVD 0x800f8424000002ae
KEY_EPG 0x800f0426000002ae
KEY_TV 0x800f8425000002ae
KEY_NUMERIC_1 0x0200001e00000000
KEY_NUMERIC_2 0x0200001f00000000
KEY_NUMERIC_3 0x0200002000000000
KEY_NUMERIC_4 0x0200002100000000
KEY_NUMERIC_5 0x0200002200000000
KEY_NUMERIC_6 0x0200002300000000
KEY_NUMERIC_7 0x0200002400000000
KEY_NUMERIC_8 0x0200002500000000
KEY_NUMERIC_9 0x0200002600000000
KEY_NUMERIC_STAR 0x0220002500000000
KEY_NUMERIC_0 0x0200002700000000
KEY_NUMERIC_POUND 0x0220002000000000
KEY_DELETE 0x0200002900000000
KEY_ENTER 0x0200002800000000
KEY_TEXT 0x800f845a000002ae
KEY_RED 0x800f845b000002ae
KEY_GREEN 0x800f845c000002ae
KEY_YELLOW 0x800f845d000002ae
KEY_BLUE 0x800f845e000002ae
end codes
end remote
begin remote
name MCE_via_iMON_ffdc
bits 32
eps 30
aeps 100
one 0 0
zero 0 0
gap 203992
toggle_bit_mask 0x8000
begin codes
KEY_POWER 0x800f040c
KEY_STOP 0x800f8419
KEY_RECORD 0x800f0417
KEY_PAUSE 0x800f8418
KEY_PLAY 0x800f0416
KEY_REWIND 0x800f8415
KEY_FASTFORWARD 0x800f0414
KEY_PREVIOUS 0x800f841b
KEY_NEXT 0x800f041a
KEY_BACK 0x0200002a
KEY_INFO 0x800f040f
KEY_UP 0x02000052
KEY_LEFT 0x02000050
KEY_OK 0x02000028 # OK -- same code as KEY_ENTER
KEY_RIGHT 0x0200004f
KEY_DOWN 0x02000051
KEY_VOLUMEUP 0x800f0410
KEY_VOLUMEDOWN 0x800f8411
KEY_MENU 0x800f040d # Big ugly windows logo
KEY_CHANNELUP 0x800f0412
KEY_CHANNELDOWN 0x800f8413
KEY_MUTE 0x800f840e
KEY_PVR 0x800f0448
KEY_DVD 0x800f8424
KEY_EPG 0x800f0426
KEY_TV 0x800f8425
KEY_NUMERIC_1 0x0200001e
KEY_NUMERIC_2 0x0200001f
KEY_NUMERIC_3 0x02000020
KEY_NUMERIC_4 0x02000021
KEY_NUMERIC_5 0x02000022
KEY_NUMERIC_6 0x02000023
KEY_NUMERIC_7 0x02000024
KEY_NUMERIC_8 0x02000025
KEY_NUMERIC_9 0x02000026
KEY_NUMERIC_STAR 0x02200025
KEY_NUMERIC_0 0x02000027
KEY_NUMERIC_POUND 0x02200020
KEY_DELETE 0x02000029
KEY_ENTER 0x02000028
KEY_TEXT 0x800f845a
KEY_RED 0x800f845b
KEY_GREEN 0x800f845c
KEY_YELLOW 0x800f845d
KEY_BLUE 0x800f845e
end codes
end remote
By the way: Does anyone know why irrecord does not work with the imon devices?
Now I installed the old modules:
Quote:aptitude install lirc-modules-sourceat this point dkms refuses to install lirc_imon since the kernel version is newer. Thats right, but it doesn't support my imon display anymore, so I forced the installation:
Quote:dkms uninstall -m lirc -v 0.8.7
dkms install -m lirc -v 0.8.7 --force
now a fast:
Quote:depmod -ato ensure that all modifications to the module config will be considered
update-initramfs -u
With the old lirc_imon driver lcdproc works without problems, no stall of xbmc to loss of contact to the display, as you can observe in syslog after a while.
