OK, if you don't have the keyboard any more, I guess it's too hard to
get the debugging data out of it. Thanks for your patience anyway!
** Changed in: udev (Ubuntu)
Status: Incomplete = Invalid
--
X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
On Monday 03 August 2009 22:37:42 Martin Pitt wrote:
So does it work with
ENV{ID_VENDOR}==MOSART_Semi., ENV{ID_MODEL_ID}==0102,
ENV{ID_CLASS}==mouse, RUN=+keymap $name usb-mosart-0102
?
Hi Martin,
sorry about the delay.
Unfortunately this does not solve the problem. xev still reports the
Am Sonntag, den 02.08.2009, 20:56 + schrieb Martin Pitt:
Is there a way to trace the whole sequence done during boot-up?
Something like this. udevadm test /devices/.../ (the sysfs path) will
show the matches and commands run.
# udevadm
test
Am Sonntag, den 02.08.2009, 20:59 + schrieb Martin Pitt:
Also, to get current data on this, can you please give me the output of
these commands:
udevadm info --query=all --name=/dev/input/event7
udevadm info --attribute-walk --name=/dev/input/event7
udevadm info --query=all
So does it work with
ENV{ID_VENDOR}==MOSART_Semi., ENV{ID_MODEL_ID}==0102,
ENV{ID_CLASS}==mouse, RUN=+keymap $name usb-mosart-0102
?
--
X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
https://bugs.launchpad.net/bugs/94366
You received this bug notification because you are a member
Argh, it would help if I wouldn't make typos in rules. Sorry for that!
Can you please try
sudo gedit /lib/udev/rules.d/95-keymap.rules
and in this line
ENV{ID_VENDOR}==MOSART_Semi., ENV{ID_MODEL_ID}==0102,
ID_CLASS=kbd RUN=+keymap $name usb-mosart-0102
add the missing comma after the kbd
Oops, another typo, it needs to be ID_CLASS==. Please replace the line
with
ENV{ID_VENDOR}==MOSART_Semi., ENV{ID_MODEL_ID}==0102,
ID_CLASS==kbd, RUN=+keymap $name usb-mosart-0102
Now for real!
--
X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
Am Sonntag, den 02.08.2009, 15:34 + schrieb Martin Pitt:
Oops, another typo, it needs to be ID_CLASS==. Please replace the line
with
ENV{ID_VENDOR}==MOSART_Semi., ENV{ID_MODEL_ID}==0102,
ID_CLASS==kbd, RUN=+keymap $name usb-mosart-0102
Now for real!
No luck. If I run the kbd
Is there a way to trace the whole sequence done during boot-up?
Something like this. udevadm test /devices/.../ (the sysfs path) will
show the matches and commands run.
Unfortunately the original lsinput/ udev dump logs don't match your
current USB setup any more (event7/event8), so I had to
Also, to get current data on this, can you please give me the output of
these commands:
udevadm info --query=all --name=/dev/input/event7
udevadm info --attribute-walk --name=/dev/input/event7
udevadm info --query=all --name=/dev/input/event8
udevadm info --attribute-walk
Am Dienstag, den 28.07.2009, 18:56 + schrieb Martin Pitt:
Hello Dominik,
ok, so it seems that something in the chain doesn't like the
extraordinarily high scan code. Could you please do
sudo strace -fvvo /tmp/keymap.trace /lib/udev/keymap input/event7 usb-
mosart-0102
and then
Hello Dominik,
ok, so it seems that something in the chain doesn't like the
extraordinarily high scan code. Could you please do
sudo strace -fvvo /tmp/keymap.trace /lib/udev/keymap input/event7 usb-
mosart-0102
and then attach /tmp/keymap.trace here?
Thanks!
--
X-Tension XK-200 Multimedia
Hi Martin,
the mute key now works, but the media key still returns config which
is translated to XF86Tools:
domi...@scaleo:~$ sudo /lib/udev/keymap -i input/event7
Press ESC to finish
scan code: 0xC0183 key code: config
scan code: 0xC0183 key code: config
Cheers,
Dominik
--
X-Tension
sudo cp usb-mosart-0102 /lib/udev/keymaps/
** Attachment added: keymap file
http://launchpadlibrarian.net/29224896/usb-mosart-0102
** Changed in: udev (Ubuntu)
Status: In Progress = Incomplete
--
X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
OK, I have a tentative fix for this. In current Karmic (daily live
system) or Jaunty with my PPA's udev-extras (see
http://martinpitt.wordpress.com/2009/05/08/devicekit-update-future-
handling-of-fn-key-maps/), please apply the attached patch with
sudo patch /lib/udev/rules.d/95-keymap.rules
** Changed in: udev (Ubuntu)
Importance: Wishlist = Medium
** Changed in: udev (Ubuntu)
Status: Incomplete = In Progress
--
X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
https://bugs.launchpad.net/bugs/94366
You received this bug notification because you are a member of
On Mo, 2009-06-29 at 10:57 +, Martin Pitt wrote:
Ugh, seems that input event enumeration changes severely with every
reboot. In the attached udev log and lsinput, event2 is the mouse. Can
you please attach lsinput output and then check with /lib/udev/keymap
which device outputs these keys
Ugh, seems that input event enumeration changes severely with every
reboot. In the attached udev log and lsinput, event2 is the mouse. Can
you please attach lsinput output and then check with /lib/udev/keymap
which device outputs these keys in the same session, i. e. without
rebooting in between?
** Package changed: udev-extras (Ubuntu) = udev (Ubuntu)
--
X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
https://bugs.launchpad.net/bugs/94366
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On Mi, 2009-06-24 at 06:06 +, Martin Pitt wrote:
Dominik,
seems these keys are on a different input device then. Can you please
just try all from input/event1 to input/event5? (it's most likely 4
then)
Yes, they were reported via the second event channel:
scan code: 0xC00B7 key
Dominik,
seems these keys are on a different input device then. Can you please
just try all from input/event1 to input/event5? (it's most likely 4
then)
--
X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
https://bugs.launchpad.net/bugs/94366
You received this bug notification
Dominik, thanks for the udev log. However, you still didn't tell me the
scan code of the key which is wrong. (See comment 7).
On current karmic, you can use sudo /lib/udev/keymap -i input/event3
to figure out the scan code. (See /usr/share/doc/udev-
extras/README.keymap.txt).
If you want to do
Martin,
I tried /lib/udev/keymap -i input/event3, but I don't get a keycode
displayed for the multimedia keys. Not even for those that do work as
expected.
Cheers,
Dominik
--
X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
https://bugs.launchpad.net/bugs/94366
You received this
No problem and sorry about the delay.
** Attachment added: udev
http://launchpadlibrarian.net/28208691/udev
--
X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
https://bugs.launchpad.net/bugs/94366
You received this bug notification because you are a member of Ubuntu
Bugs, which
Sorry for bothering you some more. The handling of keymaps changed
recently, and since this is an external keyboard, the usual system
vendor/product match does not work. I need to write a custom udev rule
for this external keyboard.
Can you please attach /var/log/udev?
** Package changed:
** Summary changed:
- Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard
+ X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
--
X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
https://bugs.launchpad.net/bugs/94366
You received this bug notification because
26 matches
Mail list logo
