After upgrading to lirc-0.7.0-r1, it just plain stops working. Its unable to receive any signals from my remote control at all. I am using a Hauppauge remote using the devinput LIRC driver under Linux 2.6.10. Simply downgrading to 0.7.0_pre3 solves the problem. Reproducible: Always Steps to Reproduce: 1. Use a hauppauge remote using the devinput lirc driver 2. upgrade to lirc-0.7.0-r1 3. try to use the remote Actual Results: remote did not work Expected Results: should have worked Portage 2.0.51-r15 (!/usr/portage/profiles/default-linux/x86/2004.0, gcc-3.3.5,glibc-2.3.4.20040808-r1, 2.6.10-ac12 i686) ================================================================= System uname: 2.6.10-ac12 i686 AMD Athlon(tm) MP 2200+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Oct 16 2004, 23:23:41)] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r1, 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-mp -O2 -fomit-frame-pointer -s -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config/usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /usr/X11R6/lib/X11/xkb /usr/X11R6/lib/X11/xkb/compat /usr/X11R6/lib/X11/xkb/geometry /usr/X11R6/lib/X11/xkb/keycodes /usr/X11R6/lib/X11/xkb/keymap /usr/X11R6/lib/X11/xkb/rules /usr/X11R6/lib/X11/xkb/symbols /usr/X11R6/lib/X11/xkb/symbols/macintosh /usr/X11R6/lib/X11/xkb/symbols/pc /etc/env.d" CXXFLAGS="-march=athlon-mp -O2 -fomit-frame-pointer -s -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/slug/usr/portage" PORTDIR_OVERLAY="/usr/slug/usr/local/portage" SYNC="rsync://jove.eng.yale.edu/gentoo-portage" USE="x86 3dnow X acpi aim alsa apache2 avi berkdb bitmap-fonts cdr crypt divx4linux dvd encode f77 fam flac font-server foomaticdb fortran gdbm gif gphoto2 gpmgtk gtk2 icq imagemagick imlib ipv6 java joystick jpeg kde libg++ libwww lirc mad mikmod mmx motif mozilla mpeg mysql ncurses nls nptl offensive oggvorbis opengl oss pam pdflib perl png python qt quicktime readline real samba sdl slang spell sse ssl svga tcpd tiff truetype truetype-fonts type1-fonts usb v4l v4l2 videos xml2 xmms xosd xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
maybe the device is not correctly set in /etc/conf.d/lirc?
i remember that it changed during the development of 0.7
dogshu@delta-9 conf.d $ pwd /etc/conf.d dogshu@delta-9 conf.d $ cat lircd # Options to pass to the lircd process LIRCD_OPTS="-d /dev/input/event0" dogshu@delta-9 conf.d $ That looks right to me. I don't use any LIRC kernel patches, so I don't understand why the device would change when upgrading LIRC and not the kernel. Any idea what I should change it to?
Well, here the correct device is LIRCD_OPTS="-d /dev/lirc0"
/dev/lircd doesn't seem to work, irexec and irw say "Connection refused", and this shows up in my /var/log/messages: Feb 20 12:42:17 delta-9 0.7.0[7973]: accepted new client on /dev/lircd Feb 20 12:42:17 delta-9 0.7.0[7973]: initializing '/dev/lircd' Feb 20 12:42:17 delta-9 0.7.0[7973]: unable to open '/dev/lircd' When the device is set to /dev/input/event0 lircd starts up correctly: Feb 20 12:46:34 delta-9 0.7.0[8385]: lircd(devinput) ready Feb 20 12:46:37 delta-9 0.7.0[8385]: accepted new client on /dev/lircd However, neither irw or irexec ever receive any input when I try to use my remote. As before, downgrading to lirc-0.7.0_pre3 solves the problem. Here's what irw prints when I press the "TV" button under 0.7.0_pre3: 0000000000010179 00 KEY_TV Hauppauge I'll post some of my configuration files in case that helps to figure out what's happening here. I have this line in my make.conf: LIRC_OPTS="--with-driver=devinput" and here is my lircd.conf: begin remote name Hauppauge begin codes KEY_0 0x00010052 KEY_1 0x0001004f KEY_2 0x00010050 KEY_3 0x00010051 KEY_4 0x0001004b KEY_5 0x0001004c KEY_6 0x0001004d KEY_7 0x00010047 KEY_8 0x00010048 KEY_9 0x00010049 KEY_MUTE 0x00010071 KEY_VOLUMEUP 0x00010073 KEY_VOLUMEDOWN 0x00010072 KEY_RESERVED 0x000100d9 KEY_MINIMIZE 0x0001008e KEY_RADIO 0x00010074 KEY_TV 0x00010179 KEY_CHANNELUP 0x00010192 KEY_CHANNELDOWN 0x00010193 KEY_CHANNEL 0x0001016b KEY_ZOOM 0x0001008b end codes end remote
Sorry, I misread your post. /dev/lirc0 doesn't exist on my system: delta-9 root # ls -al /dev/lirc* srw-rw-rw- 1 root root 0 Feb 20 12:50 /dev/lircd delta-9 root # And it does not appear to work either: Feb 20 12:59:11 delta-9 0.7.0[26446]: lircd(devinput) ready Feb 20 12:59:28 delta-9 0.7.0[26446]: accepted new client on /dev/lircd Feb 20 12:59:28 delta-9 0.7.0[26446]: initializing '/dev/lirc0' Feb 20 12:59:28 delta-9 0.7.0[26446]: unable to open '/dev/lirc0' irw and irexec both say "connection refused".
I finally figured it out! After looking around for a while, I found this post: http://sourceforge.net/mailarchive/message.php?msg_id=10159895 I added "bits 32" to my lircd.conf, so now it looks like this: begin remote name Hauppauge bits 32 begin codes KEY_0 0x00010052 KEY_1 0x0001004f KEY_2 0x00010050 KEY_3 0x00010051 KEY_4 0x0001004b KEY_5 0x0001004c KEY_6 0x0001004d KEY_7 0x00010047 KEY_8 0x00010048 KEY_9 0x00010049 KEY_MUTE 0x00010071 KEY_VOLUMEUP 0x00010073 KEY_VOLUMEDOWN 0x00010072 KEY_RESERVED 0x000100d9 KEY_MINIMIZE 0x0001008e KEY_RADIO 0x00010074 KEY_TV 0x00010179 KEY_CHANNELUP 0x00010192 KEY_CHANNELDOWN 0x00010193 KEY_CHANNEL 0x0001016b KEY_ZOOM 0x0001008b end codes end remote And it works! All of the buttons on my remote are being recognized again.
FYI I consider this problem to be fixed... it was a configuration issue as you can see from my previous post.