Bug 25072 - KMS Gf 6200 - wrong fb and X resolution
Summary: KMS Gf 6200 - wrong fb and X resolution
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-13 07:40 UTC by David Heidelberg (okias)
Modified: 2010-01-26 11:31 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg (35.79 KB, text/plain)
2009-11-13 07:40 UTC, David Heidelberg (okias)
no flags Details
Xorg.log (25.69 KB, text/plain)
2009-11-13 07:41 UTC, David Heidelberg (okias)
no flags Details
lspci -vvv (8.31 KB, text/plain)
2009-11-13 07:41 UTC, David Heidelberg (okias)
no flags Details
console_photo (236.91 KB, image/jpeg)
2009-11-13 07:44 UTC, David Heidelberg (okias)
no flags Details

Description David Heidelberg (okias) 2009-11-13 07:40:45 UTC
Created attachment 31171 [details]
dmesg

With same LCD work fine on NV17
Comment 1 David Heidelberg (okias) 2009-11-13 07:41:13 UTC
Created attachment 31172 [details]
Xorg.log
Comment 2 David Heidelberg (okias) 2009-11-13 07:41:43 UTC
Created attachment 31173 [details]
lspci -vvv
Comment 3 David Heidelberg (okias) 2009-11-13 07:44:40 UTC
Created attachment 31174 [details]
console_photo

As you can see, only circa 1/4 screen is used. When I switch to Xorg, fullscreen is used...
Comment 4 David Heidelberg (okias) 2009-11-13 07:47:58 UTC
Monitor is of course connected over DVI, can't test with VGA cable (no cable around me). His correct resolution is 1440x900/60 or 75hz.
Comment 5 Francisco Jerez 2009-11-23 08:19:26 UTC
Does it work with latest git? If it doesn't, could you grab an mmiotrace from the blob as explained here [1]?

[1] https://bugs.freedesktop.org/show_bug.cgi?id=24996#c18
Comment 6 David Heidelberg (okias) 2010-01-26 11:31:56 UTC
Fixed. Tested with 2.6.33-git.


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.