Installing latest Open Source ATI drivers under Ubuntu 8.04

Printable View

Show 40 post(s) from this thread on one page

07-10-2008, 04:23 PM
groo_pcd

Hi tormod, just created a new thread.
My apologies, i just posted here because i thought it was relevant.

Best regards.

Update, new thread:
07-10-2008, 04:34 PM
benitoa

Quote:

Originally Posted by benitoa

Hi here it is:
"LIBGL_DEBUG=verbose glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 5.3.0 r200 (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/r200_dri.so
libGL error: dlopen /usr/lib/dri/r200_dri.so failed (/usr/lib/dri/r200_dri.so: undefined symbol: _glapi_tls_Context)
libGL error: unable to load driver: r200_dri.so
display: :0 screen: 0
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:"

This is my Xorg log too:
(==) RADEON(0): Backing store disabled
(II) RADEON(0): [DRI] installation complete
(II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers
(II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers
(II) RADEON(0): [drm] dma control initialized, using IRQ 11
(II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808
(WW) RADEON(0): DRI init changed memory map, adjusting ...
(WW) RADEON(0): MC_FB_LOCATION was: 0xebffe800 is: 0xebffe800
(WW) RADEON(0): MC_AGP_LOCATION was: 0xffffffc0 is: 0xe07fe000
(II) RADEON(0): RADEONRestoreMemMapRegisters() :
(II) RADEON(0): MC_FB_LOCATION : 0xebffe800 0xebffe800
(II) RADEON(0): MC_AGP_LOCATION : 0xe07fe000
(II) RADEON(0): Direct rendering enabled
(II) RADEON(0): Render acceleration enabled
(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
Scanline Image Writes
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
14 512x512 slots
(II) RADEON(0): Acceleration enabled
(II) RADEON(0): DPMS enabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Using hardware cursor 0 (scanline 1202)
(II) RADEON(0): Using hardware cursor 1 (scanline 1204)
(II) RADEON(0): Largest offscreen area available: 1408 x 4749
(II) RADEON(0): No video input capabilities detected and no information is provided - disabling multimedia i2c
(II) Loading sub module "theatre_detect"
(II) LoadModule: "theatre_detect"
(II) Loading /usr/lib/xorg/modules/multimedia//theatre_detect_drv.so
(II) Module theatre_detect: vendor="X.Org Foundation"
compiled for 1.4.0.90, module version = 1.0.0
ABI class: X.Org Video Driver, version 2.0
(II) RADEON(0): no multimedia table present, disabling Rage Theatre.
(II) RADEON(0): Set up overlay video
(II) RADEON(0): Textured video disabled on RV250 due to HW bug
(II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(--) RandR disabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension XAccessControlExtension
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
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
(EE) AIGLX error: dlopen of /usr/lib/dri/r200_dri.so failed (/usr/lib/dri/r200_dri.so: undefined symbol: _glapi_tls_Context)
(EE) AIGLX: reverting to software rendering
(II) Loading sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/lib/xorg/modules/extensions//libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
compiled for 1.4.0.90, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) GLX: Initialized MESA-PROXY GL provider for screen 0
(II) RADEON(0): Setting screen physical size to 370 x 277
Atom 4, CARD32 4, unsigned long 4
[.....]

benoit@mintlab ~ $ locate libGL.so
/usr/lib/libGL.so
/usr/lib/libGL.so.1
/usr/lib/libGL.so.1.2
/usr/lib/fglrx/libGL.so.1.2.xlibmesa
/usr/lib/fglrx/libGL.so.1.xlibmesa

benoit@mintlab ~ $ ldd /usr/X11R6/bin/glxinfo
linux-gate.so.1 => (0xb7fdd000)
libGL.so.1 => /usr/lib/libGL.so.1 (0xb7f52000)
libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xb7f2d000)
libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7ddd000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xb7cf6000)
libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb7cde000)
libXext.so.6 => /usr/lib/libXext.so.6 (0xb7cd0000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7cc5000)
/lib/ld-linux.so.2 (0xb7fde000)
libxcb-xlib.so.0 => /usr/lib/libxcb-xlib.so.0 (0xb7cc2000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb7caa000)
libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb7ca6000)
libXau.so.6 => /usr/lib/libXau.so.6 (0xb7ca3000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb7c9e000)

$ls -al /usr/lib/libGL.*
benoit@mintlab ~ $ ls -al /usr/lib/libGL*
lrwxrwxrwx 1 root root 16 2008-06-22 01:33 /usr/lib/libGLEW.so.1.5 -> libGLEW.so.1.5.0
-rw-r--r-- 1 root root 225068 2008-02-11 17:48 /usr/lib/libGLEW.so.1.5.0
lrwxrwxrwx 1 root root 10 2008-07-09 23:38 /usr/lib/libGL.so -> libGL.so.1
lrwxrwxrwx 1 root root 12 2008-07-04 23:44 /usr/lib/libGL.so.1 -> libGL.so.1.2
-rw-r--r-- 1 root root 478188 2008-06-11 11:51 /usr/lib/libGL.so.1.2
lrwxrwxrwx 1 root root 20 2008-07-09 23:38 /usr/lib/libGLU.so.1 -> libGLU.so.1.3.070100
-rw-r--r-- 1 root root 532520 2008-07-04 19:38 /usr/lib/libGLU.so.1.3.070100

benoit@mintlab ~ $ ls -al /usr/lib/dri/r*
-rw-r--r-- 1 root root 2132308 2008-07-04 19:38 /usr/lib/dri/r128_dri.so
-rw-r--r-- 1 root root 2199892 2008-07-04 19:38 /usr/lib/dri/r200_dri.so
-rw-r--r-- 1 root root 2233268 2008-07-04 19:38 /usr/lib/dri/r300_dri.so
-rw-r--r-- 1 root root 2167928 2008-07-04 19:38 /usr/lib/dri/radeon_dri.so

I checked and i don't have installed fglrx.
I read those 2 threads but it is not gving an answer to me really.
https://launchpad.net/ubuntu/+source/mesa/+bug/48029
https://answers.launchpad.net/ubuntu/+question/32636

Hope this helps.

Hi i fixed it finally:
I had to remove this via apt-get remove:
fglrx-amdcccle-envy fglrx-control-envy xorg-driver-fglrx-dev-envy xorg-driver-fglrx-envy

I'm on linuxmint and this is installed by default.
Works well now thanks!
07-10-2008, 07:26 PM
Melcar

Question: What exactly does the "GARTSize" option do? On both my 9800pro and 200M I need to specify a value for it, otherwise my games seg. fault or I get that "ran out of GART memory" error. What value should be the optimal to set it at? Right now I have it at 32, since setting anything higher seems to do nothing except eat up memory and leave heavy footprints on the swap file.
07-11-2008, 12:05 AM
agd5f

Quote:

Originally Posted by Melcar

Question: What exactly does the "GARTSize" option do? On both my 9800pro and 200M I need to specify a value for it, otherwise my games seg. fault or I get that "ran out of GART memory" error. What value should be the optimal to set it at? Right now I have it at 32, since setting anything higher seems to do nothing except eat up memory and leave heavy footprints on the swap file.

"GARTSize" refers to the amount of system memory in MB that the driver reserves for use by the GPU. This space is used for the ring buffer and vertex/indirect buffers and in some cases, textures. GART stands for Graphics Address Remapping Table. Disparate pages in system memory are made to look contiguous to the GPU via the remapper (either on the GPU in the case of PCI or PCIE, or on the northbridge in the case of AGP). It's sort of like an IOMMU for the GPU.

The default size is 8 MB and the max size is 32 MB.
07-11-2008, 01:40 AM
hobbes

Quote:

Originally Posted by agd5f

"GARTSize" refers to the amount of system memory in MB that the driver reserves for use by the GPU. This space is used for the ring buffer and vertex/indirect buffers and in some cases, textures. GART stands for Graphics Address Remapping Table. Disparate pages in system memory are made to look contiguous to the GPU via the remapper (either on the GPU in the case of PCI or PCIE, or on the northbridge in the case of AGP). It's sort of like an IOMMU for the GPU.

The default size is 8 MB and the max size is 32 MB.

Since you are X.org developer. What is the appropriate GARTSize to an AGP X1600pro?

Right now I'm using 256.

I based my xorg.conf on some posts here at phoronix.

http://pastebin.com/m50d0ecf0

Am I losing memory for nothing?
07-11-2008, 03:58 AM
tormod

netiquette please

Hey everybody, stop hijacking this thread! If it's not a follow-up of the original posting, please start a new thread. :mad:

And keep quoting to a minimum. The worst example is the guy quoting his own log files all over again for no purpose. :eek:

Remember that some people subscribe to a thread because they're interested in the topic, and not in all kind of other stuff. And relevant information gets lost in all the noise.

This is just common netiquette that seems to be missing on the Phoronix forum.
07-11-2008, 08:42 AM
Melcar

Quote:

Originally Posted by tormod

Hey everybody, stop hijacking this thread! If it's not a follow-up of the original posting, please start a new thread. :mad:

And keep quoting to a minimum. The worst example is the guy quoting his own log files all over again for no purpose. :eek:

Remember that some people subscribe to a thread because they're interested in the topic, and not in all kind of other stuff. And relevant information gets lost in all the noise.

This is just common netiquette that seems to be missing on the Phoronix forum.

We're still discussing the driver and it's configuration settings.

Quote:

Originally Posted by hobbes

Since you are X.org developer. What is the appropriate GARTSize to an AGP X1600pro?

Right now I'm using 256.

I based my xorg.conf on some posts here at phoronix.

http://pastebin.com/m50d0ecf0

Am I losing memory for nothing?

agd5f already said the maximum GARTSize is 32, so setting it higher will either have no effect or just eat up more memory for nothing. I tried 128 before and the only thing I noticed was increased memory usage (very noticeable when you have 512MB of RAM, and most likely even more if you have less). Most people end up thinking (erroneously) this specifies the memory for your GPU; that number is specified by another option altogether.
07-11-2008, 09:39 AM
rbmorse

Quote:

Originally Posted by tormod

Hey everybody, stop hijacking this thread! If it's not a follow-up of the original posting, please start a new thread. :mad:

And keep quoting to a minimum. The worst example is the guy quoting his own log files all over again for no purpose. :eek:

Remember that some people subscribe to a thread because they're interested in the topic, and not in all kind of other stuff. And relevant information gets lost in all the noise.

This is just common netiquette that seems to be missing on the Phoronix forum.

That's not a follow-up to the original. You should start a new thread.
07-23-2008, 09:29 PM
paul

Thanks for the packages. I tried this on a fresh install of kubuntu hardy.1. The xorg pushers script kicked out a bunch of packages, and didn't install everything from ppa. After some manual intervention, I got everything installed and now it's working. Only problem is that when I logout of kde (using kdm), it freezes and I have to power off and reboot.

I also tried kubuntu intrepid on another partition. It works with the radeon driver version there. Unfortunately, kde4 is still a bit unstable. I notice the same problem when logout (with kdm running) of freeze up. I swithed to gdm and gnome and it doesn't freeze.

Any ideas why kde doesn't like radeon of how to fix?

regards,

edit: forget this since I've now had a freeze using gnome / gdm.
07-25-2008, 09:34 AM
Akingboy

Quote:

3D not yet supported (experimental support in git)

That means most games can't be played with those drivers?

Quote:

Testing openarena:

Quote:

On my RV530 with "Very High Quality" setting I get a very nice

Oh it does work then?
I'm bit confused.

I was thinking trying these drivers but then saw that 3d not supported.
And why try these is because cs 1.6 keeps freezing on my machine and everyones machine pretty much so though maybe these could fix the problem.
Also there seems to be some textures missing in some games with the other drivers.

Can anyone answer short that can you play games with these drivers?
Games like World Of Warcraft or Warcraft 3 or steam games?

EDIT: Found this too:

Quote:

The following subsystems have not been implemented yet or show some limitations:

* 3D acceleration doesn't work together with 2D acceleration, and is only implemented on R5xx upto now. No XVideo (needs 3D engine for scaling). Still, fullscreen video is working fluently for many users.

Show 40 post(s) from this thread on one page