[i945GM] weird behavior of brightness control, especially with Jaunty

Bug #370773 reported by tangerine
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

This resembles Bug #312518, Bug #367309 and Bug #356510, but there is some significant difference, so I decided to file new one. I have a similar problem with flickering screen on Jaunty with my Lenovo 3000 c200 (intel 945GM). It has nothing to do with logging in. It just flickers occasionally from time to time. I think most of the times this happens right after the machine is idle for some time - moving the mouse a bit makes it flicker for a moment until it gets stable. Yet this also happens unpredictably during use.
When flickering, screen does not get completely black, but rather gets to the minimum brightness for a short moment and then back to the adjusted level.

When using Power Manager Brightness Applet to adjust brightness, dragging is extremely slow and accompanied by massive flickering. When using "Set Display Brightness" in Power Manager Preferences, dragging is normal, but yet screen flickers rapidly. In both cases adjustment works. If trying to adjust with keyboard shortcuts (Fn key+F10 or F11), screen gets dimmed and flickers, and I can only adjust one step before it falls back to minimum brightness, so brightness cannot be adjusted. There is also reproducable flickering when launching Power Manager Preferences. Turning off "Dim display when idle" doesn't make things better.

Previously I was using Hardy, and this problem wasn't there, not with the default kernel nor with custom-compiled 2.6.29. I believe this could be connected to another problem which I did have on Hardy and which remains on Jaunty: when switching video modes, brightness falls to minimum, for example when logging out or switching to virtual terminal by pressing ctrl-alt-f2 (also sometimes when playing a video file or 3D game). Strangely right after installing Hardy it was ok, the problems only started after updating bios to the most recent version. Reverting bios had no effect, so I decided to stick with the most recent version.

When trying the proposed solution (Bug #367309):

xrandr --output LVDS --set BACKLIGHT_CONTROL combination

it actually gets better: the hotkeys work again and using the gnome applet is faster (though a bit slow yet). Also switching between video modes doesn't reset brightness anymore. Though now changing brightness gets accomponied by clicking sound, coming probably from my hard disk. I looked into System Log Viewer and I noticed that every little change in brightness, be it via applet, hotkey or Power Management Preferences, triggers this message in auth.log:

<username> dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.42" (uid=1000 pid=3586 comm="/usr/lib/indicator-applet/indicator-applet --oaf-a") interface="org.freedesktop.DBus.Properties" member="Get" error name="(unset)" requested_reply=0 destination=":1.140" (uid=111 pid=6568 comm="/usr/lib/policykit/polkit-read-auth-helper 1000 "))

In addition, after the initial command to xrandr I am able to switch back to

xrandr --output LVDS --set BACKLIGHT_CONTROL kernel

without any consequences, everything behaves the same way, the flickering doesn't occur again (until logout). Actually after initial switching to any type of BACKLIGHT_CONTROL but "kernel", it doesn't matter at all which type I select next: nothing appears to change.

I'm using Ubuntu 9.04
xserver-xorg-video-intel: 2:2.6.3-0ubuntu9

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
 Subsystem: Lenovo Device [17aa:3800]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
 Subsystem: Lenovo Device [17aa:3801]

Revision history for this message
tangerine (2wtangerine) wrote :
Revision history for this message
tangerine (2wtangerine) wrote :
Revision history for this message
tangerine (2wtangerine) wrote :
Revision history for this message
tangerine (2wtangerine) wrote :
Revision history for this message
Geir Ove Myhr (gomyhr) wrote :

Thank you for reporting this bug. Could you please upload the output of `lspci -vvnn`. That gives us more information than simply `lspci` which you already have uploaded and helps us identify your exact hardware.

Geir Ove Myhr (gomyhr)
tags: added: 945gm backlight intel needs-lspci-vvnn xorg
Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Incomplete
Revision history for this message
tangerine (2wtangerine) wrote :
Geir Ove Myhr (gomyhr)
description: updated
tags: removed: needs-lspci-vvnn
Changed in xserver-xorg-video-intel (Ubuntu):
status: Incomplete → Confirmed
Bryce Harrington (bryce)
summary: - [945GM] wierd behavior of brightness control, especially with Jaunty
+ [i945GM] wierd behavior of brightness control, especially with Jaunty
summary: - [i945GM] wierd behavior of brightness control, especially with Jaunty
+ [i945GM] weird behavior of brightness control, especially with Jaunty
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

A new major version of the -intel driver is now available in Karmic.

This version includes a major reworking of the acceleration
architecture, which resolves a huge number of issues. We do not know
whether it resolves the issue you reported.

Would you mind testing Karmic Alpha-2 and seeing if it is still a
problem? CD ISO images are available here:

  http://cdimages.ubuntu.com/releases/karmic/

If the issue can still be reproduced on karmic, please report here with
your findings, and attach a fresh Xorg.0.log from your test, and we will
be able to forward the bug upstream.

Otherwise, if the bug no longer exists in Karmic, let us know that as
well.

In the off chance you encounter different bugs while attempting to test
Karmic, please report those as new bug reports.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Confirmed → New
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

It seems likely to me this bug is gone; the -intel driver has improved immensely in Karmic and a lot of bugs are being reported as no longer present. So hopefully that's the case here too.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.