[mythtv-users] Can't get lirc or irw to work, but mode2 works

Jerry Rubinow jerrymr at gmail.com
Mon Jun 29 17:40:16 UTC 2015


On Mon, Jun 29, 2015 at 1:22 PM, Jerry Rubinow <jerrymr at gmail.com> wrote:
>> On Mon, Jun 29, 2015 at 12:28 PM, Alec Leamas <leamas.alec at gmail.com> wrote:
>>> On 29/06/15 17:31, Jerry Rubinow wrote:
>>>>
>>>> On Sun, Jun 28, 2015 at 2:50 PM, Jerry Rubinow <jerrymr at gmail.com> wrote:
>>>>>
>>>>>
>>>>> On Jun 28, 2015 13:36, "Alec Leamas" <leamas.alec at gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> On 28/06/15 15:54, Jerry Rubinow wrote:
>>>>>>
>>>>>>>
>>>>>>> Nick, it looks like 3.16, what I've been running, has that patch
>>>>>>> integrated into the kernel driver.  I tried a clean Ubuntu 15.04
>>>>>>> install
>>>>>>> and the problem is there as well.  Unfortunately the bios doesn't let
>>>>>>> me
>>>>>>> disable xHCI.    I think it may be time to visit newegg for a new ir
>>>>>>> receiver.
>>>>>>
>>>>>>
>>>>>>
>>>>>> TBH, I havn't read the complete thread. That said, I understand your
>>>>>> situation as if the kernel decoding route is at a dead end for you (?).
>>>>>>
>>>>>> Note, the alternative is to let lirc decode the raw timing data. I know
>>>>>> this has been mentioned before, but perhaps you missed this opportunity?
>>>>>>
>>>>>> Obviously, the existing config files doesn't work for you. One option
>>>>>> would be to use irrecord to create a new config file after setting the
>>>>>> protocol to 'lirc' and re-checking that mode2 still works as expected.
>>>>>> Might
>>>>>> work, dunno, but given that mode2 is OK for you I think you have a fair
>>>>>> chance.
>>>>>>
>>>>>> Cheers!
>>>>>>
>>>>>> --alec
>>>>>
>>>>>
>>>>> Alec, that's probably worth trying, I'll try irrecord.  However, my
>>>>> expectation is that the bits coming out of the driver will be faulty due
>>>>> to
>>>>> something in the USB 3/xHCI implementation.
>>>>>
>>>>> I'll try that tonight.
>>>>>
>>>>> -Jerry
>>>>
>>>>
>>>> Nope, I tried the config generated by irrecord and maybe one out of 10
>>>> to 20 presses would generate something it could recognize in irw, but
>>>> usually not the key I pressed.
>>>
>>>
>>> But you did run irrecord successfully enough to create a config file?! This
>>> does indeed looks strange.
>>>
>>> Just a double check: you don't have physical (i. e., IR) disturbances
>>> around? Low energy/fluorescent lamps or so?
>>>
>>> If you run irrecord twice, beginning from scratch and just recording one
>>> button, do they two generated files looks more or less identical?
>>>
>>> Cheers!
>>>
>>> --alec
>>>
>
> On Mon, Jun 29, 2015 at 1:16 PM, Jerry Rubinow <jerrymr at gmail.com> wrote:
>> Alec, yes I created a file from irrecord successfully.  No IR
>> disturbances around.  In fact, I have the two frontend machines right
>> next to each other, an Acer Revo and the Liva, and I am just changing
>> which machine the USB receiver is plugged into, not even changing the
>> location of the receiver end.  In the Acer, running 12.04, everything
>> is fine.  In the Liva, running either 14.04 or 15.04, does not work.
>> In the Liva, running Windows, it works fine.
>>
>> After your last email, I created two different runs of irrecord just
>> pressing the 1 button, and they came out different.  The gap is 93745
>> vs 93766.  And the raw codes contain 55 numbers vs 41 numbers.
>>
>> I think what I'm experiencing is the same bug reported (but
>> unresolved) here:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1405907
>> involving a USB 2.0 device plugged into a USB port with an xHCI controller.
>
> I think I'll try upgrading my kernel from 3.19 to 4.0 and see if that
> changes anything.

Oh well, the 4.0 kernel is no better.

-Jerry


More information about the mythtv-users mailing list