Here is the output of `fbset -i` mode "1280x1024-71" # D: 100.000 MHz, H: 75.758 kHz, V: 71.201 Hz geometry 1280 1024 1280 1024 8 timings 10000 16 16 16 16 8 8 rgba 8/0,8/0,8/0,0/0 endmode Frame buffer device information: Name : OFfb display Address : 0xde000000 Size : 4194304 Type : PACKED PIXELS Visual : STATIC PSEUDOCOLOR XPanStep : 0 YPanStep : 0 YWrapStep : 0 LineLength : 4096 Accelerator : No I can recompile X with debugging on sometime next week to run it in gdb, but it will take some time. The machine is old and slow. <div>On 10/13/06, Michel Dänzer <<a href="mailto:michel@tungstengraphics.com">michel@tungstengraphics.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Fri, 2006-10-13 at 09:31 -0400, Tom Moyer wrote: > The GXT2000P has 32MB of RAM as far as I know. I think part of the > problem might be that X is only seeing 4MB, but for some reason, even > when I specify the amount of VideoRAM, it still only shows 4MB. That's up to the framebuffer device... looks like OFfb only exposes as much memory as the video mode takes up. > On 10/13/06, Rene Rebe <<a href="mailto:rene@exactcode.de">rene@exactcode.de</a>> wrote: > On Friday 13 October 2006 15:01, Tom Moyer wrote: > > I have tried to disable the ShadowFB by setting Option > ShadowFB "false", > > and now I get a signal 11 when I startx. The new log is at > > <a href="http://geodyn.psu.edu/xorg_errors/Xorg.0.log.sig11">http://geodyn.psu.edu/xorg_errors/Xorg.0.log.sig11</a> Hmm, maybe fb tries to access beyond the end of the screen? Can you try running the X server (preferably built with debugging symbols) within gdb? The output of fbset -i would still be interesting as well. -- Earthling Michel Dänzer | <a href="http://tungstengraphics.com">http://tungstengraphics.com</a> Libre software enthusiast | Debian, X and DRI developer </blockquote></div>