Matthew Brooks, thank you for reporting this and helping make Ubuntu
better.

In order to allow additional upstream developers to examine the issue, at your 
earliest convenience, could you please test the latest upstream kernel 
available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please 
keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest upstream kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** This bug is no longer a duplicate of bug 1329510
   [Asus X200M] Changing Backlight not working

** Tags added: bios-outdated-506

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

** Description changed:

- Same bug as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329510
- Was asked to use the "ubuntu-bug linux" to post this along with the laptop 
info.
- 
  Fn + F5 or F6 is supposed to lower or raise the brightness respectively.
- By default, nothing happens when pushing the buttons. Editing the grub
+ By default, nothing happens when pushing the buttons.Editing the grub
  config to add "acpi_osi=" to the kernel command line seems to make the
  buttons get recognized, and the brightness popup displays, but the
  actual brightness doesn't change.
  
- Changing the brightness by piping a number into
- "/sys/class/backlight/intel_backlight/brightness" works fine, and the
- brightness slider that shows up in the drop-down from the Gnome status
- bar thing works fine, but the actual hardware buttons don't do anything
- even when they get recognized.
+ WORKAROUND: Pipe a number into
+ "/sys/class/backlight/intel_backlight/brightness", or use the brightness
+ slider that shows up in the drop-down from the Gnome status bar.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
-  USER        PID ACCESS COMMAND
-  /dev/snd/controlC0:  alicethegorgon   1381 F.... pulseaudio
+  USER        PID ACCESS COMMAND
+  /dev/snd/controlC0:  alicethegorgon   1381 F.... pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
-  Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp. 
-  Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
+  Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
+  Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=<set>
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=<set>
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.8.0-32-generic N/A
-  linux-backports-modules-4.8.0-32-generic  N/A
-  linux-firmware                            1.161.1
+  linux-restricted-modules-4.8.0-32-generic N/A
+  linux-backports-modules-4.8.0-32-generic  N/A
+  linux-firmware                            1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  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.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1651629

Title:
  [Asus X200M] Brightness keys don't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fn + F5 or F6 is supposed to lower or raise the brightness
  respectively. By default, nothing happens when pushing the
  buttons.Editing the grub config to add "acpi_osi=" to the kernel
  command line seems to make the buttons get recognized, and the
  brightness popup displays, but the actual brightness doesn't change.

  WORKAROUND: Pipe a number into
  "/sys/class/backlight/intel_backlight/brightness", or use the
  brightness slider that shows up in the drop-down from the Gnome status
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  alicethegorgon   1381 F.... pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware                            1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  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.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651629/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to