Brightness controls only work after coming out of suspend

Bug #1132785 reported by Rainer Rohde
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
nvidia-common (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I've got an Asus G75VW laptop with an nVidia GTX660M video card.

After some tweaking of the xorg.conf file to include "Option "registryDwords" "EnableBrightnessControl=1"", I am able to use the Fn+F5 and Fn+F6 brightness control keys (and the brightness slider inside System Settings > Brightness and Lock), but ONLY after first going into suspend, and coming back out again.

The expected behavior should be brightness control working directly after a reboot, not rebooting and going into suspend first.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: nvidia-experimental-310 (not installed)
ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
Uname: Linux 3.8.0-7-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 313.18 Wed Jan 9 17:02:09 PST 2013
 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-21ubuntu3)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity.support.test.0:

ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Feb 25 06:51:23 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
DkmsStatus: nvidia-313, 313.18, 3.8.0-7-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation Device [10de:0fd4] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:2115]
MachineType: ASUSTeK COMPUTER INC. G75VW
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-7-generic root=UUID=e3421aae-fa91-41b0-a0fa-0b8291f791d1 ro elevator=noop quiet splash vt.handoff=7
SourcePackage: nvidia-graphics-drivers-experimental-310
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/07/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G75VW.223
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G75VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VW.223:bd01/07/2013:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: G75VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.9~daily13.02.19-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.42+git20130211.20c5607b-0ubuntu0sarvatt
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.0~git20130216.dd599188-0ubuntu0sarvatt
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.0~git20130216.dd599188-0ubuntu0sarvatt
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.99+git20130211.343b01c9-0ubuntu0sarvatt2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6+git20130107.8f934fad-0ubuntu0sarvatt
xserver.bootTime: Mon Feb 25 06:40:34 2013
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.13.2-0ubuntu2

Revision history for this message
Rainer Rohde (rainer-rohde) wrote :
affects: nvidia-graphics-drivers-experimental-310 (Ubuntu) → nvidia-common (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nvidia-common (Ubuntu):
status: New → Confirmed
Revision history for this message
Darlan Cavalcante (darcamo) wrote :

I have a similar model, the Asus G75Vx with the GTX670M card.
I'm only able to change brightness after suspending and with the Brightness and Lock app.

The buttons do not work and are not even reported by xev (even if I create a xorg.conf file with the Options - Yes, I restarted xorg after creating the xorg.conf file). But I think that is another bug. Changing the brightness without the need to suspend first, even if only through the Brightness and Lock app, is more important.

Revision history for this message
Rainer Rohde (rainer-rohde) wrote :

I can also confirm that this issue still persists, even after 13.04 got released. I am now on NVIDIA Driver Version: 319.17, and the behavior is exactly the same -- go into suspend, come out of suspend, and -- only then -- can the brightness can be adjusted.

Revision history for this message
Dani Louca (dani-louca) wrote :

Same issue, different laptop HP 8570w , Nvidia 319.23
After suspend , brightness control starts working.
Any tip on what call resume does to get this working?

Revision history for this message
Rainer Rohde (rainer-rohde) wrote :

Would be nice to hear something from the devs towards a possible fix. :)

Revision history for this message
Magnus Söderling (magnus-soderling) wrote :

I can confirm the issue on a HP 8570w with nvidia Quadro Q2000M and 313-updates driver, in my case brightness change pop up and slider moves but screen stays the same.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.