Ubuntu

[Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down keys

Reported by mlx on 2010-09-03
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

1) Kubuntu maverick beta
2) 2.6.35.19.20 0
3) Pressing the brightness keys should increase/decrease the brightness by 1 step
4) Pressing brightness-down decreases brightness by two steps, pressing brightness-up increases the brightness for a split-second, then decreases it back to what it was. It's impossible to increase brightness using the keys, I have to increase by other means (powerdevil slider, xrandr --set, etc..)

Hardware: Notebook Fujitsu-Siemens Esprimo mobile U9200 (intel GM965)
Annotated showkey - s output:
# single brightness-down
0xe0 0x4c 0xe0 0xcc
#single brighness-up
0xe0 0x54 0xe0 0xd4 0xe0 0x4c 0xe0 0xcc

Tried "acpi-backlight=vendor" option to no avail. Worked fine way back before intel KMS (Kubuntu 8.04). Xrandr show two backlight properties, in case that's relevant:

$ xrandr --prop
...
LVDS1 connected 1280x800+0+0 (normal left inverted right x axis y axis) 261mm x 163mm
        EDID:
      ...
        BACKLIGHT: 7 (0x00000007) range: (0,7)
        Backlight: 7 (0x00000007) range: (0,7)
...

WORKAROUND: Use kernel parameter:
acpi_backlight=vendor

WORKAROUND:
echo N > /sys/module/video/parameters/brightness_switch_enabled

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-19-generic 2.6.35-19.28
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: michal 1751 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc400000 irq 47'
   Mixer name : 'Realtek ALC262'
   Components : 'HDA:10ec0262,17340000,00100202'
   Controls : 16
   Simple ctrls : 11
Date: Fri Sep 3 10:39:43 2010
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100902.1)
MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic root=UUID=c34e4451-0744-48d0-9912-745565e9441e ro acpi-backlight=vendor quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=sk_SK.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
dmi.bios.date: 04/22/2008
dmi.bios.vendor: Phoenix
dmi.bios.version: 1.11 - 067 - 1566
dmi.board.name: S11D
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: 1.0
dmi.chassis.asset.tag: FSC
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnPhoenix:bvr1.11-067-1566:bd04/22/2008:svnFUJITSUSIEMENS:pnESPRIMOMobileU9200:pvr1.0:rvnFUJITSUSIEMENS:rnS11D:rvr1.0:cvnFUJITSUSIEMENS:ct10:cvr1.0:
dmi.product.name: ESPRIMO Mobile U9200
dmi.product.version: 1.0
dmi.sys.vendor: FUJITSU SIEMENS

---
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: michal 1839 F.... pulseaudio
 /dev/snd/pcmC0D0p: michal 1839 F...m pulseaudio
DistroRelease: Ubuntu 12.10
HibernationDevice: RESUME=UUID=ef804bcd-8a5b-472d-b05d-8a8f0d0a2dfe
InstallationDate: Installed on 2012-10-28 (3 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=56c7d3eb-ec24-4b78-82ff-dd808df8c6e0 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-17-generic N/A
 linux-backports-modules-3.5.0-17-generic N/A
 linux-firmware 1.95
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
Tags: quantal
Uname: Linux 3.5.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 04/22/2008
dmi.bios.vendor: Phoenix
dmi.bios.version: 1.11 - 067 - 1566
dmi.board.name: S11D
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: 1.0
dmi.chassis.asset.tag: FSC
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnPhoenix:bvr1.11-067-1566:bd04/22/2008:svnFUJITSUSIEMENS:pnESPRIMOMobileU9200:pvr1.0:rvnFUJITSUSIEMENS:rnS11D:rvr1.0:cvnFUJITSUSIEMENS:ct10:cvr1.0:
dmi.product.name: ESPRIMO Mobile U9200
dmi.product.version: 1.0
dmi.sys.vendor: FUJITSU SIEMENS

mlx (myxal-mxl) wrote :
mlx (myxal-mxl) wrote :

Mainline kernel (2.6.35-02063503-generic #201008211321 SMP Sat Aug 21 13:24:00 UTC 2010) behaves the same way.

My messenger log reveals that this apparently worked in an early maverick daily build (2010-06-27 or thereabout), shortly before alpha 2 - is there any way to get it now so I can check?

mlx (myxal-mxl) on 2010-09-10
tags: added: acpi brightness
removed: needs-upstream-testing
Brad Figg (brad-figg) on 2010-12-04
tags: added: acpi-aml-opcode
tags: added: acpi-apic
mlx (myxal-mxl) on 2010-12-05
tags: added: apport-collected
description: updated
mlx (myxal-mxl) wrote :

Darn, meant to add new info rather than change the original description...

Anyway, I found a kernel from around the time Maverick alpha1 was released - Linux 2.6.35-020635rc3-generic x86_64 from Ubuntu's mainline kernel repository> http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc3-maverick/ and indeed the buttons now work perfectly. xrandr --prop still shows two Backlight properties and and KDE's brightness indicator rarely shows up when it should (I've seen it once or twice in ~2 minutes I've played with the buttons) which didn't happen before but I could live with that.

Interestingly, showkey -s now reports nothing upon pressing either of the brightness keys. Setting the brightness through software (Powerdevil, xrandr --set) still works fine.

Brad Figg (brad-figg) on 2011-04-07
Changed in linux (Ubuntu):
status: New → Confirmed
David Dean (ddean-ieee) wrote :

I am also affected by this bug, and it is still occuring in a fresh install of Ubuntu 11.10. Please let me know if any extra details would be helpfull.

tags: removed: acpi brightness

mlx, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please provide the information following https://wiki.ubuntu.com/Hotkeys/Troubleshooting ?

As well, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

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 text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
mlx (myxal-mxl) wrote : AlsaInfo.txt

apport information

tags: added: quantal
description: updated
mlx (myxal-mxl) wrote : BootDmesg.txt

apport information

mlx (myxal-mxl) wrote : CRDA.txt

apport information

apport information

mlx (myxal-mxl) wrote : IwConfig.txt

apport information

mlx (myxal-mxl) wrote : Lspci.txt

apport information

mlx (myxal-mxl) wrote : Lsusb.txt

apport information

apport information

apport information

apport information

apport information

apport information

mlx (myxal-mxl) wrote : UdevDb.txt

apport information

mlx (myxal-mxl) wrote : UdevLog.txt

apport information

apport information

description: updated
mlx (myxal-mxl) wrote : AlsaInfo.txt

apport information

apport information

mlx (myxal-mxl) wrote : CRDA.txt

apport information

apport information

mlx (myxal-mxl) wrote : IwConfig.txt

apport information

mlx (myxal-mxl) wrote : Lspci.txt

apport information

mlx (myxal-mxl) wrote : Lsusb.txt

apport information

apport information

apport information

apport information

apport information

apport information

mlx (myxal-mxl) wrote : UdevDb.txt

apport information

mlx (myxal-mxl) wrote : UdevLog.txt

apport information

apport information

mlx (myxal-mxl) on 2012-11-01
tags: added: kernel-bug-exists-upstream-3.7.0-030700rc2-generic

Bug still exists, tested with quantal:
stock kernel (3.5.0-17)
mainlinee build (3.7.0-030700rc2-generic)
Both kernels show the same behaviour.
As in previous releases, can be worked around by disabling the brightness_switch_enabled parameter:

# echo N > /sys/module/video/parameters/brightness_switch_enabled

tags: added: kernel-bug-exists-upstream

mlx, could you please test the latest upstream kernel available (v3.7-rc3-raring) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.7-rc3-raring

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

description: updated
tags: added: needs-upstream-testing
removed: kernel-bug-exists-upstream
description: updated
mlx (myxal-mxl) wrote :

Same behaviour on 3.7.0-030700rc3-generic

tags: added: kernel-bug-exists-upstream-3.7.0-030700rc3-generic
removed: kernel-bug-exists-upstream-3.7.0-030700rc2-generic needs-upstream-testing
tags: added: kernel-bug-exists-upstream

mlx, thank you for testing the newest mainline kernel. Did this problem occur in Lucid?

tags: added: kernel-fixed-upstream-v3.7-rc3-raring
removed: kernel-bug-exists-upstream-3.7.0-030700rc3-generic
summary: - Incorrect response to Brightness Up/Down keys
+ [Fujitsu ESPRIMO Mobile U9200] Incorrect response to Brightness Up/Down
+ keys
mlx (myxal-mxl) wrote :

Yes, just booted a live session of 10.04.4 and it behaves the same way.

mlx, thank you for testing Lucid. Could you please provide the information following https://wiki.ubuntu.com/Kernel/Debugging/Backlight ?

tags: added: lucid
mlx (myxal-mxl) wrote :
mlx (myxal-mxl) wrote :
mlx (myxal-mxl) wrote :
mlx (myxal-mxl) wrote :
mlx (myxal-mxl) wrote :
mlx (myxal-mxl) wrote :
mlx (myxal-mxl) wrote :

I'll reboot to try the acpi=vendor trick and report on that in a while.

mlx (myxal-mxl) wrote :

Using the acpi_backlight=vendor boot option fixes the button behaviour

mlx (myxal-mxl) wrote :

Writing "8" to the brightness file errors out with "Invalid argument". According to max_brightness, highest value is 1. Writing either 0 or 1 into the brightness file does not change the physical backlight brightness level.

mlx (myxal-mxl) wrote :

Oh, btw - with the vendor boot option, I can no longer change the brightness using KDE's power management widget.

mlx (myxal-mxl) wrote :

With the video.use_bios... parameter set to 0, the backlight keys are as broken as with stock configuration.
Chris, should I boot the kernel with only "atkbd.softraw=0" option, or with both atkbd.. and video.use_bios..?

mlx, only:
atkbd.softraw=0

mlx (myxal-mxl) wrote :

The key codes with atkbd.softraw=0 are the same as posted in the summary:

# single brightness-down
0xe0 0x4c 0xe0 0xcc
#single brighness-up
0xe0 0x54 0xe0 0xd4 0xe0 0x4c 0xe0 0xcc

When the brightness level is at either extreme, the key, which can no longer change the brightness does not produce any output in showkey.

tags: added: kernel-bug-exists-upstream-v3.7-rc3-raring
removed: kernel-fixed-upstream-v3.7-rc3-raring
tags: removed: kernel-fs
description: updated
tags: added: needs-reverse-mainline-bisect
removed: regression-release
Changed in linux (Ubuntu):
status: Incomplete → Confirmed

mlx, thank you for providing the requested information. Could you please test http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc4-raring/ ?

tags: added: kernel-bug-exists-upstream-v3.7-rc3
removed: kernel-bug-exists-upstream-v3.7-rc3-raring
tags: removed: needs-reverse-mainline-bisect
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
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.