Brightness control on Toshiba Satellite C660 laptop

Bug #939569 reported by Olivero
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Backlight control does not work on Toshiba Satellite C660 with Ubuntu 10.04 64 bits.
The only trick I've found is : xgamma -gamma 0.5 and that works.
Hot keys Fn 6 and Fn 7 are active but have no effect on the brightness of the LCD.

WORKAROUND: I have fixed my problem by installing nvidia-current (through Synaptics package manager) which was not installed.
After installation I had to add this line in the Device section of xorg.conf :
on "RegistryDwords" "EnableBrightnessControl=1"

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: solea 1395 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf7200000 irq 22'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,1179fc94,00100100'
   Controls : 13
   Simple ctrls : 8
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xf7080000 irq 17'
   Mixer name : 'Nvidia ID b'
   Components : 'HDA:10de000b,10de0101,00100200'
   Controls : 0
   Simple ctrls : 0
Card1.Amixer.values:

DistroRelease: Ubuntu 10.04
Frequency: Once a day.
HibernationDevice: RESUME=UUID=a9db3f95-03cc-46ff-b102-2afaac3182de
InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214.2)
Lsusb:
 Bus 002 Device 002: ID 8087:0024
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 04f2:b1d6 Chicony Electronics Co., Ltd
 Bus 001 Device 002: ID 8087:0024
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: TOSHIBA SATELLITE C660
Package: linux 2.6.32.38.44
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-38-generic root=UUID=9f75943a-f922-4d92-bd6c-5133d82ee331 ro quiet splash
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-38.83-generic 2.6.32.52+drm33.21
Regression: No
RelatedPackageVersions: linux-firmware 1.34.7
Reproducible: No
RfKill:

Tags: lucid graphics needs-upstream-testing
Uname: Linux 2.6.32-38-generic x86_64
UserGroups:

dmi.bios.date: 07/11/2011
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.10
dmi.board.asset.tag: NULL
dmi.board.name: PWWHA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvr1.10:bd07/11/2011:svnTOSHIBA:pnSATELLITEC660:pvrPSC1QE-03P00FFR:rvnTOSHIBA:rnPWWHA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: SATELLITE C660
dmi.product.version: PSC1QE-03P00FFR
dmi.sys.vendor: TOSHIBA

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 939569

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Olivero (cholivero) wrote : AlsaDevices.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Olivero (cholivero) wrote : BootDmesg.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : Card1.Codecs.codec.0.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : Card1.Codecs.codec.1.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : Card1.Codecs.codec.2.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : Card1.Codecs.codec.3.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : Dependencies.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : IwConfig.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : Lspci.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : PciMultimedia.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : ProcModules.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : UdevDb.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : UdevLog.txt

apport information

Revision history for this message
Olivero (cholivero) wrote : WifiSyslog.txt

apport information

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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 by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.3-rc4 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.3-rc4'.

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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc4-precise/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Olivero (cholivero)
description: updated
tags: removed: needs-upstream-testing
tags: removed: apport-collected
tags: added: kernel-bug-exists-upstream
tags: added: apport-collected
Olivero (cholivero)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Olivero (cholivero) wrote :

Hi,

I have fixed my problem by installing nvidia-current (through Synaptics package manager) which was not installed.
After installation I had to add this line in the Device section of xorg.conf :
on "RegistryDwords" "EnableBrightnessControl=1"
After reboot it works.
Can we close this case ?

Revision history for this message
Bob M Brown (gurubob) wrote :

Workaround confirmed, /etc/X11/xorg.conf reads as follows (entire file):

Section "Device"
 Identifier "Default Device"
 Option "NoLogo" "True"
 Option "RegistryDwords" "EnableBrightnessControl=1"
EndSection

Log out and logged back in and brightness control works as expected.

penalvch (penalvch)
tags: added: needs-full-computer-model needs-upstream-testing
tags: added: lucid
description: updated
Revision history for this message
penalvch (penalvch) wrote :

Olivero, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/939569/comments/22 regarding this being fixed by installing nvidia-current. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Bob M Brown (gurubob) wrote :

@penalvch If the C660 brightness controls don't work out of the box with Ubuntu should this bug be closed/invalid? I always come back to this issue after a reinstall to find my comment above. Seems it should be fixed somehow in Unbuntu but I don't know how to triage it.

Revision history for this message
penalvch (penalvch) wrote :

Bob M Brown, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Revision history for this message
Bob M Brown (gurubob) wrote :
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.