kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

unggnu, 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>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. 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.11-rc5

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

** Tags added: needs-kernel-logs needs-upstream-testing

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

** Summary changed:

- Sony TX series and possible many other Sony laptops couldn't use the lowest brightness setting
+ Can't use the lowest brightness setting

-- 
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/117327

Title:
  Can't use the lowest brightness setting

Status in The Linux Kernel:
  In Progress
Status in “linux” package in Ubuntu:
  Incomplete
Status in “linux-source-2.6.22” package in Ubuntu:
  Won't Fix

Bug description:
  Sony TX series and possible many other Sony laptops couldn't use the lowest brightness setting because the default  sony_acpi.c restrict the lowest value to one instead of zero. This could save some energy so the difference between Linux and Windows isn't that high any more. I have always patched the sony_acpi.c on my own but since this module isn't integrated in linux.source anymore it is much more harder without recompiling the whole kernel. If there is any Sony laptop which haven't zero as the lowest value it should be no problem since a bug in /etc/acpi/sonybright.sh sets brightness on the lowest option to 33 (which is out of bound 0-8) instead of zero because of spicctrl which seems to have no impact.
  Of course the /etc/acpi/sonybright.sh of the acpi-support package have to be patched too.

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