** Changed in: linux (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/326986
Title:
Key stuck with Samsung IR remote (USB 0419:0001)
--
ubuntu-bugs
Refactored 171b patch was applied upstream in the HID preintegration branch:
http://www.spinics.net/lists/linux-input/msg06276.html
--
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
Robert, good jobs, ubuntu kernel will have your fix after rebasing with
upstream kernel.
** Changed in: linux (Ubuntu)
Assignee: AceLan Kao (acelankao) = (unassigned)
--
Key stuck with Samsung IR remote (USB 0419:0001)
https://bugs.launchpad.net/bugs/326986
You received this bug
And for the 171b patch, Robert(rs), will you sent the patch to the
upstream kernel, or do you need me to send the patch?
I will baseline the 171 byte quirk fix to the new 2.6.32 kernel and
submit to the kernel list soon.
Unsure, whether you want to split this tracking off into a new ticket,
rs, did you send back your patches to the lkml?
--
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
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
Sounds good, we could help to push the patch to the upstream kernel, if the
author needs our help.
Besides, we could also cherry-pick the patch from upstream kernel to the karmic
kernel, so that you can have the fix on karmic.
The hash value of the 203b patch in the upstream kernel is
** 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
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
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
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) = ...
Please test the attached patch. It is on
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
** 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
** 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
** 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.
--
Please let me know if anything else is needed.
OK, just checked your attachments.
The volume keys are used from the consumer page.This array range looks
suspicious to me:
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x01 ] 1
I would rather try to
What daemons do you mean? What if I have the hid-samsung built in-
kernel, not as a module?
You need to have the usbhid driver disabled (and any daemons on top like
Lirc). If usbhid is a module, unload it via modprobe -r usbhid. If
built in, compile kernel without it or as module.
The same as
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
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
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.
Yet another 0419:0001 device. I already read about descriptors with 184, 203,
135, 199 bytes.
After patching my kernel with this patch
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: New = Triaged
--
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
Integrated into the HID kernel preintegration branch now:
http://www.spinics.net/lists/linux-input/msg03763.html
--
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
** Also affects: archlinux
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
This is not a bug in the linux-meta package, moving to the linux
package.
** Package changed: linux-meta (Ubuntu) = linux (Ubuntu)
--
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
For the remote, the patch works great. There is only one key not working, the
ENTER key, and that may be a problem with the device rather than the driver.
Great work!
Is there anything else I can do?
Very well. As said before, each key must be reported via one of the
reports from the
Sorry this took a while, but the graphics card does not like 2.6.29 -
I will have to figure that out at some point.
For the remote, the patch works great. There is only one key not
working, the ENTER key, and that may be a problem with the device rather
than the driver. Great work!
Is there
Thanks for the patch, I will try that once I have some time for it. And
I hope I can answer at least some of the questions:
- Precisely, which device was this?
Excellent question, but it is part of a media TV branded optronix (but
made by amazepc, at least the board), so I am not quite sure.
I have a Samsung IR remote that should work as a USB HID device. I need
to do some tweaking with modprobe options in /etc/modprobe.d/options to
get it recognised (see options), and then it mostly works.
OK, so you already performed some good preanalysis. Your quirk option
0x10 reenables the input
BTW, please doublecheck whether usage code 0224 is really contained
twice in the report descriptor. This looks very strange.
Also peculiar is that the logical maximum is claimed to be 18, but only
15 usages are provided. Maybe array indices 16..18 are generated, but
dropped due to missing usage
** Attachment added: fixing patch?
http://launchpadlibrarian.net/22301251/hid-core.patch
--
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.
--
** Attachment added: raw HID stream
http://launchpadlibrarian.net/22301257/hidraw.dump
--
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.
--
** Attachment added: sanitized/cooked HID stream (without patch)
http://launchpadlibrarian.net/22301275/hiddev-before.dump
--
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,
** Attachment added: sanitized/cooked HID stream (with patch)
http://launchpadlibrarian.net/22301276/hiddev-after.dump
--
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
** Attachment added: modprobe options (disable some of the quirks)
http://launchpadlibrarian.net/22301298/options
--
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
** Attachment added: kernel log: HID descriptor
http://launchpadlibrarian.net/22301280/kern.log.gz
--
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
** Attachment added: lsusb
http://launchpadlibrarian.net/22301307/lsusb-v.log
--
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
** Attachment added: xinput query-state when the key is stuck
http://launchpadlibrarian.net/22301318/xinput-query-state-3.log.gz
--
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
37 matches
Mail list logo
