You are not logged in.
I have Radeon 9000 and work good (for me:) ):
glxgears:
Mesa: CPU vendor: GenuineIntel
Mesa: CPU name: Intel(R) Pentium(R) 4 CPU 2.60GHz
Mesa: MMX cpu detected.
Mesa: SSE cpu detected.
Mesa: Not testing OS support for SSE, leaving enabled.
14297 frames in 5.0 seconds = 2859.386 FPS
14375 frames in 5.0 seconds = 2874.920 FPS
14394 frames in 5.0 seconds = 2878.748 FPS
14352 frames in 5.0 seconds = 2870.363 FPS
14386 frames in 5.0 seconds = 2877.060 FPS
My xorg.conf looks like:
Section "Module"
Load "ddc"
Load "freetype"
Load "type1"
Load "bitmap"
Load "dbe"
Load "extmod"
Load "record"
Load "glx"
Load "dri"
EndSectionSection "Device"
BoardName "RV250 If"
BusID "1:0:0"
Driver "radeon"
Identifier "Device[0]"
Option "AccelMethod" "XAA"
Option "AGPMode" "1"
Option "AGPFastWrite" "1"
Option "EnablePageFlip" "1"
Option "ColorTiling" "1"
Screen 0
VendorName "ATI"
EndSectionSection "DRI"
Group "video"
Mode 0666
EndSection
Maybe will help to you.
Offline
Ok, I just managed to get it working on a radeon 9600 pro, dri enabled, good speed in glxgears (I even almost got aiglx + compiz running)
BUT:
-) the memory usage of Xorg seems to be a lot higher as with the fglrx driver
-) the quality of video in xine (using xv) is really bad compared to fglrx
so I'm using fglrx now again, but it's good to see there's progress...
Offline
Hey spack great how-to.
Could you please add this to your post, it will save people a lot of grief. sven mentioned this, I just want to crystalize it:
Install Mesa DRI OpenGL library and drivers:
pacman -S libgl-dri
If you get a conflict with ati-fglrx-utils:
pacman -Rd ati-fglrx-utils
Then install libgl-dri.
Attention, anyone who was previously using the fglrx drivers:
Both the ati-fglrx-utils package and the libgl-dri package provide a version of the openGL shared library /usr/lib/libGL.so.1 (your version may be different).
However the one supplied by the Mesa package implements things not implemented by the one in ATI's package. That's why it can
be exceedingly confusing trying to figure out why things aren't working even though you apparently have the necessary libraries.
The solution is to install libgl-dri and everything shoud work as outlined in spack's guide.
This is my understanding of the issue, just wanted to clarify for anyone else that was confused.
BTW, I've got this working using a Radeon 9800 Pro which is an R350 chip.
$ glxinfo | grep -C3 direct
libGL warning: 3D driver claims to not support visual 0x4b
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
[moveek@atomicbulldog ~]$ glxgears
libGL warning: 3D driver claims to not support visual 0x4b
18284 frames in 5.0 seconds = 3656.774 FPS
18454 frames in 5.0 seconds = 3690.717 FPS
18449 frames in 5.0 seconds = 3689.732 FPS
18453 frames in 5.0 seconds = 3690.435 FPS
I noticed someone with a 9700 getting higher frame rates...not sure why.
But the frame rates from the radeon drivers beat the pants off the frame
rates I got from the fglrx drivers. fglrx gave me around 900 FPS.
So I finally have 3D acceleration and composite support, sweet!
Offline
$ glxinfo | grep -C3 direct libGL warning: 3D driver claims to not support visual 0x4b
[moveek@atomicbulldog ~]$ glxgears libGL warning: 3D driver claims to not support visual 0x4b
how to set up the proble related to this warning message?
Offline
Veek: Do you notice a drop in video quality for xvid movies when using xv?
in videos surfaces that almost had the same color were really bad, it was like a gif image when using too few colors.
Offline
furester,
I noticed that warning and found an explanation on the dri-devel mailing list:
http://www.mail-archive.com/dri-devel@l … 28133.html
Seems it is nothing to worry about, here's the important bit from the link:
It's caused by the visual being marked
non-conformant by AIGLX. A solution is being discussed on the mesa3d-dev mailing
list.Note that this is completely cosmetic and has no functional impact.
(I italicized that last bit)
mouse256,
I checked out a couple videos using xv in mplayer, and I'm not seeing
a difference.
I think for the xv extension to work properly, the TexturedVideo option needs to be on, or maybe the VideoOverlay option:
Section "Device"
Identifier "ATI Radeon 9800 Pro"
Driver "radeon"
#BusID "PCI:1:0:0"
Option "TexturedVideo" "on"
Option "VideoOverlay" "on"
....
EndSection
Not sure though. At any rate video quality seems identical to me.
Plus I can actually use gl and gl2 OpenGL drivers in mplayer,
but I didn't notice any quality difference between any of the drivers
I've used so far, including when I was using fglrx.
Offline
One more thing.
I tried out the options mentioned by NecroRomancist.
Adding
Option "EnablePageFlip" "true"
to the device section boosted my frame rate by about 1700FPS!
My current results from glxgears on a Radeon 9800 Pro:
$ glxgears
libGL warning: 3D driver claims to not support visual 0x4b
26882 frames in 5.0 seconds = 5376.247 FPS
26912 frames in 5.0 seconds = 5382.311 FPS
26832 frames in 5.0 seconds = 5366.331 FPS
26957 frames in 5.0 seconds = 5391.254 FPS
Offline
When I switched to "radeon" driver from "fglrx", my fps increased (Radeon 9000) by 300. But when I played ppracer, there were artefacts with colors. Speed was the same as with "fglrx". When I started Heroes V with wine, colors were really bad. What can I do with it?
P. S. I used config from lumiwa as my card is Radeon 9000.
Offline
YEAY Thanks for this tutorial it works great once you figure out the correct modules for your own PC.
Offline
GroXx -- the same problem
XFCE4 under Arch on Honor MagicBook
Offline
Same as GroXx : ATI Radeon 9600 and black screen after installing open source drivers.
This is fixed when I add
BusID "PCI:1:0:0"
on the device section of my rc.conf.
man xorg.conf says that :
BusID "bus-id"
This specifies the bus location of the graphics card. For PCI/AGP cards, the bus-id string has the form PCI:bus:device:function (e.g., "PCI:1:0:0" might be appropriate for an AGP card). This field is usually optional in single-head configurations when using the primary graphics card. In multi-head configurations, or when using a secondary graphics card in a single-head configuration, this entry is mandatory. Its main purpose is to make an unambiguous connection between the device section and the hardware it is representing. This information can usually be found by running the Xorg server with the -scanpci command line option.
Don't know if it helps...
Offline
When i see if i have direct rendering i get
[root@arch log]# glxinfo | grep 'direct rendering'
direct rendering: No
[root@arch log]#
I then looked at the log and found this
(WW) RADEON(0): [agp] AGP not available
(EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI.
(II) RADEON(0): [agp] You may want to make sure the agpgart kernel module
is loaded before the radeon kernel module.
Heres my rc.conf
MODULES=(via-velocity agpgart radeon drm)
I'm a noob with ati cards, so i'm pretty lost here
Offline