← Back to team overview

kernel-packages team mailing list archive

[Bug 340513] Re: Acpi brightness control fails

 

oCean, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux REPLACE-WITH-BUG-NUMBER

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc7

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** Package changed: acpid (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/340513

Title:
  Acpi brightness control fails

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: acpid

  acpid fails command lsmod (wrong path) and modprobe (incorrect usage)
  - see 'investigation' below.

  ubuntu: 9.04 (x86_64) vmlinuz-2.6.28-8-generic
  acpid: 1.0.6-9ubuntu4
  powernowd: powernowd-1.00-1ubuntu3
  hardw: laptop asus x71a

  1. SYMPTOMS

  * When booting, brightness falls back (all the way), special functionkeys (fn+f6) only work one-step: full brightness, or least brightness.
  * When logged in, brightness is full when on AC power, but brightness is all the way down when on battery power
  * Added brightness applet to panel. Initially, after login, slider is always all the way down. Moving works, with results ok, allthough screen flickers very much.
  * Also, after a period of time, when I'm considered 'idle', the screen should go less bright (powersave I guess) but it just flickers a little, and that's it. When I resume working, (going out of 'idle') again, screen flickers

  After boot, in dmesg output is:
  [    1.452296] pci 0000:00:02.0: Boot video device
  [   10.325975] asus-laptop: Brightness ignored, must be controlled by ACPI video driver

  2. PARTIAL WORKAROUND

  rmmod video -> results in brightness adjustment impossible
  modprobe video -> results in screen going to lowest brightness
  However, after the rmmod/modprobe, the brightness can be adjusted through fn+f6 keys

  3. INVESTIGATION

  * during startup:

  first:
  ACPI: expecting a [Reference] package element, found type c

  then:
  udevd-event (2260) exec of program /sbin/ failed
  --> this is the exact moment that brightness falls back (all the way)

  * then, lsmod errors in acpid startup:
  S10acpid: 113 /sbin/lsmod not found
  loading acpi modules...
  starting acpi modules...
  gives "modprobe usage" messages - failing to load module(s) ??

  * and also:
  powernowd: 180 /sbin/lsmod not found

  lsmod is actually in /bin. Creating link to /sbin/lsmod - then the
  acpid script returns no lsmod errors, but the "modprobe usage messages
  still appear.

  4. RELATED
  https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/210453
  * see also
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/313231
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/305935
  * and possibly
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/12637

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/340513/+subscriptions