[Bug 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
>From what I can see, patches for all the devices, discussed here (except of 171 one), are in 2.6.32 release. I hope to see the 171 device (which is actually the one I have) in the later releases. -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
** Attachment added: "test %" http://launchpadlibrarian.net/35788912/1%2520 ** Attachment removed: "test %" http://launchpadlibrarian.net/35788912/1%2520 -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
Thanks a lot! Works perfectly with kernel 2.6.31. -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
I am attaching the full dmesg output. For some reason, it does not output all the data upon initial plugging in the device, but if you then plug it out and plug in again - you'll get the whole picture including report descriptor (size 171, read 1) = ... So, I believe the attached is what you asked for. By the way, "kernel log: HID descriptor" attachment from initial poster is not readable for me, even unpacked. How can it be read and how to create such a dump? ** Attachment added: "full_dmesg" http://launchpadlibrarian.net/35474987/full_dmesg -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
** Attachment added: "hidraw output" http://launchpadlibrarian.net/35436414/hidraw -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
** Attachment added: "lsusb" http://launchpadlibrarian.net/35436398/lsusb -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
** Attachment added: "dmesg output upon plugging in the device" http://launchpadlibrarian.net/35436363/dmesg -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
OK, I managed to gather all the logs you suggested (or at least I think so). The first is the dmesg output upon plugging in the device. See the dmesg attachment, it describes all the steps I took. The second is the lsusb -v output. This output was got with hid, usbhid and hid_samsung modules _unloaded_ And the last is cat /dev/hidraw1 upon pressing the volume keys (hidraw attachment). The problem here is that every other key on the remote, when pressed, except the volume ones, results in two lines of code in console on cat /dev/hidraw1 (from what I understand, the first line is key press code, the second is key release code). The volume keys result only one line of code (the press code only), that is why they stuck. So, the hidraw attachment shows two codes: the first is vol down key press, the second is vol up key press. The freaky symbols '^@' are produced because the keys are actually stuck. Please let me know if anything else is needed. -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
I am attaching the output of lsusb -v for my device. >If the report descriptor is shown as unavailable The report descriptors are indeed shown as unavailable, but I am not sure how to proceed with your further instructions. >you might need to unload any daemons or even the hid module. What daemons do you mean? What if I have the hid-samsung built in-kernel, not as a module? >Alternatively, load the HID kernel module with the debug option enabled -- >similar to the original poster above. The same as above: what if I have the hid-samsung built in-kernel, not as a module? I have hid_debug enabled (in-kernel also). How do I dump the debug log? >Brand/device info of this remote would be interesting It's a "noname" device. The website is here: http://www.pcpult.com.ua/en_index.html >Probably /dev/hidraw output for vol keys would also be interesting (w/o the >workaround patch). Not sure if that is what you need, but did a cat /dev/hidraw* and the output in the console while pressing the volume keys was just a mess like this: ^...@^@^...@^@^...@^@^...@^@^@ ** Attachment added: "lsusb -v" http://launchpadlibrarian.net/35352482/lsusb -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
I've got a similar device. Bus 004 Device 002: ID 0419:0001 Samsung Info. Systems America, Inc. IrDA Remote Controller The wDescriptorLength for it is 171. After patching my kernel with this patch http://launchpadlibrarian.net/25472216/samsung203b-2.6.29.patch the device works fine, except of two keys: Volume Up and Volume Down. When pressing any of these 2 keys, they stuck with the code of Volume Down key (I was investigating it with the showkey command). Then i applied this patch http://launchpadlibrarian.net/22301251/hid-core.patch This fixed key stuck, but another problem rose: now only the Volume Up key works. Volume down does not at all, at least # cat /dev/hidraw* does not show anything when pressing Volume Down. As I mentioned, the device has a descriptor 171, which is something new (it is not listed in the patch http://launchpadlibrarian.net/25472216/samsung203b-2.6.29.patch, though it works when applying it). I'm eager to help if any additional info is needed. ** Also affects: gentoo Importance: Undecided Status: New -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
