Bug 1128740

Summary:	[Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
Product:	[Fedora] Fedora	Reporter:	Paul Lambert <eb30750>
Component:	linux-firmware	Assignee:	David Woodhouse <dwmw2>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	dwmw2, kernel-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-29 22:01:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Paul Lambert 2014-08-11 13:03:11 UTC

Description of problem:  ACPI initial brightness for laptops is not determined for laptops resulting in dmesg log error; [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness


Version-Release number of selected component (if applicable):
Fed 3.15.7-200.fc20.x86_64

How reproducible:
every boot

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
There are several previously reported bugs related to laptop brightness on bootup.  None were resolved.  These as well as my report are all most likely related to the firmware DSDT file not having an entry defined for "method _BQC" The fix for this is documented at this link;
http://cannibalcandy.wordpress.com/2011/02/18/dsdt-editing-put-an-end-to-your-acpi-woes/

This fix requires decompiling the DSDT file and adding the BQC definition and then recompiling.  This is most likely upstrem kernel task.  Rather than fix just my DSDT firmware configuration this bug needs to be fixed so that anyone with a laptop does not need to go through the same effort of modifying their DSDT file.  Additionally, there are a few other errors in the DSDT configuration that are detailed in this same link and should be addressed as well.

Comment 1 Fedora End Of Life 2015-05-29 12:36:37 UTC

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 2 Fedora End Of Life 2015-06-29 22:01:17 UTC

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.