brightness keys don't work on HP 8710w laptop when using nvidia driver

Bug #207641 reported by Jay Finger
4
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.24 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I am using an HP 8710w laptop that has an NVidia Quadro 1600M 512M video card built in, and have just installed the Hardy Beta x86 desktop CD.

When using the keyboard brightness controls, the brightness does not change. Note that the keys are working, because I can see the little on-screen notification that shows brightness going up and down. It's just that the actuall display brightness does not change.

The problem started when I activated the NVidia proprietary driver. There was no problem when using the basic video driver.

I think the same problem existed in Gutsy. But I can't verify that since I overwrote my Gutsy installation in order to run the Hardy beta.

ProblemType: Bug
Architecture: i386
Date: Thu Mar 27 03:16:14 2008
DistroRelease: Ubuntu 8.04
NonfreeKernelModules: nvidia
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/code/play/main/private/av/ihd/wayvd/tools/linux:/code/play/main/developr/jayf/linux
 LANG=en_US.UTF-8
Uname: Linux 2.6.24-12-generic i686

Tags: apport-bug
Revision history for this message
Jay Finger (jcfinger) wrote :

This was using the restricted nvidia driver. The keys work fine using standard drivers.

So: The restricted nvidia drivers do not seem to be able to control the display brightness in a laptop using Quadro 1600M cards

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi jcfinger,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

Changed in linux-restricted-modules-2.6.24:
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in linux-restricted-modules-2.6.24:
status: Incomplete → Invalid
Revision history for this message
bogdan (kuko200099) wrote :

Same problem still present in Jaunty. I have an HP elitebook 8530w with Nvidia Quadro FX770M (see here https://bugs.launchpad.net/ubuntu/+bug/366793?comments=all )

Revision history for this message
chix (pdomenig) wrote :

Solved on my HP 8530w using Ubuntu Jaunty x64, kernel 2.6.28-12 and newest Beta NVIDIA Driver 185.18.08

ftp://download.nvidia.com/XFree86

Revision history for this message
bogdan (kuko200099) wrote :

Thank you for information, i've already tried with 185.18.08, but there are still some problems, like dimm screen after suspend, appearance of black dots on screen, and brightness adjustment range very limited. Furthermore, the gnome brightness applet says "Cannot get laptop panel brightness".

Revision history for this message
chix (pdomenig) wrote :

Brightness applet, dimm display when idle as well brightness control after suspend work perfectly. on my 8530w.

but i got some kind of artefacts (little balck squares) after resuming from standby sometimes.

have you tried kernel 2.6.18-12, you got to enable unsupported repositories...

Revision history for this message
chix (pdomenig) wrote :

new Nvidia Driver 180.60 (which is now a stable release and no more beta) fixes problem too and runs even smother...

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.