Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: ivtv: users

recent work with HVR-1600 irblaster?

 

 

ivtv users RSS feed   Index | Next | Previous | View Threaded


cctsurf at gmail

Mar 26, 2010, 8:17 PM

Post #1 of 13 (4223 views)
Permalink
recent work with HVR-1600 irblaster?

I see some really old work with the lirc_zilog / lirc_pvr150 drivers,
http://www.blushingpenguin.com/mark/blog/?p=24 is especially nice,
however, the kernel options are fairly limited. Is there anything
newer available? I have been using the v4l-dvb drivers in order to
have the best possible digital cable (qam256), however, they don't
seem to compile anymore against the 2.6.31 kernel that Ubuntu Karmic
ships with. Therefore I have been using the generic 2.6.33 kernels
available. Recently, I moved to Dish Network, and I need a irblaster
to control the receiver, so I'm looking for modern options for that.
I suppose I don't need those modules any more, but I'd really prefer
not to go back. Thanks
James

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


cctsurf at gmail

Mar 26, 2010, 9:56 PM

Post #2 of 13 (4111 views)
Permalink
Re: recent work with HVR-1600 irblaster? [In reply to]

Notably, one website seems to be the answer to all of my questions here;
Jarod is the one who has been keeping the lirc_zilog driver up, and he
writes about it here: http://wilsonet.com/?cat=11
I'll be testing it tomorrow, I'll post the results.
Thanks again,
James

On Fri, Mar 26, 2010 at 9:17 PM, James Grossmann <cctsurf [at] gmail> wrote:
> I see some really old work with the lirc_zilog / lirc_pvr150 drivers,
> http://www.blushingpenguin.com/mark/blog/?p=24 is especially nice,
> however, the kernel options are fairly limited.  Is there anything
> newer available?  I have been using the v4l-dvb drivers in order to
> have the best possible digital cable (qam256), however, they don't
> seem to compile anymore against the 2.6.31 kernel that Ubuntu Karmic
> ships with.  Therefore I have been using the generic 2.6.33 kernels
> available.  Recently, I moved to Dish Network, and I need a irblaster
> to control the receiver, so I'm looking for modern options for that.
> I suppose I don't need those modules any more, but I'd really prefer
> not to go back.    Thanks
> James
>

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


cctsurf at gmail

Mar 26, 2010, 11:33 PM

Post #3 of 13 (4112 views)
Permalink
Re: recent work with HVR-1600 irblaster? [In reply to]

Might I ask someone how to build this as a module? I have figured out
how to build as a .o, but not as a .ko
Thanks,
James

On Fri, Mar 26, 2010 at 10:56 PM, James Grossmann <cctsurf [at] gmail> wrote:
> Notably, one website seems to be the answer to all of my questions here;
> Jarod is the one who has been keeping the lirc_zilog driver up, and he
> writes about it here:  http://wilsonet.com/?cat=11
> I'll be testing it tomorrow, I'll post the results.
> Thanks again,
> James
>
> On Fri, Mar 26, 2010 at 9:17 PM, James Grossmann <cctsurf [at] gmail> wrote:
>> I see some really old work with the lirc_zilog / lirc_pvr150 drivers,
>> http://www.blushingpenguin.com/mark/blog/?p=24 is especially nice,
>> however, the kernel options are fairly limited.  Is there anything
>> newer available?  I have been using the v4l-dvb drivers in order to
>> have the best possible digital cable (qam256), however, they don't
>> seem to compile anymore against the 2.6.31 kernel that Ubuntu Karmic
>> ships with.  Therefore I have been using the generic 2.6.33 kernels
>> available.  Recently, I moved to Dish Network, and I need a irblaster
>> to control the receiver, so I'm looking for modern options for that.
>> I suppose I don't need those modules any more, but I'd really prefer
>> not to go back.    Thanks
>> James
>>
>

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


cctsurf at gmail

Mar 27, 2010, 6:55 AM

Post #4 of 13 (4110 views)
Permalink
Re: recent work with HVR-1600 irblaster? [In reply to]

Once again, I seem to be answering my own questions, the build code is
as follows (modify for your own distro)
$ make CONFIG_INPUT_LIRC=m CONFIG_LIRC_ZILOG=m -C
/usr/src/kernels/$(uname -r) M=$PWD modules

On Sat, Mar 27, 2010 at 12:33 AM, James Grossmann <cctsurf [at] gmail> wrote:
> Might I ask someone how to build this as a module?  I have figured out
> how to build as a .o, but not as a .ko
> Thanks,
> James
>
> On Fri, Mar 26, 2010 at 10:56 PM, James Grossmann <cctsurf [at] gmail> wrote:
>> Notably, one website seems to be the answer to all of my questions here;
>> Jarod is the one who has been keeping the lirc_zilog driver up, and he
>> writes about it here:  http://wilsonet.com/?cat=11
>> I'll be testing it tomorrow, I'll post the results.
>> Thanks again,
>> James
>>
>> On Fri, Mar 26, 2010 at 9:17 PM, James Grossmann <cctsurf [at] gmail> wrote:
>>> I see some really old work with the lirc_zilog / lirc_pvr150 drivers,
>>> http://www.blushingpenguin.com/mark/blog/?p=24 is especially nice,
>>> however, the kernel options are fairly limited.  Is there anything
>>> newer available?  I have been using the v4l-dvb drivers in order to
>>> have the best possible digital cable (qam256), however, they don't
>>> seem to compile anymore against the 2.6.31 kernel that Ubuntu Karmic
>>> ships with.  Therefore I have been using the generic 2.6.33 kernels
>>> available.  Recently, I moved to Dish Network, and I need a irblaster
>>> to control the receiver, so I'm looking for modern options for that.
>>> I suppose I don't need those modules any more, but I'd really prefer
>>> not to go back.    Thanks
>>> James
>>>
>>
>

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


cctsurf at gmail

Mar 27, 2010, 12:28 PM

Post #5 of 13 (4102 views)
Permalink
Re: recent work with HVR-1600 irblaster? [In reply to]

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
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!
Thanks
James

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


awalls at md

Mar 27, 2010, 1:02 PM

Post #6 of 13 (4117 views)
Permalink
Re: recent work with HVR-1600 irblaster? [In reply to]

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
> 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!

There is active discussion of linux IR on linux-media [at] vger
and linux-kernel [at] vger and linux-input [at] vger . There
is also a lirc list on sourceforge somewhere.

In summary, changes are being implemented to get IR Rx mostly in kernel,
and lirc-dev in kernel as well. IR Tx will still be handled by lirc
userspace.

The I2C subsytem changes broke what used to work, and Jarrod should have
updated lirc and the lirc modules to handle it.

There are some things I wanted to get fixed as well, but I just haven't
had the time.



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?


Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


cctsurf at gmail

Mar 27, 2010, 2:59 PM

Post #7 of 13 (4097 views)
Permalink
Re: recent work with HVR-1600 irblaster? [In reply to]

On Sat, Mar 27, 2010 at 2:02 PM, Andy Walls <awalls [at] md> 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
>> 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!
>
> There is active discussion of linux IR on linux-media [at] vger
> and linux-kernel [at] vger and linux-input [at] vger . There
> is also a lirc list on sourceforge somewhere.
>
> In summary, changes are being implemented to get IR Rx mostly in kernel,
> and lirc-dev in kernel as well.  IR Tx will still be handled by lirc
> userspace.
>
> The I2C subsytem changes broke what used to work, and Jarrod should have
> updated lirc and the lirc modules to handle it.
>
> There are some things I wanted to get fixed as well, but I just haven't
> had the time.
>
>
>
> 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?
>
>
> Regards,
> Andy
>
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

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]

I attempted to cat the device /etc/input/event6 (which is what
/proc/bus/input/devices noted was the Handler), but nothing
Here is the associated part of /proc/bus/input/devices:
I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="i2c IR (Hauppauge HVR-1600)"
P: Phys=i2c-2/2-0071/ir0
S: Sysfs=/devices/virtual/irrcv/irrcv0/input8
U: Uniq=
H: Handlers=kbd event6
B: EV=100003
B: KEY=100fc312 214a802 0 0 0 0 18000 41a8 4801 9e1680 0 0 10000ffc

Thanks,
James

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


awalls at md

Mar 28, 2010, 5:18 AM

Post #8 of 13 (4085 views)
Permalink
Re: recent work with HVR-1600 irblaster? [In reply to]

On Sat, 2010-03-27 at 15:59 -0600, James Grossmann wrote:
> On Sat, Mar 27, 2010 at 2:02 PM, Andy Walls <awalls [at] md> 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
> >> 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!
> >
> > There is active discussion of linux IR on linux-media [at] vger
> > and linux-kernel [at] vger and linux-input [at] vger . There
> > is also a lirc list on sourceforge somewhere.
> >
> > In summary, changes are being implemented to get IR Rx mostly in kernel,
> > and lirc-dev in kernel as well. IR Tx will still be handled by lirc
> > userspace.
> >
> > The I2C subsytem changes broke what used to work, and Jarrod should have
> > updated lirc and the lirc modules to handle it.
> >
> > There are some things I wanted to get fixed as well, but I just haven't
> > had the time.
> >
> >
> >
> > 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?
> >
> >
> > Regards,
> > Andy
> >
> >
> > _______________________________________________
> > ivtv-users mailing list
> > ivtv-users [at] ivtvdriver
> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
> >
>
> 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 attempted to cat the device /etc/input/event6 (which is what
> /proc/bus/input/devices noted was the Handler), but nothing

In my experience, that shouldn't be needed.

Regards,
Andy

> Here is the associated part of /proc/bus/input/devices:
> I: Bus=0018 Vendor=0000 Product=0000 Version=0000
> N: Name="i2c IR (Hauppauge HVR-1600)"
> P: Phys=i2c-2/2-0071/ir0
> S: Sysfs=/devices/virtual/irrcv/irrcv0/input8
> U: Uniq=
> H: Handlers=kbd event6
> B: EV=100003
> B: KEY=100fc312 214a802 0 0 0 0 18000 41a8 4801 9e1680 0 0 10000ffc
>
> Thanks,
> James



_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


cctsurf at gmail

Mar 29, 2010, 6:20 AM

Post #9 of 13 (4078 views)
Permalink
Re: recent work with HVR-1600 irblaster? [In reply to]

On Sun, Mar 28, 2010 at 6:18 AM, Andy Walls <awalls [at] md> wrote:
> On Sat, 2010-03-27 at 15:59 -0600, James Grossmann wrote:
>> On Sat, Mar 27, 2010 at 2:02 PM, Andy Walls <awalls [at] md> 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!
>> >
>> > There is active discussion of linux IR on linux-media [at] vger
>> > and linux-kernel [at] vger and linux-input [at] vger . There
>> > is also a lirc list on sourceforge somewhere.
>> >
>> > In summary, changes are being implemented to get IR Rx mostly in kernel,
>> > and lirc-dev in kernel as well.  IR Tx will still be handled by lirc
>> > userspace.
>> >
>> > The I2C subsytem changes broke what used to work, and Jarrod should have
>> > updated lirc and the lirc modules to handle it.
>> >
>> > There are some things I wanted to get fixed as well, but I just haven't
>> > had the time.
>> >
>> >
>> >
>> > 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?
>> >
>> >
>> > Regards,
>> > Andy
>> >
>> >
>> > _______________________________________________
>> > ivtv-users mailing list
>> > ivtv-users [at] ivtvdriver
>> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>> >
>>
>> 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.

>
>
>
>> I attempted to cat the device /etc/input/event6 (which is what
>> /proc/bus/input/devices noted was the Handler), but nothing
>
> In my experience, that shouldn't be needed.
>
> Regards,
> Andy
>
>> Here is the associated part of /proc/bus/input/devices:
>> I: Bus=0018 Vendor=0000 Product=0000 Version=0000
>> N: Name="i2c IR (Hauppauge HVR-1600)"
>> P: Phys=i2c-2/2-0071/ir0
>> S: Sysfs=/devices/virtual/irrcv/irrcv0/input8
>> U: Uniq=
>> H: Handlers=kbd event6
>> B: EV=100003
>> B: KEY=100fc312 214a802 0 0 0 0 18000 41a8 4801 9e1680 0 0 10000ffc
>>
>> Thanks,
>> James
>
>
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

Thank You!
James

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


awalls at md

Mar 30, 2010, 4:19 AM

Post #10 of 13 (4033 views)
Permalink
Re: recent work with HVR-1600 irblaster? [In reply to]

On Mon, 2010-03-29 at 07:20 -0600, James Grossmann wrote:
> On Sun, Mar 28, 2010 at 6:18 AM, Andy Walls <awalls [at] md> wrote:
> > On Sat, 2010-03-27 at 15:59 -0600, James Grossmann wrote:

> >
> > 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.

Thanks. I didn't get time to look at things yet. I've had obligations
at home every night this week and will through Wednesday. Thursday
night would be the first day I can do any Linux driver work.


> Thank You!
> James

You're welcome. And thanks in advance for your patience.

Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


awalls at md

Mar 31, 2010, 4:52 AM

Post #11 of 13 (4015 views)
Permalink
Re: recent work with HVR-1600 irblaster? [In reply to]

On Mon, 2010-03-29 at 07:20 -0600, James Grossmann wrote:
> On Sun, Mar 28, 2010 at 6:18 AM, Andy Walls <awalls [at] md> wrote:
> > On Sat, 2010-03-27 at 15:59 -0600, James Grossmann wrote:
> >> On Sat, Mar 27, 2010 at 2:02 PM, Andy Walls <awalls [at] md> 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
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


cctsurf at gmail

Apr 1, 2010, 2:26 PM

Post #12 of 13 (3955 views)
Permalink
Re: recent work with HVR-1600 irblaster? [In reply to]

On Wed, Mar 31, 2010 at 5:52 AM, Andy Walls <awalls [at] md> wrote:
> On Mon, 2010-03-29 at 07:20 -0600, James Grossmann wrote:
>> On Sun, Mar 28, 2010 at 6:18 AM, Andy Walls <awalls [at] md> wrote:
>> > On Sat, 2010-03-27 at 15:59 -0600, James Grossmann wrote:
>> >> On Sat, Mar 27, 2010 at 2:02 PM, Andy Walls <awalls [at] md> 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
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

Thank You! It does seem to have worked, I twisted the cable in the
plug a fair amount and it started to display numbers/codes when I
pushed buttons on the remote! At first, I didn't see it, because I am
sshing into the machine, but I was getting notes of keypresses in
dmesg (using debug=2), so I thought I'd check again, and twisting it
seems to have fixed it. I was at the point of downloading the
v4l-apps, but I couldn't find something with the cx18-ctl util in it.
Were you referring to the I downloaded the dvd-apps tip.tar.bz2, from
http://linuxtv.org/hg/dvb-apps/, but no cx18-ctl, I searched
ivtvdrivers.org, but no reference. I'm just curious where I would
have found them.
I'm also curious, now that I've got receive (which I wasn't worried
about), how do I get transmit?
Thanks again,
James

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


awalls at md

Apr 2, 2010, 5:17 PM

Post #13 of 13 (3906 views)
Permalink
Re: recent work with HVR-1600 irblaster? [In reply to]

On Thu, 2010-04-01 at 15:26 -0600, James Grossmann wrote:
> On Wed, Mar 31, 2010 at 5:52 AM, Andy Walls <awalls [at] md> wrote:

> > 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.
> >

> Thank You! It does seem to have worked, I twisted the cable in the
> plug a fair amount and it started to display numbers/codes when I
> pushed buttons on the remote! At first, I didn't see it, because I am
> sshing into the machine, but I was getting notes of keypresses in
> dmesg (using debug=2), so I thought I'd check again, and twisting it
> seems to have fixed it.

Good.

I had once wasted about 3 hours of debugging code when I first ran
across the "oops I didn't push the cable in all the way" bug. :)



> I was at the point of downloading the
> v4l-apps, but I couldn't find something with the cx18-ctl util in it.
> Were you referring to the I downloaded the dvd-apps tip.tar.bz2, from
> http://linuxtv.org/hg/dvb-apps/, but no cx18-ctl, I searched
> ivtvdrivers.org, but no reference. I'm just curious where I would
> have found them.

Mea culpa. They were recently moved out of the driver tree into their
own git repository:

http://git.linuxtv.org/v4l-utils.git

http://git.linuxtv.org/v4l-utils.git?a=tree;f=utils/v4l2-ctl;h=9c40b0506a44a9640eda38bb48360d65f6f910f7;hb=HEAD



> I'm also curious, now that I've got receive (which I wasn't worried
> about), how do I get transmit?

Unload ir-kbd-i2c, and use lirc_dev, lirc_zilog (or lirc_pvr150) and all
of the lirc userspace tools.

Regards,
Andy

> Thanks again,
> James



_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users

ivtv users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.