|
From: Alex D. <ale...@gm...> - 2006-11-27 16:25:50
|
On 11/26/06, Micha Feigin <mi...@po...> wrote: > My system is running kernel 2.6.18.3 with debian unstable. I installed > the mach64 drm module from the git sources (compiled locally) and it loads fine > with the message: > > [drm] Initialized drm 1.1.0 20060810 PCI: Unable to reserve mem region #1:1000000@e9000000 for device 0000:01:00.0 > [drm] Initialized mach64 2.0.0 20060718 on minor 0: > [drm] Used old pci detect: framebuffer loaded > > I then start X and I get that direct rendering is disabled. Looking in dmesg > the only message is: > > [drm:mach64_dma_init] *ERROR* mach64_dma_init called without lock held, held 0 owner 00000000 cf64f900 > [drm:drm_unlock] *ERROR* Process 5352 using kernel context 0 > > and in Xorg.0.log: > > (II) ATI(0): [drm] DRM interface version 1.3 > (II) ATI(0): [drm] created "mach64" driver at busid "pci:0000:01:00.0" > (II) ATI(0): [drm] added 8192 byte SAREA at 0xd0d55000 > (II) ATI(0): [drm] mapped SAREA 0xd0d55000 to 0xb729a000 > (II) ATI(0): [drm] framebuffer handle = 0xe9000000 > (II) ATI(0): [drm] added 1 reserved context for kernel > (EE) ATI(0): [dri] ATIDRIScreenInit failed because of a version mismatch. > [dri] mach64.o kernel module version is 2.0.0, but version 1.0 or greater is needed. > [dri] Disabling DRI. > > Any way to solve this or is the xorg version in debian unstable too old? > you need the ati ddx from git and the latest libdrm. Alex |