Bug#523724: Further information as requested

[Michel Dänzer]

On Wed, 2009-04-15 at 14:47 +0100, Anthony Campbell wrote:
> 
> 2. I don't know why direct rendering is shown as disabled in the log
> file. glxinfo says it is enabled with both versions of xorg.

It's probably using the software rasterizer swrast_dri.so, which
(technically correctly) reports direct rendering.


> 3. /proc/mtrr is different with the two versions. With the older
> (working) version I get:
> 
>  reg00: base=0x000000000 (    0MB), size= 1024MB, count=1: write-back
>  reg01: base=0x03ff00000 ( 1023MB), size=    1MB, count=1: uncachable
>  reg02: base=0x0d8000000 ( 3456MB), size=  128MB, count=1: write-combining
> 
> With the newer one I get only:
> 	reg00: base=0x000000000 (    0MB), size= 1024MB, count=1: write-back
> 	reg01: base=0x03ff00000 ( 1023MB), size=    1MB, count=1: uncachable

That could be the problem then. I don't think it's due to the driver
though but either xserver-xorg-core or possibly libpciaccess0.


> 4. Here is the output from dmesg. I don't know if the stuff about
> missing firmware at the bottom is relevant.

[...]

> [   44.844178] [drm] Initialized radeon 1.29.0 20080528 on minor 0
> [   46.024870] [drm] Setting GART location based on new memory map
> [   46.027874] [drm] Loading R500 Microcode
> [   46.027881] platform radeon_cp.0: firmware: requesting radeon/R520_cp.bin
> [   46.079325] radeon_cp: Failed to load firmware "radeon/R520_cp.bin"
> [   46.079332] [drm:radeon_do_init_cp] *ERROR* Failed to load firmware!

It explains why direct rendering is disabled, you probably want to
install the firmware-linux package.


-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer