imon driver (or IT87 driver) does not work, irw crashes lircd

[Jacob Jarick]

Binary package hint: lirc

Description: Ubuntu 8.10
Release: 8.10
lirc 0.8.3-0ubuntu2 Linux Infra-red Remote Control support

oot@mediapc:~# dmesg | grep imon
[ 334.839718] lirc_imon: Driver for Soundgraph iMON MultiMedia IR/VFD w/imon pad2keys patch, v0.3p2k
[ 334.839733] lirc_imon: Venky Raju <email address hidden>
[ 334.841034] usbcore: registered new interface driver lirc_imon

root@mediapc:~# lsmod | grep lirc
lirc_imon 23052 0
lirc_dev 20020 1 lirc_imon
usbcore 148848 7 lirc_imon,usbhid,usb_storage,libusual,ohci_hcd,ehc i_hcd

When I run irw it simply exits the 1st time without any message, the second time it errors and the lirc daemon crashes.

root@mediapc:~# /etc/init.d/lirc restart
* Stopping remote control daemon(s): LIRC [ OK ]
* Loading LIRC modules [ OK ]
* Starting remote control daemon(s) : LIRC [ OK ]
root@mediapc:~# irw
root@mediapc:~# irw
connect: Connection refused
root@mediapc:~# /etc/init.d/lirc restart
* Stopping remote control daemon(s): LIRC [fail]
* Loading LIRC modules [ OK ]
* Starting remote control daemon(s) : LIRC [ OK ]
I do not have a /dev/lirc0 but I do have /dev/lircd.
Running irw /dev/lircd does not help.

Mode 2 errors:

root@mediapc:~# mode2
mode2: error opening /dev/lirc
mode2: No such file or directory

[zcrar70 (eliemedeiros)]

I have exactly the same issue. I'm also using Ubuntu 8.10 (the 64 bit version). I've found that the error occurs because /dev/lirc0 doesn't exist:

welles@rosebud:~$ sudo /etc/init.d/lirc restart
 * Stopping remote control daemon(s): LIRC [ OK ]
 * Loading LIRC modules [ OK ]
 * Starting remote control daemon(s) : LIRC [ OK ]
welles@rosebud:~$ irw
welles@rosebud:~$ irw
connect: Connection refused
welles@rosebud:~$ tail /var/log/syslog
Jan 24 16:16:25 rosebud lircd-0.8.3[13618]: caught signal
Jan 24 16:16:25 rosebud lircd-0.8.3[15018]: lircd(userspace) ready
Jan 24 16:16:28 rosebud lircd-0.8.3[15018]: accepted new client on /dev/lircd
Jan 24 16:16:28 rosebud lircd-0.8.3[15018]: could not get file information for /dev/lirc0
Jan 24 16:16:28 rosebud lircd-0.8.3[15018]: default_init(): No such file or directory
Jan 24 16:16:28 rosebud lircd-0.8.3[15018]: caught signal
welles@rosebud:~$

I'm using an Imon VFD / IR receiver. Output from lsusb:

welles@rosebud:~$ lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 15c2:0038 SoundGraph Inc.
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Output from lsmod (note that the lirc_imon module is loaded):

lirc_imon 25996 0
lirc_mceusb2 21764 0
lirc_dev 22216 2 lirc_imon,lirc_mceusb2
usbcore 175376 6 lirc_imon,lirc_mceusb2,usbhid,ohci_hcd,ehci

Any help greatly appreciated -

[Jacob Jarick (mem-namefix)]

I wouldnt wait for any ubuntu dev's to help mate, they dont actually do any coding they just compile the package and their done. Ive been through a similar issue with ubuntu before and your 2 best choices are to buy different hardware or swap to another Distro.

Im going to be using anyremote with a usb bluetooth adaptor to get this HTPC up and running.

[aschuring (aelschuring)]

Several Soundgraph iMon models are only supported since lirc 0.8.4, which is included in 9.04 (Jaunty). You could try using intrepid-backports, but I'm not sure if the kernel modules are backported as well. I'm currently using a pre-release of lirc 0.8.5, but my device gets recognized correctly:

root@satyr:/etc/init.d# dmesg | grep -i imon
[ 30.264999] Driver for Soundgraph iMON MultiMedia IR/Display, v0.5
[ 30.265028] imon_probe: found iMON device
[ 30.265086] imon_probe: Registered iMON driver(minor:0)
[ 30.265123] imon_probe: iMON device on usb<9:3> initialized
[ 30.265131] imon_probe: found iMON device
[ 30.265158] imon_probe: Registered iMON driver(minor:1)
[ 30.265179] imon_probe: iMON device on usb<9:3> initialized
[ 30.265192] usbcore: registered new interface driver lirc_imon

I also had to use a small patch to the init script to fix stability issues in lirc (it would sometimes stop responding after a while). I'll attach it, but it should not be necessary and I haven't yet figured out why it solves my problems.

[herrmidnquer (wac071083-launchpad)]

okay, in my opinion the patch your have applied, is handling the case when you have 2 infrared receivers installed

maybe a onboard ir-receiver on your tv-tuner

[aschuring (aelschuring)]

@herrmidnquer: actually, several Soundgraph remotes (including the -PAD models) register themselves as two separate modules (see minor:0 and minor:1 in my log above). One is the "normal" remote function, and the other is the "pad" - a mouse-like input device with movement keys and buttons, controlled from the same remote.

[Julien Valgrès (julien-valgres)]

Hello,

I have the same problem with IT87 driver (built-in IR chipset), i can't control my remote on my ASUS P4-P5N9300. I have try with different kernel. irw crash.

I use Ubuntu 10.10 whith kernel 2.6.36-020636-generic found at http://www.ramoonus.nl/2010/10/linux-kernel-2-6-36-installation-guide-ubuntu-linux/

whith kernel 2.6.35 xxxx i have the same problem.

julien@julien-desktop:~$ sudo /etc/init.d/lirc restart
[sudo] password for julien:
 * Stopping remote control daemon(s): LIRC [ OK ]
 * Loading LIRC modules [ OK ]
 * Starting remote control daemon(s) : LIRC [ OK ]
julien@julien-desktop:~$ dmesg | grep lirc
[ 22.105355] lirc_dev: IR Remote Control driver registered, major 61
[ 22.229875] lirc_dev: lirc_register_driver: sample_rate: 0
[ 22.229970] lirc_it87: found IT8720.
[ 22.229986] lirc_it87: set default io 0x310
[ 22.230001] lirc_it87: set default irq 0xb
[ 22.230039] lirc_it87: I/O port 0x0310, IRQ 11.
[ 22.230049] lirc_it87: Installed.

dmesg look like ok

julien@julien-desktop:~$ irw
julien@julien-desktop:~$ irw
connect: Connection refused

after launching irw there is some changes:

julien@julien-desktop:~$ dmesg | grep lirc
[ 22.105355] lirc_dev: IR Remote Control driver registered, major 61
[ 22.229875] lirc_dev: lirc_register_driver: sample_rate: 0
[ 22.229970] lirc_it87: found IT8720.
[ 22.229986] lirc_it87: set default io 0x310
[ 22.230001] lirc_it87: set default irq 0xb
[ 22.230039] lirc_it87: I/O port 0x0310, IRQ 11.
[ 22.230049] lirc_it87: Installed.
[ 1619.568660] IP: [<f807348b>] irctl_ioctl+0x2b/0x310 [lirc_dev]
[ 1619.568679] last sysfs file: /sys/module/lirc_it87/initstate
[ 1619.568683] Modules linked in: xt_limit xt_tcpudp ipt_LOG ipt_MASQUERADE xt_DSCP ipt_REJECT nf_conntrack_irc nf_conntrack_ftp xt_state 8712u snd_seq_dummy aes_i586 aes_generic binfmt_misc vboxnetadp vboxnetflt vboxdrv lirc_it87 lirc_dev parport_pc ppdev iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_mangle iptable_filter ip_tables snd_hda_codec_nvhdmi snd_hda_codec_realtek x_tables snd_hda_intel snd_hda_codec nvidia(P) snd_hwdep snd_pcm hwmon_vid snd_seq_midi snd_rawmidi coretemp snd_seq_midi_event snd_seq snd_timer snd_seq_device ircomm_tty ircomm snd i2c_nforce2 psmouse irda crc_ccitt soundcore video snd_page_alloc output asus_atk0110 agpgart shpchp lp joydev serio_raw parport raid10 raid456 async_raid6_recov async_pq hid_logitech ff_memless usbhid hid raid6_pq async_xor ahci firewire_ohci r8169 xor sdhci_pci async_memcpy firewire_core libahci async_tx sdhci mii crc_itu_t led_class raid1 raid0 multipath linear
[ 1619.568779] Pid: 3220, comm: lircd Tainted: P 2.6.36-020636-generic #201010210905 P-P5N9300/System Product Name
[ 1619.568788] EIP is at irctl_ioctl+0x2b/0x310 [lirc_dev]
[ 1619.568801] Process lircd (pid: 3220, ti=f5e6e000 task=ee276580 task.ti=f5e6e000)
[ 1619.568848] [<f8073460>] ? irctl_ioctl+0x0/0x310 [lirc_dev]
[ 1619.568925] EIP: [<f807348b>] irctl_ioctl+0x2b/0x310 [lirc_dev] SS:ESP 0068:f5e6ff4c
julien@julien-desktop:~$

[Julien Valgrès (julien-valgres)]

just after this:

julien@julien-desktop:~$ sudo /etc/init.d/lirc restart
 * Stopping remote control daemon(s): LIRC [fail]
 * Loading LIRC modules [ OK ]
 * Starting remote control daemon(s) : LIRC [ OK ]
julien@julien-desktop:~$

and "dmesg | grep lirc" haven't changed.

[Alec Leamas (leamas-alec)]

The last note in this bug is five years old, end both the kernel and lirc startup sequence is heavily changed. Could you please test this bug on upcoming zesty and lirc0.9.4c if you are still interested in this bug?

Setting status to Incomplete, since without input on status on current code we cannot triage this bug.

When testing, the primary test tool is mode2 - using that with correct --driver and --device should reveal if this problem in in the kernel or in lircd. Please also raise the lircd loglevel to 'trace' and submit the lircd logs.

[Launchpad Janitor (janitor)]

[Expired for lirc (Ubuntu) because there has been no activity for 60 days.]