On Sun, Jan 22, 2012 at 21:37, Kay Sievers <kay.sievers@xxxxxxxx> wrote:
> On Sun, Jan 22, 2012 at 21:08, Kay Sievers <kay.sievers@xxxxxxxx> wrote:
>> On Sun, Jan 22, 2012 at 21:03, Tobias Frilling
>> <tobias@xxxxxxxxxxxxxxxxxx> wrote:
>>> Since the upgrade from 175 to 178 udev does not load the correct keymap
>>> file on my Samsung netbook.
>>> Keys like BrightnessUp/Down and a bunch of others do not work.
>>>
>>> The correct keymap is samsung-other and it should be loaded from
>>> 95-keymap.rules, line 141:
>>> ENV{DMI_VENDOR}=="[sS][aA][mM][sS][uU][nN][gG]*", RUN+="keymap $name
>>> samsung-other"
>>>
>>> $ cat /sys/class/dmi/id/{sys_vendor,product_name}
>>> SAMSUNG ELECTRONICS CO., LTD.
>>> N145P/N250P/N260P
>>>
>>> Manual loading of the keymap (# /lib/udev/keymap -i input/event0
>>> samsung-other) fixes the issue.
>>>
>>> Other users reported similar bugs, see
>>> https://bugs.archlinux.org/task/28049
>>
>> What does:
>> $ udevadm test /sys/class/dmi/id
>> say?
>
> And find the keyboard number X:
> $ grep . /sys/class/input/input*/name
>
> and run:
> $ udevadm test /sys/class/input/eventX
The test run shows that it would execute the keymap tool:
udev_rules_apply_to_event: RUN 'keymap $name samsung-other'
/lib/udev/rules.d/95-keymap.rules:141
...
USEC_INITIALIZED=8199737
run: 'keymap event0 samsung-other'
If you run '/lib/udev/keymap event0 samsung-other', does it work?
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
