Summary:
This is fixed in kernel 3.17-rc1.
Detail:
Researching this for my daughter (Ruth Marsden) I've found this issue has been
known on the kernel mailing lists for sometime. See
http://www.spinics.net/lists/linux-input/msg29123.html.
The issue relates to touchpad devices using the ALPS v7
Workround provided from upstream dialogue - Thank you Aaron.
See http://marc.info/?l=linux-acpi&m=140686098023199&w=2
In summary:
Switching to use the "intel-backlight" interface rather than the "acpi_video0"
interface makes the controls for brightness work after suspend. This can be
done by
Reported upstream. See http://marc.info/?l=linux-
acpi&m=140658075422146&w=2.
As requested from upstream am attaching output from acpidump as
acpidump.txt
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4165307/+files/acpidump.txt
Christopher, Thank you for your guidance on this issue. I want to make
sure I report this upstream in the correct way and am unsure of which
upstream list I should be using.
https://wiki.ubuntu.com/DebuggingKernelSuspend mentions says "Suspend and
Resume use facilities within your BIOS called AC
I have tested against the kernel at http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.16-rc5-utopic/ and can confirm that the bug as reported
still persists.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags removed: kernel-bug-exists-upstream-3.16-rc4
** Tags added: ke
In answer to: "if you remove the kernel parameter elevator=noop does this
change anything?"
No it does not change anything. I tried with this kernel parameter removed on
the latest mainline upstream kernel 3.16-rc4.
As requested, tested on Precise 12.04.0 and 12.04.3 both obtained from
http://o
In answer to "did this problem not occur in a release prior to Trusty?":
I'm sorry, I don't know for sure. I only noticed the problem the day I
first reported it, however my behaviour regarding shutdowns rather than
suspends has recently changed so that may well be why I noticed it. My
wife hadn
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4148946/+files/Xorg.0.log
--
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/13380
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4148947/+files/Xorg.0.log.old
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4148945/+files/dmesg.txt
--
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/1338063
As requested I followed the steps in
https://wiki.ubuntu.com/DebuggingKernelSuspend.
Results are:
1. Information from sticker on computer:
Manufacurer: Toshiba
Model: Protege Z835-ST6N03
Part No: PT224U-01W00C
2. Bios is already upgraded to latest version 1.80.
3. Booted in mianline upst
Clarification:
I have gone back to older kernels on my machine to confirm my feeling
that this only started happening recently. The oldest kernel on my
machine is 3.8.0-31-generic. The problem also occurs with when booted
with this kernel so my feeling that this was recent is wrong.
I have edit
Installed latest upstream mainline kernel: 3.16.0-031600rc4-generic
Unfortunately this failed to solve the problem. Brightness control on
systems settings and via function keys works on initial boot but ceases
to work after a suspend, as before.
Thank you for your help.
** Changed in: linux (
Christopher, thank you for your advice and my apologies for not
following the protocol of first checking for BIOS updates.
I have now updated the BIOS. Results of "sudo dmidecode -s bios-version &&
sudo dmidecode -s bios-release-date" are:
Version 1.80
04/18/2013
so the update has worke
Upgrade to Ubuntu 3.13.0-30.55-generic 3.13.11.2 does not solve the
problem.
--
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/1338063
Title:
Brightness control lost after suspend screen di
Clarification:
Screen does not always come up dimmed after suspend. Screen comes up
with setting prior to suspend.
If the computer has gone into suspend itself after being unused for a
certain amount of time it comes up dimmed, even if not deliberately set
to this by the user. In these circumst
Public bug reported:
Using Ubuntu 14.04. Recently updated to kernel version Ubuntu
3.13.0-30.54-generic 3.13.11.2
I expect brightness of my LCD screen to remain the same and be
controllable after waking from suspend. It doesn't and isn't.
This seems to have only started recently - presumably a
17 matches
Mail list logo
