Bug 492175

Summary:	nouveau does not do dynamic framebuffer reallocation for multihead setups
Product:	[Fedora] Fedora	Reporter:	Jan ONDREJ <ondrejj>
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, awilliam, bskeggs, control-center-maint, rstrode, thuforuk
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 22:39:52 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 Jan ONDREJ 2009-03-25 18:24:25 UTC

Description of problem:
When trying to set virtual resolution on multihead configuration to resolution larger than 1680x1680, then it shows information, that I can't. On current displays this is not very large and I don't know, why this application can't allow me to set larger resolution.

May be I should report this bug to nouveau driver, I am not sure.

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. set 1. display to 1280x1024
2. set 2. display to 1280x1024
3. apply
  
Actual results:
fails, I have no exact message now.

Expected results:
set display

Comment 1 Adam Williamson 2009-03-26 18:17:32 UTC

This is a driver issue, nothing to do with GNOME.

Ben, it seems nouveau has the same problem intel used to have: it sets a square framebuffer the size of the largest dimension of the primary display, which is obviously not enough for multihead. What's the deal here? Is dynamic framebuffer reallocation planned? Does the old intel dodge of a Virtual line in xorg.conf get around the problem?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Ben Skeggs 2009-03-26 22:39:52 UTC

Yeah, it's the same problem as intel had before framebuffer resize.  It's planned, but not currently viable in most situations.  I could probably implement it for pre-nv5x cards very quickly for brave users that want to test some other mostly untested code at the same time.

Adding a Virtual line will work around the issue.

*** This bug has been marked as a duplicate of bug 487356 ***