| Summary: | ServerLayout section causes both outputs to be disabled in 2-card 4-head setup. | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | abortretryfail | ||||||||||
| Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||||||
| Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||
| Severity: | normal | ||||||||||||
| Priority: | medium | CC: | abortretryfail | ||||||||||
| Version: | unspecified | ||||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||||
| OS: | Linux (All) | ||||||||||||
| Whiteboard: | |||||||||||||
| i915 platform: | i915 features: | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
abortretryfail
2011-09-26 09:33:20 UTC
Created attachment 51628 [details]
xorg.conf for working layout
Created attachment 51629 [details]
Xorg.0.log for working layout
Created attachment 51630 [details]
xorg.conf for broken layout
Created attachment 51631 [details]
Xorg.0.log for broken layout
I have 2 radeon cards (HD5680 and HD2600) set up in a 4-head configuration. If DVI-1 on the HD2600 is Above DVI-2 in the ServerLayout section, xorg errors out and disables both outputs on the HD2600 and logs the following in dmesg: [22676.145643] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id [22676.557971] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id When I change DVI-2 to Above DVI-1, it works as expected. I've worked around this issue by swapping the displays on the physical connectors, but this may be a problem for someone else where that's not an option (ie, HDMI and VGA or something...) See attached log and configuration files for details. -Alex Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases. |
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.