Bug 44036 - i810 KDE Xf86 cannot allocate memory
Summary: i810 KDE Xf86 cannot allocate memory
Status: CLOSED DUPLICATE of bug 32338
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 7.1
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-06-10 01:05 UTC by Mike Vanecek
Modified: 2007-04-18 16:33 UTC (History)
0 users

Clone Of:
Last Closed: 2001-06-12 07:12:16 UTC

Attachments (Terms of Use)
Configuration File at time of error (1.79 KB, text/plain)
2001-06-10 01:06 UTC, Mike Vanecek
no flags Details
XF86 log after error (16.86 KB, text/plain)
2001-06-10 01:08 UTC, Mike Vanecek
no flags Details
Output from startx > xoutput 2>&1 (8.42 KB, text/plain)
2001-06-10 01:10 UTC, Mike Vanecek
no flags Details

Description Mike Vanecek 2001-06-10 01:05:41 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.2-2 i686)

Description of problem:
Loading KDE with startx on an i810 gets an error i810 KDE Xf86 cannot
allocate memory 

How reproducible:

Steps to Reproduce:
1. startx (only KDE is installed, do not know what happens with Gnome)
2. Look in XFree86 log.

Additional info:

(WW) I810(0): xf86AllocateGARTMemory: allocation of 1024 pages failed
	(Cannot allocate memory)
(II) I810(0): No physical memory available for 4194304 bytes of DCACHE

Comment 1 Mike Vanecek 2001-06-10 01:06:29 UTC
Created attachment 20699 [details]
Configuration File at time of error

Comment 2 Mike Vanecek 2001-06-10 01:08:53 UTC
Created attachment 20700 [details]
XF86 log after error

Comment 3 Mike Vanecek 2001-06-10 01:10:03 UTC
Created attachment 20701 [details]
Output from startx > xoutput 2>&1

Comment 4 Mike A. Harris 2001-06-12 04:48:34 UTC
Disable the RENDER extension in your config file.  Render isn't supported
on i810.  This means no AA fonts in KDE also, so make sure AA fonts are
disabled.  The missing symbol errors have been fixed already in
XFree86-4.0.3-21 which will be released shortly on my test site.

Does the problem go away if you run "modprobe agpgart" as root prior
to starting X?

Comment 5 Mike A. Harris 2001-06-12 07:12:12 UTC
It appears that this might also be a CMOS misconfiguration problem.
Others have reported i810/815 bugs have went away after correcting
bad settings for memory in their CMOS configuration.

Comment 6 Mike A. Harris 2001-06-12 07:14:17 UTC
This bug is a dupe.  Please update the dupe report with any info.  I'll add
you to the Cc.

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

Note You need to log in before you can comment on or make changes to this bug.