Bug 502976 - lcd does not restore backlight after black or suspend
lcd does not restore backlight after black or suspend
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-05-28 00:23 EDT by cornel panceac
Modified: 2009-06-03 04:38 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-06-03 04:38:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description cornel panceac 2009-05-28 00:23:38 EDT
Description of problem:
after closing the lcd on my thinkpad x40, the screen does not restore backlight.

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

How reproducible:

Steps to Reproduce:
1.close the lcd
2.wait about 30 seconds
3.open the lcd
Actual results:
screen remains black

Expected results:
screen restores brightness

Additional info:

same thing happens either i'm on ac power or on battery, if the system has actually started or it's just prompting for the decrypt partitions password at the begining.

worked fine (more or less) with f10.
Comment 1 cornel panceac 2009-05-28 00:48:45 EDT
lspci -vv:

00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) (prog-if 00 [VGA controller])
	Subsystem: IBM Device 0557
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx+
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
	Region 1: Memory at d0000000 (32-bit, non-prefetchable) [size=512K]
	Region 2: I/O ports at 1800 [size=8]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: <access denied>
	Kernel driver in use: i915
	Kernel modules: i915
Comment 2 cornel panceac 2009-05-28 10:30:12 EDT
with (wich i understand that it disables kms for some intel
chipsets) i no longer have this problem, but i (still?) have the bug

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