<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 4, 2015 at 10:27 AM, Kirk Bocek <span dir="ltr"><<a href="mailto:t004@kbocek.com" target="_blank">t004@kbocek.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On 9/4/2015 7:49 AM, Alec Leamas wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 04/09/15 16:24, Kirk Bocek wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
On 9/4/2015 1:50 AM, Alec Leamas wrote:<br>
</blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Here is a kernel oops. As long as this is with us, anything can<br>
happen. Now, the question is if you can reproduce this without your<br>
patches to mceusb.c. If so, this is a kernel bug which should be<br>
reported. If not, you need to find out (bisect?) which part of your<br>
patch which causes this.<br>
</blockquote>
<br>
This is all I added:<br>
<br>
/* Philips/Spinel plus IR transceiver for ASUS */<br>
{ USB_DEVICE(VENDOR_PHILIPS, 0x20cc) },<br>
<br>
Remove those lines from source file, recompile and reinstall and crash<br>
goes away. But IR instance goes away too. No /sys/class/rc, etc. No<br>
driver tree:<br>
</blockquote>
<br>
One question here is if the crash happens directly when the driver is loaded. If so, it should be easy to check by loading it on another box with different hardware. It's more complicated if you need the actual remote to trigger the crash.<br>
<br>
Still, we have finally got a clear cut problem with the current kernel code. Obviously, it's about the interaction between the mceusb driver, the kernel usb code, the actual physical device and perhaps also the actual (chip) driver used. However, this is above my paygrade. Unless someone else chimes in on this list, I guess you need to try the LKML. It's not always easy to get attention there, though. There is also a linux-usb list on <a href="http://news.gmane.org/gmane.linux.usb.general" rel="noreferrer" target="_blank">http://news.gmane.org/gmane.linux.usb.general</a>, perhaps it worth a try since the actual crash in in the usb code. Dunno, really.<br>
<br>
Of course, I (and I think a few others) would appreciate if you reported back here :)<br>
<br>
</blockquote>
<br>
I happen to have a Topseed receiver sitting right next to this Liva. And that ID *is* included in the source. So using my modified source:<br>
<br>
$dmesg<br>
...<br>
[ 7.468499] mceusb: module verification failed: signature and/or required key missing - tainting kernel<br>
[ 7.504062] Registered IR keymap rc-rc6-mce<br>
[ 7.504246] input: Media Center Ed. eHome Infrared Remote Transceiver (1784:0008) as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/rc/rc0/input7<br>
[ 7.504554] rc0: Media Center Ed. eHome Infrared Remote Transceiver (1784:0008) as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/rc/rc0<br>
[ 7.511510] IR NEC protocol handler initialized<br>
[ 7.514722] IR RC5(x/sz) protocol handler initialized<br>
[ 7.519599] IR JVC protocol handler initialized<br>
[ 7.522863] IR SANYO protocol handler initialized<br>
[ 7.524106] IR RC6 protocol handler initialized<br>
[ 7.531823] IR Sharp protocol handler initialized<br>
[ 7.531828] IR Sony protocol handler initialized<br>
[ 7.536244] IR MCE Keyboard/mouse protocol handler initialized<br>
[ 7.538649] lirc_dev: IR Remote Control driver registered, major 248<br>
[ 7.538999] input: MCE IR Keyboard/Mouse (mceusb) as /devices/virtual/input/input8<br>
[ 7.546432] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0<br>
[ 7.546439] IR LIRC bridge handler initialized<br>
[ 7.548881] IR XMP protocol handler initialized<br>
[ 7.641111] mceusb 1-2:1.0: Registered Topseed Technology Corp. eHome Infrared Transceiver with mce emulator interface version 1<br>
[ 7.641120] mceusb 1-2:1.0: 2 tx ports (0x0 cabled) and 2 rx sensors (0x0 active)<br>
[ 7.641196] usbcore: registered new interface driver mceusb<br>
<br>
<br>
Nothing from IRW. But ir-keytable:<br>
<br>
$ir-keytable<br>
Found /sys/class/rc/rc0/ (/dev/input/event7) with:<br>
Driver mceusb, table rc-rc6-mce<br>
Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC RC-5-SZ SHARP XMP other<br>
Enabled protocols: RC-6<br>
Name: Media Center Ed. eHome Infrared<br>
bus: 3, vendor/product: 1784:0008, version: 0x0101<br>
Repeat delay = 500 ms, repeat period = 125 ms<br>
$ir-keytable -t<br>
Testing events. Please, press CTRL-C to abort.<br>
1441379965.700583: event type EV_MSC(0x04): scancode = 0x800f04<br>
1441379965.700583: event type EV_SYN(0x00).<br>
1441379970.692471: event type EV_MSC(0x04): scancode = 0x800f84<br>
1441379970.692471: event type EV_SYN(0x00).<br>
1441379978.500329: event type EV_MSC(0x04): scancode = 0x800f84<br>
1441379978.500329: event type EV_SYN(0x00).<br>
<br>
It wasn't grabbed by usb-hid:<br>
<br>
$tree /sys/bus/usb/drivers/usbhid/<br>
/sys/bus/usb/drivers/usbhid/<br>
âââ bind<br>
âââ module -> ../../../../module/usbhid<br>
âââ new_id<br>
âââ remove_id<br>
âââ uevent<br>
âââ unbind<br>
<br>
Kinda feeling like a hardware incompatibility.<br>
<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://lists.mythtv.org/mailman/listinfo/mythtv-users" rel="noreferrer" target="_blank">http://lists.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<a href="http://wiki.mythtv.org/Mailing_List_etiquette" rel="noreferrer" target="_blank">http://wiki.mythtv.org/Mailing_List_etiquette</a><br>
MythTV Forums: <a href="https://forum.mythtv.org" rel="noreferrer" target="_blank">https://forum.mythtv.org</a><br>
</blockquote></div><br><br></div><div class="gmail_extra">It's a kernel thing, works fine under openelec, I just don't know what kernel version that they are using and what they have done to make things work. I have the same IR hardware receiver, plug it in and it just works with my Liva. Hopefully I will have some time and I can pull some information from the version that I have running.<br></div></div>