SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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?
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.
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.
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
I will try.
Some more questions what is macros and protos?
Do you have any idea about I need to rebuild after?
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.
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.
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.
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.
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.
Last edited by andrewthomas; 11-01-2013 at 05:13 AM.
Reason: added video card info
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.