On Mon, 2010-03-29 at 07:20 -0600, James Grossmann wrote: > On Sun, Mar 28, 2010 at 6:18 AM, Andy Walls <[email protected]> wrote: > > On Sat, 2010-03-27 at 15:59 -0600, James Grossmann wrote: > >> On Sat, Mar 27, 2010 at 2:02 PM, Andy Walls <[email protected]> > >> wrote: > >> > On Sat, 2010-03-27 at 13:28 -0600, James Grossmann wrote: > >> >> I'm now running into some more fun, I don't seem to be connecting > >> >> correctly with the lircd daemon, I have downloaded the "firmware" from > >> >> http://www.blushingpenguin.com/mark/lmilk/haup-ir-blaster.bin and put > >> >> Mike's lircd.conf for the blaster in, I get numerous errors when I run > >Cantata Practice> >> lircd -n -d /dev/lirc(0 or 1) of the type: > >> >> lircd-0.8.6[13604]: error in configfile line 30924: > >> >> lircd-0.8.6[13604]: "2195390500" is out of range > >> >> lircd-0.8.6[13604]: error in configfile line 30926: > >> >> lircd-0.8.6[13604]: "2195390501" is out of range > >> >> lircd-0.8.6[13604]: error in configfile line 30928: > >> >> lircd-0.8.6[13604]: "2195390502" is out of range > >> >> lircd-0.8.6[13604]: error in configfile line 30930: > >> >> lircd-0.8.6[13604]: "2195390505" is out of range > >> >> lircd-0.8.6[13604]: error in configfile line 30932: > >> >> lircd-0.8.6[13604]: "2195390511" is out of range > >> >> lircd-0.8.6[13604]: error in configfile line 30934: > >> >> lircd-0.8.6[13604]: "2195390512" is out of range > >> >> lircd-0.8.6[13604]: error in configfile line 30936: > >> >> lircd-0.8.6[13604]: "2195390513" is out of range > >> >> lircd-0.8.6[13604]: error in configfile line 30938: > >> >> lircd-0.8.6[13604]: "2195390514" is out of range > >> >> lircd-0.8.6[13604]: error in configfile line 30940: > >> >> lircd-0.8.6[13604]: "2195390515" is out of range > >> >> lircd-0.8.6[13604]: error in configfile line 30942: > >> >> lircd-0.8.6[13604]: "2195390541" is out of range > >> >> lircd-0.8.6[13604]: error in configfile line 30944: > >> >> lircd-0.8.6[13604]: "2195390542" is out of range > >> >> and then it ends: > >> >> lircd-0.8.6[13604]: lircd(default) ready, using /var/run/lirc/lircd > >> >> > >> >> I have the feeling that everything in the lircd.conf has been > >> >> essentially thrown out. When I load the lirc_zilog module with > >> >> debug=1, I get indications in dmesg that the hauppauge remote is being > >> >> received, but irw doesn't output anything > >> >> I do note that the lirc package installed from ubuntu's repositories > >> >> doesn't list the zilog remote as a valid remote (when I type lircd > >> >> --device=help, it lists everything else), but from what I can tell, > >> >> that shouldn't necessarily be a problem, others are working with an > >> >> unpatched lirc install, while using the patched lirc-modules-source > >> >> package. > >> >> Jarod if you're on this list, or anybody else who can point me in the > >> >> right direction, PLEASE, there must be an easier way! > >> >
> >> > BTW, forget about LIRC for the moment. With all the lirc modules > >> > unloaded, load the ir_kbd_i2c module. Does it recognize the HVR-1600's > >> > IR and in a terminal window do remote button pushes (like the buttons > >> > 0-9) get input as key presses? >> > > >> > >> Thanks, Andy, > >> It seems almost to be working, but I'm having great difficulty getting > >> that last inch to the finish. The details available on the internet > >> are pretty sketchy--at least to me. I would say that the modules work > >> fine, but that I'm getting a conflict between the module and the lircd > >> program, or I've got something configured wrong...anyway, I'd really > >> like to get the ir blaster working, it seems so close... > >> About the ir_kbd_i2c module, it inserts fine, however, I do not get > >> any input at a terminal. This is the dmesg output: > >> > >> [27334.864527] input: i2c IR (Hauppauge HVR-1600) as > >> /devices/virtual/irrcv/irrcv0/input7 > >> [27334.864740] irrcv0: i2c IR (Hauppauge HVR-1600) as > >> /devices/virtual/irrcv/irrcv0 > >> [27334.864747] ir-kbd-i2c: i2c IR (Hauppauge HVR-1600) detected at > >> i2c-2/2-0071/ir0 [cx18 i2c driver #0-0] > > > > OK. It looks like the HVR-1600's IR chip is getting registered as an > > input device - i.e. like a keyboard. > > > > If the digit buttons aren't giving you keypresses, it might be due to > > something in the cx18 driver or Mauro's recent IR changes. Let's get > > this working first. There's not point in trying to get LIRC working, > > until the very basic I2C communications from the CX23418 to the Z8 > > microcontroller are working. I'll try to test mine on a Fedora 12 > > system later today. > > > > What kernel version, cx18 driver version, and distribution are you > > using? > > > I'm running Ubuntu Server using the mainline kernel 2.6.33, In order > to compile the http://www.linuxtv.org/hg/v4l-dvb tip.tar.bz2, the > current version I am using is v4l-dvb-640ed513e03a, wherein the cx18 > driver cx18_version.h says 1.4.0. Last night I had time to try this on my Fedora 12 system (kernel 2.6.32) with a v4l-dvb tree I cloned last night. The ir-kbd-i2c module with the cx18 module works fine with my HVR-1600 and Hauppauge remote for IR receive. Some simple thing for you to try: 1. Check the IR receveir transmitter cable. Twice in the past I myself have failed to push it in the socket all the way. IR will not work without the cable pushed into the socket fully. 2. Load the ir-kbd-i2c module with the debug=2 option. That will give you verbose debugging on IR keypresses from the microcontroller, even if they fail to make it to the input subsystem and show up on the screen. 3. With the modules loaded, use cx18-ctl (from the v4l-apps in the source tree) to reset the IR microcontroller: $ cx18-ctl -d /dev/video0 --reset 1 and see if it starts responding. 4. Look under /lib/modules for duplicates of the cx18.ko and ir-kbd-i2c.ko and other ir related modules. There was a time (and maybe there still is), when Ubuntu had modules in a non-standard location that the v4l-dvb build system didn't know about. In other words, make sure you're not loading older modules or mixing modules. Regards, Andy _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
