Can't get X to start in 1280 x 1024 resolution

[Russell Shaw]

Tom wrote:
> --- Russell Shaw <rjshaw at netspace.net.au> wrote:
> 
>>>I can't figure out why it won't
>>>start at all when I put in a modes
>>>line exactly like you have above.
>>
>>That's when you should see what the
>>log file says.
> 
> 
> I included that the first time, but I
> will repeat the relevant parts of it.
> I don't really understand the problem
> (the reason I asked the list in the
> first place :) ).
> 
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 7, (OK)
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 7, (OK)
> drmOpenByBusid: Searching for BusID pci:0000:00:01.0
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 7, (OK)
> drmOpenByBusid: drmOpenMinor returns 7
> drmOpenByBusid: drmGetBusid reports pci:0000:00:01.0
> (II) I810(0): [drm] DRM interface version 1.2
> (II) I810(0): [drm] created "i810" driver at busid "pci:0000:00:01.0"
> (II) I810(0): [drm] added 8192 byte SAREA at 0xd8901000
> (II) I810(0): [drm] mapped SAREA 0xd8901000 to 0xb7945000
> (II) I810(0): [drm] framebuffer handle = 0xf8000000
> (II) I810(0): [drm] added 1 reserved context for kernel
> (II) I810(0): [drm] Registers = 0xff000000
> (II) I810(0): [agp] dcacheHandle : 0x3
> (II) I810(0): [agp] GART: Found 4096K Z buffer memory
> (II) I810(0): [agp] Bound backbuffer memory
> (EE) I810(0): [agp] Unable to bind system texture memory. Disabling
> DRI.
> (II) I810(0): [drm] removed 1 reserved context for kernel
> (II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xd8901000 at
> 0xb7945000
> (II) I810(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is
> 0x0000
> (II) I810(0): Setting dot clock to 108.0 MHz [ 0x10 0x2 0x20 ] [ 18 4 2
> ]
> (II) I810(0): chose watermark 0x22210000: (tab.freq 108.0)
> (II) I810(0): xf86BindGARTMemory: bind key 2 at 0x00000000 (pgoffset 0)
> (WW) I810(0): xf86BindGARTMemory: binding of gart memory with key 2
>         at offset 0x0 failed (Device or resource busy)
> 
> Fatal server error:
> AddScreen/ScreenInit failed for driver 0
> 
>>There shouldn't be much change in
>>speed, but it might use double the
>>video ram. But you get 8 bits per
>>r/g/b pixel or 256 levels per colour
>>channel which would make things look
>>much better.
> 
> What about DRI? If I understand (far
> from a sure thing :) ), it won't work
> with a pixel depth greater than 16.

It seems only 16-bit is accelerated. Maybe you need to
increase your VideoRam.

Google for README.DRI, or get it from the sources:

xorg/xserver/hw/xfree86/doc/README.DRI



10.2.3  Troubleshooting

    o 3D acceleration for the i810 is only available in the 16 bit/pixel
      screen mode at this time.  32bpp acceleration is not supported by this
      hardware.  Use xdpyinfo to verify that all your visuals are depth 16.
      Edit your XF86Config file if needed.

    o The i810 uses system ram for video and 3d graphics.  The X server will
      ordinarily reserve 4mb of ram for graphics, which is too little for an
      effective 3d setup.  To tell the driver to use a larger amount, specify
      a VideoRam option in the Device section of your XF86Config file.  A num-
      ber between 10000 and 16384 seems adequate for most requirements.  If
      too little memory is available for DMA buffers, back and depth buffers
      and textures, direct rendering will be disabled.

10.2.4  Performance and Features

Basically all of the i810 features which can be exposed through OpenGL 1.2
are implemented.  However, the following OpenGL features are implemented in
software and will be slow:

    o Stencil buffer and accumulation buffer operations

    o Blend subtract, min/max and logic op blend modes

    o glColorMask when any mask is set to false

    o GL_SEPARATE_SPECULAR_COLOR lighting mode

    o glDrawBuffer(GL_FRONT_AND_BACK)

    o Using 1D or 3D textures

    o Using texture borders