From: joeyli <jlee@suse.com>
To: Artur Flinta <aflinta@gmail.com>
Cc: linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: Fwd: [Bugreport] Screen backllight issues on FirePro M5950 (HP EliteBook 8560w)
Date: Sun, 22 Jan 2012 09:45:27 +0800 [thread overview]
Message-ID: <1327196727.15960.118.camel@linux-s257.site> (raw)
In-Reply-To: <CAEPe-G+H6CDDzg9-fXZK4MJbKw_-MJFSMheCL9=yN4Gt=fmaTQ@mail.gmail.com>
於 五,2012-01-20 於 22:38 +0100,Artur Flinta 提到:
> Hi Joey!
>
> On Fri, Jan 20, 2012 at 4:35 AM, joeyli <jlee@suse.com> 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
next prev parent reply other threads:[~2012-01-22 1:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 20:34 [Bugreport] Screen backllight issues on FirePro M5950 (HP EliteBook 8560w) Artur Flinta
[not found] ` <CAGB3EUR750VpHdvrZ25mn9bcS-4ZT+BSJ_zD4-sRncyYNT=0Zg@mail.gmail.com>
2011-12-09 14:54 ` Fwd: " joeyli
[not found] ` <CAEPe-G+iooX_BOD=5m1nMgn+t63XGsLR+4JCfvHKOyTx98qydg@mail.gmail.com>
2011-12-21 4:55 ` joeyli
2011-12-21 9:42 ` Artur Flinta
2012-01-20 3:35 ` joeyli
[not found] ` <CAEPe-G+H6CDDzg9-fXZK4MJbKw_-MJFSMheCL9=yN4Gt=fmaTQ@mail.gmail.com>
2012-01-22 1:45 ` joeyli [this message]
[not found] ` <CAEPe-GKff7y1g4qc5gSz4vuhz5P0XpGgPTO570YzkjO6AZNV4A@mail.gmail.com>
2012-01-22 23:55 ` joeyli
[not found] ` <CAEPe-G+jNsa5VScrk-Nii2e=0U5bVWtcCT5apOy0BAJrjKri4Q@mail.gmail.com>
2012-01-24 0:58 ` joeyli
[not found] ` <CAEPe-GLe9d7V9YLq+gGpb8N+a-9ELzeuvLbr=gKFbWU4JJxV-Q@mail.gmail.com>
2012-01-25 1:52 ` joeyli
2012-01-26 6:43 ` Artur Flinta
2012-01-26 16:40 ` joeyli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1327196727.15960.118.camel@linux-s257.site \
--to=jlee@suse.com \
--cc=aflinta@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.