Lenovo is quite a different working site. You can try
acpi_backlight=vendor on the grub command line, plus
options thinkpad_acpi brightness_enable=1
somewhere in /etc/modprobe.d
Though if that does not help, please open another bug as the solution
needs a different approach than for the Acers.
Here's my dmidecode output. I experienced wrong value change with
brigthness too, but it's a start
** Attachment added: demidecode.txt
http://launchpadlibrarian.net/29678660/demidecode.txt
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received
I am running kubuntu 9.10 alpha 3 on Lenovo 3000 N100 and I can't change
the brightness of the screen.
When trying to change it using the fn keys, dmesg says:
ACPIFailed to switch the brightness
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You
I reported that partial success back. To get that into Jaunty I need to
come up with a patch that only matches specific laptops. Can you post me
the output from your sudo demidecode, please?
For the strange behavior of the keys: Was this happening before as well
or only with the never kernels? I
Doh, it seems there was another check somewhere else to prevent getting
to the other check. I changed that as well and made a v3 version. I hope
this was the last place which restricts the stuff from working.
--
Cannot change brightness with 2.6.27-11+ kernel
@Stefan Bader
I'm glad to inform you that now brightness *DO* react to brightnessup and
brightnessdown scripts (/etc/acpi/video_*
) and seems fixed. The second check was the problem, definitely =).
Also brightness gnome applet and brightness gnome control (as gnome panel
add-on) wok well.
the v2 versions of kernel posted at
http://people.ubuntu.com/~smb/bug86/ does not seem to change
anything in brightness control (*unfortunately*).
please find attached the DMESG output with modified kernel. let me know
if I can help you anyhow.
** Attachment added: dmesg output
gidantribal wrote:
I updated the bios to 1.14 (last) version. NO effects on brightness.
Attached you can find lspci output.
Thanks for confirming that this has no change. Did you see my post with the
test kernel? This has a good chance of getting your brightness working again
and it would be
I updated the bios to 1.14 (last) version. NO effects on brightness.
Attached you can find lspci output.
** Attachment added: sudo lspci -vvvnn
http://launchpadlibrarian.net/29207119/lspci
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received
After talking with Matthew about this, there probably is a way to relax
the check for available video devices. I added those changes and build a
test kernel which can be found at
http://people.ubuntu.com/~smb/bug86/ (the v2 versions). Maybe you
could try to install this kernel and see whether
this sounds really bad... as far as I understood, there's supposed to be
a bug on acer bios? that sounds quite bad... is it possible kernel code
that discriminates the right PCI device is buggy? isn't it possible to
perform any action but a simple workaround?
--
Cannot change brightness with
I believe the BIOS is buggy with that respect (not sure why the DSDT compiler
freaks out but that might be a different issue). I manually looked up those
values in the DSDT you provided, so based on that data the kernel takes the
right steps. The question is whether the new BIOS fixes this or
I can understand that. No it makes no difference from which kernel this is run.
To be exact, it was somehow working as Linux did not check the information in
the DSDT close enough. So GFX0 might be the right device to look at but it
points to another pci device (supposedly one that does not
Ok, I can post the results, does it make the difference if I post results
from the 'normal' distribution and not from yours (modified)? That's so
weird, so previously it was working because no programmatic check was done
by DSDT? I agree, new bios should be tried, but since it's a critical step
Hm, with that info I understand what is going on. But I cannot see how Linux
could safely make this working. The problem is that graphic devices are
detected by certain methods in the ACPI BIOS. From all available alternatives
only _DOS and _DOD methods are defined for the GFX0 device. So far,
@Stefan Bader:
Okay, now i'm posting all DMESG output with your modified kernel version.
Please let me know what else do you need.
** Attachment added: Dmesg output
http://launchpadlibrarian.net/28628061/output_dmesg.txt
--
Cannot change brightness with 2.6.27-11+ kernel
The option suggested by Stefan did not work for me. So I will make a new
bug report.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
An update.
I was using the nvidia proprietary driver. After removing this driver
and instead using the open source driver, the brightness control works.
I would still want to use the nvidia driver as the open source driver
does not give me the full resolution. Seems my case is similar to
@gidantribal, Err, sorry, my fault of not being specific enough. The
acpidump dumps your ACPI BIOS, so it will remain the same, regardless of
the kernel. What I was interested in was the dmesg output which contains
the messages from the boot.
@Jaya, while the effects are similar, I'd like to keep
Thanks for the suggestions, I will try setting the kernel command line.
I found another solution that worked for me. With my nvidia driver enabled, I
tried running the script from,
http://www.thouret.co.uk/blog/2008/12/shell-script-for-linux-nvidia-kernel-module-laptop-brightness-workaround/
It doesn't help with our acer's, I've just tryed, so It should not be
classified as a duplicate.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the same problem with Lenovo Ideapad Y450 laptop. With Jaunty
Live CD, the brightness control worked. But after installation and
update, it doesn't wok anymore. The file
/proc/acpi/video/VGA/LCD/brightness is updated with the Fn+arrow_keys,
but the bightness just don't change.
If any input
Here you can find attached the requested output of 'acpidump' from your
modified kernel image.
Linux gidan-notebook 2.6.28-13-generic #44bug86v1 SMP Wed Jun 24
10:29:48 CEST 2009 x86_64 GNU/Linux
** Attachment added: AcpiDump output
http://launchpadlibrarian.net/28417814/acpidump.txt
--
@gidantribal, no, that would require to know what to change. So far I know the
in the working kernels, there was a GFX0 object in /proc/acpi/video (and likely
that hat the brightness control). The acpidump shows that there should be the
required methods to detect the brightness control
ok i will test them asap...
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
FYI, 2.6.28-13-generic x86_64 kernel didnt solve this issue yet.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Please let me know if I can help debugging this, or provide more
information. This problem also exists on a Thinkpad T61. Just can't seem
to change the brightness. Period.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification
The same here..it's one of the worst bug I'm affected... I still have to
switch to *vista* just to change brightness... it's a shame... :\
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of
from a custom 2.6.30-rc8 kernel in Xorg.0.log:
(WW) NVIDIA(0): ACPI: Error: Unable to find the DOS (Enable/Disable output
(WW) NVIDIA(0): switching) file path under /proc/acpi/video. The NVIDIA X
(WW) NVIDIA(0): driver will not be able to respond to ACPI display change
(WW) NVIDIA(0):
@Marc-André Turcotte :
I don't know what you want to point out exactly. We already know brightness
works under kernel 2.6.27-4-generic and doesn't under jaunty 9.04 (i.e.
kernel 2.6.28-11). if we don't fix this bug it will not be solved in any kernel
2.6.28-11 ...
--
Cannot change brightness
@gidantribal:
It was more to state that it was not fixed in that one. I'm trying to give the
more information I can.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Marc-André Turcotte:
I thought it was to point out brightness problem was related to nvidia drivers.
My fault, sorry.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is
If you can also provide the same data for a working case (either with a
kernel from https://wiki.ubuntu.com/KernelMainlineBuilds or with the
last working kernel) this would help to determine which part broke (and
maybe got fixed upstream).
--
Cannot change brightness with 2.6.27-11+ kernel
Okay, I'm providing required data from WORKING, LIVE version of Ubuntu 8.10:
__
uname -a:
Linux ubuntu 2.6.27-4-generic #1 SMP Wed Sep 24 01:29:06 UTC 2008 x86_64
GNU/Linux
__
cat /sys/devices/platform/acer-wmi/interface:
WMID
** Attachment added: acpi directories
http://launchpadlibrarian.net/27728562/locate_acpi.txt
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: 'brightness' directories
http://launchpadlibrarian.net/27728575/locate_brightness.txt
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Now _that_ is a step forward! Stupid me. So not the wmi driver is
broken. It was not used before. But the acpi driver does not handle the
laptop anymore. Ok, one more thing then. Regardless from which kernel.
Please add the output of sudo acpidump -o acpidump.txt. Thanks.
--
Cannot change
Ok, attached you can find the requested output.
Please note this is from *NON WORKING* 9.04 kernel img (Linux gidan-notebook
2.6.28-11-generic x86_64 GNU/Linux).
** Attachment added: Output from acpidump
http://launchpadlibrarian.net/27762116/acpidump.txt
--
Cannot change brightness with
Accepted linux into intrepid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
Which package?
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Accepted linux into intrepid-proposed, the package will build now and be
available in a few hours.
Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you in advance!
I tried to install the
Accepted linux into intrepid-proposed, the package will build now and be
available in a few hours.
Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you in advance!
I tried to install the
I am currently travelling, so responses can be slow.
cat /sys/devices/platform/acer-wmi/interface:
WMID
Thanks, so that rules out the other interfaces.
How to test which sysfs interface is working? i'll download a liveCD and
try...
When, using the Intrepid liveCD, brightness control
I don't know what you mean with 'elusive' problem. To replicate it you
just need an Acer Aspire 6920G or 6930G (my friend has the same problem)
and a FRESH installation of Jaunty 9.04 x64. And here we posted
everything asked...
As said before, in kernel 2.6.27-9 everything worked fine,
gidantribal wrote:
I don't know what you mean with 'elusive' problem. To replicate it you
just need an Acer Aspire 6920G or 6930G (my friend has the same problem)
and a FRESH installation of Jaunty 9.04 x64.
This is the first problem. I do not have one. I only got an Acer Aspire One
for which
Thank you for the quick reply. I'll try my best to get rid of this
bug...
cat /sys/devices/platform/acer-wmi/interface:
WMID
Like: was the sysfs interface working whith
2.6.27-9 or was something else in control. Wouldn't a live-cd run work? This
should be 2.6.27-7. That would safe you the hassle
** Also affects: linux (Ubuntu Intrepid)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jaunty)
Importance: Undecided
Status: New
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification
Setting this to fix-commited for Intrepid for the acer-wmi fix regarding
the inverted logic. There still are those problems on Jaunty. Still have
to sort out the problems on Jaunty.
** Changed in: linux (Ubuntu Intrepid)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu Intrepid)
@gidantribal,
the problem is still a bit elusive. The things you see on Jaunty sound
like the laptop is not responding to the wmi-calls. I think you said
this works on a vanilla 2.6.27 version. Does this also work on a vanilla
2.6.28 or .30? In any case I would be interested if you could check
Hey guys, is there any news concerning this bug? I still have crazily to
*fakely* switch to Vista to change startup brightness... It's really
annoying and a waste of time... moreover my eyes are suffering for this
problem.
--
Cannot change brightness with 2.6.27-11+ kernel
yes, all values are 9 by default.
if i do
echo 4 brightness
laptop brightness isn't affected, brightness file changes to 4, but
actual_brightness file keeps 9 value.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification
Yeah, sysfs has a lot of recursion. So that confirms the wmi driver is at least
registering itself. The interesting variables would be actual_brightness,
brightness, max_brightness and maybe bl_power.
From one of the earlier posts, I take it that all values are 9. And even if
you sudo -i and
ls -la /proc/acpi/video:
totale 0
dr-xr-xr-x 2 root root 0 2009-04-25 14:12 .
dr-xr-xr-x 11 root root 0 2009-04-25 14:06 ..
ls -la /sys/devices/platform/acer-wmi/backlight:
totale 0
drwxr-xr-x 3 root root 0 2009-04-25 14:06 .
drwxr-xr-x
Let me try to give more information. The big problem with backlight control is
that there are many ways to do it. There is a generic implementation in the
acpi subsystem and then there are several vendor specific drivers that do the
same with all the different interfaces vendors came up with.
I don't a working kernel anymore but what would happen if we copied file
from /proc/acpi/video of a working kernel into a non-working one, where
these files are non-existing?
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug
maybe it will not change anything since kernel has not reference to
them? no idea, btw...
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Marc-André Turcotte wrote:
I don't a working kernel anymore but what would happen if we copied file
from /proc/acpi/video of a working kernel into a non-working one, where
these files are non-existing?
That would not help/work. The proc filesystem is a virtual filesystem that
reflects kernel
found another repport for the 6920g, which one should be marked as duplicate of
which one?
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/344640
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification
the last report you posted is not related to our issue. it's about
applet problems, not really about ACPI problem itself... in our case it
doesnt work even from command line :\
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug
Sorry, I have just read that bug's EDIT:
EDIT: Now (after ~150MB of updates) on-screen notification for
brightness works (as respons to Fn + and ), but nothing happens with
actual brightness level... Hope you'll fix it soon
it seems to be our problem reflected to jaunty. that's why i am sure
It worked in intrepid with kernel 2.6.27-7 and -9 and stopped at
-11(never tried -10). I don't know for i386. We have limited bandwidth,
i'll download the i386 live cd on the 25th when our month start over
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
@Marc-André Turcotte: Ok, definitely we have the same defect (completely
overlapped). Hope we will get rid of it.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Marc-André Turcotte: then let me understand.. with jaunty live cd x64
brightness is not solved at all. But I don't know if it is the same with
i386 Jaunty? Did you get any working recent distribution?
@unclben: I'm happy it worked for thinkpad.. I know linux team was
working on Thinkpad problems
@unclben have you got an acer 6920G? How can it be possible mine
doesn't still work on Jaunty beta? Maybe it's because mine is a x64
distribution? By the way it soulds quite weird!!! By the way i tried
only by applet, maybe i should try directly by commands...
--
Cannot change brightness with
If I'm right, maybe we are missing something that get's installed with
jaunty. We upgraded to jaunty, so we may miss some package. Maybe a
clean install would solve this. I have the beta jaunty live cd 64x
somewhere on my desktop. I'll try tonight to see if it's 64bit related.
--
Cannot change
Found that bug which is close to ours:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/280518. I don't
know if it's a real duplicate, I'll let someone who knows what he's
doing mark it.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received
Brightness doesn't change on my beta jaunty 64x livecd. There was a
message telling that it did, but nothing really happened.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs,
@gidantribal: See earlier in this bug report. I have a ThinkPad X61s,
but I was having the same problem as Marc-Andre. I'm currently running
the generic 2.6.27-19 kernel from the mainline kernel PPA, which solved
the problem for me.
--
Cannot change brightness with 2.6.27-11+ kernel
First, no we do not give up on this, but things can get delayed by the
bulk of other things.
@gidantribal, I saw that the test kernel did not help (or made things
worse?). Could you post the dmesg from that kernel and 'grep -r .
/proc/acpi/video'. Is the brightness changing when changing the
In the 2.6.29-1 mainline kernel, on jaunty, grep -r ./proc/acpi/video
gets stuck. I looked in that folder and there is no file in it. For he
dmsg part, i' not sure what I have to do, but raising or lowering the
brightness didn't change the output of dmsg
--
Cannot change brightness with
Marc-André Turcotte wrote:
In the 2.6.29-1 mainline kernel, on jaunty, grep -r ./proc/acpi/video
You need the space between . and /proc/acpi/video otherwise the grep won't
work. The . is the search argument.
gets stuck. I looked in that folder and there is no file in it. For he
If there are
grep gave me nothing like you said. Here's the dmesg log.
In the acer-wmi folder, there's only: a link to device folder, power
folder, a link to subsystem folder, and 5 files I cannot read with
gedit: actual_brightness, bl_power, brightness, max_brightness, uevent.
Is there another way you think
Marc-André Turcotte wrote:
gedit: actual_brightness, bl_power, brightness, max_brightness, uevent.
Is there another way you think I could write something in these files?
Did you try cat to read and echo value file to write? (It can be possible
you have to get root with sudo -i before
cat works( you're making me learn very usefull command thanks) with
everything but uevent and the output is like it should, but echo says
permission denied for actual_brightness and max_brightness (I tried 1
for each) even under root. There was no brightness modification in the
process
--
Cannot
echo x filesays permission dedied even in ubuntu 8.10 (for each
file). Values are all set to '9'.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
echo x filesays permission denied even in ubuntu 8.10 (for each
file). Values are all set to '9'.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
bl_power gave me 0. Add sudo before it, or to be sure log in as root (
sudo su or sudo -su) to take out some permission denied
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs,
FWIW, I loaded up the Jaunty Beta i386 LiveCD (well... on a USB stick)
and brightness now works perfectly on my laptop.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I placed test kernels (for Intrepid -proposed) to
http://people.ubuntu.com/~smb/bug86/. Could someone try that version
and verify that this enables brightness again?
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification
I tested your kernel (x64) and as result i just can't get even the
applet animation working. no news in brightness control either...
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
I'm in jaunty right now, and 2.6.28-11 (output of uname -r, but not on
kernel.org?!) doesn't work too. the brightness applet shows it raise and
goes down, but there's no change on the screen
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received
Same thing in 2.6.29-1. I forgot to add last post that the key to raise
the brightness doesn't send ± anymore
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I tested mainline kernel 27-19 and
brightness control WORKS again, sending the ± when is enhancing.
By the way I can't use mainline kernel since i have restricted drivers
to use :\
Jaunty-beta3: doens't solve anything, only applet works again.
--
Cannot change brightness with 2.6.27-11+ kernel
@Marc
It's bad Jaunty-beta3 doens't solve the issue. Are they giving up
solving this issue for our pc?
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Marc
It's bad Jaunty-beta3 doens't solve the issue. Are they giving up
solving this issue for our pcs?
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm still pretty new to linux, but first I would say that since it
works again in 27-29, it should someday in the 28 series also. I don't
really understand what's the problem with restricted drivers and a
mainline kernel since sound and compiz effects worked with no problem
when I tried. Maybe
I have a problem with NVIDIA drivers and mainline kernel. It is also
written in limitations that restricted drivers will not work...and
that's what happened to me.
Did you try Jaunty and brightness worked? You said in your previous
posts that:
I'm in jaunty right now, and 2.6.28-11 (output of
I tried installing the generic 2.6.27-19 mainline kernel as provided by
the kernel team (https://wiki.ubuntu.com/KernelMainlineBuilds - even I
can install a .deb!). Brightness changes work like a charm. I wish a
developer would chime in and let us know if/when we'll get a newer
kernel, since this
** Changed in: linux (Ubuntu)
Sourcepackagename: None = linux
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I managed to compile the 2.6.27-19 kernel with patch and the brightness
adjust works again. I ran into a error with the image file but it seems
to work anyway.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you
Any idea when 2.6.27-16 or newer will make it into Intrepid? I'm not
comfortable compiling my own kernel.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have no idea, but i think there's an update each week.
--
Cannot change brightness with 2.6.27-11+ kernel
https://bugs.launchpad.net/bugs/86
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can confirm this on my ThinkPad (dmidecode outputs below).
Lenovo
7668CTO
ThinkPad X61s
The laptop is only a few days old. When running the Intrepid Live CD
(which I assume is an older kernel than 2.6.27-11), backlight control
worked fine. Since installing and updating to current kernel,
I've just looked at the changelog for the 2.6.27 kernel, and there's no
mention of brightness in patch 10 and 11. Maybe something completely
different is interfering. There seems to be some patch with brightness
in the patch 15 and 16. For an unknown reason I can't compile kernels,
but if you can
94 matches
Mail list logo
