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.
It was left purposfully vague. I know it sounds cruel and callous, but I don't have the time, nor the desire, to make a list. If you don't know, search Google or this forum. If you can't find an answer, look at the vendors site.
READ THE DOCUMENTATION. This post was originally aimed at Slackware users, who as a whole, don't go for much handholding. You want a feature? Find it, add it, compile it, make it work. You want a fancy gui and all the choice taken from you? Use Windows.
You want a list? Look at the manufacturers website. But not in this thread.
It was left purposfully vague. I know it sounds cruel and callous, but I don't have the time, nor the desire, to make a list. If you don't know, search Google or this forum. If you can't find an answer, look at the vendors site.
READ THE DOCUMENTATION. This post was originally aimed at Slackware users, who as a whole, don't go for much handholding. You want a feature? Find it, add it, compile it, make it work. You want a fancy gui and all the choice taken from you? Use Windows.
You want a list? Look at the manufacturers website. But not in this thread.
You missed my point really... I'm not asking you to make any list or for any hand holding. In fact, in your original post, you wanted anyone to provide input and you said any input is useful. All I'm saying is to add a simply line that says "Some ATI cards require vendor drivers, some don't. For a list of the ones that don't, see /usr/X11R6/lib/X11/doc/html/radeon.4.html".
I mean it's great you're going through the trouble of providing this guide for people. The guide becomes greater when people contribute. I think I'm contributing a good piece of information.
Left purposefully vague... Why?
And by the way, I've always used Slackware, and only dabbled in other more "friendly" distros just to see what they're all about.
cwwilson721 is purposefully vague about what chipsets the proprietary ATI drivers support because support ATI often drop support for older chipsets as they add new ones.
No ATI chipsets require the proprietary drivers to function at the moment. Many require them to provide 3d support, but that is different.
As a general rule of thumb at the moment, anything older than a 9500 is probably not supported.
The most accurate list is probably that that ATI themselves keep, as cwwilson721 said.
Quote:
Originally Posted by cwwilson721
You want a list? Look at the manufacturers website. But not in this thread.
Thanks. That was EXACTLY why I don't want a list. Too many changes, etc...
As this is a general guide, I don't want it dated by the informmation contained. It is here to help in as general way as possible, without extreme voids. I want it to be useful down the road, too.
The posts in the thread,on the other hand, are great for things like this...
I just want the top post to be as generic as possible, while still giving relevant info (If I post the url to the list today, who's to say the address won't change in a week?)
I searched the thread for "Xinerama" and "dual" but found nothing, so hopefully this is a new question. What are the prospects for enabling DRI under Xinerama on the i810 chipset? I have a laptop with an Intel 855GM and I just got it working with Xinerama on the internal LCD and an external CRT. I had gotten DRI working on the single head already.
In /var/log/Xorg.0.log I found the line
Code:
(WW) I810(0): Direct rendering is not supported when Xinerama is enabled
Obviously that doesn't look too encouraging. Does anyone know if it's possible in any way? Or will I have to resort to a dual screen (or is it "display"?) setup?
I want to make sure that 3D acceleration will work on my video card. My video card is: ATI Rage Pro Turbo 2x AGP with Crystal.
It's on an old 1998 IBM computer with Slackware running on it, of course. Will it work?
I want to make sure that 3D acceleration will work on my video card. My video card is: ATI Rage Pro Turbo 2x AGP with Crystal.
It's on an old 1998 IBM computer with Slackware running on it, of course. Will it work?
Did you look at ATI's website and see if the card is listed for the OEM driver? Usually, if not, it won't have DRI capabilities.
I tried old fogie's long and detailed method. While trying to get my ATI drivers installed the following error popped up. Note that I do have all of his Kernel options set.
root@asd:/home/Blah/Drivers# cd /lib/modules/fglrx/build_mod
root@asd:/lib/modules/fglrx/build_mod# sh make.sh
ATI module generator V 2.0
==========================
initializing...
cat: /lib/modules/2.6.20.3/build/include/linux/version-*.h: No such file or directory
Error:
kernel includes at /lib/modules/2.6.20.3/build/include do not match current kernel.
they are versioned as ""
instead of "2.6.20.3".
you might need to adjust your symlinks:
- /usr/include
- /usr/src/linux
root@asd:/lib/modules/fglrx/build_mod#
Looks like the ATI drivers are incompatible with the Xorg version in the lastest -current update. Hrmph. at their usual pace it will take a couple of months they start working again. That sucks.
VirtualComputer: version 8.19 is seriously old and won't work with newer kernels.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.