Mailing List Archive: MythTV: Users

HD-PVR IR blaster

Index | Next | Previous | View Threaded

ozdror at adelphia

Aug 29, 2009, 6:39 PM

Post #1 of 23 (7473 views)
Permalink

HD-PVR IR blaster

I am in a process of installing HD-PVR in mythtv.

Is there a changing channel program for DISH HD box, that is compatible
with the built in IR blaster.

-Thanks

Oz

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

drew.einhorn at gmail

Aug 29, 2009, 7:45 PM

Post #2 of 23 (7378 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On Sat, Aug 29, 2009 at 7:39 PM, Oz<ozdror [at] adelphia> wrote:
>
> I am in a process of installing HD-PVR in mythtv.
>
> Is there a changing channel program for DISH HD box, that is compatible
> with the built in IR blaster.
>

I will be in the same position in a few days.

The box I have is also a poor excuse for a DVR,
I do have some recordings on Dish box I'd like to transfer to the new
myth box. Does anybody have any tools to automate the process?

--
Drew Einhorn
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Aug 29, 2009, 8:09 PM

Post #3 of 23 (7369 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On Saturday 29 August 2009 21:39:42 Oz wrote:
>
> I am in a process of installing HD-PVR in mythtv.
>
> Is there a changing channel program for DISH HD box, that is compatible
> with the built in IR blaster.

The IR part isn't yet fully functional under Linux. Should be soon
though.

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

dherman516 at gmail

Aug 30, 2009, 6:49 AM

Post #4 of 23 (7357 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

>
> >
> > I am in a process of installing HD-PVR in mythtv.
> >
> > Is there a changing channel program for DISH HD box, that is compatible
> > with the built in IR blaster.
>
>
Look at an IguanaIR (http://iguanaworks.net/) It is a little expensive, but
it is a USB based linux supported IR Blaster/reciever

Dave

perveilerj at gmail

Aug 30, 2009, 9:40 AM

Post #5 of 23 (7337 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On Sat, Aug 29, 2009 at 11:09 PM, Jarod Wilson <jarod [at] wilsonet> wrote:

> On Saturday 29 August 2009 21:39:42 Oz wrote:
> >
> > I am in a process of installing HD-PVR in mythtv.
> >
> > Is there a changing channel program for DISH HD box, that is compatible
> > with the built in IR blaster.
>
> The IR part isn't yet fully functional under Linux. Should be soon
> though.
>
> --
>

"Soon" as in a week or so, or "soon" as in any month now? :) I'm certainly
no lirc contributer so please don't take the question as in ingrate being
impatient.

I only ask because my current serial blaster has decided to become less
accurate since an update from mythbuntu 8.04 to 9.04 (drops about 1 in 15
digits now), and I'm in the market for a new blaster. The iguanaworks one
didn't work for me, which leaves my options at either commandir ii for a lot
of money or hd-pvr for a little bit more (since it's on sale and with a
rebate, deal ends tomorrow).

I've been following the hd-pvr updates for ir blasting threads over at the
sagetv forums. It seems like they're having luck, but I think they use the
sage app to communicate with the i2c device instead of lirc. Or maybe I'm
misinterpreting what they're saying.

Anyways, any hints would be appreciated :)

--Jack

jarod at wilsonet

Aug 30, 2009, 10:06 AM

Post #6 of 23 (7329 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On Sunday 30 August 2009 12:40:19 Jack Perveiler wrote:
> On Sat, Aug 29, 2009 at 11:09 PM, Jarod Wilson <jarod [at] wilsonet> wrote:
>
> > On Saturday 29 August 2009 21:39:42 Oz wrote:
> > >
> > > I am in a process of installing HD-PVR in mythtv.
> > >
> > > Is there a changing channel program for DISH HD box, that is compatible
> > > with the built in IR blaster.
> >
> > The IR part isn't yet fully functional under Linux. Should be soon
> > though.
> >
> > --
> >
>
> "Soon" as in a week or so, or "soon" as in any month now? :) I'm certainly
> no lirc contributer so please don't take the question as in ingrate being
> impatient.

Could be later today, could be a few weeks, depends on how messy the
final details are and how much free time I have to work on it. Its a
bit further complicated by some major i2c changes in 2.6.31, and the
fact that I've got another neat project I'm working on that's quite
honestly a whole lot cooler than making yet another IR part work... :)

> I only ask because my current serial blaster has decided to become less
> accurate since an update from mythbuntu 8.04 to 9.04 (drops about 1 in 15
> digits now), and I'm in the market for a new blaster. The iguanaworks one
> didn't work for me, which leaves my options at either commandir ii for a lot
> of money or hd-pvr for a little bit more (since it's on sale and with a
> rebate, deal ends tomorrow).

Or an mceusb transceiver + remote bundle for $20?

> I've been following the hd-pvr updates for ir blasting threads over at the
> sagetv forums. It seems like they're having luck, but I think they use the
> sage app to communicate with the i2c device instead of lirc. Or maybe I'm
> misinterpreting what they're saying.

Are they doing that under Linux or Windows (of Mac OS X)? The i2c bus
wasn't even exposed until a very recent patch that isn't even in the
upstream v4l-dvb repo yet.

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

perveilerj at gmail

Aug 30, 2009, 10:35 AM

Post #7 of 23 (7332 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On Sun, Aug 30, 2009 at 1:06 PM, Jarod Wilson <jarod [at] wilsonet> wrote:

> On Sunday 30 August 2009 12:40:19 Jack Perveiler wrote:
> > On Sat, Aug 29, 2009 at 11:09 PM, Jarod Wilson <jarod [at] wilsonet>
> wrote:
> >
> > > On Saturday 29 August 2009 21:39:42 Oz wrote:
> > > >
> > > > I am in a process of installing HD-PVR in mythtv.
> > > >
> > > > Is there a changing channel program for DISH HD box, that is
> compatible
> > > > with the built in IR blaster.
> > >
> > > The IR part isn't yet fully functional under Linux. Should be soon
> > > though.
> > >
> > > --
> > >
> >
> > "Soon" as in a week or so, or "soon" as in any month now? :) I'm
> certainly
> > no lirc contributer so please don't take the question as in ingrate being
> > impatient.
>
> Could be later today, could be a few weeks, depends on how messy the
> final details are and how much free time I have to work on it. Its a
> bit further complicated by some major i2c changes in 2.6.31, and the
> fact that I've got another neat project I'm working on that's quite
> honestly a whole lot cooler than making yet another IR part work... :)
>
Sure, I can understand that :)

>
> > I only ask because my current serial blaster has decided to become less
> > accurate since an update from mythbuntu 8.04 to 9.04 (drops about 1 in 15
> > digits now), and I'm in the market for a new blaster. The iguanaworks
> one
> > didn't work for me, which leaves my options at either commandir ii for a
> lot
> > of money or hd-pvr for a little bit more (since it's on sale and with a
> > rebate, deal ends tomorrow).
>
> Or an mceusb transceiver + remote bundle for $20?

Yeah, it's been quite the saga for me (after my serial blaster started
getting sketchy, that is). This was the first thing I tried... I bought one
cheap off of ebay and sure enough it ended up being the philips ehome
variety that doesn't blast under lirc (I get the "this hardware does not
support transmitting" message). I just saw your post here though:

http://www.acetylcholine.com/node/6941

Maybe I'll give lirc cvs a try before I do anything else.

>
> > I've been following the hd-pvr updates for ir blasting threads over at
> the
> > sagetv forums. It seems like they're having luck, but I think they use
> the
> > sage app to communicate with the i2c device instead of lirc. Or maybe
> I'm
> > misinterpreting what they're saying.
>
> Are they doing that under Linux or Windows (of Mac OS X)? The i2c bus
> wasn't even exposed until a very recent patch that isn't even in the
> upstream v4l-dvb repo yet.

They're doing it under linux. Looks like they started with a v4l-dvb repo
and they have instructions posted on how to edit the code to re-enable the
i2c adapter:

http://forums.sagetv.com/forums/showthread.php?p=370184&postcount=119

--Jack

perveilerj at gmail

Aug 30, 2009, 5:23 PM

Post #8 of 23 (7314 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On Sun, Aug 30, 2009 at 1:35 PM, Jack Perveiler <perveilerj [at] gmail>wrote:

>
>
> On Sun, Aug 30, 2009 at 1:06 PM, Jarod Wilson <jarod [at] wilsonet> wrote:
>
>> On Sunday 30 August 2009 12:40:19 Jack Perveiler wrote:
>> > On Sat, Aug 29, 2009 at 11:09 PM, Jarod Wilson <jarod [at] wilsonet>
>> wrote:
>> >
>> > > On Saturday 29 August 2009 21:39:42 Oz wrote:
>> > > >
>> > > > I am in a process of installing HD-PVR in mythtv.
>> > > >
>> > > > Is there a changing channel program for DISH HD box, that is
>> compatible
>> > > > with the built in IR blaster.
>> > >
>> > > The IR part isn't yet fully functional under Linux. Should be soon
>> > > though.
>> > >
>> > > --
>> > >
>> >
>> > "Soon" as in a week or so, or "soon" as in any month now? :) I'm
>> certainly
>> > no lirc contributer so please don't take the question as in ingrate
>> being
>> > impatient.
>>
>> Could be later today, could be a few weeks, depends on how messy the
>> final details are and how much free time I have to work on it. Its a
>> bit further complicated by some major i2c changes in 2.6.31, and the
>> fact that I've got another neat project I'm working on that's quite
>> honestly a whole lot cooler than making yet another IR part work... :)
>>
> Sure, I can understand that :)
>
>
>>
>> > I only ask because my current serial blaster has decided to become less
>> > accurate since an update from mythbuntu 8.04 to 9.04 (drops about 1 in
>> 15
>> > digits now), and I'm in the market for a new blaster. The iguanaworks
>> one
>> > didn't work for me, which leaves my options at either commandir ii for a
>> lot
>> > of money or hd-pvr for a little bit more (since it's on sale and with a
>> > rebate, deal ends tomorrow).
>>
>> Or an mceusb transceiver + remote bundle for $20?
>
>
> Yeah, it's been quite the saga for me (after my serial blaster started
> getting sketchy, that is). This was the first thing I tried... I bought one
> cheap off of ebay and sure enough it ended up being the philips ehome
> variety that doesn't blast under lirc (I get the "this hardware does not
> support transmitting" message). I just saw your post here though:
>
> http://www.acetylcholine.com/node/6941
>
> Maybe I'll give lirc cvs a try before I do anything else.
>
>
As a follow up, lirc cvs was a LITTLE better (it didn't give me the
"hardware does not support sending" message), but it still doesn't do any
blasting. Bummer.

--Jack

jarod at wilsonet

Aug 31, 2009, 9:00 PM

Post #9 of 23 (7290 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On Sunday 30 August 2009 13:35:02 Jack Perveiler wrote:
> On Sun, Aug 30, 2009 at 1:06 PM, Jarod Wilson <jarod [at] wilsonet> wrote:
>
> > On Sunday 30 August 2009 12:40:19 Jack Perveiler wrote:
> > > On Sat, Aug 29, 2009 at 11:09 PM, Jarod Wilson <jarod [at] wilsonet>
> > wrote:
> > >
> > > > On Saturday 29 August 2009 21:39:42 Oz wrote:
> > > > >
> > > > > I am in a process of installing HD-PVR in mythtv.
> > > > >
> > > > > Is there a changing channel program for DISH HD box, that is
> > compatible
> > > > > with the built in IR blaster.
> > > >
> > > > The IR part isn't yet fully functional under Linux. Should be soon
> > > > though.
> > >
> > > "Soon" as in a week or so, or "soon" as in any month now? :) I'm
> > certainly
> > > no lirc contributer so please don't take the question as in ingrate being
> > > impatient.
> >
> > Could be later today, could be a few weeks, depends on how messy the
> > final details are and how much free time I have to work on it. Its a
> > bit further complicated by some major i2c changes in 2.6.31, and the
> > fact that I've got another neat project I'm working on that's quite
> > honestly a whole lot cooler than making yet another IR part work... :)
> >
> Sure, I can understand that :)

Or maybe tonight. Both transmit and receive are working perfectly on my
own hdpvr now, and I've pushed the bits for this into my git tree. I'm
also about to add them all to a new Fedora 11 2.6.30.x kernel build, as
well as tack them onto rawhide (current Fedora 12 devel tree).

> http://forums.sagetv.com/forums/showthread.php?p=370184&postcount=119

That part was actually only minimally helpful, most of the legwork was
in fixing the lirc_zilog driver to make irsend happy, but sagetv might
not be using lirc at all.

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

greg at pryzby

Sep 1, 2009, 6:40 AM

Post #10 of 23 (7281 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

Jarod Wilson wrote:
> On Sunday 30 August 2009 13:35:02 Jack Perveiler wrote:
>> On Sun, Aug 30, 2009 at 1:06 PM, Jarod Wilson <jarod [at] wilsonet> wrote:
>>
>>> On Sunday 30 August 2009 12:40:19 Jack Perveiler wrote:
>>>> On Sat, Aug 29, 2009 at 11:09 PM, Jarod Wilson <jarod [at] wilsonet>
>>> wrote:
>>>>> On Saturday 29 August 2009 21:39:42 Oz wrote:
<SNIP>

>>> Could be later today, could be a few weeks, depends on how messy the
>>> final details are and how much free time I have to work on it. Its a
>>> bit further complicated by some major i2c changes in 2.6.31, and the
>>> fact that I've got another neat project I'm working on that's quite
>>> honestly a whole lot cooler than making yet another IR part work... :)
>>>
>> Sure, I can understand that :)
>
> Or maybe tonight. Both transmit and receive are working perfectly on my
> own hdpvr now, and I've pushed the bits for this into my git tree. I'm
> also about to add them all to a new Fedora 11 2.6.30.x kernel build, as
> well as tack them onto rawhide (current Fedora 12 devel tree).

Sounds like in the next day or two (if not already) it is possible to
pull the bits, build a kernel and test?

TY!

--
greg pryzby greg at pryzby dot org
http://www.linkedin.com/in/gpryzby
BLOG: http://restonartistree.blogspot.com/
WEB: http://www.RestonArtisTree.com/
TWTR: gpryzby
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Sep 1, 2009, 6:54 AM

Post #11 of 23 (7281 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On Sep 1, 2009, at 9:40 AM, greg pryzby wrote:

> Jarod Wilson wrote:
>> On Sunday 30 August 2009 13:35:02 Jack Perveiler wrote:
>>> On Sun, Aug 30, 2009 at 1:06 PM, Jarod Wilson <jarod [at] wilsonet>
>>> wrote:
>>>
>>>> On Sunday 30 August 2009 12:40:19 Jack Perveiler wrote:
>>>>> On Sat, Aug 29, 2009 at 11:09 PM, Jarod Wilson
>>>>> <jarod [at] wilsonet>
>>>> wrote:
>>>>>> On Saturday 29 August 2009 21:39:42 Oz wrote:
> <SNIP>
>
>>>> Could be later today, could be a few weeks, depends on how messy
>>>> the
>>>> final details are and how much free time I have to work on it.
>>>> Its a
>>>> bit further complicated by some major i2c changes in 2.6.31, and
>>>> the
>>>> fact that I've got another neat project I'm working on that's quite
>>>> honestly a whole lot cooler than making yet another IR part
>>>> work... :)
>>>>
>>> Sure, I can understand that :)
>> Or maybe tonight. Both transmit and receive are working perfectly
>> on my
>> own hdpvr now, and I've pushed the bits for this into my git tree.
>> I'm
>> also about to add them all to a new Fedora 11 2.6.30.x kernel
>> build, as
>> well as tack them onto rawhide (current Fedora 12 devel tree).
>
> Sounds like in the next day or two (if not already) it is possible
> to pull the bits, build a kernel and test?

Its possible to pull the bits now (including a pre-build kernel for
Fedora 11).

In thinking about this some more, the assorted options are currently:

1) run Fedora 11, download the kernel I built last night from Fedora
build system:

http://kojipkgs.fedoraproject.org/packages/kernel/2.6.30.5/45.fc11/

2) git clone my lirc driver git tree, build a 2.6.31-rcX kernel (best
to git clone linus' tree off git.kernel.org, then add me as a remote,
I only have 5Mbps outbound).

3) grab just the lirc bits from git, using gitweb's snapshot
capability, i.e.

http://git.wilsonet.com//linux-2.6-lirc.git?a=snapshot;h=d58c0c8000b4f59e09b5e88398389fe4561dc32c;sf=tgz

Unpack them, then 'make -C /path/to/kernel/source M=$PWD
modules' (assumes you have the config vars for lirc properly set, I
think).

If running on pre-2.6.31, you'll want to back out the 2.6.31-specific
i2c changes, which this patch will do:

http://wilsonet.com/jarod/junk/hdpvr-ir/lirc-revert-2.6.31-i2c-changes.patch

4) grab the lirc patches that are in my Fedora kernel build directly:

http://wilsonet.com/jarod/junk/hdpvr-ir/lirc-2.6.31.patch
http://wilsonet.com/jarod/junk/hdpvr-ir/lirc-revert-2.6.31-i2c-changes.patch

The second is only needed for pre-2.6.31.

All of the above also require some patching of the hdpvr driver as it
exists in kernel 2.6.30, using this:

http://wilsonet.com/jarod/junk/hdpvr-ir/hdpvr-ir-enable.patch

That's now a roll-up of things in Janne's hdpvr hg tree that aren't in
the upstream kernel yet, and a few minor additional tweaks that I need
to send over to Janne still.

--
Jarod Wilson
jarod [at] wilsonet

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

greg at pryzby

Sep 12, 2009, 1:06 PM

Post #12 of 23 (7070 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On 09/01/2009 09:54 AM, Jarod Wilson wrote:
> On Sep 1, 2009, at 9:40 AM, greg pryzby wrote:
>
>> Jarod Wilson wrote:
>>> On Sunday 30 August 2009 13:35:02 Jack Perveiler wrote:
>>>> On Sun, Aug 30, 2009 at 1:06 PM, Jarod Wilson <jarod [at] wilsonet>
>>>> wrote:
>>>>
>>>>> On Sunday 30 August 2009 12:40:19 Jack Perveiler wrote:
>>>>>> On Sat, Aug 29, 2009 at 11:09 PM, Jarod Wilson <jarod [at] wilsonet>
>>>>> wrote:
>>>>>>> On Saturday 29 August 2009 21:39:42 Oz wrote:
>> <SNIP>
>>
>>>>> Could be later today, could be a few weeks, depends on how messy the
>>>>> final details are and how much free time I have to work on it. Its a
>>>>> bit further complicated by some major i2c changes in 2.6.31, and the
>>>>> fact that I've got another neat project I'm working on that's quite
>>>>> honestly a whole lot cooler than making yet another IR part work... :)
>>>>>
>>>> Sure, I can understand that :)
>>> Or maybe tonight. Both transmit and receive are working perfectly on my
>>> own hdpvr now, and I've pushed the bits for this into my git tree. I'm
>>> also about to add them all to a new Fedora 11 2.6.30.x kernel build, as
>>> well as tack them onto rawhide (current Fedora 12 devel tree).
>>
>> Sounds like in the next day or two (if not already) it is possible to
>> pull the bits, build a kernel and test?
>
> Its possible to pull the bits now (including a pre-build kernel for
> Fedora 11).

Pick one of the 4 below and they the last item (hdpvr-ir-enable.patch).

Or has this stuff been moved upstream now?

THANKS for all the work. Finally have some free time to get this ironed out.

> In thinking about this some more, the assorted options are currently:
>
> 1) run Fedora 11, download the kernel I built last night from Fedora
> build system:
>
> http://kojipkgs.fedoraproject.org/packages/kernel/2.6.30.5/45.fc11/
>
>
> 2) git clone my lirc driver git tree, build a 2.6.31-rcX kernel (best to
> git clone linus' tree off git.kernel.org, then add me as a remote, I
> only have 5Mbps outbound).
>
>
> 3) grab just the lirc bits from git, using gitweb's snapshot capability,
> i.e.
>
> http://git.wilsonet.com//linux-2.6-lirc.git?a=snapshot;h=d58c0c8000b4f59e09b5e88398389fe4561dc32c;sf=tgz
>
>
> Unpack them, then 'make -C /path/to/kernel/source M=$PWD modules'
> (assumes you have the config vars for lirc properly set, I think).
>
> If running on pre-2.6.31, you'll want to back out the 2.6.31-specific
> i2c changes, which this patch will do:
>
> http://wilsonet.com/jarod/junk/hdpvr-ir/lirc-revert-2.6.31-i2c-changes.patch
>
>
>
> 4) grab the lirc patches that are in my Fedora kernel build directly:
>
> http://wilsonet.com/jarod/junk/hdpvr-ir/lirc-2.6.31.patch
> http://wilsonet.com/jarod/junk/hdpvr-ir/lirc-revert-2.6.31-i2c-changes.patch
>
>
> The second is only needed for pre-2.6.31.
>
>
> All of the above also require some patching of the hdpvr driver as it
> exists in kernel 2.6.30, using this:
>
> http://wilsonet.com/jarod/junk/hdpvr-ir/hdpvr-ir-enable.patch
>
> That's now a roll-up of things in Janne's hdpvr hg tree that aren't in
> the upstream kernel yet, and a few minor additional tweaks that I need
> to send over to Janne still.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Sep 12, 2009, 5:47 PM

Post #13 of 23 (7067 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On Sep 12, 2009, at 4:06 PM, greg pryzby wrote:

> On 09/01/2009 09:54 AM, Jarod Wilson wrote:
>> On Sep 1, 2009, at 9:40 AM, greg pryzby wrote:
>>
>>> Jarod Wilson wrote:
>>>> On Sunday 30 August 2009 13:35:02 Jack Perveiler wrote:
>>>>> On Sun, Aug 30, 2009 at 1:06 PM, Jarod Wilson <jarod [at] wilsonet>
>>>>> wrote:
>>>>>
>>>>>> On Sunday 30 August 2009 12:40:19 Jack Perveiler wrote:
>>>>>>> On Sat, Aug 29, 2009 at 11:09 PM, Jarod Wilson <jarod [at] wilsonet
>>>>>>> >
>>>>>> wrote:
>>>>>>>> On Saturday 29 August 2009 21:39:42 Oz wrote:
>>> <SNIP>
>>>
>>>>>> Could be later today, could be a few weeks, depends on how
>>>>>> messy the
>>>>>> final details are and how much free time I have to work on it.
>>>>>> Its a
>>>>>> bit further complicated by some major i2c changes in 2.6.31,
>>>>>> and the
>>>>>> fact that I've got another neat project I'm working on that's
>>>>>> quite
>>>>>> honestly a whole lot cooler than making yet another IR part
>>>>>> work... :)
>>>>>>
>>>>> Sure, I can understand that :)
>>>> Or maybe tonight. Both transmit and receive are working perfectly
>>>> on my
>>>> own hdpvr now, and I've pushed the bits for this into my git
>>>> tree. I'm
>>>> also about to add them all to a new Fedora 11 2.6.30.x kernel
>>>> build, as
>>>> well as tack them onto rawhide (current Fedora 12 devel tree).
>>>
>>> Sounds like in the next day or two (if not already) it is possible
>>> to
>>> pull the bits, build a kernel and test?
>>
>> Its possible to pull the bits now (including a pre-build kernel for
>> Fedora 11).
>
> Pick one of the 4 below and they the last item (hdpvr-ir-
> enable.patch).
>
> Or has this stuff been moved upstream now?

For some value of, yes. All the hdpvr driver bits are in Janne's hdpvr
tree, but I don't believe they've been pulled over to the main v4l-dvb
tree, and definitely didn't go into kernel 2.6.31. The lirc bits are
in my lirc git tree. I suppose I should forward a copy of things over
to Mark Weaver, the originator of lirc_pvr150, but at this point, its
quite different from lirc_zilog, I believe (2.6.31 i2c changes, hdpvr
support additions, other cleanups)...

> THANKS for all the work. Finally have some free time to get this
> ironed out.
>
>
>> In thinking about this some more, the assorted options are currently:
>>
>> 1) run Fedora 11, download the kernel I built last night from Fedora
>> build system:
>>
>> http://kojipkgs.fedoraproject.org/packages/kernel/2.6.30.5/45.fc11/
>>
>>
>> 2) git clone my lirc driver git tree, build a 2.6.31-rcX kernel
>> (best to
>> git clone linus' tree off git.kernel.org, then add me as a remote, I
>> only have 5Mbps outbound).
>>
>>
>> 3) grab just the lirc bits from git, using gitweb's snapshot
>> capability,
>> i.e.
>>
>> http://git.wilsonet.com//linux-2.6-lirc.git?a=snapshot;h=d58c0c8000b4f59e09b5e88398389fe4561dc32c;sf=tgz
>>
>>
>> Unpack them, then 'make -C /path/to/kernel/source M=$PWD modules'
>> (assumes you have the config vars for lirc properly set, I think).
>>
>> If running on pre-2.6.31, you'll want to back out the 2.6.31-specific
>> i2c changes, which this patch will do:
>>
>> http://wilsonet.com/jarod/junk/hdpvr-ir/lirc-revert-2.6.31-i2c-changes.patch
>>
>>
>>
>> 4) grab the lirc patches that are in my Fedora kernel build directly:
>>
>> http://wilsonet.com/jarod/junk/hdpvr-ir/lirc-2.6.31.patch
>> http://wilsonet.com/jarod/junk/hdpvr-ir/lirc-revert-2.6.31-i2c-changes.patch
>>
>>
>> The second is only needed for pre-2.6.31.
>>
>>
>> All of the above also require some patching of the hdpvr driver as it
>> exists in kernel 2.6.30, using this:
>>
>> http://wilsonet.com/jarod/junk/hdpvr-ir/hdpvr-ir-enable.patch
>>
>> That's now a roll-up of things in Janne's hdpvr hg tree that aren't
>> in
>> the upstream kernel yet, and a few minor additional tweaks that I
>> need
>> to send over to Janne still.
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

--
Jarod Wilson
jarod [at] wilsonet

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

vbrunini at mit

Sep 14, 2009, 2:24 PM

Post #14 of 23 (6999 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

I've been trying to test the IR blaster functionality on my HD-PVR
with this patch,
unfortunately I'm running into some issues. First I tried option 1, the prebuilt
Fedora kernel package, and using that lirc_zilog recognizes the hd-pvr's ir

chip perfectly and I've been able to successfully use it to change
channels on my
cable box. However, using that version causes the hd-pvr to lock up
randomly 5-10
minutes into a recording, and attempting to modprobe -r either the hdpvr or

lirc_zilog modules hangs and eventually leads to a kernel oops after a minute or
so.

I decided to try to follow your 2nd suggestion and pull your 2.6.31
git tree by cloning
Linus' and then adding you as a remote to see if it was any more
stable. I also applied

the *http://wilsonet.com/jarod/junk/hdpvr-ir/hdpvr-ir-enable.patch* as
you said to.
The kernel compiles and boots fine and the hdpvr records without any
of the instability

I observed with your precompiled Fedora kernel, however the lirc_zilog
module no longer
recognizes the IR chip. When I run modprobe lirc_zilog debug=1 I get:

lirc_dev: IR Remote Control driver registered, major 248

lirc_zilog: Zilog/Hauppauge IR driver initializing
lirc_zilog: initialization complete

but no mention of it probing for the device. I've looked through
lirc_zilog.c a bit and
it seems that in 2.6.31 the ir_probe function is never getting run,
whereas it is in 2.6.30,

but I haven't been able to figure out why. I've checked to make sure
that the hdpvr i2c adapter
is still being created using i2cdetect and it shows:

i2c-0 i2c Hauppauge HD PVR I2C I2C adapter

which is the same as for the 2.6.30 kernel. Any idea what I'm doing
wrong? Thanks for all
the work you've already put in to getting the driver working.

Victor

On Sep 12, 2009, at 4:06 PM, greg pryzby wrote:

>* On 09/01/2009 09:54 AM, Jarod Wilson wrote:
*>>* On Sep 1, 2009, at 9:40 AM, greg pryzby wrote:
*>>*
*>>>* Jarod Wilson wrote:
*>>>>* On Sunday 30 August 2009 13:35:02 Jack Perveiler wrote:

*>>>>>* On Sun, Aug 30, 2009 at 1:06 PM, Jarod Wilson <jarod at
wilsonet.com <http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users>>
*>>>>>* wrote:
*>>>>>*

*>>>>>>* On Sunday 30 August 2009 12:40:19 Jack Perveiler wrote:
*>>>>>>>* On Sat, Aug 29, 2009 at 11:09 PM, Jarod Wilson <jarod at
wilsonet.com <http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users>

*>>>>>>>* >
*>>>>>>* wrote:
*>>>>>>>>* On Saturday 29 August 2009 21:39:42 Oz wrote:
*>>>* <SNIP>
*>>>*

*>>>>>>* Could be later today, could be a few weeks, depends on how
*>>>>>>* messy the
*>>>>>>* final details are and how much free time I have to work on it.

*>>>>>>* Its a
*>>>>>>* bit further complicated by some major i2c changes in 2.6.31,
*>>>>>>* and the
*>>>>>>* fact that I've got another neat project I'm working on that's

*>>>>>>* quite
*>>>>>>* honestly a whole lot cooler than making yet another IR part
*>>>>>>* work... :)
*>>>>>>*
*>>>>>* Sure, I can understand that :)

*>>>>* Or maybe tonight. Both transmit and receive are working perfectly
*>>>>* on my
*>>>>* own hdpvr now, and I've pushed the bits for this into my git

*>>>>* tree. I'm
*>>>>* also about to add them all to a new Fedora 11 2.6.30.x kernel
*>>>>* build, as
*>>>>* well as tack them onto rawhide (current Fedora 12 devel tree).

*>>>*
*>>>* Sounds like in the next day or two (if not already) it is possible
*>>>* to
*>>>* pull the bits, build a kernel and test?
*>>*

*>>* Its possible to pull the bits now (including a pre-build kernel for
*>>* Fedora 11).
*>*
*>* Pick one of the 4 below and they the last item (hdpvr-ir-
*>* enable.patch).

*>*
*>* Or has this stuff been moved upstream now?
*
For some value of, yes. All the hdpvr driver bits are in Janne's hdpvr
tree, but I don't believe they've been pulled over to the main v4l-dvb

tree, and definitely didn't go into kernel 2.6.31. The lirc bits are
in my lirc git tree. I suppose I should forward a copy of things over
to Mark Weaver, the originator of lirc_pvr150, but at this point, its

quite different from lirc_zilog, I believe (2.6.31 i2c changes, hdpvr
support additions, other cleanups)...

>* THANKS for all the work. Finally have some free time to get this
*>* ironed out.

*>*
*>*
*>>* In thinking about this some more, the assorted options are currently:
*>>*
*>>* 1) run Fedora 11, download the kernel I built last night from Fedora

*>>* build system:
*>>*
*>>* http://kojipkgs.fedoraproject.org/packages/kernel/2.6.30.5/45.fc11/

*>>*
*>>*
*>>* 2) git clone my lirc driver git tree, build a 2.6.31-rcX kernel
*>>* (best to
*>>* git clone linus' tree off git.kernel.org, then add me as a remote, I

*>>* only have 5Mbps outbound).
*>>*
*>>*
*>>* 3) grab just the lirc bits from git, using gitweb's snapshot
*>>* capability,
*>>* i.e.

*>>*
*>>* http://git.wilsonet.com//linux-2.6-lirc.git?a=snapshot;h=d58c0c8000b4f59e09b5e88398389fe4561dc32c;sf=tgz

*>>*
*>>*
*>>* Unpack them, then 'make -C /path/to/kernel/source M=$PWD modules'
*>>* (assumes you have the config vars for lirc properly set, I think).
*>>*

*>>* If running on pre-2.6.31, you'll want to back out the 2.6.31-specific
*>>* i2c changes, which this patch will do:
*>>*
*>>* http://wilsonet.com/jarod/junk/hdpvr-ir/lirc-revert-2.6.31-i2c-changes.patch

*>>*
*>>*
*>>*
*>>* 4) grab the lirc patches that are in my Fedora kernel build directly:
*>>*
*>>* http://wilsonet.com/jarod/junk/hdpvr-ir/lirc-2.6.31.patch

*>>* http://wilsonet.com/jarod/junk/hdpvr-ir/lirc-revert-2.6.31-i2c-changes.patch
*>>*
*>>*

*>>* The second is only needed for pre-2.6.31.
*>>*
*>>*
*>>* All of the above also require some patching of the hdpvr driver as it
*>>* exists in kernel 2.6.30, using this:

*>>*
*>>* http://wilsonet.com/jarod/junk/hdpvr-ir/hdpvr-ir-enable.patch
*>>*
*>>* That's now a roll-up of things in Janne's hdpvr hg tree that aren't

*>>* in
*>>* the upstream kernel yet, and a few minor additional tweaks that I
*>>* need
*>>* to send over to Janne still.
*>*
*>* _______________________________________________

*>* mythtv-users mailing list
*>* mythtv-users at mythtv.org
<http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users>
*>* http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

*
--
Jarod Wilson
jarod at wilsonet.com <http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users>

jarod at wilsonet

Sep 14, 2009, 8:01 PM

Post #15 of 23 (6981 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On 09/14/2009 05:24 PM, Victor Brunini wrote:
> I've been trying to test the IR blaster functionality on my HD-PVR with this patch,
> unfortunately I'm running into some issues. First I tried option 1, the prebuilt
> Fedora kernel package, and using that lirc_zilog recognizes the hd-pvr's ir
>
>
> chip perfectly and I've been able to successfully use it to change channels on my
> cable box. However, using that version causes the hd-pvr to lock up randomly 5-10
> minutes into a recording, and attempting to modprobe -r either the hdpvr or
>
>
> lirc_zilog modules hangs and eventually leads to a kernel oops after a minute or
> so.
>
> I decided to try to follow your 2nd suggestion and pull your 2.6.31 git tree by cloning
> Linus' and then adding you as a remote to see if it was any more stable. I also applied
>
>
> the/http://wilsonet.com/jarod/junk/hdpvr-ir/hdpvr-ir-enable.patch/ as you said to.
> The kernel compiles and boots fine and the hdpvr records without any of the instability

Sorry, you actually want this for 2.6.31, instead of the above:

http://wilsonet.com/jarod/junk/hdpvr-ir/hdpvr-ir-2.6.31.patch

Lockups recording sound very... Not good. I have to admit, I've not
actually tried recording and using the IR part on mine at the same time
yet...

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

vbrunini at mit

Sep 16, 2009, 11:05 AM

Post #16 of 23 (6899 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

It's recognizing the device again properly in 2.6.31 with that patch, but
I'm still getting the instability problem. Got through 2 recordings fine
last night, then on the third the file ends about 5 minutes in and dmesg is
filled with:

lirc_zilog: i2c_master_send failed with -110
lirc_zilog: polling the IR receiver chip failed, trying reset
lirc_zilog: i2c_master_send failed with -110
lirc_zilog: polling the IR receiver chip failed, trying reset
lirc_zilog: i2c_master_send failed with -110
lirc_zilog: polling the IR receiver chip failed, trying reset
lirc_zilog: i2c_master_send failed with -110
lirc_zilog: unable to read from the IR chip after 3 resets, giving up

repeating until i turned off my hdpvr. Then there is:

usb 2-2: USB disconnect, address 5
lirc_zilog: i2c_master_send failed with -108
lirc_zilog: polling the IR receiver chip failed, trying reset
lirc_zilog: i2c_master_send failed with -19
lirc_zilog: polling the IR receiver chip failed, trying reset
lirc_zilog: poll called
lirc_zilog: poll result = POLLIN|POLLRDNORM
INFO: task khubd:28 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
khubd D c201d91c 0 28 2 0x00000000
f6db3ce8 00000046 f6dab624 c201d91c c0a24734 c0a29140 f6dab624 c0a29140
c0a29140 013bcbb9 00000000 00000000 8ac07894 00001318 c2012140 f6dab380
f31e6a80 00000000 00000000 00000000 f331c460 f6dab380 f331c464 f6db3d1c
Call Trace:
[<c0772fb9>] __mutex_lock_common+0xdd/0x12a
[<c077301d>] __mutex_lock_slowpath+0x17/0x1a
[<c077310c>] ? mutex_lock+0x30/0x3e
[<c077310c>] mutex_lock+0x30/0x3e
[<fc5e603b>] ir_remove+0x1b/0x132 [lirc_zilog]
[<c0515262>] ? sysfs_hash_and_remove+0x42/0x55
[<f85171f1>] i2c_device_remove+0x40/0x7b [i2c_core]
[<c06377e3>] __device_release_driver+0x4a/0x80
[<c06378b6>] device_release_driver+0x1d/0x28
[<c0636d9b>] bus_remove_device+0x95/0xbe
[<f85180ee>] ? __unregister_client+0x0/0x1f [i2c_core]
[<c0635599>] device_del+0xf1/0x132
[<f85180ee>] ? __unregister_client+0x0/0x1f [i2c_core]
[<c0635608>] device_unregister+0x2e/0x53
[<f8517eb8>] i2c_unregister_device+0x10/0x12 [i2c_core]
[<f8518109>] __unregister_client+0x1b/0x1f [i2c_core]
[<c0634fb9>] device_for_each_child+0x2d/0x57
[<f85182b0>] i2c_del_adapter+0xa9/0x170 [i2c_core]
[<f7d81514>] hdpvr_disconnect+0xc4/0x107 [hdpvr]
[<c06810a9>] usb_unbind_interface+0x50/0xc0
[<c06377e3>] __device_release_driver+0x4a/0x80
[<c06378b6>] device_release_driver+0x1d/0x28
[<c0636d9b>] bus_remove_device+0x95/0xbe
[<c0635599>] device_del+0xf1/0x132
[<c067e711>] usb_disable_device+0xab/0x177
[<c0679761>] usb_disconnect+0xcc/0x167
[<c067ab9e>] hub_events+0x508/0xea5
[<c043000a>] ? tg_shares_up+0x64/0x1bb
[<c067b562>] hub_thread+0x27/0x165
[<c067b562>] ? hub_thread+0x27/0x165
[<c045234d>] ? autoremove_wake_function+0x0/0x34
[<c067b53b>] ? hub_thread+0x0/0x165
[<c04520af>] kthread+0x64/0x69
[<c045204b>] ? kthread+0x0/0x69
[<c0403eb3>] kernel_thread_helper+0x7/0x10
INFO: task lirc_zilog:2527 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
lirc_zilog D 00000000 0 2527 2 0x00000080
f24cfec8 00000046 f6514fe4 00000000 c0a24734 c0a29140 f6514fe4 c0a29140
c0a29140 013bcbf2 00000001 00000001 8ac06432 00001318 c2022140 f6514d40
00000000 00000000 00000000 00000000 f331ede4 f6514d40 f331ede8 f24cfefc
Call Trace:
[<c0772fb9>] __mutex_lock_common+0xdd/0x12a
[<c077301d>] __mutex_lock_slowpath+0x17/0x1a
[<c077310c>] ? mutex_lock+0x30/0x3e
[<c077310c>] mutex_lock+0x30/0x3e
[<f7d81e2c>] hdpvr_transfer+0x2c/0x96 [hdpvr]
[<f85174d7>] i2c_transfer+0x6f/0xe0 [i2c_core]
[<f8517d33>] i2c_master_send+0x39/0x48 [i2c_core]
[<fc5e6f90>] lirc_thread+0xe0/0x2ec [lirc_zilog]
[<fc5e6eb0>] ? lirc_thread+0x0/0x2ec [lirc_zilog]
[<c04520af>] kthread+0x64/0x69
[<c045204b>] ? kthread+0x0/0x69
[<c0403eb3>] kernel_thread_helper+0x7/0x10
INFO: task khubd:28 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
khubd D c201d91c 0 28 2 0x00000000
f6db3ce8 00000046 f6dab624 c201d91c c0a24734 c0a29140 f6dab624 c0a29140
c0a29140 013bcbb9 00000000 00000000 8ac07894 00001318 c2012140 f6dab380
f31e6a80 00000000 00000000 00000000 f331c460 f6dab380 f331c464 f6db3d1c
Call Trace:
[<c0772fb9>] __mutex_lock_common+0xdd/0x12a
[<c077301d>] __mutex_lock_slowpath+0x17/0x1a
[<c077310c>] ? mutex_lock+0x30/0x3e
[<c077310c>] mutex_lock+0x30/0x3e
[<fc5e603b>] ir_remove+0x1b/0x132 [lirc_zilog]
[<c0515262>] ? sysfs_hash_and_remove+0x42/0x55
[<f85171f1>] i2c_device_remove+0x40/0x7b [i2c_core]
[<c06377e3>] __device_release_driver+0x4a/0x80
[<c06378b6>] device_release_driver+0x1d/0x28
[<c0636d9b>] bus_remove_device+0x95/0xbe
[<f85180ee>] ? __unregister_client+0x0/0x1f [i2c_core]
[<c0635599>] device_del+0xf1/0x132
[<f85180ee>] ? __unregister_client+0x0/0x1f [i2c_core]
[<c0635608>] device_unregister+0x2e/0x53
[<f8517eb8>] i2c_unregister_device+0x10/0x12 [i2c_core]
[<f8518109>] __unregister_client+0x1b/0x1f [i2c_core]
[<c0634fb9>] device_for_each_child+0x2d/0x57
[<f85182b0>] i2c_del_adapter+0xa9/0x170 [i2c_core]
[<f7d81514>] hdpvr_disconnect+0xc4/0x107 [hdpvr]
[<c06810a9>] usb_unbind_interface+0x50/0xc0
[<c06377e3>] __device_release_driver+0x4a/0x80
[<c06378b6>] device_release_driver+0x1d/0x28
[<c0636d9b>] bus_remove_device+0x95/0xbe
[<c0635599>] device_del+0xf1/0x132
[<c067e711>] usb_disable_device+0xab/0x177
[<c0679761>] usb_disconnect+0xcc/0x167
[<c067ab9e>] hub_events+0x508/0xea5
[<c043000a>] ? tg_shares_up+0x64/0x1bb
[<c067b562>] hub_thread+0x27/0x165
[<c067b562>] ? hub_thread+0x27/0x165
[<c045234d>] ? autoremove_wake_function+0x0/0x34
[<c067b53b>] ? hub_thread+0x0/0x165
[<c04520af>] kthread+0x64/0x69
[<c045204b>] ? kthread+0x0/0x69
[<c0403eb3>] kernel_thread_helper+0x7/0x10
INFO: task lircd:1526 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
lircd D f31bac90 0 1526 1 0x00000084
f429fefc 00000086 f3854304 f31bac90 c0a24734 c0a29140 f3854304 c0a29140
c0a29140 00000202 c057b249 00000000 d31fc476 0000131e c2012140 f3854060
f429fefc 00000286 f24d6060 00000286 f331c460 f3854060 f331c464 f429ff30
Call Trace:
[<c057b249>] ? selinux_inode_free_security+0x55/0x5a
[<c0772fb9>] __mutex_lock_common+0xdd/0x12a
[<c077301d>] __mutex_lock_slowpath+0x17/0x1a
[<c077310c>] ? mutex_lock+0x30/0x3e
[<c077310c>] mutex_lock+0x30/0x3e
[<fc5e6d1f>] close+0x2d/0x47 [lirc_zilog]
[<c04cdf72>] __fput+0xef/0x17f
[<c04ce01a>] fput+0x18/0x1a
[<c04ca811>] filp_close+0x56/0x60
[<c04ca87a>] sys_close+0x5f/0x8d
[<c0403298>] sysenter_do_call+0x12/0x2d
INFO: task lirc_zilog:2527 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
lirc_zilog D 00000000 0 2527 2 0x00000080
f24cfec8 00000046 f6514fe4 00000000 c0a24734 c0a29140 f6514fe4 c0a29140
c0a29140 013bcbf2 00000001 00000001 8ac06432 00001318 c2022140 f6514d40
00000000 00000000 00000000 00000000 f331ede4 f6514d40 f331ede8 f24cfefc
Call Trace:
[<c0772fb9>] __mutex_lock_common+0xdd/0x12a
[<c077301d>] __mutex_lock_slowpath+0x17/0x1a
[<c077310c>] ? mutex_lock+0x30/0x3e
[<c077310c>] mutex_lock+0x30/0x3e
[<f7d81e2c>] hdpvr_transfer+0x2c/0x96 [hdpvr]
[<f85174d7>] i2c_transfer+0x6f/0xe0 [i2c_core]
[<f8517d33>] i2c_master_send+0x39/0x48 [i2c_core]
[<fc5e6f90>] lirc_thread+0xe0/0x2ec [lirc_zilog]
[<fc5e6eb0>] ? lirc_thread+0x0/0x2ec [lirc_zilog]
[<c04520af>] kthread+0x64/0x69
[<c045204b>] ? kthread+0x0/0x69
[<c0403eb3>] kernel_thread_helper+0x7/0x10
INFO: task khubd:28 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
khubd D c201d91c 0 28 2 0x00000000
f6db3ce8 00000046 f6dab624 c201d91c c0a24734 c0a29140 f6dab624 c0a29140
c0a29140 013bcbb9 00000000 00000000 8ac07894 00001318 c2012140 f6dab380
f31e6a80 00000000 00000000 00000000 f331c460 f6dab380 f331c464 f6db3d1c
Call Trace:
[<c0772fb9>] __mutex_lock_common+0xdd/0x12a
[<c077301d>] __mutex_lock_slowpath+0x17/0x1a
[<c077310c>] ? mutex_lock+0x30/0x3e
[<c077310c>] mutex_lock+0x30/0x3e
[<fc5e603b>] ir_remove+0x1b/0x132 [lirc_zilog]
[<c0515262>] ? sysfs_hash_and_remove+0x42/0x55
[<f85171f1>] i2c_device_remove+0x40/0x7b [i2c_core]
[<c06377e3>] __device_release_driver+0x4a/0x80
[<c06378b6>] device_release_driver+0x1d/0x28
[<c0636d9b>] bus_remove_device+0x95/0xbe
[<f85180ee>] ? __unregister_client+0x0/0x1f [i2c_core]
[<c0635599>] device_del+0xf1/0x132
[<f85180ee>] ? __unregister_client+0x0/0x1f [i2c_core]
[<c0635608>] device_unregister+0x2e/0x53
[<f8517eb8>] i2c_unregister_device+0x10/0x12 [i2c_core]
[<f8518109>] __unregister_client+0x1b/0x1f [i2c_core]
[<c0634fb9>] device_for_each_child+0x2d/0x57
[<f85182b0>] i2c_del_adapter+0xa9/0x170 [i2c_core]
[<f7d81514>] hdpvr_disconnect+0xc4/0x107 [hdpvr]
[<c06810a9>] usb_unbind_interface+0x50/0xc0
[<c06377e3>] __device_release_driver+0x4a/0x80
[<c06378b6>] device_release_driver+0x1d/0x28
[<c0636d9b>] bus_remove_device+0x95/0xbe
[<c0635599>] device_del+0xf1/0x132
[<c067e711>] usb_disable_device+0xab/0x177
[<c0679761>] usb_disconnect+0xcc/0x167
[<c067ab9e>] hub_events+0x508/0xea5
[<c043000a>] ? tg_shares_up+0x64/0x1bb
[<c067b562>] hub_thread+0x27/0x165
[<c067b562>] ? hub_thread+0x27/0x165
[<c045234d>] ? autoremove_wake_function+0x0/0x34
[<c067b53b>] ? hub_thread+0x0/0x165
[<c04520af>] kthread+0x64/0x69
[<c045204b>] ? kthread+0x0/0x69
[<c0403eb3>] kernel_thread_helper+0x7/0x10
INFO: task lircd:1526 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
lircd D f31bac90 0 1526 1 0x00000084
f429fefc 00000086 f3854304 f31bac90 c0a24734 c0a29140 f3854304 c0a29140
c0a29140 00000202 c057b249 00000000 d31fc476 0000131e c2012140 f3854060
f429fefc 00000286 f24d6060 00000286 f331c460 f3854060 f331c464 f429ff30
Call Trace:
[<c057b249>] ? selinux_inode_free_security+0x55/0x5a
[<c0772fb9>] __mutex_lock_common+0xdd/0x12a
[<c077301d>] __mutex_lock_slowpath+0x17/0x1a
[<c077310c>] ? mutex_lock+0x30/0x3e
[<c077310c>] mutex_lock+0x30/0x3e
[<fc5e6d1f>] close+0x2d/0x47 [lirc_zilog]
[<c04cdf72>] __fput+0xef/0x17f
[<c04ce01a>] fput+0x18/0x1a
[<c04ca811>] filp_close+0x56/0x60
[<c04ca87a>] sys_close+0x5f/0x8d
[<c0403298>] sysenter_do_call+0x12/0x2d
INFO: task lirc_zilog:2527 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
lirc_zilog D 00000000 0 2527 2 0x00000080
f24cfec8 00000046 f6514fe4 00000000 c0a24734 c0a29140 f6514fe4 c0a29140
c0a29140 013bcbf2 00000001 00000001 8ac06432 00001318 c2022140 f6514d40
00000000 00000000 00000000 00000000 f331ede4 f6514d40 f331ede8 f24cfefc
Call Trace:
[<c0772fb9>] __mutex_lock_common+0xdd/0x12a
[<c077301d>] __mutex_lock_slowpath+0x17/0x1a
[<c077310c>] ? mutex_lock+0x30/0x3e
[<c077310c>] mutex_lock+0x30/0x3e
[<f7d81e2c>] hdpvr_transfer+0x2c/0x96 [hdpvr]
[<f85174d7>] i2c_transfer+0x6f/0xe0 [i2c_core]
[<f8517d33>] i2c_master_send+0x39/0x48 [i2c_core]
[<fc5e6f90>] lirc_thread+0xe0/0x2ec [lirc_zilog]
[<fc5e6eb0>] ? lirc_thread+0x0/0x2ec [lirc_zilog]
[<c04520af>] kthread+0x64/0x69
[<c045204b>] ? kthread+0x0/0x69
[<c0403eb3>] kernel_thread_helper+0x7/0x10
INFO: task khubd:28 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
khubd D c201d91c 0 28 2 0x00000000
f6db3ce8 00000046 f6dab624 c201d91c c0a24734 c0a29140 f6dab624 c0a29140
c0a29140 013bcbb9 00000000 00000000 8ac07894 00001318 c2012140 f6dab380
f31e6a80 00000000 00000000 00000000 f331c460 f6dab380 f331c464 f6db3d1c
Call Trace:
[<c0772fb9>] __mutex_lock_common+0xdd/0x12a
[<c077301d>] __mutex_lock_slowpath+0x17/0x1a
[<c077310c>] ? mutex_lock+0x30/0x3e
[<c077310c>] mutex_lock+0x30/0x3e
[<fc5e603b>] ir_remove+0x1b/0x132 [lirc_zilog]
[<c0515262>] ? sysfs_hash_and_remove+0x42/0x55
[<f85171f1>] i2c_device_remove+0x40/0x7b [i2c_core]
[<c06377e3>] __device_release_driver+0x4a/0x80
[<c06378b6>] device_release_driver+0x1d/0x28
[<c0636d9b>] bus_remove_device+0x95/0xbe
[<f85180ee>] ? __unregister_client+0x0/0x1f [i2c_core]
[<c0635599>] device_del+0xf1/0x132
[<f85180ee>] ? __unregister_client+0x0/0x1f [i2c_core]
[<c0635608>] device_unregister+0x2e/0x53
[<f8517eb8>] i2c_unregister_device+0x10/0x12 [i2c_core]
[<f8518109>] __unregister_client+0x1b/0x1f [i2c_core]
[<c0634fb9>] device_for_each_child+0x2d/0x57
[<f85182b0>] i2c_del_adapter+0xa9/0x170 [i2c_core]
[<f7d81514>] hdpvr_disconnect+0xc4/0x107 [hdpvr]
[<c06810a9>] usb_unbind_interface+0x50/0xc0
[<c06377e3>] __device_release_driver+0x4a/0x80
[<c06378b6>] device_release_driver+0x1d/0x28
[<c0636d9b>] bus_remove_device+0x95/0xbe
[<c0635599>] device_del+0xf1/0x132
[<c067e711>] usb_disable_device+0xab/0x177
[<c0679761>] usb_disconnect+0xcc/0x167
[<c067ab9e>] hub_events+0x508/0xea5
[<c043000a>] ? tg_shares_up+0x64/0x1bb
[<c067b562>] hub_thread+0x27/0x165
[<c067b562>] ? hub_thread+0x27/0x165
[<c045234d>] ? autoremove_wake_function+0x0/0x34
[<c067b53b>] ? hub_thread+0x0/0x165
[<c04520af>] kthread+0x64/0x69
[<c045204b>] ? kthread+0x0/0x69
[<c0403eb3>] kernel_thread_helper+0x7/0x10
INFO: task lircd:1526 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
lircd D f31bac90 0 1526 1 0x00000084
f429fefc 00000086 f3854304 f31bac90 c0a24734 c0a29140 f3854304 c0a29140
c0a29140 00000202 c057b249 00000000 d31fc476 0000131e c2012140 f3854060
f429fefc 00000286 f24d6060 00000286 f331c460 f3854060 f331c464 f429ff30
Call Trace:
[<c057b249>] ? selinux_inode_free_security+0x55/0x5a
[<c0772fb9>] __mutex_lock_common+0xdd/0x12a
[<c077301d>] __mutex_lock_slowpath+0x17/0x1a
[<c077310c>] ? mutex_lock+0x30/0x3e
[<c077310c>] mutex_lock+0x30/0x3e
[<fc5e6d1f>] close+0x2d/0x47 [lirc_zilog]
[<c04cdf72>] __fput+0xef/0x17f
[<c04ce01a>] fput+0x18/0x1a
[<c04ca811>] filp_close+0x56/0x60
[<c04ca87a>] sys_close+0x5f/0x8d
[<c0403298>] sysenter_do_call+0x12/0x2d

Let me know if you'd like me to run any further tests for more information
or if the
contents of another log file would be helpful.

Thanks,
Victor

------------------------------------------------------------
On 09/14/2009 05:24 PM, Victor Brunini wrote:
> I've been trying to test the IR blaster functionality on my HD-PVR with
this patch,
> unfortunately I'm running into some issues. First I tried option 1, the
prebuilt
> Fedora kernel package, and using that lirc_zilog recognizes the hd-pvr's
ir
>
>
> chip perfectly and I've been able to successfully use it to change
channels on my
> cable box. However, using that version causes the hd-pvr to lock up
randomly 5-10
> minutes into a recording, and attempting to modprobe -r either the hdpvr
or
>
>
> lirc_zilog modules hangs and eventually leads to a kernel oops after a
minute or
> so.
>
> I decided to try to follow your 2nd suggestion and pull your 2.6.31 git
tree by cloning
> Linus' and then adding you as a remote to see if it was any more stable.
I also applied
>
>
> the/http://wilsonet.com/jarod/junk/hdpvr-ir/hdpvr-ir-enable.patch/ as you
said to.
> The kernel compiles and boots fine and the hdpvr records without any of
the instability

Sorry, you actually want this for 2.6.31, instead of the above:

http://wilsonet.com/jarod/junk/hdpvr-ir/hdpvr-ir-2.6.31.patch

Lockups recording sound very... Not good. I have to admit, I've not
actually tried recording and using the IR part on mine at the same time
yet...

--
Jarod Wilson
jarod [at] wilsonet

david at istwok

Oct 14, 2009, 1:34 PM

Post #17 of 23 (6509 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On Mon, Sep 14, 2009 at 11:01:04PM -0400, Jarod Wilson wrote:
> Sorry, you actually want this for 2.6.31, instead of the above:
>
> http://wilsonet.com/jarod/junk/hdpvr-ir/hdpvr-ir-2.6.31.patch
>
> Lockups recording sound very... Not good. I have to admit, I've not
> actually tried recording and using the IR part on mine at the same
> time yet...

Is anyone successfully using Jarod's patches for IR blasting,
particularly with a Motorola STB? IF so what STB and codes are you
using?

I'm using Jarod's patches as found in the 2.6.31.1-56.fc12 Fedora
kernel. IR reception appears to work as the Hauppauge remote keys are
recognized and reported. IR blasting reports no errors, but I don't
see any activity on the STB. Either it's not actually transmitting
anything or I can't find the right codes.

David
--
David Engel
david [at] istwok
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

david at istwok

Oct 14, 2009, 4:21 PM

Post #18 of 23 (6494 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On Wed, Oct 14, 2009 at 03:34:45PM -0500, David Engel wrote:
> recognized and reported. IR blasting reports no errors, but I don't
> see any activity on the STB. Either it's not actually transmitting
> anything or I can't find the right codes.

IR blasting does indeed work! The transmitter just must be week as it
has to be in *exactly* the right place.

David
--
David Engel
david [at] istwok
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jedi at mishnet

Oct 14, 2009, 6:20 PM

Post #19 of 23 (6498 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On Wed, Oct 14, 2009 at 06:21:35PM -0500, David Engel wrote:
> On Wed, Oct 14, 2009 at 03:34:45PM -0500, David Engel wrote:
> > recognized and reported. IR blasting reports no errors, but I don't
> > see any activity on the STB. Either it's not actually transmitting
> > anything or I can't find the right codes.
>
> IR blasting does indeed work! The transmitter just must be week as it
> has to be in *exactly* the right place.

This is a very common sort of problem. I've had this same exact issue
with my MCE emitters from my old PVR-150 kit.

[deletia]
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Oct 14, 2009, 6:38 PM

Post #20 of 23 (6509 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On 10/14/2009 07:21 PM, David Engel wrote:
> On Wed, Oct 14, 2009 at 03:34:45PM -0500, David Engel wrote:
>> recognized and reported. IR blasting reports no errors, but I don't
>> see any activity on the STB. Either it's not actually transmitting
>> anything or I can't find the right codes.
>
> IR blasting does indeed work! The transmitter just must be week as it
> has to be in *exactly* the right place.

Meant to reply sooner. Mine had to be placed quite precisely as well,
but most certainly does work. Still haven't had a chance to try to
reproduce or debug the crashes reported while recording w/lirc_zilog
loaded and talking to the thing though...

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

david at istwok

Oct 15, 2009, 12:59 PM

Post #21 of 23 (6473 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On Wed, Oct 14, 2009 at 09:38:42PM -0400, Jarod Wilson wrote:
> Still haven't had a chance to
> try to reproduce or debug the crashes reported while recording
> w/lirc_zilog loaded and talking to the thing though...

I hadn't even thought to try that, so I did today. The first time,
the HD-PVR locked up fairly tightly and needed a power cycle to get it
back. The second time, there weren't any problems -- I was able to
send and receive IR just fine while recording.

David
--
David Engel
david [at] istwok
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

david at istwok

Oct 16, 2009, 2:38 PM

Post #22 of 23 (6422 views)
Permalink

Re: HD-PVR IR blaster [In reply to]

On Wed, Oct 14, 2009 at 06:21:35PM -0500, David Engel wrote:
> IR blasting does indeed work! The transmitter just must be week as it
> has to be in *exactly* the right place.

Next issue. Jarod, do you know how to determine which lirc device
goes with which HD-PVR? When my RMA replacement comes next week, I'll
have two HD-PVRs on one system. udev rules can be used to force each
HD-PVR to used a fixed video device name. That doesn't look possbile
for the lirc devices since there don't appear to be any identifying
attributes. Here the output I get from running "udevadm info
--attribute-walk" on my current setup:

looking at device '/devices/virtual/lirc/lirc0':
KERNEL=="lirc0"
SUBSYSTEM=="lirc"
DRIVER==""

David
--
David Engel
david [at] istwok
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

May 20, 2010, 12:39 PM

Post #23 of 23 (4217 views)
Permalink

Re: HD-PVR IR Blaster [In reply to]

On Thu, May 20, 2010 at 11:46 AM, Michael Knoll <michael.knoll [at] gmail> wrote:
> I am stuck trying to get the IR Blaster on the HD-PVR working. �I was
> hoping someone could help.
>
> I am running Ubuntu 10.04. �The machine previously had an MCE Remote,
> but there was no blaster. �I followed the directions on the wiki at
> http://www.mythtv.org/wiki/HD-PVR. �I used the lircd.conf from
> http://www.blushingpenguin.com/mark/lmilk/lircd.conf. �I copied the
> firmware. �I also needed to do a "depmod", since the lirc_zilog.ko
> module was added, not replace. �I'd add it to the wiki, but I'm not
> certain I am correct since it still doesn't work. �The modules load,
> but every time I try to send IR, I get:
>
> $irsend SEND_ONCE blaster 0_1_KEY_0
> irsend: command failed: SEND_ONCE blaster 0_1_KEY_0
> irsend: unknown remote: "blaster"
>
> The lircd.conf has a remote named blaster. �I've tried removing
> everything in the lircd.conf but the blaster remote and one button,
> but it still did not work. �This made me think it was not an error in
> the lircd.conf. �I tried setting the conf attribute in hardware.conf
> to the full path to my lircd.conf, thinking it wasn't finding the
> file, but I still got the same error. �I tried adding the -L and -D
> options to lircd's args, but it does not appear Ubuntu's lircd is
> compiled with support for them
>
> Can anyone offer any ideas?
>
> I have included a few command outputs and files that might be relevant.
>
> $ lsmod |grep lirc
> lirc_zilog � � � � � � 15651 �3
> lirc_dev � � � � � � � 12832 �1 lirc_zilog
>
> $ dmesg |grep lirc
> [ �234.267482] lirc_dev: IR Remote Control driver registered, major 250
> [ �234.445062] lirc_zilog: Zilog/Hauppauge IR driver initializing
> [ �234.455942] lirc_zilog: chip found with RX and TX
> [ �234.458513] lirc_dev: lirc_register_driver: sample_rate: 0
> [ �235.547832] lirc_zilog: Zilog/Hauppauge IR blaster firmware version
> 2.1.0 loaded
> [ �235.547870] lirc_zilog: initialization complete
>
> $ ls -l /dev/lirc*
> crw-rw---- 1 root root 250, 0 2010-05-19 23:43 /dev/lirc0
> lrwxrwxrwx 1 root root � � 19 2010-05-20 11:16 /dev/lircd -> /var/run/lirc/lircd
> lrwxrwxrwx 1 root root � � 20 2010-05-20 11:16 /dev/lircd1 ->
> /var/run/lirc/lircd1
>
> $ cat /etc/lirc/hardware.conf

I would like to take that file out back and put it out of my misery.
Its almost *always* being populated incorrectly (not by you, but by
the package setup thingy)...

> # /etc/lirc/hardware.conf
> #
> #Chosen Remote Control
> REMOTE="Windows Media Center Transceivers/Remotes (all)"
> REMOTE_MODULES="lirc_dev lirc_zilog"
> REMOTE_DRIVER=""
> REMOTE_DEVICE="/dev/lirc0"
> REMOTE_SOCKET=""
> REMOTE_LIRCD_CONF=""

You have no lircd.conf specified here, though /etc/lirc/lircd.conf
should be used by default. Run 'irsend LIST "" ""' (yes, two sets of
quotes w/nothing in between), and lircd will tell you what remote
names it actually knows about. From your earlier output, lircd knows
nothing about the remote "blaster", so until you get that part sorted,
nothing is going to work.

> REMOTE_LIRCD_ARGS=""
>
> #Chosen IR Transmitter
> TRANSMITTER="HD-PVR"
> TRANSMITTER_MODULES="lirc_dev lirc_zilog"
> TRANSMITTER_DRIVER=""
> TRANSMITTER_DEVICE="/dev/lirc0"
> TRANSMITTER_SOCKET=""
> TRANSMITTER_LIRCD_CONF=""
> TRANSMITTER_LIRCD_ARGS=""

This is the part that should be slaughtered. When there is only a
single device, there should only be one setup stanza. You've got two
lircd instances running for no reason at all, both binding to the same
device here. (This is jokes and fail galore when people answer "yes, I
have a transmitter and a remote!" when they're using a single device
capable of both transmit and receive. It only makes sense if there are
multiple devices to have both stanzas filled in. A simple "are your
transmit and receive devices one in the same?" asked of the user would
probably eliminate this folly...)

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads