[SOLVED] Remote not working after update to 8.0.1

stack · March 30, 2017 at 8:58 PM

Code

# ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event2) with:
    Driver mceusb, table rc-rc6-mce
    Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo mce-kbd rc-6 sharp xmp
    Enabled protocols: lirc nec rc-6
    Name: Media Center Ed. eHome Infrared
    bus: 3, vendor/product: 147a:e03e, version: 0x1101
    Repeat delay = 500 ms, repeat period = 125 ms
# lsusb
Bus 001 Device 006: ID 147a:e03e Formosa Industrial Computing, Inc. Infrared Receiver [IR605A/Q]

Greetings,
I was running 7.0.3 on a Raspberry Pi 3 with a Rosewill RHRC-12001 MCE Infrared remote which I have used with Kodi for many years.

I had some spare time to do an update, so I did a manual update. I downloaded LibreELEC-RPi2.arm-8.0.1.tar into the /storage/.update folder and rebooted. Install seems to have gone well. It rebooted itself and all looks good. Except the remote doesn't work...

I plugged in a USB keyboard and that is working just fine. Plugged the remote into a second Kodi install (on a Ubuntu system) and it works so I know it isn't the hardware.

When I look at the Pi, the ir receiver is there. When I push buttons on the remote, the ir receiver lights up but nothing happens in Kodi.

I am poking around in the Kodi menus seeing if anything changed there, but nothing obvious is jumping out at me as being different.

Has anyone else had issues with their remote after upgrading?
Thoughts on things to try?

Thanks!
~Stack~

[Edit]: Saw some interesting errors in the log files.

Code

mceusb 1-1.5:1.0: Error: urb status = -32

Not sure yet what or why on that, but I reset the the IR receiver. Below is the dmesg output, but no luck so far.

Code

[  322.341532] usb 1-1.5: USB disconnect, device number 5
[  329.457526] usb 1-1.5: new full-speed USB device number 6 using dwc_otg
[  329.557138] usb 1-1.5: New USB device found, idVendor=147a, idProduct=e03e
[  329.557152] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  329.557160] usb 1-1.5: Product: eHome Infrared Transceiver
[  329.557167] usb 1-1.5: Manufacturer: Formosa21
[  329.557174] usb 1-1.5: SerialNumber: 00007B62
[  329.562289] Registered IR keymap rc-rc6-mce
[  329.562864] input: Media Center Ed. eHome Infrared Remote Transceiver (147a:e03e) as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/rc/rc0/input4
[  329.563113] rc rc0: Media Center Ed. eHome Infrared Remote Transceiver (147a:e03e) as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/rc/rc0
[  329.563432] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
[  329.727513] mceusb 1-1.5:1.0: Registered Formosa21 eHome Infrared Transceiver with mce emulator interface version 2
[  329.727527] mceusb 1-1.5:1.0: 0 tx ports (0x0 cabled) and 1 rx sensors (0x1 active)
[  329.730952] hid-generic 0003:147A:E03E.0004: hiddev0,hidraw2: USB HID v1.00 Device [Formosa21 eHome Infrared Transceiver] on usb-3f980000.usb-1.5/input1

Display More

EDIT: SOLVED!!
I was at a Python meetup today. A guy was doing a project on a Pi3. A group started to chat about Pi3 and to get to the point, I mentioned my issues with the remote and OpenELEC. A suggestion came forward. Wipe and start fresh WITHOUT the remote receiver plugged in. After the setup menu, plug in. He claimed he's never gotten OpenELEC or LibreELEC to work with his remote if it is physically plugged in when he does an update. I thought it was worth a try. So 8.0.2 fresh install, got through the intro config menu, then plugged in the remote.

Dang thing worked!

WTF? I have no idea why that would work except there has to be a setup script that doesn't run right on initial boot or maybe it runs better after the services are all started? Dunno. Those are just wild guesses. Regardless, I can shutdown, reboot, whatever and it still works afterwards.

If anyone else is having issues, it's an easy try to see if it works for you. I will keep this in mind for future upgrades.

Henk50 · March 30, 2017 at 9:18 PM

I had nearly the same experience with a HP USB MCE. Sometimes a key will respond, or with a long delay. I deleted lircd.conf and Lircmap.xml and everything is working. I think still something wrong in 8.0.1. In 8.0.0 the remote doesn't work at all. So a little progress. In 7.0.3 no problem.

stack · March 30, 2017 at 9:36 PM

Quote from Henk50

I had nearly the same experience with a HP USB MCE. Sometimes a key will respond, or with a long delay. I deleted lircd.conf and Lircmap.xml and everything is working. I think still something wrong in 8.0.1. In 8.0.0 the remote doesn't work at all. So a little progress. In 7.0.3 no problem.

Since the Raspberry Pi uses a squash-fs for its / file system, how do you delete those files without recompiling the image?

Thanks!
~Stack~

**HiassofT** · March 30, 2017 at 10:10 PM

Quote from stack
[Edit]: Saw some interesting errors in the log files.
Code
mceusb 1-1.5:1.0: Error: urb status = -32

This could be the culprit. Please upload the full dmesg

Code

dmesg | paste

The majority of USB errors on RPi are caused by insufficient power supplies. Try another power supply and also check with the following command if an undervoltage condition has occurred

Code

vcgencmd get_throttled

It should print "throttled=0x0", if you got anything else please post the full output.

so long,

Hias

stack · March 30, 2017 at 10:42 PM

Quote from HiassofT
This could be the culprit. Please upload the full dmesg
Code
dmesg | paste

I turned off the device, so this is a fresh boot. Here is the link: BNMc

Quote from HiassofT
The majority of USB errors on RPi are caused by insufficient power supplies. Try another power supply and also check with the following command if an undervoltage condition has occurred
Code
vcgencmd get_throttled
It should print "throttled=0x0", if you got anything else please post the full output.

That is what I get:

Code

# vcgencmd get_throttled
throttled=0x0

Thanks!
~Stack~

Henk50 · March 31, 2017 at 1:02 PM

I use my own:
/storage/.config/lircd.conf
/storage/.kodi/userdata/Lircmap.xml

stack · June 6, 2017 at 3:48 AM

Sorry to drag this thread up again, however, a relevant update. Under 8.0.1 the remote sometimes works, sometimes doesn't. It's just been a so-low-priority that I never got around to figuring out why. I never got reliable behavior even when I tried making my own config files.

Well, today I had a bit of time to kill so i thought, why not attempt this again? The wife pretty much won't touch this if it has a keyboard, but will use the remote so it is worth getting it working again.

First thing I did, update to 8.0.2. I can't get it to work at all. Wipe the SD card, install 8.0.2 fresh. Nothing works. Not the defaults. Nor the /storage/.kodi/userdata/Lircmap.xml and /storage/.config/lircd.conf that I copied from another Kodi system (Ubuntu based) where this remote works perfectly. Nothing.

Let's try 7.0.3 again. Dang thing works right off the bat with ZERO modification!! So I absolutely know it isn't the hardware now!

Wipe the SD card again and slap 8.0.2 back on. Nothing. Nada. Zero. Zilch. Bupkis.

This last round I did *NOT* restore from a backup. Just made changes on my own hoping the defaults would fix it.

I used the interface to generate WMEb paste.

Any help getting this working would be appreciated. I'm 2 hours in tonight and the only thing that works is downgrading to 7.0.3.

What else can I try?

Thanks!

stack · June 15, 2017 at 12:55 AM

Edited first post for solution.