From: <si...@hi...> - 2002-02-14 15:24:07
|
I've just installed an original Radeon QD 32MB DDR, built XFree86 4.2 from CVS, built the mesa-4-0-branch of the DRI CVS tree, and installed them both, along with kernel 2.4.18-pre9. X starts up nicely (and quickly) and opengl apps run successfully, but without hardware acceleration.=20 XFree86.log shows an apparently normal DRM/DRI initialisation, with no errors at all listed, and ending by saying direct rendering is=20 enabled: drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 5, (OK) drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 5, (OK) drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 5, (OK) drmGetBusid returned '' (II) RADEON(0): [drm] created "radeon" driver at busid "PCI:1:5:0" (II) RADEON(0): [drm] added 8192 byte SAREA at 0xe0a7c000 (II) RADEON(0): [drm] mapped SAREA 0xe0a7c000 to 0x40016000 (II) RADEON(0): [drm] framebuffer handle =3D 0xd8000000 (II) RADEON(0): [drm] added 1 reserved context for kernel (II) RADEON(0): [agp] Mode 0x0f000201 [AGP 0x1022/0x7006; Card 0x1002/0x514= 4] (II) RADEON(0): [agp] 8192 kB allocated with handle 0xe2a80000 (II) RADEON(0): [agp] ring handle =3D 0xe8000000 (II) RADEON(0): [agp] Ring mapped at 0x42261000 (II) RADEON(0): [agp] ring read ptr handle =3D 0xe8101000 (II) RADEON(0): [agp] Ring read ptr mapped at 0x40018000 (II) RADEON(0): [agp] vertex/indirect buffers handle =3D 0xe8102000 (II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0x42362000 (II) RADEON(0): [agp] AGP texture map handle =3D 0xe8302000 (II) RADEON(0): [agp] AGP Texture map mapped at 0x42562000 (II) RADEON(0): [drm] register handle =3D 0xefe80000 (II) RADEON(0): [dri] Visual configs initialized (II) RADEON(0): CP in BM mode (II) RADEON(0): Using 8 MB AGP aperture (II) RADEON(0): Using 1 MB for the ring buffer (II) RADEON(0): Using 2 MB for vertex/indirect buffers (II) RADEON(0): Using 5 MB for AGP textures (II) RADEON(0): Memory manager initialized to (0,0) (1280,2047) (II) RADEON(0): Reserved area from (0,1024) to (1280,1026) (II) RADEON(0): Largest offscreen area available: 1280 x 1021 (II) RADEON(0): Reserved back buffer at offset 0xa00000 (II) RADEON(0): Reserved depth buffer at offset 0xf00000 (II) RADEON(0): Reserved 12288 kb for textures at offset 0x1400000 (=3D=3D) RADEON(0): Backing store disabled (=3D=3D) RADEON(0): Silken mouse enabled (II) RADEON(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles Solid Lines Dashed Lines Offscreen Pixmaps Setting up tile and stipple cache: 32 128x128 slots 9 256x256 slots (II) RADEON(0): Acceleration enabled (II) RADEON(0): Using hardware cursor (scanline 4104) (II) RADEON(0): Largest offscreen area available: 1280 x 1019 (II) RADEON(0): X context handle =3D 0x00000002 (II) RADEON(0): [drm] installed DRM signal handler (II) RADEON(0): [DRI] installation complete (II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers (II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers (II) RADEON(0): Direct rendering enabled glxinfo has a different opinion: name of display: :0.0 display: :0 screen: 0 direct rendering: No server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context client glx vendor string: SGI client glx version string: 1.2 client glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context GLX extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context OpenGL vendor string: Mesa project: www.mesa3d.org OpenGL renderer string: Mesa GLX Indirect OpenGL version string: 1.3 Mesa 4.0.1 As far as I can tell all the libraries are the right ones - libGL.so is the one installed by the DRI build, as is libOSMesa.so, and the symlinks point to the right places. ldd indicates that the right files are being loaded. xdpyinfo lists the GLX, SGI-GLX and XFree86-DRI extensions. I've been running DRI successfully for the last six months or so with a g400, without any such problems - it's only with the Radeon that these problems come up. Thanks for any help, Simon Fowler --=20 PGP public key Id 0x144A991C, or ftp://bg77.anu.edu.au/pub/himi/himi.asc (crappy) Homepage: http://bg77.anu.edu.au doe #237 (see http://www.lemuria.org/DeCSS)=20 My DeCSS mirror: ftp://bg77.anu.edu.au/pub/mirrors/css/=20 |