HP MCE IR receiver stops working, works again when plugged into different USB port

[ptr727]

Running OE 4.2.0 OpenELEC-Generic.x86_64-4.2.0 on a Zotac XBOX ID84.
Using HP MCE remote, http://www.amazon.com/gp/product/B00KDNIRYA

Remote works ok, and after some time, couple minutes to hours, it stops working.
Unplug and replug in same USB port and it still does not work, replug into a different USB port and it works again.

When remote does not work irw produces no output, but red light on IR receiver flashes indicating signal received.
Same remote on a Win8.1 system and Windows XBMC works, left running a day and it kept on working.

I have 3 x ID84 systems and 3 x HP MCE remotes, I am going to test on the other 2 systems, and I'll report back.

I initially ran 3.x manually upgraded to 4.0 auto updated to 4.2.
I then did a fresh install of 4.2.0, same problem.

I do not know if this problem also happened on 3.x or on 4.0, as I only converted the the HP MCE remotes a few days ago. I used to use FLIRC's, but they are prone to electrical interference from light dimmers at night.

Forum thread with similar symptoms here:
http://openelec.tv/forum/103-infared-remotes/70403-hp-ir-receiver-not-working

DMESG: http://sprunge.us/bPOV
XBMC: http://pastebin.com/z2Aru5px
System: http://pastebin.com/GMsTvzdr
Input: http://pastebin.com/8uXgycVM

P.

[ptr727]

I now installed fresh 4.2's on three ID84's, and all three using new out of the box HP MCE IR receivers.
All three systems exhibit the same behavior, remote would just stop working, unplug replug in different ports brings it back up, and then it dies again.

Sample DMESG from a system that had IR die very quickly: http://sprunge.us/cUPP

[fritsch]

Find the latest 4.1.x version that does not have this bug, please.

2014-09-28 20:36 GMT+02:00 ptr727 notifications@github.com:

I now installed fresh 4.2's on three ID84's, and all three using new out
of the box HP MCE IR receivers.
All three systems exhibit the same behavior, remote would just stop
working, unplug replug in different ports brings it back up, and then it
dies again.

Sample DMESG from a system that had IR die very quickly:
http://sprunge.us/cUPP

Reply to this email directly or view it on GitHub
#3515 (comment)
.

               Key-ID:     0x1A995A9B
               keyserver: pgp.mit.edu

Fingerprint: 4606 DA19 EC2E 9A0B 0157 C81B DA07 CF63 1A99 5A9B

[ptr727]

Ok, reverted to 4.1.6, remote still works after more than 30 mins, looks promising.

[fritsch]

Cool - so, let's see what commits we had.

[sraue]

ca you test the build from http://openelec.tv/forum/120-news-announcements/73013-openelec-4-2-0-released?start=90#118362 and report back?

[ptr727]

Ok, I updated one system, will report back this evening.

[ptr727]

Sorry to report the remote is again not working after leaving the system on for the day.
IR receiver light flashes as remote keys are pressed, but system does not respond.

New DMESG here: http://sprunge.us/LBji

[stefansaraev]

it's a kernel regression, iirc it was introduced in linux 3.12 or .13 (I've had the same remote)
boot OE with usbcore.autosuspend=-1 (see APPEND in /flash/extlinux.conf)

[ptr727]

Need some help editing extlinux.conf please.
SFTP write fails, in SSH nano reports read-only filesystem when I try to write?

Weird thing, last night I noticed:
ID84 system 1 running the released 4.2 was still working
ID84 system 2 running the released 4.2 was not working
ID84 system 3 running test build was not working
Only difference on the three systems is SSD size, I had done a BIOS update and default options reset on all three, clean install on all three.
Could there be an environmental influence, or timing,or randomness?

[sraue]

you need to run mount -o remount,rw /flash first before you edit /flash/extlinux.conf

[ptr727]

Thank you, done, will report back this evening.

[ptr727]

The system with usbcore.autosuspend=-1 is still working.

[ptr727]

Same system is still working, so I can say with high confidence the autosuspend setting works.

1. Is this something that can be fixed, i.e. code change in the kernel or OE, or default configuration change in OE, or should I just revert to make the autosuspend change on every version?

2. Will an auto or manual upgrade revert the setting, or will it stick once set?

[stefansaraev]

1. it can be done by default, but I am unsure if that's a good idea
2. no. bootloader configuration is never touched on upgrade.

[ptr727]

Now that I know how, changing the bootloader once after install is pretty easy.
Thank you.

[jaspov]

Same issue but editting the conf file doesnt work for me. See http://openelec.tv/forum/103-infared-remotes/73189-4-2-4-2-1-hp-remote-drops-out-afte-a-while#120049

also added screenshot of conf file to ptr727's post
http://openelec.tv/forum/103-infared-remotes/70403-hp-ir-receiver-not-working

happy to help with anything to get this fixed.

[stefansaraev]

disable xhci (usb3) in bios. nothing more can be done for now.

[jaspov]

Thanks but my asrock 330 doesn't have USB3, Only USB 2.0. Anything else I can try?

[jaspov]

Have been googling with what you postes: xhci and usb3 . I seem to have found an issue where USB devices are now handled through the Linux kernel and ever since that time some have these issues but mostly with USB3 which can be solved by switching to USB2 which I can't do as I only have USB2 but itr looks like the same root cause. Will this issue stay open until the issue is solved in a new Linux kernel and incorporated in a new Openelec Release? Would be a great way to track when I can upgrade again.

[jaspov]

Does the new kernel in Openelec 5.1 perhaps fix this?

[stefansaraev]

cleaning up. please test OE 5.0 rc1 and if it's still an issue, open a new ticket. make sure to read our guidelines for contributing first. thanks.

[jaspov]

ok thanks. issue still exists though. Tested last week, see http://openelec.tv/forum/103-infared-remotes/73189-4-2-4-2-1-hp-remote-drops-out-afte-a-while#123874