>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 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? "hid_debug=1" is a module option on module "hid". If it is enabled and you plug in the device (or during startup), you should see a report similar to "kernlog.gz" from the original poster. It shows the key mappings from parsing the report descriptor and a descriptor hexdump. >It's a "noname" device. The website is here: http://www.pcpult.com.ua/en_index.html Funnily, this site claims that it works under Linux. Might have been before 2.6.25, when support for the 184 byte variant disabled the HID input mapping which is essential for your variant. Abovementioned patch resolves this for all variants. But even then those 2 vol keys should not have worked before, as they seem to need a separate quirk entry. >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 Binary. Try something like "hexdump /dev/hidraw" and note down which key event (press / release) triggered which hex bytes. Again, similar to what the original poster attached. @ticket admin: I am unsure whether tracking belongs into this or a new ticket. Original issue to be solved with patch in upcoming Linux 2.6.32. If other variants come up, we might never get this closed. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
