Created attachment 15745 [details] Complete log of Xserver It's not possible to limit the size of videoram used by videocard. It eats too much of RAM on low-end system with only 256MB ram. <pre> (WW) intel(0): VideoRam configuration found, which is no longer recommended. (II) intel(0): Continuing with default 262144kB VideoRam instead of 16384 kB. (II) intel(0): Kernel reported 50176 total, 1 used (II) intel(0): I830CheckAvailableMemory: 200700 kB available </pre>
yeah, current driver ignores VideoRam set. Originally user usually ask driver to allocate for more mem with this option, but current driver wants more mem natually for all 2D and 3D memory needs, so the option doesn't make sense for this. On the other hand like if user don't want so much features which eat most of memory available for gfx device, you can disable those features instead, like "DRI" option to disable 3D memory allocations, or "NoAccel" to disable 2D accel memory allocations.
So I will use i810 driver, because it is much faster im 3D rendering (supertuxkart runs with normal speed), with only 16MB ram defined by VideoRam set. intel eats cca 50MB more memory and supertuxkart has 1fps :-( glxgears has also less fps. I don't want to disable 3D rendering. Can I ask, why it is so hungry and lazy ??? (In reply to comment #1) > yeah, current driver ignores VideoRam set. Originally user usually ask driver > to allocate for more mem with this option, but current driver wants more mem > natually for all 2D and 3D memory needs, so the option doesn't make sense for > this. > > On the other hand like if user don't want so much features which eat most of > memory available for gfx device, you can disable those features instead, like > "DRI" option to disable 3D memory allocations, or "NoAccel" to disable 2D accel > memory allocations. >
This problem should go away with intel-batchbuffer merge.
This option won't be supported any more. sorry.
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.