Bug 675295 - Brightness unchangeable on Asus G53J
Brightness unchangeable on Asus G53J
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: kernel-module-thinkpad (Show other bugs)
14
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Jason Carpenter
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-02-04 14:51 EST by bruno.leiber
Modified: 2012-08-16 09:31 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-08-16 09:31:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description bruno.leiber 2011-02-04 14:51:09 EST
Description of problem:
Using nvidia driver, with a GTX460m. This laptop is the not-so-high grade G53J, with the screen : 1356x768@15.6''
On a fresh installation of FC14 with KDE, brightness controls works ( both fn keys and power manager appears as working, and everything seems okay in /sys/class/backlight/acpi_video0/ and /proc/acpi/video/GFX0/LCDD/, the values are okay and change accordingly).
However, in reality, brightness is stuck at approximately 75% of max luminosity, and will not change.
I also added the following section in /etc/X11/xorg.conf.d/00-system-setup-keyboard.conf :

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
Option "RegistryDwords" "EnableBrightnessControl=1"
EndSection

Before, when trying to increase brightness over approximately 75% resulted in the brightness moving back on forth around this value without being able to exceed it (on "paper", the brightness was also stuck in reality).

I found this bug : https://bugzilla.redhat.com/show_bug.cgi?id=646322

However, I cannot load thinkpad_acpi.

su -c 'modprobe thinkpad_acpi'
Password: 
FATAL: Error inserting thinkpad_acpi (/lib/modules/2.6.35.10-74.fc14.x86_64/kernel/drivers/platform/x86/thinkpad_acpi.ko): No such device

su -c 'modprobe thinkpad_acpi force_load=true'
Password: 
FATAL: Error inserting thinkpad_acpi (/lib/modules/2.6.35.10-74.fc14.x86_64/kernel/drivers/platform/x86/thinkpad_acpi.ko): Invalid argument


Version-Release number of selected component (if applicable):
nvidia driver version : 260.19.29
kernel : 2.6.35.10-74.fc14.x86_64


How reproducible:
Always


Steps to Reproduce:
1.Install FC14 on the same laptop.
2.
3.
  
Actual results:
Brightness cannot be changed.

Expected results:
Brightness can be changed.

Additional info:
Comment 1 Fedora End Of Life 2012-08-16 09:31:15 EDT
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

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

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

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