| 1 |
On Mon, 2006-05-01 at 13:21 +0200, Jannis Achstetter wrote: |
| 2 |
> You can check your config with "glxinfo | grep direct" which should |
| 3 |
> return "Yes". |
| 4 |
|
| 5 |
$ glxinfo | grep direct |
| 6 |
direct rendering: No |
| 7 |
OpenGL renderer string: Mesa GLX Indirect |
| 8 |
|
| 9 |
> If it doesn't, check your /var/log/Xorg.0.log (assuming |
| 10 |
> we are talking about display "0". |
| 11 |
|
| 12 |
I see a: |
| 13 |
(II) LoadModule: "dri" |
| 14 |
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so |
| 15 |
(II) Module dri: vendor="X.Org Foundation" |
| 16 |
compiled for 7.0.0, module version = 1.0.0 |
| 17 |
ABI class: X.Org Server Extension, version 0.2 |
| 18 |
|
| 19 |
and |
| 20 |
|
| 21 |
(WW) RADEON(0): Enabling DRM support |
| 22 |
|
| 23 |
*** Direct rendering support is highly experimental for Radeon 9500 |
| 24 |
*** and newer cards. The 3d mesa driver is not provided in this tree. |
| 25 |
*** A very experimental (and incomplete) version is available from Mesa CVS. |
| 26 |
*** Additional information can be found on http://r300.sourceforge.net |
| 27 |
*** This message has been last modified on 2005-08-07. |
| 28 |
|
| 29 |
|
| 30 |
Don't tell me my 9600 isn't supported by the radeon driver?... |
| 31 |
also, there's this interesting section that I'm having trouble understanding: |
| 32 |
(WW) RADEON(0): Enabling DRM support |
| 33 |
|
| 34 |
*** Direct rendering support is highly experimental for Radeon 9500 |
| 35 |
*** and newer cards. The 3d mesa driver is not provided in this tree. |
| 36 |
*** A very experimental (and incomplete) version is available from Mesa CVS. |
| 37 |
*** Additional information can be found on http://r300.sourceforge.net |
| 38 |
*** This message has been last modified on 2005-08-07. |
| 39 |
|
| 40 |
drmOpenDevice: node name is /dev/dri/card0 |
| 41 |
drmOpenDevice: open result is 6, (OK) |
| 42 |
drmOpenDevice: node name is /dev/dri/card0 |
| 43 |
drmOpenDevice: open result is 6, (OK) |
| 44 |
drmOpenByBusid: Searching for BusID pci:0000:01:00.0 |
| 45 |
drmOpenDevice: node name is /dev/dri/card0 |
| 46 |
drmOpenDevice: open result is 6, (OK) |
| 47 |
drmOpenByBusid: drmOpenMinor returns 6 |
| 48 |
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 |
| 49 |
(II) RADEON(0): [drm] DRM interface version 1.2 |
| 50 |
(II) RADEON(0): [drm] created "radeon" driver at busid "pci:0000:01:00.0" |
| 51 |
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe13b2000 |
| 52 |
(II) RADEON(0): [drm] mapped SAREA 0xe13b2000 to 0xb7f07000 |
| 53 |
(II) RADEON(0): [drm] framebuffer handle = 0xf0000000 |
| 54 |
(II) RADEON(0): [drm] added 1 reserved context for kernel |
| 55 |
(WW) RADEON(0): [agp] AGP not available |
| 56 |
(EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. |
| 57 |
(II) RADEON(0): [agp] You may want to make sure the agpgart kernel module |
| 58 |
is loaded before the radeon kernel module. |
| 59 |
(II) RADEON(0): [drm] removed 1 reserved context for kernel |
| 60 |
(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xe13b2000 at 0xb7f07000 |
| 61 |
|
| 62 |
but agpgart and radeon are both "compiled in" to the kernel. |
| 63 |
|
| 64 |
I heard something about the RV350 or RV300 (not sure) chipset not being |
| 65 |
supported - is this true? |
| 66 |
|
| 67 |
thanks, |
| 68 |
-- |
| 69 |
Iain Buchanan <iaindb at netspace dot net dot au> |
| 70 |
|
| 71 |
<Iambe> conning the most intellegent people on the planet is not easy |
| 72 |
|
| 73 |
-- |
| 74 |
gentoo-user@g.o mailing list |
Archives