Bug 675116

Summary:	intel [GM45] Screen brightness is dimmed irreversively and repetitively after screen lid was closed/locked
Product:	[openSUSE] openSUSE 11.4	Reporter:	Robert Schenk <rs205>
Component:	X.Org	Assignee:	Stefan Dirsch <sndirsch>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <xorg-maintainer-bugs>
Severity:	Major
Priority:	P3 - Medium	CC:	rs205
Version:	Factory
Target Milestone:	---
Hardware:	i686
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Robert Schenk 2011-02-25 16:54:03 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13

The Test device is a Asus UL30vt Notebook, an external DVD drive and a openSUSE 11.4 M6* KDE live CD.

After locking the screen or going into suspend, the screen shuts down. However, when I reactivated the screen for logging in, the screen brightness was dimmed down a bit. It is not possible to readjust the brightness after that. I was able to repeat this until the screen was completely dark and I could not but disconnect the device from power and restart.

More severly, the same behaviour occured even after closing the notebook lid. After 5-7 times the screen was completely blank. That makes it unusable so far.

I will provide more information if necessary.

*It is possible that it is actually RC1, since I am not able to recognize the difference.

Reproducible: Always

Steps to Reproduce:
1. Use Asus Ul30vt as test device 
2. Shut the lid or lock the screen
3. Try the relogin
Actual Results:  
The screen was dimmed a bit. The difference was not far much, but It was recognizable.

Expected Results:  
The screen brightness should not been altered by that.

ASUS ul30vt

Comment 1 Stefan Dirsch 2011-02-25 18:01:25 UTC

Which graphics hardware is this? Please add the output of "hwinfo --gfxcard".

Comment 2 Robert Schenk 2011-02-25 19:19:41 UTC

linux:/home/linux # hwinfo --gfxcard
10: PCI 02.0: 0300 VGA compatible controller (VGA)              
  [Created at pci.318]
  Unique ID: _Znp.VGg1kf4in3D
  SysFS ID: /devices/pci0000:00/0000:00:02.0
  SysFS BusID: 0000:00:02.0
  Hardware Class: graphics card
  Model: "Mobile Intel® GM45 Express Chipset"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x2a42 "Mobile Intel® GM45 Express Chipset"
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
  SubDevice: pci 0x1af2 
  Revision: 0x07
  Driver: "i915"
  Driver Modules: "drm"
  Memory Range: 0xfcc00000-0xfcffffff (rw,non-prefetchable)
  Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
  I/O Ports: 0xcc00-0xcc07 (rw)
  IRQ: 47 (8545 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00008086d00002A42sv00001043sd00001AF2bc03sc00i00"
  Driver Info #0:
    XFree86 v4 Server Module: intel
  Driver Info #1:
    XFree86 v4 Server Module: intel
    3D Support: yes
  Config Status: cfg=new, avail=yes, need=no, active=unknown

26: PCI 100.0: 0300 VGA compatible controller (VGA)
  [Created at pci.318]
  Unique ID: VCu0.Kl1ManH5idD
  Parent ID: vSkL.tGAA5cTEGvF
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: graphics card
  Model: "nVidia VGA compatible controller"
  Vendor: pci 0x10de "nVidia Corporation"
  Device: pci 0x0a74                                                                                                                                                                            
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."                                                                                                                                                 
  SubDevice: pci 0x1af2                                                                                                                                                                         
  Revision: 0xa2                                                                                                                                                                                
  Memory Range: 0xfd000000-0xfdffffff (rw,non-prefetchable,disabled)                                                                                                                            
  Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable,disabled)                                                                                                                            
  Memory Range: 0xfa000000-0xfbffffff (ro,non-prefetchable,disabled)
  I/O Ports: 0xdc00-0xdc7f (rw,disabled)
  Memory Range: 0xfe980000-0xfe9fffff (ro,non-prefetchable,disabled)
  IRQ: 10 (no events)
  Module Alias: "pci:v000010DEd00000A74sv00001043sd00001AF2bc03sc00i00"
  Driver Info #0:
    Driver Status: nvidiafb is not active
    Driver Activation Cmd: "modprobe nvidiafb"
  Driver Info #1:
    Driver Status: nouveau is not active
    Driver Activation Cmd: "modprobe nouveau"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #9 (PCI bridge)

Primary display adapter: #10

Comment 3 Stefan Dirsch 2011-02-25 20:01:06 UTC

Known issue. Workaround is disabling display power management or going into S3 and resume when this happens.

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

Comment 4 Robert Schenk 2011-02-25 21:03:57 UTC

Some questions:

Will this be fixed in the final version of 11.4? 
Is there another way of finding a fix such a another mesa version?
Why is this a Dup of 666162? In that issue the screen gets completely blank, while here it just gets a bit darker.

will disabling display power management mean that any display controls will not work?

Comment 5 Stefan Dirsch 2011-02-25 21:17:24 UTC

(In reply to comment #4)
> Will this be fixed in the final version of 11.4? 

Unlikely. We're already behind RC2.

> Is there another way of finding a fix such a another mesa version?

Not that I'm aware of.

> Why is this a Dup of 666162? In that issue the screen gets completely blank,
> while here it just gets a bit darker.

It's just the darkest backlight level. This differs from panel to panel. JFYI,
I see the same problem on my laptop which I'm using all the time.

> will disabling display power management mean that any display controls will 
> not work?

No, you can still control the backlight level. You just disable the display
suspend modes.

Comment 6 Robert Schenk 2011-05-28 09:06:45 UTC

Going into S3 mode does not affect that issue. Therefore trying to disable display power management would be my next step. How is that properly made in 11.4?