You are not logged in.
I have a R300, that should be ready for gallium (as I read)... now I'm cloning mesa git and I'll try to build it, then I'll let you know if it's working and how
Offline
Awesome!! I successfully compiled my first mesa!!
I compiled but not installed... however I can run Gallium temporary with LIBGL_DRIVER_PATH. My glxinfo now says
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
and glxinfo (even if it is not a real benchmark) changed from about 1200 FPS to about 1600 FPS. Now I have to test some applications like games.
Perry, the configure options I used were:
./autogen.sh \
--prefix=/usr \
--with-dri-driverdir=/usr/lib/xorg/modules/dri \
--with-dri-drivers=radeon,r300 \
--enable-glx-tls \
--with-driver=dri \
--enable-xcb \
--disable-glut \
--enable-gallium \
--enable-gallium-radeon
But I compiled only for my architecture. I took the original options from the mesa-git-gallium PKGBUILD and they were
./autogen.sh \
--prefix=/usr \
--with-dri-driverdir=/usr/lib/xorg/modules/dri \
--with-dri-drivers=swrast,nouveau,radeon,r200,r300,r600,i810,i915,i965,unichrome,mach64,mga,r128,savage,sis,tdfx \
--enable-glx-tls \
--with-driver=dri \
--enable-xcb \
--disable-glut \
--enable-gallium \
--enable-gallium-intel \
--enable-gallium-nouveau \
--enable-gallium-swrast \
--enable-gallium-radeon
Unfortunately your R700 chipset is not yet fully supported, and as you have already said I think this could be the cause of your errors. :-/
I hope this could help you...
Offline
I added a new package to the repo called mesa-full-gallium. It installs the libs in /usr/lib/xorg/modules/dri_g/.
So if you want to enable gallium for an application set the environment variable to this path.
For example:
$ LIBGL_DRIVERS_PATH=/usr/lib/xorg/modules/dri_g/ glxinfo |grep -i opengl
EE r600_texture.c/r600_translate_texformat:624 - Unable to handle texformat 108 PIPE_FORMAT_DXT5_RGBA
EE r600_texture.c/r600_translate_texformat:624 - Unable to handle texformat 14 PIPE_FORMAT_UYVY
EE r600_texture.c/r600_translate_texformat:624 - Unable to handle texformat 15 PIPE_FORMAT_YUYV
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on R700 (HD4XXX)
OpenGL version string: 2.1 Mesa 7.9-devel
OpenGL shading language version string: 1.20
OpenGL extensions:
Without the variable set:
$ glxinfo |grep -i opengl
failed to get tiling info
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: Mesa DRI R600 (RV770 9442) 20090101 TCL DRI2
OpenGL version string: 2.1 Mesa 7.9-devel
OpenGL shading language version string: 1.20
OpenGL extensions:
This is with an r700 card. I hope the errors disappears with a r300-r500 card.
I tested world of padman: it runs but it is very slow for my gpu.
Can somebody with a r300-r500 give me some feedback?
Offline
I'm sorry Perry, but I have a 32bit and you have packaged mesa-full-gallium only for 64bit, so I can't try it and give you feedback
Offline
Perry, what is /usr/lib/egl/pipe_r600.so used for? I'm using this PKGBUILD, but "pipe_r600.so" is not present after build.
# Maintainer: Sven-Hendrik Haase <sh@lutzhaase.com>
# Contributor: Antti "Tera" Oja <antti.bofh@gmail.com>
pkgname=mesa-gallium-r600-git
pkgver=20100826
pkgrel=1
pkgdesc='Gallium3D-enabled Mesa OpenGL Library from GIT repository'
url='http://www.mesa3d.org'
license=('custom')
arch=('x86_64' 'i686')
depends=('libgl' 'glproto' 'libdrm' 'dri2proto' 'libxxf86vm>=1.1.0' 'libxdamage>=1.1.2' 'expat>=2.0.1' 'libxmu>=1.0.5' 'libx11>=1.3.2' 'libxt>=1.0.7' 'libxext>=1.1.1' 'gcc-libs>=4.4.2')
makedepends=('git' 'pkgconfig')
conflicts=('mesa-full-gallium' 'mesa-git-gallium')
options=('!makeflags')
_gitroot='git://anongit.freedesktop.org/git/mesa/mesa'
_gitname='mesa'
build() {
msg 'Connecting to git.freedesktop.org GIT server....'
if [ -d ${_gitname} ] ; then
cd ${_gitname} && git pull origin
else
git clone ${_gitroot}
fi
msg 'GIT checkout done or server timeout'
msg 'Starting make...'
# Work around a problem in LDFLAGS
export LDFLAGS="${LDFLAGS//-Wl,--as-needed}"
cd ${srcdir}
# Cleanup and prepare the build dir
[ -d build ] && rm -rf build
cp -r ${_gitname} build
cd build
./autogen.sh \
--prefix=/usr \
--with-dri-driverdir=/usr/lib/xorg/modules/dri_g \
--with-dri-drivers=swrast,r600 \
--enable-glx-tls \
--with-driver=dri \
--enable-xcb \
--disable-glut \
--enable-gallium \
--enable-gallium-radeon
msg 'Starting actual compile. Go get some coffee...'
make
}
package() {
cd build
make DESTDIR=${pkgdir} install
rm -f ${pkgdir}/usr/lib/lib*
rm -rf ${pkgdir}/usr/lib/pkgconfig
rm -rf ${pkgdir}/usr/include
rm -rf ${pkgdir}/usr/share
rm -f ${pkgdir}/usr/lib/xorg/modules/drivers/radeon_drv.so
rm -f ${pkgdir}/usr/lib/egl/egl_glx.so
rm -f ${pkgdir}/usr/lib/egl/egl_dri2.so
rm -f ${pkgdir}/usr/lib/egl/st_GL.so
}
EDIT:
Maybe it's because I'm not using libgl-git, glproto-git and libdrm-git?
Last edited by kfgz (2010-08-26 14:54:47)
Offline
Well, I've tried gallium with different games; all my old games (armagetron, UrbanTerror...) which runs OpenGL 1.4 seems to run very well, even little better then before!
Instead, strange effects appear when I try new games I cannot run before, because they require OpenGL 2.1...:
- Dolphin Wii emulator seems to go, but when I run a rom only a black screen appears!
http://img835.imageshack.us/img835/7531/schermatas.png
and, more strange, glxinfo says:
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
dolphin log says instead:
27:35:012 Source/Plugins/Plugin_VideoOGL/Src/GLUtil.cpp:352 N[Video]: glX-Version 1.4
- Savage2, that with standard driver didn't start at all, with gallium appears very corrupted and veeeery slow!!:
http://img835.imageshack.us/img835/9839/schermata3.png
This are the games I know use 2.1, if someone wants to suggest me other OpenGL 2.1 games, I will do a try!
Offline
Hi BigLouis87,
OpenGl is not GLX, so it is normal that the versions differ: http://en.wikipedia.org/wiki/GLX .
Did you try my mesa-full-gallium package? I also uploaded one for i686.
Its good to hear that is faster than the classic mesa.
@kfgz: Sorry, i don't know the meaning of this lib.
But i don't think it is a good idea to use this package without the corresponding mesa-git, libgl-git, ati-dri-git.
I take a short look over this PKGBUILD: I think there is a configure option missing if you want to use it with a r600/r700 card: --enable-gallium-r600.
This is disabled by default.
Last edited by Perry3D (2010-08-27 12:11:39)
Offline
GtkLocker - I'm using testing repo too. And yours package saved my time (I've read this thread before update to Xorg 1.9). Thanks
Offline
OpenGl is not GLX, so it is normal that the versions differ: http://en.wikipedia.org/wiki/GLX .
Did you try my mesa-full-gallium package? I also uploaded one for i686.
Thanks for the explanation!!
Yes, I tried your package and I also renamed dri_g into dri so gallium starts with the system, without any problem.
Perhaps I have understood why Dolphin doesn't run... this is an answer of a Dolphin developer:
«I'm not sure if the open source drivers are really good enough to run Dolphin meanwhile..
Do they expose NPOT texture functionality for r300-r500? If not, that's most likely the culprit here... (on the other hand, I don't know if the blob would expose the extension.. Then again, I don't know if Dolphin would be able to run with the blob on r300-r500 either...)»
If you look at http://www.x.org/wiki/RadeonFeature it says: "Hardware doesn't support ARB NPOT textures fully." for R300/R500... doh!
This could be the reason of the Savage2 failure too... :-/
Do you think this could be fixed in the future?
Offline
Perry3D/gtklocker, could you please rebuild the lib32 packages from the x86_64 repo taking the new multilib repo into account? At least lib32-mesa-full needs lib32-gcc, which should now be provided by the new gcc-multilib (right? ). Maybe it's just renaming the dependencies.
Or maybe explain how to build it? I don't have a clue how to make lib32 packages (I do have a 32 bit chroot ready, for some other stuff).
Thanks!
Offline
Sources can be found here -> http://gitorious.org/radeon/radeon/trees/master
Offline
Sources can be found here -> http://gitorious.org/radeon/radeon/trees/master
Thank you!
Offline
$ LIBGL_DRIVERS_PATH=/usr/lib/xorg/modules/dri_g/ glxinfo |grep -i opengl
EE r600_texture.c/r600_translate_texformat:624 - Unable to handle texformat 108 PIPE_FORMAT_DXT5_RGBA
EE r600_texture.c/r600_translate_texformat:624 - Unable to handle texformat 14 PIPE_FORMAT_UYVY
EE r600_texture.c/r600_translate_texformat:624 - Unable to handle texformat 15 PIPE_FORMAT_YUYV
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on R600 (HD2XXX,HD3XXX)
OpenGL version string: 2.1 Mesa 7.9-devel
OpenGL shading language version string: 1.20
OpenGL extensions:
Offline
Uhm, the first post says I can use the sysfs interface ( /sys/class/drm/card0/device/power_profile ) but I don't have a power profile entry in there. I'm using the stock 2.6.34 kernel (.35 has wireless problems for me) and the radeon driver from [extra]. I also have kms enabled and added radeon.dynpm=1 to my kernel line. Any ideas?
Last edited by dcc24 (2010-08-28 20:49:19)
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
Uhm, the first post says I can use the sysfs interface ( /sys/class/drm/card0/device/power_profile ) but I don't have a power profile entry in there. I'm using the stock 2.6.34 kernel (.35 has wireless problems for me) and the radeon driver from [extra]. I also have kms enabled and added radeon.dynpm=1 to my kernel line. Any ideas?
Wasn't power_profile introduced in 2.6.35?
Offline
Uhm, the first post says I can use the sysfs interface ( /sys/class/drm/card0/device/power_profile ) but I don't have a power profile entry in there. I'm using the stock 2.6.34 kernel (.35 has wireless problems for me) and the radeon driver from [extra]. I also have kms enabled and added radeon.dynpm=1 to my kernel line. Any ideas?
you have to use kernel26-drm-radeon-testing. Try to resolve wireless problems... wireless could be a temporary bug, but you cannot use power profiles with stock kernel...
Use also the radeon driver from radeon repo.
Last edited by BigLouis87 (2010-08-28 22:44:30)
Offline
you have to use kernel26-drm-radeon-testing. Try to resolve wireless problems... wireless could be a temporary bug, but you cannot use power profiles with stock kernel...
Use also the radeon driver from radeon repo.
The wireless issue is an upstream regression (confirmed by Intel) and it breaks wireless connection completely. If Vi0L0 is right, meaning 2.6.35 is the first kernel with power_profile, does the stock 2.6.35 kernel work? Do I have to use kernel26-drm-testing? Do I have to use the driver from the radeon repo?
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
The power profile should work with the 2.6.35 stock kernel. And no, power management is completely done in the kernel, so you don't need to upgrade the userspace - driver (libdrm, mesa, xf86-video-ati).
Offline
Thanks. So the only way for me is embedding the iwlagn driver used in 2.6.34 into a 2.6.35 kernel, then using power_profile. Should be fun
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
Perry3D/gtklocker, could you please rebuild the lib32 packages from the x86_64 repo taking the new multilib repo into account? At least lib32-mesa-full needs lib32-gcc, which should now be provided by the new gcc-multilib (right? ). Maybe it's just renaming the dependencies.
Or maybe explain how to build it? I don't have a clue how to make lib32 packages (I do have a 32 bit chroot ready, for some other stuff).
Thanks!
Done.
Offline
Hi their !
I'm just back under arch (ho man bye bye ubuntu) since AMD has made a huge code drop for evergreen. Consequently I'm running some test but it appear that it need some work before beeing completly usable (actually this isn't a worse as on the screenshot : my background is correctly displayed and generally speacking applications' window are correctly displayed. I have some cursor corruption though.).
At first I have installed all the package from the first page (thank Perry by the way for gathering those informations) but it kept me falling back on software rasterizer so I installed xf86-video-evergreen-git from AUR. And then :
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: Mesa DRI R600 (JUNIPER 68B8) 20090101 TCL DRI2
OpenGL version string: 2.1 Mesa 7.9-devel
OpenGL shading language version string: 1.20
I'm gonna try the same but with the standard package, but I'm very satisfied by the power management. The doesn't turn as low as with catalyst but my hears have stopped bleeding
edit: no situation difference between stable and git packages
Last edited by xheyther (2010-08-29 17:30:04)
Offline
There are some new commits to kernel26-drm-radeon-testing. For example write back is implemented. I compiled it a few minutes ago, but everything gets very slow.
If somebody experience the same problem append
radeon.no_wb=1
to your kernel parameters.
Uploading now ...
Offline
There are some new commits to kernel26-drm-radeon-testing. For example write back is implemented. I compiled it a few minutes ago, but everything gets very slow.
If somebody experience the same problem appendradeon.no_wb=1
to your kernel parameters.
Uploading now ...
I tried it, and did experience the slowdown (everything becomes "laggy"). Fixed it by disabling writeback like you suggested, now everything is back to normal.
I looked at the newest commit for writeback, and according to the changelog there shouldn't have been any major changes besides the merging of patches for older and newer cards, so I don't understand why it slows down like that.
Anyway, thanks!
BTW, does suspend work for you guys?
Last edited by txus (2010-09-03 14:39:09)
Offline
This writeback is laggy for me too. I think that something is broken with this patch.
Offline
same problem for me (rv620)
Offline