[MAVERICK] brightness (function/hotkey) key does not work.

[Manoj Iyer]

Fn+F6/F7 controls the brightness of the screen, but this key combination does not work. Similarly, Fn+F8,F9 wifi and mouse control also does not work.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-19-generic 2.6.35-19.28
Regression: No
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
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:
 Cannot stat file /proc/3650/fd/37: Stale NFS file handle
 Cannot stat file /proc/3650/fd/43: Stale NFS file handle
                      USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3662 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x40a00000 irq 46'
   Mixer name : 'Realtek ALC272'
   Components : 'HDA:10ec0272,1179ff30,00100001'
   Controls : 17
   Simple ctrls : 10
Date: Mon Aug 30 16:44:28 2010
Frequency: Once a day.
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100830)
MachineType: TOSHIBA TOSHIBA NB305
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 03/16/2010
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.40
dmi.board.name: NPVAA
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:bvrV1.40:bd03/16/2010:svnTOSHIBA:pnTOSHIBANB305:pvrPLL3AU-00L00C:rvnTOSHIBA:rnNPVAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: TOSHIBA NB305
dmi.product.version: PLL3AU-00L00C
dmi.sys.vendor: TOSHIBA

[Jeremy Foshee (jeremyfoshee)]

Hi Manoj,

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.]

[Andrew Sorensen (andrew-localcoast)]

This is fixed upstream. Can we get this patch: https://bugzilla.kernel.org/attachment.cgi?id=27236 backported?

[Daniele Napolitano (dnax88)]

Brightness adjustment was fixed in the kernel 2.6.36.

Here there is the packages ready to install in Maverick: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.36-maverick/

[Seth Forshee (sforshee)]

Looks like the referenced patch is currently present in both maverick and natty. Testing against natty confirms that the brightness hotkeys do work.