Discussion: the ati/radeon open source drivers & radeon repository

Viper_Scull · 2011-07-07 00:45:46

We have MLAA on github. Testing phase.
http://www.phoronix.com/scan.php?page=n … &px=OTY0MA

Lone_Wolf are you going to include it to the R600g PKGBUILD?

Last edited by Viper_Scull (2011-07-07 11:34:39)

hoschi · 2011-07-07 07:24:35

Viper_Scull wrote:

We have MLAA on github. Testing phase.
http://www.phoronix.com/scan.php?page=n … &px=OTY0MA
Lone_Wolf are you going to include to the R600g PKGBUILD?

So much...WIN! Thats great!

Does anyone know why xf86-video-ati-6.14.2-1 doesn't move to stable? I don't negative bug reports.

Last edited by hoschi (2011-07-07 07:29:02)

Lone_Wolf · 2011-07-07 10:33:32

Phoronix wrote:

The MLAA code hasnt been merged to master for now, but is currently living on GitHub.

The packages mentioned in this thread (incuding mine) all use mesa git master branch , not out-of-tree code.

Apart from that, the code on github is for a testprogram of MLAA functionality, that doesn't depend on a specific viceocard driver.
I feel it should get it's own package.

Cdh · 2011-07-08 20:12:28

Perry3D wrote:

I tried to compile the radeon-testing branch a few days ago. But i got a compile error.

Any updates? The kernel is more than a month old now which kind of defeats the purpose of running a cutting edge kernel...

Perry3D wrote:

/edit: @splashy: Mesa is using gallium by default. So mesa-full-gallium is obsolete. You can remove mesa-full-gallium.

As well as lib32-mesa-full-gallium I would think. Would be good if you remove it from the repository too because I like to do

pacman -S $(pacman -Sql radeon)

Perry3D · 2011-07-09 08:19:54

I don't really think it is worth to compile a new version. The last commits are also over a month old: http://git.kernel.org/?p=linux/kernel/g … on-testing

And at the moment i use the catalyst driver cause of the bug i mentioned a few posts ago. So now i'm not able to compile new mesa updates (at least for x86_64) without switching the driver .

lordheavy · 2011-07-11 07:25:16

Perry3D wrote:

I don't really think it is worth to compile a new version. The last commits are also over a month old: http://git.kernel.org/?p=linux/kernel/g … on-testing
And at the moment i use the catalyst driver cause of the bug i mentioned a few posts ago. So now i'm not able to compile new mesa updates (at least for x86_64) without switching the driver .

You don't build them inside a chroot ?

Perry3D · 2011-07-11 14:59:43

lordheavy wrote:

Perry3D wrote:
I don't really think it is worth to compile a new version. The last commits are also over a month old: http://git.kernel.org/?p=linux/kernel/g … on-testing
And at the moment i use the catalyst driver cause of the bug i mentioned a few posts ago. So now i'm not able to compile new mesa updates (at least for x86_64) without switching the driver .
You don't build them inside a chroot ?

Only the i686 packages. But you are right, i will arrange one for x86_64 too. Anyway, it is cleaner way!

Viper_Scull · 2011-07-11 21:34:13

Nice news:
http://www.phoronix.com/scan.php?page=n … &px=OTY1OQ

Hope to see it soon in master branch and try it out.

handy · 2011-07-12 06:52:53

Too right! It looks like the next 12 months are really going to start delivering some dramatic improvements for us.

Of course, time will tell...

volalto · 2011-07-13 09:11:05

Hello everybody,

I recently purchased a laptop with Intel integrated card and ATI Radeon HD5470. I would like to test git packages in Perry's repo, to take advantage of the latest driver developments.

I followed the instructions contained in the first post, but I get this:

$ pacman -S dri2proto-git glproto-git libdrm-git mesa-full mesa-demos-git xf86-video-ati-git
resolving dependencies...
looking for inter-conflicts...
...
error: failed to prepare transaction (could not satisfy dependencies)
:: intel-dri: requires libgl=7.10.3

Does anybody know if (and how) it's possible to install ati development packages alongside with intel ones (from "normal" repo)?
Thanks...

Viper_Scull · 2011-07-13 09:59:05

You are tring to install with pacman AUR packages...

Mesa-full is out of date. You have mesa-full-i915g for intel with gallium 3d.

Last edited by Viper_Scull (2011-07-13 10:01:17)

handy · 2011-07-13 12:45:11

@volalto: Have a look here, it should help you with your installation as it seems that you aren't familiar with the differences between the supported Arch repos & the AUR (Arch User Repository):

https://wiki.archlinux.org/index.php/Be … _Guide#AUR

Last edited by handy (2011-07-13 12:46:34)

volalto · 2011-07-13 15:17:37

I did not use AUR, but the [radeon] repo suggested in the first post (radeon/mesa-full 20110702-1 package). As I told you I tried to stick to the instructions contained in the first post.

The only package named mesa-full-i915 is in fact an AUR package! So are you telling me I should not use the [radeon] repo and stick to AUR packages?!

Perry3D · 2011-07-13 17:41:37

Hello volalto,

the problem is that mesa-full from my repo doesn't include the intel-dri files, only the files for ati-dri (cause it is a radeon repo). I didn't thought about the situation that somebody is using an ati and an intel card.
A solution would be to reconfigure the mesa-full package from my repo. So it would include the other dri-packages (intel-dri, nouveau-dri...). The negative effect would be a longer compile time and an increased package size. Also i would have to provide the xf86-video-... driver for the other vendors.
Then i could rename the repo to mesa

Cdh · 2011-07-13 19:55:36

volalto wrote:

Does anybody know if (and how) it's possible to install ati development packages alongside with intel ones (from "normal" repo)?

That's actually something I have to think about too... I have created the mesa-full-i915, mesa-full-i915g and mesa-full-i965 AUR packages just for fun and I am not comfortable with having so many specialized packages.

A problem is that intel doesn't yet believe in gallium3d, yet most development in the radeon driver happens in gallium3d. I don't actually know whether the mesa buildsystem supports building the intel mesa classic driver and the gallium radeon driver in one go.

But compiling mesa itself is usually very painless and on a fast cpu it's a matter of only a few minutes.

If your intel chip works via the i915 driver using the intel gallium driver should be good, because google worked much on it lately.
i965 gallium should work too but it's not very popular and not many people are working on it.

So if your chip works with i915 as a start you could use my mesa-full-i915g PKGBUILD and simply add r600 to the appropriate places such that it looks like

pkgname=mesa-full-i915g-r600g
pkgver=20110706
_realver=7.12
pkgrel=1
pkgdesc="Full Mesa 3D graphics library with all its components, built from the git master branch (mesa 7.11). Compiles mesa for i915g and r600g (gallium)."
arch=(i686 x86_64)
url="http://mesa3d.org/"
license=('LGPL')
depends=('libdrm-git' 'dri2proto>=2.1' 'glproto>=1.4.10' 'libxxf86vm' 'libxdamage' 'expat>=2.0.1' 'libxmu' 'talloc' 'llvm')
makedepends=('pkgconfig' 'imake' 'xorg-server-devel')
optdepends=('llvm: "configure" tests for its presence and compiles with some additional "-D" macros if found')
provides=("libgl=${_realver}" "mesa=${_realver}" "freeglut=${_realver}" "glut=${_realver}" "intel-dri=${_realver}" "ati-dri=${_realver}")
replaces=('libgl' 'mesa' 'freeglut' 'glut' 'intel-dri' 'ati-dri')
conflicts=('libgl' 'mesa' 'freeglut' 'glut' 'intel-dri' 'mesa-full-i915' 'ati-dri')

_gitroot="git://anongit.freedesktop.org/git/mesa/mesa"
_gitname="mesa"

build() {
   msg "Connecting to git.freedesktop.org GIT server...."

   if [ -d $startdir/src/$_gitname ] ; then
      cd $_gitname && git pull origin
      msg "The local files are updated."
   else
      git clone $_gitroot
   fi

   msg "GIT checkout done or server timeout"
   msg "Starting make..."

   rm -rf $startdir/src/$_gitname-build
   cp -rH $startdir/src/$_gitname $startdir/src/$_gitname-build
   cd ${srcdir}/${_gitname}-build

   cd "${startdir}/src/mesa-build"
   ./autogen.sh --prefix=/usr \
   --with-dri-drivers=i915,r600 \
   --with-gallium-drivers=i915,r600 \
   --with-dri-driverdir=/usr/lib/xorg/modules/dri \
   --enable-glx-tls \
   --enable-xcb \
   --enable-egl \
   --enable-gallium-egl \
   --enable-gallium-llvm \
   --enable-glu \
   --enable-gles1 \
   --enable-gles2 \
   --enable-glut \
   --enable-glw \
   --enable-openvg \
   --enable-xa \
   --enable-xorg \
   --enable-osmesa \
   --enable-texture-float || return 1

# not really sure if I should enable that... shared-glapi is called experimental in the configure help
#   --enable-shared-glapi \
#   --enable-gbm \
#   --enable-gallium-gbm \

   make || return 1
   make DESTDIR="${pkgdir}" install || return 1

   install -m755 -d "${pkgdir}/usr/lib/xorg/modules/extensions"
   ln -sf libglx.xorg ${pkgdir}/usr/lib/xorg/modules/extensions/libglx.so || return 1
}

Or something like that.

edit: By the way, pipe video with vdpau got merged. I tried to compile it with this pkgbuild:

pkgname=mesa-full-r600g
pkgver=20110714
_realver=7.12
pkgrel=1
pkgdesc="Full Mesa 3D graphics library with all its components, built from the git master branch (mesa 7.12). Compiles mesa for r600g (gallium)."
arch=(i686 x86_64)
url="http://mesa3d.org/"
license=('LGPL')
depends=('libdrm-git' 'dri2proto>=2.1' 'glproto>=1.4.10' 'libxxf86vm' 'libxdamage' 'expat>=2.0.1' 'libxmu' 'talloc' 'llvm')
makedepends=('pkgconfig' 'imake' 'xorg-server-devel')
optdepends=('llvm: "configure" tests for its presence and compiles with some additional "-D" macros if found')
provides=("libgl=${_realver}" "mesa=${_realver}" "freeglut=${_realver}" "glut=${_realver}" "ati-dri=${_realver}")
replaces=('libgl' 'mesa' 'freeglut' 'glut' 'ati-dri')
conflicts=('libgl' 'mesa' 'freeglut' 'glut' 'ati-dri' 'mesa-full')

_gitroot="git://anongit.freedesktop.org/git/mesa/mesa"
_gitname="mesa"

build() {
   msg "Connecting to git.freedesktop.org GIT server...."

   if [ -d $startdir/src/$_gitname ] ; then
      cd $_gitname && git pull origin
      msg "The local files are updated."
   else
      git clone $_gitroot
   fi

   msg "GIT checkout done or server timeout"
   msg "Starting make..."

   rm -rf $startdir/src/$_gitname-build
   cp -rH $startdir/src/$_gitname $startdir/src/$_gitname-build
   cd ${srcdir}/${_gitname}-build

   cd "${startdir}/src/mesa-build"
   ./autogen.sh --prefix=/usr \
   --with-dri-drivers=r600 \
   --with-gallium-drivers=r600 \
   --with-dri-driverdir=/usr/lib/xorg/modules/dri \
   --enable-glx-tls \
   --enable-xcb \
   --enable-egl \
   --enable-gallium-egl \
   --enable-gallium-llvm \
   --enable-glu \
   --enable-gles1 \
   --enable-gles2 \
   --enable-glut \
   --enable-glw \
   --enable-openvg \
   --enable-xa \
   --enable-xorg \
   --enable-osmesa \
   --enable-texture-float \
   --enable-shared-glapi \
   --enable-shared-dricore \
   --enable-gbm \
   --enable-gallium-gbm \
   --enable-xvmc \
   --enable-vdpau \
   --enable-gallium-g3dvl || return 1

   make || return 1
   make DESTDIR="${pkgdir}" install || return 1

   install -m755 -d "${pkgdir}/usr/lib/xorg/modules/extensions"
   ln -sf libglx.xorg ${pkgdir}/usr/lib/xorg/modules/extensions/libglx.so || return 1
}

But it fails with

make[3]: *** No rule to make target `../../../../src/gallium/drivers/softpipe/libsoftpipe.a', needed by `../../../../lib/egl/egl_gallium.so'.  Stop.

But in the phoronix forum there are people speaking about using it so how did they build it when the makefile is broken? How is this possible? Does anybody know what's wrong?

Last edited by Cdh (2011-07-14 11:42:08)

volalto · 2011-07-14 13:06:19

@Perry

I understand your point! :-)

Ati + Intel is a quite common setup, though. As you probably know most recent laptops are equipped with switchable graphics: an integrated Intel HD card for power-saving and a discrete ATI (or Nvidia) chip for performance.

@Cdn

Thanks for your suggestions and help! My Intel GPU is an integrated Core i5 HD chip (Arrendale) and it uses i915 as far as I can see, so I'll give your PKGBUILD a try!

Viper_Scull · 2011-07-14 13:27:07

Cdh wrote:

But in the phoronix forum there are people speaking about using it so how did they build it when the makefile is broken? How is this possible? Does anybody know what's wrong?

Remove
--enable-egl \
--enable-gallium-egl \

There is a problem building libsoftpipe.a right now due to the latest changes, so you cant build egl_gallium.so. It has to be fixed in master soon.
You don't need it to try vpdau with r600g.

You have to declare an environment variable so VPDAU use R600g though. VDPAU_DRIVER=r600

I'm waiting for Love_wolf to try a fix i've posted in the aur package for mesa-r600g-git to try it out, cause it wont install right now.

Last edited by Viper_Scull (2011-07-14 13:36:08)

Cdh · 2011-07-14 15:22:14

volalto wrote:

@Cdn
Thanks for your suggestions and help! My Intel GPU is an integrated Core i5 HD chip (Arrendale) and it uses i915 as far as I can see, so I'll give your PKGBUILD a try!

You have to be a bit careful. There is the kernel module called i915 and this kernel module is used by chips that both are using the i965 and the i915 drivers and even some chips using the i915 kernel module and the mesa i965 driver don't run with the mesa i915 driver. At least I think so.

@Viper_Scull
Thanks for the information.

What do you mean I don't need to try?

By the way: enabling

--enable-gbm
--enable-gallium-gbm

needs

--enable-shared-glapi

At least that's what configure tells me. But as far as I see it is working quite well, but it is called EXPERIMENTAL by the configure script.

Viper_Scull · 2011-07-14 15:27:13

I said that you dont need to enable egl and gallium-egl to try vpdau with R600g.

Remove the options --enable-egl, --enable-gallium-egl and --enable-openvg from the PKGBUILD so it can compile.

I installed succesfully (without egl, gallium-egl, openvg and glut support), but (always a but):

LD_LIBRARY_PATH=/usr/lib/vdpau VDPAU_DRIVER=r600 vdpauinfo
display: :0.0   screen: 0
Failed to open VDPAU backend /usr/lib/vdpau/libvdpau_r600.so: undefined symbol: drmIoctl
Error creating VDPAU device: 1

Last edited by Viper_Scull (2011-07-14 16:28:00)

Cdh · 2011-07-14 16:55:30

Oh ok. Then I'll wait until both problems are fixed.

h2 · 2011-07-16 18:29:21

Hi everyone,

I haven't used Arch in a while, since my mainboard broke. Now I have a new one, with a HD4290 onboard. First off, the xserver doesn't start at all. It says there are no devices.

I upgraded to recent Arch which resulted in mesa-full-gallium being lost, apperently its outdated. Reading through though last pages of this thread, it seems mesa-r600g-git is the way to go now. Is that correct?

Why does this package depend on dri2proto2.6 (and not take dri2proto-git), which conflicts with lib32-mesa-full (and thereby wine)?

I removed lib32-mesa-full and wine and upgraded dri2proto to 2.6 and tried to build mesa-r600g-git, but it seems many of its dependencies are not tracked (e.g. flex and bison). It is now building, but I am unsure if this is really the proper way of doing it.

Is this the only way for gallium right now? How do I get lib32 and wine support back?

Thanks for your help!

edit: Great, now it wants to remove mesa-full, which is required by nearly everything else... is there no clean upgrade / conversion path?

Last edited by h2 (2011-07-16 18:35:17)

Lone_Wolf · 2011-07-16 19:23:18

H2 :

All aur packages assume users have base-devel group, flex and bison are in that group.

pacman -Syu base-devel

Mesa-r600g-git provides mesa, libgl and ati-dri so it has everything you need.
(since i only include drivers for R600 and software rendering, i could not call my package mesa-full something.)

I prefer to have as little dependencies form aur as possible, and mesa git works fine with the dri2proto 6 , now in testing.

For wine use my lib32-mesa-r600g-git package ( wait a few hours, i need to update it).

The official mesa / libgl / at-dri packages use gallium for R600 since 7.10.1 , so you can also use those if you prefer.
Mesa switch to a 6 month release schedule, and the git master versions just have many improvements.

Added :
lib32-mesa-r600g-git updated, http://aur.archlinux.org/packages.php?ID=50696

Both my packages now use same compile options.

Last edited by Lone_Wolf (2011-07-16 21:23:56)

bog · 2011-07-17 06:29:07

I have an X1400 and I'm using the ati radeon open source driver. Watching full screen YouTube videos result in either a system crash or terrible flickering in kde4 with/without compositing. I was wondering if you people experienced the same, and whether it's worth submitting a bug report, and if the answer is yes, where I should submit it.
Thanks!

handy · 2011-07-17 09:46:31

bog wrote:

I have an X1400 and I'm using the ati radeon open source driver. Watching full screen YouTube videos result in either a system crash or terrible flickering in kde4 with/without compositing. I was wondering if you people experienced the same, and whether it's worth submitting a bug report, and if the answer is yes, where I should submit it.
Thanks!

If you are using Firefox, & the videos are Flash, you could try this Firefox add-on, it certainly improved my online Flash experience:

https://addons.mozilla.org/en-US/firefo … stall-beta

bog · 2011-07-17 21:10:13

Thanks for your suggestion, handy! Yeah, this addon is really good.

Arch Linux

#2101 2011-07-07 00:45:46

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2102 2011-07-07 07:24:35

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2103 2011-07-07 10:33:32

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2104 2011-07-08 20:12:28

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2105 2011-07-09 08:19:54

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2106 2011-07-11 07:25:16

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2107 2011-07-11 14:59:43

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2108 2011-07-11 21:34:13

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2109 2011-07-12 06:52:53

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2110 2011-07-13 09:11:05

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2111 2011-07-13 09:59:05

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2112 2011-07-13 12:45:11

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2113 2011-07-13 15:17:37

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2114 2011-07-13 17:41:37

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2115 2011-07-13 19:55:36

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2116 2011-07-14 13:06:19

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2117 2011-07-14 13:27:07

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2118 2011-07-14 15:22:14

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2119 2011-07-14 15:27:13

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2120 2011-07-14 16:55:30

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2121 2011-07-16 18:29:21

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2122 2011-07-16 19:23:18

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2123 2011-07-17 06:29:07

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2124 2011-07-17 09:46:31

Re: Discussion: the ati/radeon open source drivers & radeon repository

#2125 2011-07-17 21:10:13

Re: Discussion: the ati/radeon open source drivers & radeon repository

Board footer