Announcement

**twinkle** · 29 May 2007, 11:29 AM

I have the same problem on a T60 with x1400. It happens only with beryl/Xgl running. When not using beryl it works ok.

**Xipeos** · 03 June 2007, 08:43 AM

You are either trying to run amdcccle with the radeon driver, or have a mismaching libGL file (ex: from Mesa3d). Make sure that the radeon module AND drm are not loaded (modprobe -r radeon drm) and that in your xorg.conf "Driver" is set to fglrx in the Device section.

Next, check that your libs are properly linked. You may have an old libGL somewhere that links before fglrx's one. I've once seen Mesa install libGL.1.5 which linked before fglrx's libGL.1.2 (check in /usr/lib, /usr/local/lib, /usr/lib/xorg or /usr/X11/lib/xorg). Best way probably is to delete libGL.* and reinstall fglrx. But note that Mesa's libGL and fglrx's libGL are NOT compatible, and you won't get DRI with radeon and fglrx libGL (or vice versa).

Hope that helps.

**twinkle** · 03 June 2007, 11:01 AM

I am using fgrlx driver in my xorg.conf. Beryl is working great with all its features. All the libGl are pointing to ATI's libGl.
for example, ldd amdcccle returns this:

Code:

libGL.so.1 => //usr/lib32/opengl/ati/lib/libGL.so.1 (0xf7cae000)

I don't know what is the problem but I think it's related to the fact that running xdpyinfo w/o Xgl returns 34 extensions among them is ATIFGLEXTENSION and a couple more with ATI. While running Xgl I only have 28 and the ATI extensions are missing. I think it's related because doing strace on amdcccle shows that the last thing it tries to do before the seg fault is to write ATIFGLEXTENSION to /tmp/.X11-unix/X0.
Also with Xgl running, the xorg log shows this:

Code:

(II) LoadModule: "glesx.so" (glesx)
(WW) LoadModule: given non-canonical module name "glesx.so"
(WW) Warning, couldn't open module glesx.so

But without Xgl, the first two lines are present but the library is found and loaded.
I don't know much about X and Xgl but I'm pretty sure these things are related to my problem.

And using the 8.37 drivers doesn't help either.

**Xipeos** · 03 June 2007, 12:53 PM

This may seem redundant, but did you try amdcccle and fgl_glxgears on X and not XGL?

I don't think glesx has anything to do with your problem, as it was just recently added and doesn't seem to do anything.

**twinkle** · 04 June 2007, 01:57 AM

With X everything works fine, so I have to chose between amdcccle and the ability to work with LCD screen while the laptop is docked or I can work with Xgl and have all the eyecandy of beryl.
Of course I want it all

I only now tried to run fgl_fglxgrears while Xgl is running and I got this:

Code:

Using GLX_SGIX_pbuffer
Xlib:  extension "XFree86-DRI" missing on display ":0.0".
Error: couldn't get fbconfig

Also running fglrxinfo gives this:

Code:

Xlib:  extension "XFree86-DRI" missing on display ":0.0".
display: :0.0  screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400
OpenGL version string: 1.2 (2.0.6473 (8.37.6))

Why is the XFree86-DRI missing?

**Xipeos** · 04 June 2007, 08:55 AM

Originally posted by twinkle View Post

With X everything works fine, so I have to chose between amdcccle and the ability to work with LCD screen while the laptop is docked or I can work with Xgl and have all the eyecandy of beryl.
Of course I want it all

I only now tried to run fgl_fglxgrears while Xgl is running and I got this:

Code:

Using GLX_SGIX_pbuffer
Xlib:  extension "XFree86-DRI" missing on display ":0.0".
Error: couldn't get fbconfig

Also running fglrxinfo gives this:

Code:

Xlib:  extension "XFree86-DRI" missing on display ":0.0".
display: :0.0  screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400
OpenGL version string: 1.2 (2.0.6473 (8.37.6))

Why is the XFree86-DRI missing?

I can probably tell you if you post your Xorg.log (or is it Xgl.log?). It may have something to do with Xgl, but i have no experience with it.

**twinkle** · 04 June 2007, 09:40 AM

The log can be found here:
http://pastebin.ca/536629

**Xipeos** · 04 June 2007, 09:55 AM

According to your log, there is no problem with DRI, so I have to assume it has something to do with Xgl (ex: Xgl has composite built in, which on X it disables firegl's DRI).

At this point, I can't really help you anymore as I don't know much about Xgl. Good luck though..

**twinkle** · 04 June 2007, 10:28 AM

thanks anyway!

Announcement

amdcccle segmentation fault

amdcccle segmentation fault

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment