Function keys will not adjust brightness

Bug #1389675 reported by Paul B
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

I have just installed Ubuntu 14.04, and I cannot make the function keys adjust the brightness. I have been trying to get a solution to the problem in this forum http://ubuntuforums.org/showthread.php?t=2250862&page=2&p=13159626#post13159626 .

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-39-generic 3.13.0-39.66
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: paul 1336 F.... pulseaudio
 /dev/snd/pcmC0D0p: paul 1336 F...m pulseaudio
CurrentDesktop: Unity
Date: Wed Nov 5 13:31:30 2014
HibernationDevice: RESUME=UUID=6357ccbf-2f39-4ca6-9cc1-65eb05bf30f6
InstallationDate: Installed on 2014-10-29 (6 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b404 Chicony Electronics Co., Ltd
 Bus 001 Device 006: ID 1c4f:0003 SiGma Micro HID controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X551MA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed root=UUID=730dc0d2-8142-4bc0-a5ee-a2928da9bd65 ro quiet splash acpi_backlight=vendor vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-39-generic N/A
 linux-backports-modules-3.13.0-39-generic N/A
 linux-firmware 1.127.7
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/27/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X551MA.510
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X551MA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX551MA.510:bd06/27/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X551MA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Paul B (paulb223223) wrote :
penalvch (penalvch)
tags: added: bios-outdated-513
Changed in linux (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 kernel[0].

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

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc3-vivid/

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

Hi Christopher,

I updated the BIOS, but the function keys still do not adjust the brightness. Having entered this command:

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

I get this:

X551MA.513
09/09/2014

As far as updating the kernel... Is it very likely that this will make Ubuntu unbootable? I don't want to just create more problems trying to solve this one.

The instructions are also pretty vague for someone who doesn't already know that they are doing. For example, I am not actually sure if I should use the amd64 or the i386 build. Next, having downloaded these packages, I am supposed to enter

sudo dpkg -i *.deb

Well, according to the instructions, there's not just one package to be installed, but three, if I am reading it right. So do I enter sudo dpkg -i *.deb for each package individually, or do I enter
sudo dpkg -i *[1].deb *[2].deb *[3].deb ?

And there's a whole bunch of other stuff too:
[TXT] 0001-base-packaging.patch 02-Nov-2014 23:36 15M
[TXT] 0002-debian-changelog.patch 02-Nov-2014 23:36 376K
[TXT] 0003-configs-based-on-Ubuntu-3.18.0-1.1.patch 02-Nov-2014 23:36 85K
[ ] BUILD.LOG 03-Nov-2014 00:16 5.4M
[ ] BUILD.LOG.amd64 03-Nov-2014 00:16 2.3M
[ ] BUILD.LOG.armhf 03-Nov-2014 00:16 644K
[ ] BUILD.LOG.binary-headers 03-Nov-2014 00:16 22K
[ ] BUILD.LOG.i386 03-Nov-2014 00:16 2.4M
[ ] BUILT 03-Nov-2014 00:16 108
[ ] CHANGES 02-Nov-2014 23:35 38K
[ ] COMMIT

Do I ignore all that?

penalvch (penalvch)
tags: added: latest-bios-513
removed: bios-outdated-513
Revision history for this message
penalvch (penalvch) wrote :

Paul B, I've updated the wiki to clarify which architecture to test, and what the installation command means. As you are using a 64-bit OS, you would want to follow the amd64 instructions.

As well, there isn't a high likelihood of making your install unbootable. If the kernel doesn't work for whatever reason, one may simply boot into the default kernel and follow the support instructions to remove the mainline kernel.

Changed in linux (Ubuntu):
assignee: nobody → Chintana Prabhu (chintanarp98)
Revision history for this message
penalvch (penalvch) wrote :

Chintana Prabhu, assigning oneself to a report indicates that one is actively developing a patch for this, and will be releasing the code fix upstream imminently. Is this issue something you can reproduce and will be providing a patch within the next few days?

penalvch (penalvch)
Changed in linux (Ubuntu):
assignee: Chintana Prabhu (chintanarp98) → nobody
status: Confirmed → Incomplete
Changed in linux (Ubuntu):
assignee: nobody → Chintana Prabhu (chintanarp98)
penalvch (penalvch)
Changed in linux (Ubuntu):
assignee: Chintana Prabhu (chintanarp98) → nobody
Changed in linux (Ubuntu):
assignee: nobody → Chintana Prabhu (chintanarp98)
penalvch (penalvch)
Changed in linux (Ubuntu):
assignee: Chintana Prabhu (chintanarp98) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

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