Brightness control on nc10 broken

Bug #883431 reported by riban
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Similar to issue #295251, brightness control from Fn+up / Fn+down buttons on Samsung nc10 is broken in Ubuntu 11.10. (Was fixed in later 2.8 kernel but seems broken again in 3.0). Pressing Fn+down (brightness down) key causes brightness to reduce to 0%. Pressing Fn+up (brightness up) key causes brightness to increase by one step. Pressing Fn+up again causes brightness to increase to 100%. Sometimes, with no key press at all, brightness seems to toggle up and down at high rate, making operating system unresponsive to key presses until the brightness keys are operated. It would seem some other event is triggering brightness changes.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu3
Architecture: i386
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: brian 27435 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0340000 irq 43'
   Mixer name : 'Realtek ALC272'
   Components : 'HDA:10ec0272,144dca00,00100001'
   Controls : 19
   Simple ctrls : 11
DistroRelease: Ubuntu 11.10
HibernationDevice: RESUME=UUID=5c1a4fa1-7ae5-4742-9b11-9de418e4bb8c
MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=a95d75c8-3405-41bb-95d9-46e5d813e385 ro splash quiet vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic N/A
 linux-backports-modules-3.0.0-12-generic N/A
 linux-firmware 1.60
Tags: oneiric running-unity
Uname: Linux 3.0.0-12-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 09/08/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 11CA.M015.20090908.RHU
dmi.board.name: NC10
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: None
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: No Asset Tag
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr11CA.M015.20090908.RHU:bd09/08/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrNoAssetTag:
dmi.product.name: NC10
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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 883431

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
riban (brian-riban)
description: updated
Revision history for this message
riban (brian-riban) wrote : AcpiTables.txt

apport information

tags: added: apport-collected oneiric running-unity
description: updated
Revision history for this message
riban (brian-riban) wrote : AlsaDevices.txt

apport information

Revision history for this message
riban (brian-riban) wrote : BootDmesg.txt

apport information

Revision history for this message
riban (brian-riban) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
riban (brian-riban) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
riban (brian-riban) wrote : CurrentDmesg.txt

apport information

Revision history for this message
riban (brian-riban) wrote : IwConfig.txt

apport information

Revision history for this message
riban (brian-riban) wrote : Lspci.txt

apport information

Revision history for this message
riban (brian-riban) wrote : Lsusb.txt

apport information

Revision history for this message
riban (brian-riban) wrote : PciMultimedia.txt

apport information

Revision history for this message
riban (brian-riban) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
riban (brian-riban) wrote : ProcInterrupts.gz

apport information

Revision history for this message
riban (brian-riban) wrote : ProcModules.txt

apport information

Revision history for this message
riban (brian-riban) wrote : PulseSinks.txt

apport information

Revision history for this message
riban (brian-riban) wrote : PulseSources.txt

apport information

Revision history for this message
riban (brian-riban) wrote : RfKill.txt

apport information

Revision history for this message
riban (brian-riban) wrote : UdevDb.txt

apport information

Revision history for this message
riban (brian-riban) wrote : UdevLog.txt

apport information

Revision history for this message
riban (brian-riban) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
papukaija (papukaija) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 883431, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Revision history for this message
papukaija (papukaija) wrote :

Sorry, I meant bug 810093.

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.