Hide Forgot
When I suspend/resume my desktop with a Radeon 4850 card, the video is corrupted when I resume. It is stretched to the right and looks "ghosty" (kind of like bad analog TV signal reception). If I switch to a console, it looks the same. I tried: - nomodeset: only difference was that trying to switch to a text console after resume was completely corrupted - had mesa-dri-drivers-experimental; removed that - had BIOS "run VGA BIOS after S3" option disabled; tried enabling it and the system froze during resume This is an up-to-date F12 system. The video comes out the HDMI port to a DVI port on an LCD panel. Suspend/resume worked on F11 (had other intermittent problems with disk, but video worked 100%).
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 379354 [details] dmesg after restore
Created attachment 379355 [details] Xorg.0.log after restore
Thank you for your logs. Setting keyword triaged, status to assigned (Fedora 12) per new triage policy. Assigned to airlied, and cc:d to ajax. Please reassign or cc as necessary. This bug has been triaged -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
What is the full reference of your screen ?
I'm afraid I don't know what you are asking. What do you mean by "full reference of your screen"?
For instance: Dell P2310H, or Samsung SyncMaster 172x Ie manufacturer and model of your screen.
Ah, I see. I have a Samsung 2493HM LCD. Because it is the cable I had on hand (and because the monitor's EDID data is bogus on the HDMI port), it is connected via a HDMI cable with a DVI-HDMI adapter on the monitor end (DVI on the monitor to HDMI on the video card). The card is a Gigabyte GV-R485MC-1GI. As a FYI: I did try the latest xorg-x11-*, libdrm*, mesa*, and plymouth* from updates-testing last week; still the same result.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.