LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Latest Mesa and open source Ati driver (http://www.linuxquestions.org/questions/slackware-14/latest-mesa-and-open-source-ati-driver-4175482902/)

mlpa 10-31-2013 06:49 AM

Latest Mesa and open source Ati driver
 
Hello everyone.
I want to try the latest mesa and open source Ati driver. Apparently they provide VDPAU acceleration, dynamic power management and for older hardware a good performance.

One of the requirements is linux kernel 3.11, that is not a problem since I compiled the kernel a couple of times.
My questions is, apart from mesa and ati driver what else is necessary?
Probably libdrm is also necessary?
Is there a specific order to compile and install the packages?

Keith Hedger 10-31-2013 07:51 AM

See This:
http://www.linuxfromscratch.org/blfs...nstalling.html
And specifically this:
http://www.linuxfromscratch.org/blfs...org-ati-driver

I have just built these and they seem to be working OK.

andrewthomas 10-31-2013 08:02 AM

Quote:

Originally Posted by Keith Hedger (Post 5055849)
See This:
http://www.linuxfromscratch.org/blfs...nstalling.html
And specifically this:
http://www.linuxfromscratch.org/blfs...org-ati-driver

I have just built these and they seem to be working OK.

The problem is not building the latest mesa, but building the latest mesa from a SLACKBUILD on -current.

mlpa 10-31-2013 08:48 AM

Quote:

Originally Posted by andrewthomas (Post 5055856)
The problem is not building the latest mesa, but building the latest mesa from a SLACKBUILD on -current.

Actually in Slackware61 14 :-)

BrZ 10-31-2013 10:10 AM

2 Attachment(s)
You can try this sequence:
Quote:

- macros
- protos
- libvdpau (need dri2proto)
- libdrm (*before* ddx and mesa)
- ddx (xf86-video-ati)
- mesa
- glu
- glew
- freeglut
- xserver
Curiously, I messed with mesa and xorg a couple of days ago to try VDPAU:
Quote:

X.Org X Server 1.14.3
Release Date: 2013-09-12
[ 197.478] Build Date: 19 October 2013 01:06:08AM
...
[ 198.134] (II) RADEON(0): [DRI2] Setup complete
[ 198.134] (II) RADEON(0): [DRI2] DRI driver: r600
[ 198.134] (II) RADEON(0): [DRI2] VDPAU driver: r600
Be prepared to rebuild some other packages, most of them media related like ffmpeg, mplayer, vlc... If everything goes OK, you'll have hardware accelerated flash and video content. MPlayer seems happy:
Quote:

Iníciando reprodução...
[VD_FFMPEG] Trying pixfmt=0.
[VD_FFMPEG] XVMC-accelerated MPEG-2.
Aspecto do filme é 2.39:1 - pré-redimensionando para corrigir o aspecto do filme.
VO: [vdpau] 1280x536 => 1280x536 H.264 VDPAU acceleration
[VD_FFMPEG] XVMC-accelerated MPEG-2.
[VD_FFMPEG] Trying pixfmt=0.
[VD_FFMPEG] XVMC-accelerated MPEG-2.
[VD_FFMPEG] XVMC-accelerated MPEG-2.
Aspecto do filme é 2.39:1 - pré-redimensionando para corrigir o aspecto do filme.
VO: [vdpau] 1280x536 => 1280x536 H.264 VDPAU acceleration
You'll need the firmware for your card (microcode or radeon-ucode) under "/lib/firmware/radeon". Download from here or here. And the kernel need support for userspace firmware loading.

Research a bit first and keep a copy of Slack around as this experiment can nuke your xorg and render your system running on command line only.

I had a lot of fun :D

TobiSGD 10-31-2013 10:24 AM

Thanks, I will give that a try also. You don't need to download the firmware, by the way, -current got it already with the latest kernel-firmware update.

mlpa 10-31-2013 12:38 PM

Quote:

Originally Posted by BrZ (Post 5055918)
You can try this sequence:


Curiously, I messed with mesa and xorg a couple of days ago to try VDPAU:


Be prepared to rebuild some other packages, most of them media related like ffmpeg, mplayer, vlc... If everything goes OK, you'll have hardware accelerated flash and video content. MPlayer seems happy:


You'll need the firmware for your card (microcode or radeon-ucode) under "/lib/firmware/radeon". Download from here or here. And the kernel need support for userspace firmware loading.

Research a bit first and keep a copy of Slack around as this experiment can nuke your xorg and render your system running on command line only.

I had a lot of fun :D

I will try.
Some more questions what is macros and protos?
Do you have any idea about I need to rebuild after?

andrewthomas 10-31-2013 01:13 PM

As to the order: I would think that this should do.

Code:

dri2proto
glproto
libdrm
pixman
libvdpau
mesa
xorg-server
cairo
freeglut
glew
xf86-video-ati


BrZ 10-31-2013 01:30 PM

m4 macros and protocols headers. You don't need to rebuild these. Get the easy route and start with libvdpau. Keep the same packages of 14.1, except mesa. Try (re)building just libvdpau -> libdrm -> xf86-video-ati -> mesa -> glu -> glew -> freeglut and -> xserver. Look the source tree and build scripts from Slackware inside 'Slackware/slackware64-current/source/{x,x11}'.

To build xorg-server: "./x11.SlackBuild xserver xorg-server". To build ddx: "./x11.SlackBuild driver xf86-video-ati". And so on...

You can get the script to libvdpau at SlackBuilds. From memory, I remember rebuilding ffmpeg, mplayer, vlc, gstreamer and xine.

Make install packages or you'll risk to populate your system with lots of loose files. When you have some time, read a bit here and here.

BrZ 10-31-2013 01:32 PM

Quote:

Originally Posted by andrewthomas (Post 5056019)
As to the order: I would think that this should do.

Code:

dri2proto
glproto
libdrm
pixman
libvdpau
mesa
xorg-server
cairo
freeglut
glew
xf86-video-ati


Nice =]

andrewthomas 10-31-2013 01:51 PM

I still haven't got it working in Slackware, but :

Code:

[    0.000000] Linux version 3.12.0-rc7 (root@msi-gentoo) (gcc version 4.8.1 (Gentoo 4.8.1-r1 p1.2, pie-0.5.7) ) #1 SMP PREEMPT Tue Oct 29 20:38:10 CDT 2013

X.Org X Server 1.14.99.3
Release Date: 2013-10-18
[    17.785] X Protocol Version 11, Revision 0
[    17.785] Build Operating System: Linux 3.11.4-gentoo x86_64 Gentoo
[    17.785] Current Operating System: Linux msi-gentoo 3.12.0-rc7 #1 SMP PREEMPT Tue Oct 29 20:38:10 CDT 2013 x86_64
[    17.785] Kernel command line: BOOT_IMAGE=/boot/kernel-3.12-rc7 root=/dev/sdc8 ro
[    17.785] Build Date: 31 October 2013  12:50:25PM
[    18.221] (II) Loading sub module "dri2"
[    18.221] (II) LoadModule: "dri2"
[    18.221] (II) Module "dri2" already built-in
[    18.221] (II) Loading sub module "exa"
[    18.221] (II) LoadModule: "exa"
[    18.221] (II) Loading /usr/lib64/xorg/modules/libexa.so
[    18.228] (II) Module exa: vendor="X.Org Foundation"
[    18.228]        compiled for 1.14.99.3, module version = 2.6.0
[    18.228]        ABI class: X.Org Video Driver, version 15.0
[    18.228] (II) RADEON(0): KMS Color Tiling: enabled
[    18.228] (II) RADEON(0): KMS Color Tiling 2D: enabled
[    18.228] (II) RADEON(0): KMS Pageflipping: enabled
[    18.228] (II) RADEON(0): SwapBuffers wait for vsync: enabled
[    18.327] (II) RADEON(0): [DRI2] Setup complete
[    18.327] (II) RADEON(0): [DRI2]  DRI driver: r600
[    18.327] (II) RADEON(0): [DRI2]  VDPAU driver: r600

vdpau is certainly in the mix

mlpa 10-31-2013 09:04 PM

Quote:

Originally Posted by BrZ (Post 5056026)
m4 macros and protocols headers. You don't need to rebuild these. Get the easy route and start with libvdpau. Keep the same packages of 14.1, except mesa. Try (re)building just libvdpau -> libdrm -> xf86-video-ati -> mesa -> glu -> glew -> freeglut and -> xserver. Look the source tree and build scripts from Slackware inside 'Slackware/slackware64-current/source/{x,x11}'.

To build xorg-server: "./x11.SlackBuild xserver xorg-server". To build ddx: "./x11.SlackBuild driver xf86-video-ati". And so on...

You can get the script to libvdpau at SlackBuilds. From memory, I remember rebuilding ffmpeg, mplayer, vlc, gstreamer and xine.

Make install packages or you'll risk to populate your system with lots of loose files. When you have some time, read a bit here and here.

I have (re)compiled the code.
Everything compiled and installed normally.

But now the radeon module do not load at boot and startx fails.
If I load the radeon module manually I can startx my system.
However, glxinfo shows that the system is using software render.

Any ideas

Drakeo 10-31-2013 11:44 PM

kernel 3.11 has been well documented it is not going to be developed and on to the 3.12rc it is well know it broke nvidia billds and I spent some time tweaking the headers to get it to build. The average person does not want to extract it and play with it. every thing compiles and the driver never does build. it stays an .o not going to make the big .k0 :). look at your forum. I spent several ours on Fatdog kernel to ge it to build and wasn't worth it. So I read up on it.
:)

mlpa 11-01-2013 04:23 AM

Quote:

Originally Posted by Drakeo (Post 5056311)
kernel 3.11 has been well documented it is not going to be developed and on to the 3.12rc it is well know it broke nvidia billds and I spent some time tweaking the headers to get it to build. The average person does not want to extract it and play with it. every thing compiles and the driver never does build. it stays an .o not going to make the big .k0 :). look at your forum. I spent several ours on Fatdog kernel to ge it to build and wasn't worth it. So I read up on it.
:)

I do not think that is my problem.
If I load the module manually the system starts normally.

andrewthomas 11-01-2013 05:13 AM

Quote:

Originally Posted by Drakeo (Post 5056311)
kernel 3.11 has been well documented it is not going to be developed and on to the 3.12rc it is well know it broke nvidia billds and I spent some time tweaking the headers to get it to build. The average person does not want to extract it and play with it. every thing compiles and the driver never does build. it stays an .o not going to make the big .k0 :). look at your forum. I spent several ours on Fatdog kernel to ge it to build and wasn't worth it. So I read up on it.
:)

I will admit to having some problems with the 3.11+ kernels on one of my AM3+ (AMD 970/SB 950) motherboards, but I now have it working. Although I do use ATI video cards.


All times are GMT -5. The time now is 05:08 PM.