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

Mike Thomas mt3 at pfw.demon.co.uk
Mon Jun 29 17:04:52 UTC 2015


On Mon, 29 Jun 2015 18:28:32 +0200
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?

Dear OP,

You might like to look into the archives for my earlier comments
regarding IR disturbances. Some monitors and TV sets produce enough IR
on their own that you might as well give up using an infra red remote
control. All my monitors and TVs fall into that category. It just so
happens that the TV's own remote control protocol is transmitted in the
blanks between the IR flashes given off by the back light. I couldn't
find another remote control which would transmit in these bursts. I
even bought a Sharp IR receiver chip to go with my Sharp TV and that
didn't work. It took me weeks of trials before I eventually gave up.

I settled on a Bluetooth remote control which I ordered from Maplin.
This has been flawless. They are coded so it is possible to have
several in one building without them conflicting. You just plug it in
and it comes up as a HID input device (a keyboard and mouse). No
drivers, no nothing. I have the key mappings if you want them.

Cheers,

Mike.

> 
> 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
> 
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org


More information about the mythtv-users mailing list