[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
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:
Expired
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
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
