[Bug 34590] Re: DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64

[audiophyl]

Unfortunately, even with working DRI you won't be seeing any desktop
effects.  Those effects require very specific off-screen rendering
functionality of which Mach64 cards are not capable.  You will, however, see
a fairly drastic boost in more 'general' OpenGL functionality.

Your situation brings up another reason why this bug isn't likely to be
closed anytime soon: Mach64 DRI seems to be hit or miss with results being
insignificant to most users.

As for additional tips...  no clue, really.  In my /etc/X11/xorg.conf I have
the following changed, and I really have no clue if it makes a difference
(meaning I'm too lazy to test, sorry!):

(In Section ServerLayout make sure the following is commented out if it
exists)
#Option "AIGLX" "False"

(The following section may need to be added if it is not present, but I
believe it's there by default in newer Ubuntus)
Section "DRI"
        Mode 0666
EndSection

For more rigorous (and involved) instructions, check for earlier posts from
me in the bug notes.  There are instructions for replacing libGL in the case
that it is the culprit.  However, I really am hoping the DRM modules were
all that needed to be compiled...

-Philip


On Wed, Mar 12, 2008 at 5:19 PM, Roland Arendes <roland at arendes.de> wrote:

> Your hint seems to have brought me one step further. I compiled both
> modules successfully, rebooted, and now have some lines in the Xorg.log
> that indicate that DRI should work -
>
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 8, (OK)
> drmOpenByBusid: Searching for BusID pci:0000:01:00.0
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 8, (OK)
> drmOpenByBusid: drmOpenMinor returns 8
> drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
> (WW) AIGLX: 3D driver claims to not support visual 0x23
> (WW) AIGLX: 3D driver claims to not support visual 0x24
> (WW) AIGLX: 3D driver claims to not support visual 0x25
> (WW) AIGLX: 3D driver claims to not support visual 0x26
> (WW) AIGLX: 3D driver claims to not support visual 0x27
> (WW) AIGLX: 3D driver claims to not support visual 0x28
> (WW) AIGLX: 3D driver claims to not support visual 0x29
> (WW) AIGLX: 3D driver claims to not support visual 0x2a
> (WW) AIGLX: 3D driver claims to not support visual 0x2b
> (WW) AIGLX: 3D driver claims to not support visual 0x2c
> (WW) AIGLX: 3D driver claims to not support visual 0x2d
> (WW) AIGLX: 3D driver claims to not support visual 0x2e
> (WW) AIGLX: 3D driver claims to not support visual 0x2f
> (WW) AIGLX: 3D driver claims to not support visual 0x30
> (WW) AIGLX: 3D driver claims to not support visual 0x31
> (WW) AIGLX: 3D driver claims to not support visual 0x32
> (II) AIGLX: Loaded and initialized /usr/lib/dri/mach64_dri.so
> (II) GLX: Initialized DRI GL provider for screen 0
> Atom 4, CARD32 4, unsigned long 4
>
> However, enabling Desktop effects does not work. As you guessed, I have
> a 1024x768 TFT LCD with 8megs of RAM. I moved to 16bits beforehand.
>
> roland at roland-laptop:/var/log$ glxinfo | grep direct
> Locking assertion failure.  Backtrace:
> #0 /usr/lib/libxcb-xlib.so.0 [0xb7c61767]
> #1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_unlock+0x31) [0xb7c618b1]
> #2 /usr/lib/libX11.so.6 [0xb7cf7421]
> #3 /usr/X11R6/lib/libGL.so.1(__glXInitialize+0x596) [0xb7f2d3cc]
> #4 /usr/X11R6/lib/libGL.so.1 [0xb7f29fc8]
> #5 /usr/X11R6/lib/libGL.so.1(glXChooseVisual+0x29) [0xb7f2b124]
> #6 glxinfo [0x8049448]
> #7 glxinfo [0x8049b23]
> #8 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7db5450]
> #9 glxinfo [0x8048d51]
> direct rendering: No (If you want to find out why, try setting
> LIBGL_DEBUG=verbose.
>
> --
> DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64
> https://bugs.launchpad.net/bugs/34590
> You received this bug notification because you are a direct subscriber
> of the bug.
>

-- 
DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64
https://bugs.launchpad.net/bugs/34590
You received this bug notification because you are a member of Kernel
Bugs, which is a direct subscriber.