On Wed, 2007-10-17 at 07:41 +0100, Richard W.M. Jones wrote: > Rick Stevens wrote: > > (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) > > (WW) intel(0): /dev/agpgart is either not available, or no memory is > > available > > for allocation. Using pre-allocated memory only. > > (==) intel(0): VideoRam: 7676 KB > > (EE) intel(0): [dri] I830CheckDRIAvailable failed: glx not loaded > > (II) intel(0): Allocating 255 scanlines for pixmap cache > > (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too > > low? > > (EE) intel(0): Couldn't allocate video memory > > Are you starting X immediately after booting, or some time later? Standard time. All I did was boot the xen0 kernel instead of the standard one. It works on every other machine I have, just not this one. > I don't think the agpgart message is relevant. What I think is > happening is that the driver cannot allocate enough videoram, or perhaps > cannot allocate it contiguously in physical RAM or something along those > lines. I think it is. The standard kernel does fire up /dev/agpgart and it does allocate memory: (II) intel(0): Kernel reported 488960 total, 1 used (II) intel(0): I830CheckAvailableMemory: 1955836 kB available (==) intel(0): VideoRam: 262144 KB <<<<-----NOTE! (EE) intel(0): [dri] I830CheckDRIAvailable failed: glx not loaded (II) intel(0): Allocating 5472 scanlines for pixmap cache (II) intel(0): Memory allocation layout: (II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB) (II) intel(0): 0x00020000-0x00029fff: HW cursors (40 kB) (II) intel(0): 0x0002a000-0x00031fff: logical 3D context (32 kB) (II) intel(0): 0x00032000-0x00041fff: exa G965 state buffer (64 kB) (II) intel(0): 0x00050000-0x02147fff: front buffer (33760 kB) (II) intel(0): 0x0077f000: end of stolen memory (II) intel(0): 0x02148000-0x02157fff: xaa scratch (64 kB) (II) intel(0): 0x10000000: end of aperture Same xorg.conf file. > In any case you should read the i810 manpage (`man i810') and see if any > of the many tips / configuration settings in that page makes any > difference at all. (Particularly play with increasing or decreasing > VideoRam, and disabling DRI). I'll do that, but under the standard kernel it allocates video RAM just fine. It doesn't under the xen0 kernel. UPDATE: Just tried it. I did screw up and just say "256" rather than "256MB". /dev/agpgart still doesn't exist. The only change I see is a warning in the log: (WW) intel(0): VideoRam configuration found, which is no longer recommended. (II) intel(0): Continuing with default 262144kB VideoRam instead of 256 kB. The 262144kB bit is the same as under the regular kernel but /dev/agpart still doesn't exist. This is more and more a Xen kernel issue. > If that doesn't help then it's probably a general Xen problem, so asking > about this upstream on xen-users[1] or xen-devel[2] lists could help. Yeah, I'm thinking about that. > In any case, if you find a way to fix it please let us know. I'll keep you posted. Side note to Rich...it'd be nice if the list was in your To: as opposed to being in the Cc:. That's why I posted directly to you last time... I tend to use "Reply" not "Reply All". ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens@xxxxxxxxxxxx - - CDN Systems, Internap, Inc. http://www.internap.com - - - - Lottery: A tax on people who are bad at math. - ---------------------------------------------------------------------- -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
