Bug 947437 - Fn-F8/F9 does not change brightness
Summary: Fn-F8/F9 does not change brightness
Keywords:
Status: CLOSED DUPLICATE of bug 903136
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-02 12:24 UTC by Alexey Kardashevskiy
Modified: 2013-04-12 16:47 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-04-12 16:47:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alexey Kardashevskiy 2013-04-02 12:24:10 UTC
Description of problem:

Fn-F8/F9 stopped changing brightness on Lenovo Thinkpad X230. It worked a couple of days ago but after some recent update (simple "yum update") it stopped.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

1. Press Fn-F8/F9, the brightness control appears but does not change anything, even when I press the key again.
2. If the current brighness is <=69%, the brighness control works but cannot set brightness higher that 69%.
3. setting->power management still lets to change brightness. "echo" and "cat" work with /sys/class/backlight/acpi_video0/brightness as well.

The windows manager is MATE or Gnome3 or XFCE - all the same.
  
Actual results:


Expected results:


Additional info:
Kernel 3.8.40202.fc18.
thinkpad_acpi loaded.

Comment 1 Jaroslav Škarvada 2013-04-02 12:35:15 UTC
It does seem as kernel regression, reassigning.

Comment 2 Alexey Kardashevskiy 2013-04-02 13:38:26 UTC
Cannot be there some other service touching brightness? Like systemd (saw in google) which could do power management which could affect stuff like display dim.

Comment 3 Jaroslav Škarvada 2013-04-02 13:52:55 UTC
(In reply to comment #2)
> Cannot be there some other service touching brightness? Like systemd (saw in
> google) which could do power management which could affect stuff like
> display dim.

AFAIK systemd doesn't handle this.

> 1. Press Fn-F8/F9, the brightness control appears but does not change anything, even when I press the key again.
It seems that the special keys are passed correctly by the kernel.

> 3. setting->power management still lets to change brightness. "echo" and "cat" work with /sys/class/backlight/acpi_video0/brightness as well.
It seems the ACPI side works OK.

Is the acpi_video0 the only interface under /sys/class/backlight? If it is the only interface and reacts correctly to the echo command it maybe issue of xfce4-power-manager or/and gnome-settings-daemon.

Comment 4 Alexey Kardashevskiy 2013-04-03 00:03:58 UTC
In meanwhile I removed xfce4 and gnome (yum remove @xfce @gnome ; yum install @mate), I believe I eliminated those window managers and their services but it did not help with the problem.

Here are the backlight interfaces:

[aik@aik ~]$ ls -laR /sys/class/backlight/
/sys/class/backlight/:
total 0
drwxr-xr-x.  2 root root 0 Apr  3  2013 .
drwxr-xr-x. 57 root root 0 Apr  3  2013 ..
lrwxrwxrwx.  1 root root 0 Apr  3  2013 acpi_video0 -> ../../devices/pci0000:00/0000:00:02.0/backlight/acpi_video0
lrwxrwxrwx.  1 root root 0 Apr  3  2013 intel_backlight -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1/intel_backlight

Comment 5 Jaroslav Škarvada 2013-04-03 11:51:10 UTC
(In reply to comment #4)
> Here are the backlight interfaces:
> 
> [aik@aik ~]$ ls -laR /sys/class/backlight/
> /sys/class/backlight/:
> total 0
> drwxr-xr-x.  2 root root 0 Apr  3  2013 .
> drwxr-xr-x. 57 root root 0 Apr  3  2013 ..
> lrwxrwxrwx.  1 root root 0 Apr  3  2013 acpi_video0 ->
> ../../devices/pci0000:00/0000:00:02.0/backlight/acpi_video0
> lrwxrwxrwx.  1 root root 0 Apr  3  2013 intel_backlight ->
> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1/intel_backlight

I checked all three managers: xfce4-power-manager, gnome-settings-daemon and mate-power-manager. All prefer acpi_video0 over intel_backlight and it is unlikely that all three handle the backlight wrongly. So I still think there is something wrong with the kernel interface.

Could you debug the brightness change (especially when reached the magic boundary 69%) and what are the corresponding values in:
/sys/class/backlight/acpi_video0/actual_brightness
/sys/class/backlight/acpi_video0/brightness
/sys/class/backlight/acpi_video0/max_brightness

I think there must be some problem (discontinuity?) there.

Comment 6 Alexey Kardashevskiy 2013-04-03 12:13:56 UTC
"max" is always 100.
[aik@aik ~]$ cat /sys/class/backlight/acpi_video0/max_brightness 
100

Below are values for 50, 58, 69, 80, 79, 70. The "brightness" is what the power management shows, the "actual_brightness" is the real brightness. So the magic boundary is 69%..79% of "brightness" (69% when decreasing, 79% when incresing) is actually 70% of "actual_brightness".

btw! Just discovered that "power management" window does not change brightness when on battery power. However fn-f8/f9 does, within magic boundaries, of course :)


[aik@aik ~]$ cat /sys/class/backlight/acpi_video0/actual_brightness
50
[aik@aik ~]$ cat /sys/class/backlight/acpi_video0/brightness 
50

[aik@aik ~]$ cat /sys/class/backlight/acpi_video0/actual_brightness
55
[aik@aik ~]$ cat /sys/class/backlight/acpi_video0/brightness 
58

[aik@aik ~]$ cat /sys/class/backlight/acpi_video0/actual_brightness
65
[aik@aik ~]$ cat /sys/class/backlight/acpi_video0/brightness 
69

[aik@aik ~]$ cat /sys/class/backlight/acpi_video0/actual_brightness
80
[aik@aik ~]$ cat /sys/class/backlight/acpi_video0/brightness 
80

[aik@aik ~]$ cat /sys/class/backlight/acpi_video0/actual_brightness
80
[aik@aik ~]$ cat /sys/class/backlight/acpi_video0/brightness 
79

[aik@aik ~]$ cat /sys/class/backlight/acpi_video0/actual_brightness
70
[aik@aik ~]$ cat /sys/class/backlight/acpi_video0/brightness 
70

Comment 7 Josh Boyer 2013-04-12 16:47:34 UTC

*** This bug has been marked as a duplicate of bug 903136 ***


Note You need to log in before you can comment on or make changes to this bug.