Bug 492176
Summary: | Multihead spanning problems | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Nalley <david> |
Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | airlied, ajax, bskeggs, gene-redhat |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-03-26 01:16:32 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: |
Description
David Nalley
2009-03-25 18:29:55 UTC
I also see the same error message, although with different sizes: required virtual size does not fit available size: requested=(2720, 1024), minimum=(320,200), maximum=(1440, 1440) Smolt: http://www.smolts.org/client/show/pub_cd9ee5b7-022f-4a39-a281-4bd9c1594c27 xrandr: Screen 0: minimum 320 x 200, current 1440 x 1024, maximum 1440 x 1440 LVDS-0 connected 1440x900+0+0 (normal left inverted right x axis y axis) 303mm x 190mm 1440x900 60.0*+ VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm 1280x1024 60.0*+ 75.0 60.0* 1152x864 75.0 1024x768 75.0 60.0 800x600 75.0 60.3 640x480 75.0 59.9 720x400 70.1 DVI-2 disconnected (normal left inverted right x axis y axis) Unfortunately this is the expected behaviour currently. Due to shortcomings in our memory manager for this release we won't be able to resize the framebuffer from it's initial configuration. However, if you configure a non-cloned layout in xorg.conf as described at http://wiki.debian.org/XStrikeForce/HowToRandR12 you should be able to make this work. *** This bug has been marked as a duplicate of bug 487356 *** |