Bug 604580
| Summary: | Dual Head setup: Main Monitor goes out of range apparently randomly | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tobias Mueller <fedora-bugs> |
| Component: | xorg-x11-drv-ati | Assignee: | Jérôme Glisse <jglisse> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | jglisse, xgl-maint |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-27 18:21:29 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
|
Description
Tobias Mueller
2010-06-16 09:49:38 UTC
Please attach full dmesg, xorg log, and try with removing the xorg conf. Also does it happens when power management suspend monitor after idle (you can change setting so that it takes less than a minute for pm to turn off monitor). Hm. I was upgrading to Fedora 13 and the installer rebooted. However, an old kernel was loaded (2.6.32.14-127.fc12.x86_64) and I left the machine unattended for >5hrs. When I came back, the passphrase thing for my LUKS container was shown on one monitor and the other was, as described in the report, out of sync. I just installed F13 and I'll try to observe whether it's still an issue. Based on the observation mentioned above, I don't believe it's an X.org issue though. Here comes a dmesg and an Xorg.log just right after the screen blanked while I was working with the machine. The power management settings (from system->preferences->power management) don't seem to have any effect on me. I set "Put display to sleep" to 1 minute but it didn't go blank or anything. Created attachment 424953 [details]
Xorg log which I don't consider to be interesting
Created attachment 424956 [details]
dmesg which I don't consider to be interesting
Created attachment 425218 [details]
Another xorg log
It just happened again: The right monitor went out of sync while I was working (on the left monitor).
The log doesn't seem to be of any interest though.
Created attachment 425223 [details]
Another dmesg which I don't consider to be interesting
looks very uninteresting
I have removed the xorg.conf and I still experience the same issue. My right monitor just went from displaying something sane to "Cannot display this video mode, change computer display input to 1680x1050@60Hz." That's what, according to xrandr, is set up: muelli@bigbox ~ $ xrandr Screen 0: minimum 320 x 200, current 2960 x 1050, maximum 8192 x 8192 DVI-0 connected 1680x1050+1280+0 (normal left inverted right x axis y axis) 474mm x 296mm 1680x1050 60.0*+ 1600x1200 60.0 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1152x864 75.0 70.0 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 72.8 75.0 66.7 60.0 720x400 70.1 DIN disconnected (normal left inverted right x axis y axis) DVI-1 connected 1280x1024+0+26 (normal left inverted right x axis y axis) 376mm x 301mm 1280x1024 60.0 + 75.0* 72.0 1152x864 75.0 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 640x480 72.8 75.0 66.7 60.0 720x400 70.1 640x350 70.1 muelli@bigbox ~ $ After a sudo pm-suspend and a resume, the monitor is back to normal. The xrandr output doesn't look any different. Created attachment 426299 [details]
Another dmesg which I don't consider to be interesting
Created attachment 426301 [details]
Another xorg log
A xrandr --output DVI-0 --off && xrandr --output DVI-0 --right-of DVI-1 --mode 1680x1050 doesn't help it. I need to suspend/resume the machine in order to get the monitor back. The --off actually turns the monitor off, but resetting it yields in the same out-of-sync message. Adjusting version field because it happens on F13. I had to change video cards because I couldn't suspend/resume that often. And Fedora couldn't either: it kept freezing. So given that my other video card works (some nvidia based), I'd say it's either my graphics cards fault (i.e. heat problems) or smth is fishy with the driver or X.Org. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. |