ubuntu-bugcontrol team mailing list archive

["Christopher Penalver" <christopher.penalver@xxxxxxx>]

Hello everyone. I wanted to inquire about the layout of:
 https://wiki.ubuntu.com/Kernel/Debugging/Backlight

 Currently, content wise, it is excellent and a great first tutorial on debugging backlight bugs.

 However, I am finding that when triaging backlight bugs, non-developer bug reporters get confused as to what to do with the article.

 What I would like to see is the article be split up into two sections, a OR action item list, and a development section.

 In the OR action item list, this would give ORs specific terminal commands to execute and post the results into their report. The development part would discuss the reasons why one provides each, and debugging discussion.

 Using my experience as an example:
 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/863156
 https://bugzilla.kernel.org/show_bug.cgi?id=42993

 A rough draft template (tags could be embedded that shows it is a command) of just the OR action item list could be:

 Install the prerequisites:
 sudo apt-get install -y acpidump fwts dmidecode

 Execute each of the following via a terminal, and post the results to your report:

 grep -r . /proc/acpi/video

 ls /sys/class/backlight

 sudo acpidump -o acpidump.txt

 acpixtract acpidump.txt

 iasl -d DSDT.dat

 sudo fwts > fwts

 sudo fwts method > fwts method

 dmesg|grep 'ACPI: Video'

 dmidecode > dmidecode.log

 cat /proc/version

 * Add kernel parameter:
 atkbd.softraw=0

 to:
 /boot/grub/menu.lst

 Then, switch to any console, e.g. Ctrl+Alt+F1, login by root account and execute:
 showkey -s

 Then, press Fn+Left and Fn+Right key to check the code that shows up on screen. Post the results to the report. For example:

 Fn+Left:
 0xe0 0x4c 0xe0 0xcc

 Fn+Right:
 0xe0 0x54 0xe0 0xd4

 _________________________________________________________
 + Thinkpads
 * Add kernel parameters: thinkpad-acpi.brightness_enable=1 acpi_backlight=vendor Then execute the following and post results to your report: lsmod | grep thinkpad_acpi  _________________________________________________________
 + Intel

 * If using an intel board, add the kernel parameter:
 acpi_backlight=vendor

 Then execute the following and post results to your report:
 ls -la /sys/class/backlight/intel_backlight/  * Comment on how the brightness changes if one executes:
 sudo su
 sudo echo 8 > /sys/class/backlight/intel_backlight/brightness

 [END]

 The debugging section could incorporate the current content, including and below the section:
 https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Disabling_the_ACPI_backlight_driver

 As well, follow the current format of discussing each action item (e.g. why to run it, what certain results mean, and further information links).

 What do you think?

--
 Christopher M. Penalver
 E-Mail: christopher.penalver@xxxxxxx
 MCSE:Security, MCSA, MCDST, MCP, Security+, Network+, A+, NSSP

 This E-Mail was sent via a laptop using Xubuntu, Linux for human beings.
 www.xubuntu.org
 http://www.launchpad.net/~penalvch
 Acer Aspire 5750-9668 Xubuntu 12.04