Bug 12250 - GartSize not properly configured
Summary: GartSize not properly configured
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-01 07:24 UTC by Nicolò Chieffo
Modified: 2008-09-02 00:37 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Nicolò Chieffo 2007-09-01 07:24:15 UTC
using ubuntu 7.10 and fedora 8
xserver-xorg 1.3
ati 6.7.192
radeon mobility 9700 64MB

the Gart Size is automatically put to 8MB for my video card. this prevents running games with compiz enabled.

*********************************WARN_ONCE*********************************
File r300_vertexprog.c function valid_dst line 333
Output 3 not used by fragment program
***************************************************************************
*********************************WARN_ONCE*********************************
File radeon_mm.c function radeon_mm_alloc line 216
Ran out of GART memory (for 1048576)!
Please consider adjusting GARTSize option.
***************************************************************************

setting the GartSize to 64 fixes the problem.
Is it possible to automatically put the GartSize to a decent value?
Comment 1 Dave Airlie 2007-09-02 00:12:27 UTC
Not until we get a new memory manager support for radeon into place. it might be practical to make r300 cards get at least 16-32MB maybe, but this is memory we allocate and is wasted for users who don't need it.
Comment 2 Nicolò Chieffo 2007-09-02 04:10:12 UTC
Ok, thank you for the explanation.
Is the memory manager in the near future todo list?
Comment 3 Tormod Volden 2008-08-08 14:39:56 UTC
This has at least partly been fixed by commit 5b5441f8cc119db0d1e03dd35bd06015a26270dd (Increase default GART size to 32MB on >=R300)


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.