Bug 1180258 - Brightness control no longer works on HP Envy 17
Summary: Brightness control no longer works on HP Envy 17
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: syslinux
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-08 17:36 UTC by bryant
Modified: 2015-12-02 17:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 07:05:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg output (89.57 KB, text/plain)
2015-01-08 17:36 UTC, bryant
no flags Details
laptop details (628 bytes, text/plain)
2015-01-08 17:37 UTC, bryant
no flags Details

Description bryant 2015-01-08 17:36:26 UTC
Created attachment 977862 [details]
dmesg output

First off, I didn't know what component this was for, so sorry about this. I would think it would be for the kernel, but I didn't see an option for that.

Description of problem:
Brightness controls for my HP Envy 17t-3200 no longer works for anything between full-brightnes and no brightness (the display stays on, just the backlight turns completely off). It previously worked under the Rawhide kernels I was pulling back in my Fedora 20 days a while ago (I switched during the first F21 alpha release).

Additionally, when resuming from sleep, the screen brightness is set to something about 50% or lower, where it's hard to use, and cannot be adjusted with the buttons.

The OSD for brightness works correctly and the backlight turns off when the brightness is turned all the way down, so it doesn't seem to be a keyboard issue. Though when looking at dmesg I get "Unknown key pressed" statements.


Version-Release number of selected component (if applicable):
Kernel 3.18.1-2


How reproducible:
Always

Comment 1 bryant 2015-01-08 17:37:08 UTC
Created attachment 977863 [details]
laptop details

Comment 2 bryant 2015-01-08 17:38:13 UTC
Additionally I do not have any brightness issues on Windows.

Comment 3 bryant 2015-01-08 17:55:58 UTC
Tried some various ACPI options, to no avail (all show that "radeon_bl0" is the only device under "/sys/class/backlight" as well):

acpi_osi=
acpi_osi=Linux
acpi_osi=Linux acpi_backlight=vendor
video.use_native_backlight=1

Comment 4 Christopher Beland 2015-04-28 20:58:56 UTC
The after-sleep probably may be separate - see Bug 1058083.

Comment 5 Fedora End Of Life 2015-11-04 12:17:48 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-12-02 07:05:59 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.