Radeon Gallium on ubuntu

[Sarvatt]

Sorry I didn't see this thread earlier, but if you don't use the xorg.conf option and instead use libgl1-mesa-dri-gallium's r300_dri.so (which is a renamed radeong_dri.so) then X will load the classic mesa driver (/usr/lib/dri/r300_dri.so) because it's hardcoded to look for r300_dri.so in /usr/lib/dri and the gallium package is using a --with-dri-searchpath hack pointing at /usr/lib/dri-gallium. Indirect will use classic mesa instead of the gallium one and you'll notice you have a large amount less GLX Visuals and GLXFBConfigs available in glxinfo even when direct, and GLX over SSH will just segfault. People were reporting compiz problems to me using the /usr/lib/dri-gallium setup as well which were fixed by using the gallium stuff directly in /usr/lib/dri. Making gallium the default driver will break UMS. I added the xorg.conf option as a tradeoff to work around both of those problems.

[Duma]

Please show us your /var/log/Xorg.0.log file.

Adam

I've fresh installed Lucid, I add the same PPA and i reinstall libgl1-mesa-dri-gallium after a system update.

The problem remain, glxgears and glxinfo give me Seg Fault

Here's my Xorg0.log file:
gedit /var/log/Xorg.0.log

[Duma]

Please show us your /var/log/Xorg.0.log file.

Adam

I've fresh installed Lucid, I add the same PPA and i reinstall libgl1-mesa-dri-gallium after a system update.

Here's my Xorg0.log file:
gedit /var/log/Xorg.0.log

[Sharky]

Duma

I have a similar box with ATI-1650+Lucid+OSS(gallium). A 64bit install.
May have slower 3D than fglrx, everything works well with no issues that bother me.

http://pastebin.com/NLu9v3JN

OpenGL vendor string: X.Org R300 Project
OpenGL renderer string: Gallium 0.4 on RV530
OpenGL version string: 2.1 Mesa 7.9-devel
OpenGL shading language version string: 1.20

The only thing I use xorg.conf for is to turn on ColorTiling, everything else is xorg-edgers ppa upgrade + libgl1-mesa-dri-gallium.

Is there a reason for shutting off KMS (nomodeset)?

Software Rasterizer would certainly slow things down, and some issues.

Sharky

[adamk]

I've fresh installed Lucid, I add the same PPA and i reinstall libgl1-mesa-dri-gallium after a system update.

Here's my Xorg0.log file:
gedit /var/log/Xorg.0.log

Well that looks normal, as far as I can tell. Does 'LIBGL_DEBUG=verbose glxinfo' give you any more output? If not, you might have to install the debug version of the gallium package and glxinfo through gdb to find out what's going on.

Adam

[Duma]

Here's verbose glxinfo...

albi@albi-desktop:~$ LIBGL_DEBUG=verbose glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0)
libGL: OpenDriver: trying /usr/lib/dri-gallium/tls/r300_dri.so
libGL: OpenDriver: trying /usr/lib/dri-gallium/r300_dri.so
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 4, (OK)
drmOpenByBusid: Searching for BusID pci:0000:02:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 4, (OK)
drmOpenByBusid: drmOpenMinor returns 4
drmOpenByBusid: drmGetBusid reports pci:0000:02:00.0
Segmentation fault

Thanks a lot for your advices...
Sharky so what do you suggest for me?

[nanonyme]

Here's verbose glxinfo...

Thanks a lot for your advices...
Sharky so what do you suggest for me?

Remove nomodeset switch from kernel line, remove uvesafb from kernel line, use KMS?

[Duma]

If I use KMS:
- can't use compiz with a LOT of lag (looks like use normal open radeon driver)
Without compiz abled
- Here's my glxinfo
- glxgears: I see the gears on movement, here what my terminal give me:

albi@albi-desktop:~$ glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 4014 requests (4014 known processed) with 0 events remaining.
albi@albi-desktop:~$

Should I give you other information?
(i forget to thank you a lot for your help )

[tormod]

gallium on radeon depends on KMS, so make sure you have KMS (kernel modesetting) enabled and working if you want to try out gallium.

[Duma]

gallium on radeon depends on KMS, so make sure you have KMS (kernel modesetting) enabled and working if you want to try out gallium.

Ops... How can i able KMS?
Should I have to recompilate my kernel?