| Summary: | Corrupt display after firmware 'display sleep' | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Andrew D. Stadler <stadler> |
| Component: | Driver/Radeon | Assignee: | Xorg Project Team <xorg-team> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | high | CC: | erik.andren, m.ehinger, tmus |
| Version: | 6.8.2 | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Andrew D. Stadler
2005-04-11 09:20:08 UTC
*** Bug 2975 has been marked as a duplicate of this bug. *** The 'display sleep' is presumably an ACPI function. I am not sure that xorg supports ACPI sedation. *** Bug 4436 has been marked as a duplicate of this bug. *** *** Bug 3844 has been marked as a duplicate of this bug. *** FWIW, I'm not sure if those other two bugs are duplicates. 4436 refers to an X crash after the laptop sleeps (or perhaps hibernates). In this bug, X is not crashed; You can move the mouse around, type, etc. and see things going on (through the garbled display). 3844 refers to a problem with dynamic clocks after suspend. In this bug, the system has not slept, suspended, or hibernated. The system is awake, it's just that the screen has been disabled (by the bios) to save energy. Please don't get me wrong, I'm glad to see that the radeon 7500 issues are getting some attention. Just want to make sure that distinct issues aren't getting mixed together. I totally agree on Stadler on this one. Firstly I don't use ACPI Secondly I don't experience any garbled screen just a xorg crash the moment I open the lid. (In reply to comment #5) > FWIW, I'm not sure if those other two bugs are duplicates. > > 4436 refers to an X crash after the laptop sleeps (or perhaps hibernates). > > In this bug, X is not crashed; You can move the mouse around, type, etc. and see things going on > (through the garbled display). > > 3844 refers to a problem with dynamic clocks after suspend. > > In this bug, the system has not slept, suspended, or hibernated. The system is awake, it's just that the > screen has been disabled (by the bios) to save energy. > > > Please don't get me wrong, I'm glad to see that the radeon 7500 issues are getting some attention. Just > want to make sure that distinct issues aren't getting mixed together. Bug submitter, any improvements using a current version of xorg? Are you using the radeon framebuffer at the same time? > Bug submitter, any improvements using a current version of xorg? I'm afraid I have not upgraded past FC3 so I am still using the same versions of everything. I will update this bug when I upgrade to FC5 (soon). > Are you using the radeon framebuffer at the same time? I'm not sure what you mean, can you clarify this question please? (In reply to comment #8) > > Bug submitter, any improvements using a current version of xorg? > > I'm afraid I have not upgraded past FC3 so I am still using the same versions of > everything. I will update this bug when I upgrade to FC5 (soon). > > > Are you using the radeon framebuffer at the same time? > > I'm not sure what you mean, can you clarify this question please? Of course. Normally you can choose in the linux kernel which framebuffer that is to drive the screen. In your case you have the choice of a standard vesa framebuffer or the radeon framebuffer. Using the radeon framebuffer gives better performance in consolemode _but_ may introduce bugs when running X as the framebuffer and the X driver may change hardware states behind each others backs. I had a similar problem before where resuming caused a garbled screen. Disabling the radeon framebuffer resolved this issue for me and might do the same for you. I'm seeing what appears to be the same issue, but slightly different on my IBM ThinkPad T42, using X.org 7 (Fedora Core 5). I'm using gnome power manager to suspend system to ram, but on resume - although the system is up, i'm getting a blank black screen with a few pitches of "noise like lines" on the screen every now and again (twice a sec perhaps). In order for me to regain control of the system, I need to blindly ctrl-alt-f1, login and reboot. I'm using radeonfb on my console, but tried without it, with same result. I had a T30 before where this actually worked perfectly. The chipset in my T42 is: VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] Let me know what you need me to provide to narrow this down Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status. Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.