Hi Artur, Sorry for I am late to reply you. 於 三，2011-12-21 於 10:42 +0100，Artur Flinta 提到： > Hi Joey! > > On Wed, Dec 21, 2011 at 5:55 AM, joeyli <jlee@xxxxxxxx> wrote: > > Could you please help to enable acpi debug log? > > acpi.debug_level=0x2 acpi.debug_layer=0xFFFFFFFF > > > > Please attached dmesg and messages log that cover system boot and > > pressed brightness key a couple of times. > > Added debug parameters, restarted, after GNOME loaded pressed dozen of > times brightness shortcuts... logs in attachment. > 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. > > And, > > Please also monitor does there have any value of gpe was increased when > > you press brightness keys: > > > > watch -n 1 cat /sys/firmware/acpi/interrupts/gpe[012][0123456789ABCDEF] > > > > Please tell me which gpe's value increased if you found. > > Unfortunately none of values have changed (almost all stated 0, one 504). > hmm..... that mean the brightness function key does not emit acpi/wmi event. 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. 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
