LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Closed Thread
  Search this Thread
Old 11-30-2009, 03:40 PM   #661
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649

Original Poster
Blog Entries: 1

Rep: Reputation: 67

Post #1 has some editing now.

I REALLY NEED ATI FEEDBACK
 
Old 11-30-2009, 04:42 PM   #662
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 399Reputation: 399Reputation: 399Reputation: 399
Regarding ATI drivers... This only holds true for Slackware 13.0:

All non-HD cards (roughly the radeon 7000 through the radeon X1950) are supported by the open source drivers that come with Slackware 13.0. They are presently capable of running compiz and KDE4 desktop effects, playing ut2004, neverball, nexuiz, openarena, sauerbraten, and many other games. *None* of those GPUs are supported by the proprietary drivers any more.

If the open source drivers are working properly 'glxinfo | grep -i renderer' should show:

Mesa DRI R300 Project

R300 might be R200, R100, or even 'radeon' (depending on the model GPU).

Nearly all HD cards are supported by the proprietary drivers. On Slackware 13.0, they can be installed this way:

You need to download the driver from http://www.amd.com/. As of today, the latest version is 9.11 and can be downloaded here: http://support.amd.com/us/gpudownloa...5&lang=English . Next, as the root user, you have to run that file. From a terminal, change to the directory that you downloaded the file to and run (as root) 'sh ./ati-driver-installer-9-11-x86.x86_64.run --buildpkg Slackware/All'

This will create two Slackware packages in that same directory. These can be installed with the installpkg command. You would then run 'aticonfig --initial' and it will create an initial xorg.conf file. Reboot and cross your fingers, and when your machine comes back up, you should be running with the proprietary drivers.

If the proprietary drivers installed properly, then 'glxinfo | grep -i renderer' should show:

OpenGL renderer string: ATI Radeon HD 3870

Obviously the renderer string would change depending on the model GPU.

With either the open source or closed source drivers, if the 'glxinfo | grep -i renderer' shows 'Software Rasterizer' then there is something wrong.

You really need to get rid of the part of the post on checking glxinfo for "Direct rendering: yes". That does not mean that hardware acceleration is working. You also say "Some higher end cards do not want/will not work with DRI module loaded." Only nvidia cards will work with that module disabled. *All* other cards need that module loaded. Also, simply commenting out that line will not disable DRI from getting loaded. You need to explicitly change that line to 'Disable "dri" ' to disable direct rendering with ATI and intel GPUs.

Let me know if you have any questions.
 
Old 12-02-2009, 04:06 AM   #663
kaz2100
Senior Member
 
Registered: Apr 2005
Location: Penguin land, with apple, no gates
Distribution: SlackWare > Debian testing woody(32) sarge etch lenny squeeze(+64) wheezy .. bullseye bookworm
Posts: 1,832

Rep: Reputation: 108Reputation: 108
Hya

ATI on Debian squeeze.

chipset: Radeon Xpress 200M

This one used to work until ATI dropped support, by proprietary driver.

Now, the driver does not compile on 2.6.30 kernel.

With open source driver (libgl1-mesa-dri), Xorg.0.log says that modules (dri and dri2) are loaded,
Code:
RADEON(0): Direct rendering experimental on RS400/Xpress 200 enabled
.
.

(WW) RADEON(0): Direct rendering disabled
.
.
and does not work.

With environment variable LIBGL_DEBUG set to verbose, glxgears returns
Code:
 libGL error: XF86DRIQueryDirectRenderingCapable returned false
 
Old 12-02-2009, 05:10 AM   #664
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 399Reputation: 399Reputation: 399Reputation: 399
It is certainly possible to get direct rendering going on the Xpress 200M GPU with the open source drivers on Debian, but this is not the thread to ask for help with Debian :-)

If you do need help, start a thread in the correct location, include the full Xorg.0.log file, and PM me.

Adam
 
0 members found this post helpful.
Old 12-02-2009, 06:14 AM   #665
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649

Original Poster
Blog Entries: 1

Rep: Reputation: 67
Quote:
Originally Posted by adamk75 View Post
It is certainly possible to get direct rendering going on the Xpress 200M GPU with the open source drivers on Debian, but this is not the thread to ask for help with Debian :-)

If you do need help, start a thread in the correct location, include the full Xorg.0.log file, and PM me.

Adam
No, we try to help all who need it.

Post your Xorg.0.log file, please, and xorg.conf.

While we may not know the specifics of your distro, we should be able to guide you to where you need to go
 
Old 12-02-2009, 06:27 AM   #666
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 399Reputation: 399Reputation: 399Reputation: 399
Yeah, let's create an even bigger mess of this 45 page thread :-)

Adam
 
0 members found this post helpful.
Old 12-02-2009, 06:30 AM   #667
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649

Original Poster
Blog Entries: 1

Rep: Reputation: 67
You don't have to post anything in this thread, if you so wish.

I, however, STARTED this post with the intent of HELPING THOSE WHO NEED IT.
 
Old 12-02-2009, 06:39 AM   #668
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 399Reputation: 399Reputation: 399Reputation: 399
My point is that having posts in the correct location not only helps the person asking for help, but then helps people down the road by having the information organized in a sane manner. If someone else with a problem with an Xpress GPU on Debian goes to the debian section here looking for help with the same problem, they aren't likely to find a solution in the slackware section of the forum.

But, then again, having a 45 page thread is of limited use, anyway. Lord only knows how much helpful information is lost in here because no one wants to read through all 45 pages looking for it.

Adam
 
Old 12-02-2009, 06:46 AM   #669
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649

Original Poster
Blog Entries: 1

Rep: Reputation: 67
My point is, I HELP ALL WHO ASK

As for your 45-page comment, look at post # 1

Did you ever stop to think WHY it's 45 pages long? Maybe because we LIKE to help?

And we will help. We may not be able to do much for other distros, but we can TRY. Slackware ain't other distros. We always try to help all that ask. THAT is the reason I've been Slackware since 3.x: Because of this community.

Either contribute, or stop crying about "This post is too long!". Your whining is adding to the length, and no help is coming from you.

You're welcome to post here, but in a helpful manner, not "Go Away"
 
Old 12-02-2009, 07:01 AM   #670
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 399Reputation: 399Reputation: 399Reputation: 399
A) I never said "Go Away". I directed the user to post at the correct location and offered to continue to help them there.

B) I've seen post 1. It frightens me, frankly. I mentioned to you a while ago that checking for direct rendering via glxinfo will not indicate if 3D acceleration is enabled any more. You argued with me about that point for a while and your first post still says to check the direct rendering status. The ATI section is completely out-of-date, despite the fact that you have been given correct information for Slackware 13.0. There are numerous references to the 'i810' driver, though no such driver actually exists for Slackware 13.0.

I think the best contribution would be to sticky a new thread with updated, correct information for Slackware 13.0.

Adam
 
Old 12-02-2009, 07:37 AM   #671
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,922
Blog Entries: 44

Rep: Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158
Hi,

Quote:
Originally Posted by adamk75 View Post
It is certainly possible to get direct rendering going on the Xpress 200M GPU with the open source drivers on Debian, but this is not the thread to ask for help with Debian :-)

If you do need help, start a thread in the correct location, include the full Xorg.0.log file, and PM me.

Adam
I've been trying to get my 'Dell 1501' working which has a 'Radeon Xpress 200M' for a long time. I have jumped through so many hoops that my back is starting to hurt.

My distribution is Slackware and it's use throughout my systems.

I too agree that no one should be turned away. Sure distribution specific questions can be handled by distro users but diagnostics for trouble shooting the problem remains the same for any. It's the semantics of the distribution that get in the way.

Adamk75, I've tried some of your suggestion to get this ATI nightmare off my back to no avail.

I'm no newbie and try to help whenever or whoever needs it.That's the LQ & Slackware way!

Quote:
Originally Posted by adamk75 View Post
It is certainly possible to get direct rendering going on the Xpress 200M GPU with the open source drivers on Debian, but this is not the thread to ask for help with Debian :-)
What about Slackware 13 x86_64 on a Dell 1501 w/ Xpress 200M (RS482)? Looking forward to your positive reaction/solution.

BTW, I don't claim to be a 'X'pert.

EDIT: the content length does cause problems for some. But if you really want to find that jewel a little digging won't matter.



Last edited by onebuck; 12-02-2009 at 07:39 AM.
 
Old 12-02-2009, 07:45 AM   #672
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 399Reputation: 399Reputation: 399Reputation: 399
Quote:
Originally Posted by onebuck View Post
Hi,

What about Slackware 13 x86_64 on a Dell 1501 w/ Xpress 200M (RS482)? Looking forward to your positive reaction/solution.
Yes, it should certainly work. I'm surprised it didn't work out-of-the-box, in fact. Can you show the output of 'glxinfo' and attach your /var/log/Xorg.0.log to a post here (or pastebin it)?

Adam
 
Old 12-02-2009, 09:04 AM   #673
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,922
Blog Entries: 44

Rep: Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158
Hi,

Quote:
Originally Posted by adamk75 View Post
Yes, it should certainly work. I'm surprised it didn't work out-of-the-box, in fact. Can you show the output of 'glxinfo' and attach your /var/log/Xorg.0.log to a post here (or pastebin it)?

Adam
I'm back to where the system was with a stock install except for kernel;

Quote:
glxinfo
name of display: :0.0
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 150 (GLX)
Minor opcode of failed request: 19 (X_GLXQueryServerString)
Serial number of failed request: 13
Current serial number in output stream: 13

Xorg.o.log_pastebin

xorg.conf_pastebin

Quote:
~# uname -a
Linux buck 2.6.32-rc7 #1 SMP Tue Nov 17 11:56:33 CST 2009 x86_64 AMD Turion(tm) 64 X2 Mobile Technology TL-50 AuthenticAMD GNU/Linux
Quote:
lspci -vv;

01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200M] (prog-if 00 [VGA controller])
I'm currently using '2.6.32-r7' but also worked extensively with 'generic-2.6.29.6', 'generic-2.6.30.5', '2.6.32-rc5' to attempt to get things going. I've rolled packages back to the originals to get 'X' back; '/var/log/packages/libdrm-2.4.12-x86_64-1', '/var/log/packages/mesa-7.5.1-x86_64-1' and '/var/log/packages/xf86-video-ati-6.12.2-x86_64-2'.

This has me bugged, frustrated and very embarrassed.

 
Old 12-02-2009, 09:12 AM   #674
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 399Reputation: 399Reputation: 399Reputation: 399
You really appear to have done a number on your system. The first thing that jumps out at me is:

Code:
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed (libdri.a too old)
[dri] Disabling DRI.
libdri.a isn't even included in Slackware 13.0 and should not be present on your system. What is the output of 'find /usr/lib64 -iname libdri*' on your system?

EDIT:

Also, what is the output of 'dmesg | grep drm' and 'lsmod | grep radeon'. And, while we're at it, can you grep for 'radeon' from the .config file for your kernel build? Probably 'grep -i radeon /usr/src/linux-2.6.32-rc7/.config'

Last edited by adamk75; 12-02-2009 at 09:15 AM.
 
Old 12-02-2009, 09:16 AM   #675
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,922
Blog Entries: 44

Rep: Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158
Hi,

Quote:
Originally Posted by adamk75 View Post
You really appear to have done a number on your system. The first thing that jumps out at me is:

Code:
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed (libdri.a too old)
[dri] Disabling DRI.
libdri.a isn't even included in Slackware 13.0 and should not be present on your system. What is the output of 'find /usr/lib64 -iname libdri*' on your system?

Adam
I know, about to throw things back!

Quote:
~# find /usr/lib64 -iname libdri*
/usr/lib64/xorg/modules/extensions/libdri2.so
/usr/lib64/xorg/modules/extensions/libdri.so
/usr/lib64/xorg/modules/extensions/libdri.la
/usr/lib64/xorg/modules/extensions/libdri2.la
I appreciate another pair of eyes!

 
  


Closed Thread

Tags
3d, acceleration, ati, enabling, fglrx, glx, intel, nvidia, s3, savage, slackware, via, video, x11, xorg


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
enabling hardware acceleration PennyroyalFrog Linux - Newbie 5 02-26-2010 11:21 AM
xorg-x11 7.0 and exa acceleration jtshaw Linux - Software 0 12-19-2005 07:42 AM
3d acceleration and X11 bspus Linux - Newbie 3 09-06-2005 06:05 AM
Problem Enabling 3D Hardware acceleration. mir_sheely Linux - Hardware 0 06-14-2004 12:37 PM
Audigy Sound card and enabling 3D acceleration for GeoForce3 ti 500 heavyarmor4ever Linux - Newbie 1 01-03-2003 09:27 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:53 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration