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: Wed, 25 Jan 2012 09:52:34 +0800 [thread overview]
Message-ID: <1327456354.15260.1.camel@linux-s257.site> (raw)
In-Reply-To: <CAEPe-GLe9d7V9YLq+gGpb8N+a-9ELzeuvLbr=gKFbWU4JJxV-Q@mail.gmail.com>
於 二,2012-01-24 於 16:25 +0100,Artur Flinta 提到:
> Hi!
>
> > Thanks, but looks like your kernel didn't enable
> > CONFIG_ACPI_DEBUG=y
> >
> > So, doesn't show up any acpi debug log in messages.
>
> Fixed, now using kernel-debug package ;) Quite huge in attachment.
>
I just found the _BCM in your SSDT3 table, I am tracing it:
Method (_BCM, 1, Serialized)
{
Store (\_SB.BCM, Arg0)
Local0
If (Local0)
{
Store (BRID, Local1)
If (LEqual (SBRV (), 0x00))
{
\_SB.SSMI (0xEA74, 0x04, Local1, 0x00, 0x00)
}
Signal (\_SB.BEVT)
}
}
> > Does it work set backlight level by sysfs?
> > echo 9 > /sys/class/backlight/acpi_video0/brightness
>
> if kernel is booted with acpi_backlight=vendor parameter, then there
> are no entries in /sys/class/backlight directory.
>
OH! you are right, sorry I forgot it.
Thanks a lot!
Joey Lee
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-01-25 1:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEPe-G+b9U-vdDmU29=GjyABab=5-MzWm4U6pBj1upRgLjH1OQ@mail.gmail.com>
[not found] ` <CAGB3EUR750VpHdvrZ25mn9bcS-4ZT+BSJ_zD4-sRncyYNT=0Zg@mail.gmail.com>
2011-12-09 14:54 ` Fwd: [Bugreport] Screen backllight issues on FirePro M5950 (HP EliteBook 8560w) 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
[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 [this message]
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=1327456354.15260.1.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox