Bug 20860 - 2D part problems + KMS on NV96
Summary: 2D part problems + KMS on NV96
Status: RESOLVED WORKSFORME
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-25 07:57 UTC by David Heidelberg (okias)
Modified: 2009-07-06 05:48 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
dmesg (56.56 KB, text/plain)
2009-03-25 07:58 UTC, David Heidelberg (okias) 		no flags Details
Xorg.log (16.58 KB, text/x-log)
2009-03-25 08:00 UTC, David Heidelberg (okias) 		no flags Details
View All

Description David Heidelberg (okias) 2009-03-25 07:57:15 UTC 
nVidia 9600M GT, NV96.
KMS && MM off: Age of Empires: directdraw unsupported, Openarena loaded without text, images, only sometimes blink cursor in corner virtual 640x480 screen in my  1680x1050.

KMS off && MM on: same result

KMS && MM on: Age of Empires starts (try switch resolution, but screen remains black), music play, system can be used, only problem with LVDS not showing anything. OpenArena crashes Xorg (dmesg and Xorg attached)

It's WITHOUT gallium (P.S. Age of Empires doesn't require 3D, it's 2D game)

glxgears working fine in swrast mode (even in gallium)
Comment 1 David Heidelberg (okias) 2009-03-25 07:58:45 UTC 
Created attachment 24235 [details]
dmesg
Comment 2 David Heidelberg (okias) 2009-03-25 08:00:36 UTC 
Created attachment 24236 [details]
Xorg.log

it's when openarena crash with KMS
Comment 3 David Heidelberg (okias) 2009-05-15 02:35:31 UTC 
Only problem with resize of Age of Empires still exist. OpenArena working fine with both. So only KMS change resolution bug remain.
Comment 4 David Heidelberg (okias) 2009-07-06 05:48:18 UTC 
It works now, in wine window mode...

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.