kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

Max Oropeza, as per the previously noted URL, it advises you to fill out all the below information and send to appropriate mailing list (which would be linux-acpi in this case):
[1.] One line summary of the problem:
Paste the downstream bug title.

[2.] Full description of the problem/report:
Paste the Bug Description and a link to your Launchpad bug report.

[3.] Keywords (i.e., modules, networking, kernel): Please note,
Kernel.org uses a different keyword system then the Ubuntu Tags system.

[4.] Kernel version (from /proc/version):
While booted into the newest upstream mainline kernel only, please execute the following in a terminal and paste the results:
cat /proc/version

[5.] Output of Oops.. message (if applicable) with symbolic information resolved (see Documentation/oops-tracing.txt)
This is only relevant if you had a oops crash (ex. flashing Caps Lock light). While booted into the newest upstream mainline kernel only, if you have a kernel oops, one may consult http://www.kernel.org/doc/Documentation/oops-tracing.txt . If this is too daunting please ask for help in your bug report, and of the Ubuntu community.

[6.] A small shell script or example program which triggers the problem (if possible)
This is for advanced community members. If you feel comfortable enough to do this, please do it. It is not crtical if this is beyond your skill level.

[7.] Environment
Please execute the following in a terminal, and paste the results:
lsb_release -rd

[7.1.] Software (add the output of the ver_linux script here)
While booted into the newest upstream mainline kernel only, this is found in the directory:
/usr/src/linux-headers-<VERSION>/scripts

where <VERSION> is the version of the kernel you are using, found in the directory /usr/src. You may run the script by changing to the directory via a terminal, and paste the results:
sh ver_linux

[7.2.] Processor information (from /proc/cpuinfo):
While booted into the newest upstream mainline kernel only, execute the following in a terminal, and paste the results:
cat /proc/cpuinfo

[7.3.] Module information (from /proc/modules):
While booted into the newest upstream mainline kernel only, execute the following in a terminal, and paste the results:
cat /proc/modules

[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
While booted into the newest upstream mainline kernel only, execute the following in a terminal, and paste the results:
cat /proc/ioports
cat /proc/iomem

[7.5.] PCI information ('lspci -vvv' as root)
While booted into the newest upstream mainline kernel only, execute the following via a terminal, and paste the results:
sudo lspci -vvv

[7.6.] SCSI information (from /proc/scsi/scsi)
While booted into the newest upstream mainline kernel only, execute the following via a terminal, and paste the results:
cat /proc/scsi/scsi

[7.7.] Other information that might be relevant to the problem (please look in /proc and include all information that you think to be relevant):
While booted into the newest upstream mainline kernel only, execute the following via a terminal, and paste the results:
ls /proc

[X.] Other notes, patches, fixes, workarounds:
If this is a regression, please note the specific commit. As well, it is imperative that you include any further debugging information from http://www.kernel.org/doc/Documentation/ using the newest upstream mainline kernel available. Failure to provide the information from the documentation mentioned for the driver or subsystem your reporting a bug in, may likely result in negative unintended consequences. In addition, please be 100% certain you have included all relevant comment information not included in the Bug Description and a kernel developer should review. They are some of the busiest people in the Linux space. They do not need to dive through downstream bug reports to find something that should have been provided when the bug was first filed. If you are unsure about anything asked for, or intend on not following this format, please do not file a report. Instead, continue to ask questions in Launchpad, and of the Ubuntu community, until all issues are cleared up.

-- 
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/1173961

Title:
  [Gateway NV55C] Two backlight interfaces that wont adjust backlight.

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I couldn't get the backlight to work after I upgraded to 13.04.

  WORKAROUND: The only grub lines that seem to work are these:
  GRUB_CMDLINE_LINUX="acpi_osi=Linux acpi_backlight=vendor"
  GRUB_CMDLINE_LINUX="acpi_osi="

  I tried changing the grub parameters, and after several trys, nothing.
  I was asked to run     grep . /sys/class/backlight/*/* and got the
  results of:

  maxo@Dayman:~$ grep . /sys/class/backlight/*/*
  /sys/class/backlight/acpi_video0/actual_brightness:9
  /sys/class/backlight/acpi_video0/bl_power:0
  /sys/class/backlight/acpi_video0/brightness:9
  grep: /sys/class/backlight/acpi_video0/device: Is a directory
  /sys/class/backlight/acpi_video0/max_brightness:9
  grep: /sys/class/backlight/acpi_video0/power: Is a directory
  grep: /sys/class/backlight/acpi_video0/subsystem: Is a directory
  /sys/class/backlight/acpi_video0/type:firmware
  /sys/class/backlight/intel_backlight/actual_brightness:976
  /sys/class/backlight/intel_backlight/bl_power:0
  /sys/class/backlight/intel_backlight/brightness:976
  grep: /sys/class/backlight/intel_backlight/device: Is a directory
  /sys/class/backlight/intel_backlight/max_brightness:976
  grep: /sys/class/backlight/intel_backlight/power: Is a directory
  grep: /sys/class/backlight/intel_backlight/subsystem: Is a directory
  /sys/class/backlight/intel_backlight/type:raw

  But using the Fn Keys, you can only adjust it a little, like from full
  brightness to about half. To add something else, with the other
  parameters when I adjust with the Fn Keys, the brightness bubble you
  get on the top right of your screen doesn't appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic]
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  maxo       2482 F.... pulseaudio
  Date: Sun Apr 28 07:01:21 2013
  HibernationDevice: RESUME=UUID=f71ed279-badf-446b-afc6-d5a75316ec0a
  InstallationDate: Installed on 2013-04-25 (2 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Gateway NV55C
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=bc22ba4b-fcd9-46f3-b10a-11477dd4f618 ro acpi_osi= acpi_backlight=vendor quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware                            1.106
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2011
  dmi.bios.vendor: Gateway
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NV55C
  dmi.board.vendor: Gateway
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: V1.24
  dmi.modalias: dmi:bvnGateway:bvrV1.24:bd08/10/2011:svnGateway:pnNV55C:pvrV1.24:rvnGateway:rnNV55C:rvrV1.24:cvnGateway:ct10:cvrV1.24:
  dmi.product.name: NV55C
  dmi.product.version: V1.24
  dmi.sys.vendor: Gateway

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