Bug 352951 – unable to "wake-up" display

Bug 352951 - unable to "wake-up" display

Summary:	unable to "wake-up" display

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	xorg-x11-drv-ati (Show other bugs)
Sub Component:
Version:	8
Hardware:	i386 Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	X/OpenGL Maintenance List
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-10-25 14:20 EDT by Dave Maley
Modified:	2007-11-30 17:12 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-10-25 15:14:55 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
current Xorg log (88.76 KB, text/plain) 2007-10-25 14:20 EDT, Dave Maley	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Dave Maley 2007-10-25 14:20:31 EDT

Description of problem: Just installed F-8 Test3 on my T42 (Radeon Mobility
7500).  When the display goes into sleep mode I'm unable to wake it up.  I am
able however to switch to the console which still works fine.


Version-Release number of selected component (if applicable):
xorg-x11-drv-ati-6.7.195-3.fc8


How reproducible: so far it appears to be everytime the display goes to sleep.


Steps to Reproduce:
1. allow display to go into sleep mode
2. try "waking" it
3.
  
Actual results: blank screen


Expected results: see desktop


Additional info:

Comment 1 Dave Maley 2007-10-25 14:20:31 EDT

Created attachment 237731 [details]
current Xorg log

Comment 2 Dave Maley 2007-10-25 15:14:55 EDT

problem is related to having external monitor connected.  Once dis-connected the
problem no longer occurs.  I'm having trouble getting the external LCD
configured correctly so this is likely the cause here, so I'm closing this bug
and will open a new bug if I'm unable to get the configuration of the LCD working.

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