Brightness too low on Dell Vostro

Bug #636672 reported by Tim Wentz
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
NULL Project
Invalid
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Laptop: Dell Vostro 3400
OS: Ubuntu 10.10 beta, x64 Maverick Meercat
Graphics card: NVIDIA GeForce 310M (GT218)
Driver: nouveau

`uname -a`: Linux twentz-vostro 2.6.35-20-generic #29-Ubuntu SMP Fri Sep 3 14:55:28 UTC 2010 x86_64 GNU/Linux

When I upgraded to Maverick 10.10 (and after some initial adjustments), my brightness levels are about 50% lower than they should be -- so "0" brightness equates to literally a turned off backlight and "100%" is a dimly lit screen (probably ~50% normal brightness)

Some of the bugs related to this issue had some solutions, but I was not able to fully apply them to my problem:

using 'setpci' with the device's address didn't seem to work -- of I needed to specify a different value (other than f4.b), but I have no idea where this value came from -- it was just what was used to fix this problem on a different system.

I cannot seem to modify the "max_brightness" file in /sys/class/backlight/nv_backlight/ or /sys/class/backlight/acpi_video0/ (these directories have "./brightness" files that change when I adjust the brightness using the FN+up/down keys). I could understand why it would be unmodifiable, but I have no other ideas have to solve the problem.

twentz@twentz-vostro:/sys/class/backlight/nv_backlight$ sudo setpci -s 01:00.0 f4.b=ff
twentz@twentz-vostro:/sys/class/backlight/nv_backlight$ ls
actual_brightness brightness max_brightness subsystem
bl_power device power uevent
twentz@twentz-vostro:/sys/class/backlight/nv_backlight$ cat max_brightness
1025
twentz@twentz-vostro:/sys/class/backlight/nv_backlight$ sudo sh -c 'echo 1500 > /sys/class/backlight/nv_backlight/max_brightness'
sh: cannot create /sys/class/backlight/nv_backlight/max_brightness: Permission denied
twentz@twentz-vostro:/sys/class/backlight/nv_backlight$ ls -l
total 0
-r--r--r-- 1 root root 4096 2010-09-12 16:11 actual_brightness
-rw-r--r-- 1 root root 4096 2010-09-12 16:11 bl_power
-rw-r--r-- 1 root root 4096 2010-09-12 15:57 brightness
lrwxrwxrwx 1 root root 0 2010-09-12 16:11 device -> ../../../0000:01:00.0
-r--r--r-- 1 root root 4096 2010-09-12 15:57 max_brightness
drwxr-xr-x 2 root root 0 2010-09-12 16:11 power
lrwxrwxrwx 1 root root 0 2010-09-12 15:57 subsystem -> ../../../../../../class/backlight
-rw-r--r-- 1 root root 4096 2010-09-12 15:57 uevent
twentz@twentz-vostro:/sys/class/backlight/nv_backlight$ sudo sh -c 'echo 1500 > /sys/class/backlight/nv_backlight/max_brightness'
sh: cannot create /sys/class/backlight/nv_backlight/max_brightness: Permission denied
twentz@twentz-vostro:/sys/class/backlight/nv_backlight$ su root
Password:
root@twentz-vostro:/sys/class/backlight/nv_backlight# sh -c 'echo 1500 > /sys/class/backlight/nv_backlight/max_brightness'
sh: cannot create /sys/class/backlight/nv_backlight/max_brightness: Permission denied

(also, other forms of 'echo' or text editing don't seem to work)

My laptop's monitor corresponds to "LVDS", but that is never specified in any of the Xorg files that any program generates, nor do I know how to correctly specify it as such (if that would even help)

twentz@twentz-vostro:/sys/class/backlight/nv_backlight/device/drm/card0/card0-LVDS-1$ ls -l
total 0
lrwxrwxrwx 1 root root 0 2010-09-12 16:16 device -> ../../card0
-r--r--r-- 1 root root 4096 2010-09-12 16:16 dpms
-r--r--r-- 1 root root 0 2010-09-12 16:16 edid
-r--r--r-- 1 root root 4096 2010-09-12 16:16 enabled
-r--r--r-- 1 root root 4096 2010-09-12 16:16 modes
drwxr-xr-x 2 root root 0 2010-09-12 16:16 power
-r--r--r-- 1 root root 4096 2010-09-12 16:16 status
lrwxrwxrwx 1 root root 0 2010-09-12 15:57 subsystem -> ../../../../../../../class/drm
-rw-r--r-- 1 root root 4096 2010-09-12 15:57 uevent

I had to change graphics drivers from "nvidia" to "nouveau" because the Nvidia driver crashes on start-up (different, not germane issue) -- so I am using the "nouveau" driver

Attached is my xorg.conf that I'm using. It was generated automatically by "Xorg -configure" EXCEPT it initially used the "nv' driver, which failed to ever successfully load (something about "modesetting", also happens with the 'vesa' driver -- but 'nouveau' worked)

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-20-generic 2.6.35-20.29
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: twentz 1594 F.... pulseaudio
 /dev/snd/pcmC0D0p: twentz 1594 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfbe00000 irq 47'
   Mixer name : 'IDT 92HD81B1X5'
   Components : 'HDA:111d7605,10280440,00100104'
   Controls : 18
   Simple ctrls : 12
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfb080000 irq 16'
   Mixer name : 'Nvidia GT21x HDMI'
   Components : 'HDA:10de000b,10de0101,00100100'
   Controls : 16
   Simple ctrls : 4
CheckboxSubmission: bcb8b4c06179696af1b8bb66d96667a6
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Sun Sep 12 17:15:26 2010
HibernationDevice: RESUME=UUID=4b3d5e5a-94be-4426-8f85-2620e5629680
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: Dell Inc. Vostro 3400
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-20-generic root=UUID=d10ffc55-5e23-4966-9e5c-b2cb317f3874 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
 0: dell-wifi: Wireless LAN
  Soft blocked: yes
  Hard blocked: yes
SourcePackage: linux
UserAsoundrc:
 pcm.teeraw {
  type empty
  slave.pcm "tee:default,'/tmp/out.raw',raw"
  # 48000 S16_LE 2ch (aplay -t raw -f dat)
 }
dmi.bios.date: 06/23/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0RXV7H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd06/23/2010:svnDellInc.:pnVostro3400:pvrNotSpecified:rvnDellInc.:rn0RXV7H:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Vostro 3400
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

Revision history for this message
Tim Wentz (twentz1x) wrote :
Revision history for this message
Tim Wentz (twentz1x) wrote :

For comparison, here's the xorg.conf file that is generated by running 'nvidia-xconfig' (while nvidia-current is installed). Of course, X never succeeded in loading because it appears the NVIDIA driver itself fails, but for previous NVIDIA driver versions, the generated file worked.

Revision history for this message
Tim Wentz (twentz1x) wrote :

I forgot a very important detail:

The brightness is normal in the BIOS and the initial GDM Login -- but once GNOME session starts, the display dims for the rest of the time the computer is powered on (even after restarting X)

Using a different session (such as OpenBox) uses the full brightness, so GNOME must be reading some configuration file, but reading the logs did not reveal anything meaningful to me

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Tim,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Tim Wentz (twentz1x) wrote :

Hmm, not that any human will ever read this -- but I found that this is caused *somewhere* by gnome-power-manager.

By removing it from my start-up applications, my screen starts at full brightness (although I have no control over the brightness with the hardware controls) -- but once I start gnome-power-manager or an application that uses it (e.g. the the Update Manager or the Power Management menu) -- then my screen returns to its normal relative darkness.

If I had more faith in the Ubuntu bug reporting system, then I would file another bug specifically for gnome-power-manager; however, I have grown to expect absolutely nothing from this process except verbal abuse from developers.

Revision history for this message
Tim Wentz (twentz1x) wrote :

Also, I'll note that I tried to capture the debug & verbose outputs when manually starting gnome-power-manager, but for some reason, absolutely no output was generated. I guess now that gnome-power-manager is "working", I finally realized that the "dim display when idle for ___" option in the last distribution was not working. However, that did not even register on my mind -- but having a constantly dim screen is outright unacceptable.

Revision history for this message
Christian (c-pradelli) wrote :

I have the same problem here in my Dell Vostro 3700 with 10.10 final release. But it was solved after I enabled nVidia propietary driver.
Now I'm having problems with power management (freeze) (Bug #656745)

Revision history for this message
Tim Wentz (twentz1x) wrote :

Oh really? I would try fully installing (I tried the LiveUSB, but ran into the brightness problem again) 10.10 final to see if the Nvidia driver works now -- but the brightness is a pivotal usability issue. I guess I could theoretically try installing the driver from the Nvidia website on 10.04 since you say the driver works -- but I don't really have a need to as long as I have a driver that has CUDA capability.

Well, as I said, I found out the dimming problem is specific to gnome-power-manager -- I tested Fedora 14 with Gnome, and it had the *exact* same problem: the second I change the brightness, the screen goes to 50%. I googled a bit and found almost an identical description of the bug -- but it was 2 years old, so I guess maybe they fixed it, but then did it again...

Revision history for this message
parmeshwar89 (parmeshwar89) wrote :

I have the same problem, I installed ubuntu 10.10 in Vostro 3400, Brightness got very dim. Having no control at all.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Mathieu Pellerin (nirvn-asia) wrote :

Jeremy, this bug affects my brand new dell vostro 3700 with an nvidia gm330. It appears to be linked to the nouveau driver.

Revision history for this message
Mathieu Pellerin (nirvn-asia) wrote :
Revision history for this message
David Fraser (davidf) wrote :

Confirming based on comment #11
I also have this on a brand new dell vostro 3700 with the nouveau driver, on Maverick

Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
David Fraser (davidf) wrote :
Revision history for this message
luk156 (lucchesimatteo) wrote : apport information

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: matteo 1517 F.... pulseaudio
CRDA: Error: [Errno 2] File o directory non esistente
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf1400000 irq 47'
   Mixer name : 'Realtek ALC272'
   Components : 'HDA:10ec0272,10280418,00100001'
   Controls : 11
   Simple ctrls : 6
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xf1000000 irq 16'
   Mixer name : 'Nvidia GPU 0b HDMI/DP'
   Components : 'HDA:10de000b,10de0101,00100100'
   Controls : 16
   Simple ctrls : 4
DistroRelease: Ubuntu 11.04
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: Dell Inc. Inspiron 1370
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=it_IT:en
 LANG=it_IT.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-9-generic root=UUID=2ef46a33-dab5-46d8-ae3a-b160bec62ce5 ro acpi_backlight=vendor quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-9-generic N/A
 linux-backports-modules-2.6.38-9-generic N/A
 linux-firmware 1.52
Tags: natty
Uname: Linux 2.6.38-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 03/22/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 016YGK
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.asset.tag: None
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A03
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/22/2011:svnDellInc.:pnInspiron1370:pvrA03:rvnDellInc.:rn016YGK:rvrA03:cvnDellInc.:ct8:cvrA03:
dmi.product.name: Inspiron 1370
dmi.product.version: A03
dmi.sys.vendor: Dell Inc.

tags: added: apport-collected natty
Revision history for this message
luk156 (lucchesimatteo) wrote : AcpiTables.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : AlsaDevices.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : AplayDevices.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : BootDmesg.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : Card1.Amixer.values.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : Card1.Codecs.codec.0.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : Card1.Codecs.codec.1.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : Card1.Codecs.codec.2.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : Card1.Codecs.codec.3.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : CurrentDmesg.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : IwConfig.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : Lspci.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : Lsusb.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : PciMultimedia.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : ProcCpuinfo_.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : ProcInterrupts.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : ProcModules.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : RfKill.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : UdevDb.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : UdevLog.txt

apport information

Revision history for this message
luk156 (lucchesimatteo) wrote : WifiSyslog.txt

apport information

penalvch (penalvch)
description: updated
tags: added: regression-release
tags: removed: apport-collected natty
Revision history for this message
penalvch (penalvch) wrote :

Tim Wentz, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

affects: nouveau → null
Changed in null:
status: New → Invalid
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
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.