Summary: | Small resolution after restarting X | ||
---|---|---|---|
Product: | xorg | Reporter: | Sebastian Noack <sebastian.noack> |
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> |
Status: | RESOLVED WONTFIX | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | critical | ||
Priority: | medium | ||
Version: | 7.2 (2007.02) | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Description
Sebastian Noack
2007-11-18 08:31:49 UTC
I also tried two older versions of the linux kernel (2.6.18.8 and 2.6.23.1) and the new xorg-7.3 with xorg-server-1.4. But the problem still exists. I am currently using the "vesa" driver instead of the "radeon" and it works. But this doesn't solved this bug. Please attach (as opposed to cutting and pasting) your xorg logs (working and non-working). Created attachment 12645 [details]
Log file after first start with radeon driver, when it still works as expected.
Created attachment 12646 [details] [review] Log file after second start with radeon driver, when it fails as described in this bug. Created attachment 12647 [details]
Log file after starting with vesa driver.
The second time around the driver is finding a second monitor attached for some reason and attempting to use it. The following should fix it: Option "MergedFB" "FALSE" Thanks. This worked for me. But even though I don't use MergedFB, shouldn't it work with the radeon driver? (In reply to comment #7) > Thanks. This worked for me. But even though I don't use MergedFB, shouldn't it > work with the radeon driver? > For some reason it's detecting a phantom monitor on the second start up which is causing your problem. Turning off mergedfb causes the driver to ignore the second output. The old version of the driver is no longer actively maintained. Please upgrade to the latest version. |
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.