於 五，2012-01-20 於 22:38 +0100，Artur Flinta 提到： > Hi Joey! > > On Fri, Jan 20, 2012 at 4:35 AM, joeyli <jlee@xxxxxxxx> wrote: > > Sorry for I am late to reply you. > > No problem :) > > > Looks like the acpi debug level not enough, please kindly change acpi > > debug parameter to: > > acpi.debug_level=0xF acpi.debug_layer=0xFFFFFFFF log_buf_len=5M > > > > And, please remember press brightness function key a couple of times > > before you dump the dmesg and messages log. > > Cause the brightness function key does not emit acpi/wmi event I'll > skip this step. > OK > > Please help to check the raw scan code from the function key: > > > > + please add kernel parameter atkbd.softraw=0 to /boot/grub/menu.list > > + please switch to console 1, then run: > > showkey -s > > > > Press backlight function key and look at maybe have scan code capture by showkey. > > Brightness increase: 0xe0 0x54 0xe0 0xd4 > Brightness decrease: 0xe0 0x4c 0xe0 0xcc > > Regards > Artur > #define KEY_BRIGHTNESSDOWN 224 #define KEY_BRIGHTNESSUP 225 Suggest you can try to run the following command before run X-windows: setkeycodes e054 224 setkeycodes e04c 225 If it works, then we can add the above rules to udev keymaps. Thanks a lot! Joey Lee -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
