linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Corentin Chary <corentin.chary@gmail.com>
To: Carsten Juttner <carjay@gmx.net>
Cc: Zhang Rui <rui.zhang@intel.com>,
	linux acpi <linux-acpi@vger.kernel.org>,
	platform-driver-x86@vger.kernel.org
Subject: Re: asus-wmi for Asus G73SW
Date: Mon, 11 Apr 2011 11:11:39 +0200	[thread overview]
Message-ID: <BANLkTik36UznNKUWHQNBcMBvQa96BsVGgg@mail.gmail.com> (raw)
In-Reply-To: <4DA1D998.9090501@gmx.net>

> By default the brightness values are set to 10 (max_brightness) but changing any of them does not do anything (display stays at maximum brightness level).
>
> Do you have an idea what could be missing?
[...]
> I used acpi_backlight=vendor and /sys/class/backlight/asus-nb-wmi shows up
> as expected.
>
> Also the kernel code that sets the brightness value in the asus-nb-wmi
> driver works (no error is returned, also the changed values show up in
> sysfs).
> It just does not seem to get applied.
>
> I found out that if after I switch to the console (alt+F1) changing the
> brightness in sysfs suddenly does have an effect.
>
> Since I use the proprietary nvidia driver (for full OpenGL 3D support) I
> suspect that it has something to do with it.
> I tried the Kubuntu Live installer CD which uses nouveau and changing the
> brightness works for Xorg there, too (even using the generic acpi_backlight
> code and the brightness value in acpi_video1).
>
> I guess the Nvidia driver or something related to it is doing something
> nasty here which keeps the brightness from being applied.
> Switching back to Xorg from the console resets the value to 10 (I added some
> debug output to update_bl_status) so that's not a workaround unfortunately.
>
> Since I have no idea what actual piece of hardware controls the backlight I
> wonder if it is part of the NVidia hardware and as soon as the nvidia driver
> takes over it will no longer accept updates from the BIOS?

Unfortunatly I didn't found anything in the DSDT.
CCing Zhang Rui, maybe he can help us here.

-- 
Corentin Chary
http://xf.iksaif.net

           reply	other threads:[~2011-04-11  9:11 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <4DA1D998.9090501@gmx.net>]

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=BANLkTik36UznNKUWHQNBcMBvQa96BsVGgg@mail.gmail.com \
    --to=corentin.chary@gmail.com \
    --cc=carjay@gmx.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).