nouveau-driver sets LVDS backlight to lowest level

Bug #809629 reported by Søren Holm
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Low
Unassigned

Bug Description

My laptop normally is set to maximum backlight level, but during boot the backlight is reset to the lowest level. This happenens with nouveau as well as with nvidia proprietary driver.

WORKAROUND: I can increase it afterwards, but it is always reset during boot.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-4-generic 3.0.0-4.5
ProcVersionSignature: Ubuntu 3.0.0-4.5-generic 3.0.0-rc6
Uname: Linux 3.0.0-4-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: NVidia [HDA NVidia], device 0: ALC660-VD Analog [ALC660-VD Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: sgh 1434 F.... kded4
                      sgh 1635 F.... kmix
CRDA: Error: [Errno 2] Ingen sådan fil eller filkatalog
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfecd8000 irq 22'
   Mixer name : 'Realtek ALC660-VD'
   Components : 'HDA:10ec0660,10430000,00100001'
   Controls : 24
   Simple ctrls : 15
Date: Wed Jul 13 01:21:42 2011
HibernationDevice: RESUME=UUID=6fc16235-9eea-4880-aeef-cdc890b89248
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 003: ID 174f:a821 Syntek Web Cam - Packard Bell BU45, PB Easynote MX66-208W
 Bus 002 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
 Bus 001 Device 006: ID 03f0:110c Hewlett-Packard
MachineType: Packard Bell BV Easy Note_MX51
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-4-generic root=UUID=cc344a8a-d2aa-4acc-a86d-d1ecaa8b5d51 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-4-generic N/A
 linux-backports-modules-3.0.0-4-generic N/A
 linux-firmware 1.56
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/11/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: T12MvNC.204
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Easy Note_MX51
dmi.board.vendor: Packard Bell BV
dmi.board.version: 1.00
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell BV
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT12MvNC.204:bd10/11/2006:svnPackardBellBV:pnEasyNote_MX51:pvrPB71HD0091:rvnPackardBellBV:rnEasyNote_MX51:rvr1.00:cvnPackardBellBV:ct10:cvr1.0:
dmi.product.name: Easy Note_MX51
dmi.product.version: PB71HD0091
dmi.sys.vendor: Packard Bell BV

Revision history for this message
Søren Holm (sgh) wrote :
description: updated
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
Revision history for this message
penalvch (penalvch) wrote :

Søren Holm, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please just make a comment to this.

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

description: updated
tags: added: needs-upstream-testing regression-potential
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Søren Holm (sgh) wrote :

It's no longer an issue.

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