LMAO

I myself go by the old axiom:

If all else fails, get the instructions out of the garbage and read them...

Wow cwwilson, I only get like 900FPS!

Different things running, different tweaks, etc, can have a major effect on glxgears. That is why it's not a real good benchmark.

To try to minimize those variables, I have a special desktop that I use, and kill all but required processes. It's also booted without network or any modules that are not required to run X. (i.e. sound, usb, etc.)

That way, I have an even playing field to compare my system to itself, not to other systems.

Ah ok, cause I run it while doing lots of things too. So long as I don't get the DRI error and no jerky video/DVD playback, its all ok by me.

The main thing is that it started w/DRI enabled w/750FPS, and now is 3800+, mostly thru kernel updates, with only the last test being a full, clean 'current' install w/kernel 2.6.17-rc3.
So it seems that Xorg 6.9.0 is a boost too, although most increases have been through kernel upgrade/compiles.

I found out how to rsync the slack-current. I'm putting it in now on my desktop. Will post results hopefully soon CW I lost your email addy could you hit me up w/any notes you have for NFS to do an install over the network of slack current? I did the rsync so I'm going isntall from HD to HD on one pc and want to do over the network for my buddies laptop that has sound issues. Thank you.

Same username as on here at yahoo.com

ARGH! NO LUCK! I can't get the drivers to go in!

I'm using the same exact kernel that I used in slackware 10.2. I literally zipped it up and threw it over on slack current. That kernel worked in slack 10.2

I went thru all 4 driver versions that I have downloaded and used in slack 10.2 and no go.

I keep getting stuck at the point where i go "sh ./make_install.sh" in the /lib/modules/fglrx directory!

I event went so far as to go into Windows XP...and extract the exact driver that I have installed/copied there already in tgz format from when I went rpm2tgz.

I get the error: "FATAL: Error inserting fglrx (/lib/modules/2.6.10/kernel/drivers/char/drm/fglrx.ko): Invalid module format failed."

Such a pain.

I'd like to report it to Pat V. but he'd probably think I'm looney. Should I?

Well, back to 10.2 on my main computer I guess.

Best off to get the kernel source and recompile (use the old config from the other kernel install, tho.)

I think I know what you did, so doing a full recompile should straighten you out.

After you 'make xconfig', load the old kernel config, using the 'open' dialog, then 'make && make modules install'. Sometimes, shortcuts won't cut it.

WEll i got them in but I'm getting an xorg mismatch on startup of x. it sees xorg 7 in slackware and the latest drivers are rated to only support xorg6.8!

well anyone installing ati on slack current should check out the readme at :

https://a248.e.akamai.net/f/674/9206...ux_8.24.8.html

" The packages are available for XFree86 versions 4.1, 4.2, and 4.3, as well as X.org 6.8. One of these four versions must be installed before installing the ATI Proprietary Linux driver"

But later it says:

Minimum System Requirements

Before attempting to install the ATI Proprietary Linux driver, the following software must be installed:

* XOrg 6.7, 6.8, 6.9, or 7.0; XFree86 version 4.1, 4.2, or 4.3
* Linux kernel 2.4 or higher
* glibc version 2.2 or 2.3
* POSIX Shared Memory (/dev/shm) support is required for 3D applications

So maybe it's depending on your card may work? I don't know. The readme is either contradictory or wrong.

I'm on 9600XT just so you guys know.

Ironically, i just pulled the config file over from the other pc. Dropped it into the fresh extract of the kernel I use and it worked. Maybe different kernel compiler/environment is why it wouldnt go in before? Don't know.

I give up for now. I think these are first version 7.0 xorg drivers for ATI so, who knows they release drivers every few weeks it appears. However, I guess if slack 11 came out tomorrow I wouldnt be first on the line if you know what I mean.

Hello folks,

I just recently bought an NVIDIA PCI card (an old one). The card worked great under Fedora Core 5. Yesterday, I installed Slackware 10.2 on the same machine. I got the NVIDIA script to install fine. Now, when I do glxgears, I'm getting the same amount of fps that I was getting with Fedora, maybe a little bit more actually. The problem is though, everytime I use any GL screensavers (like glxgears) it uses 100% CPU and the machines becomes very slow. Even when I do glxinfo, my mouse becomes slow for a moment until the glxinfo command finishes up. I was not having these problems with Fedora. Is there anything that I'm missing here? I'm using the 2.4.31 kernel (the default kernel). I have already edited the Xorg file. Thanks for the help!

1. Don't hijack threads. It makes things confusing. (Your problem was not the same as the original problem posted, so this would be considered "hijacking" the thread.)

2. Make very sure you don't have that card sharing an IRQ with some other card or device. Most boards with PCI slots tend to either have four slots and four IRQs, or six slots and slot 2 sharing with 4, and 3 sharing with 5. Video cards do not like sharing IRQs.

3. It also occurs to me that you might actually be dealing with a card old enough to have fallen off the list of properly supported cards. If your card is older than an MX 440 or so, you'll likely need to stick with the 7xxx series driver. Check the README that comes with the driver for the list of cards that are supported and make sure yours is in there. If the nVidia driver can't go hardware-based GL, it's likely that Mesa is taking over, which would explain the CPU load. (Least likely possibility tho)

No need to bother with that first part. In /usr/src/linux there will be a .config file. This is the kernel config as you last saved it. Copy this somewhere. Do a `make mrproper` to clean everything out, and then copy that file back as /usr/src/linux/.config. Now run `make oldconfig`. Everything will be restored and set up as if you'd just finished doing make config/xconfig/menuconfig.

This also makes a wonderful way to recycle configs between kernels so that you don't accidentally omit something important (like ext3 support). Anything new that was added as a configuration item for the new kernel will cause make oldconfig to simply stop and ask you what you want to set it to. (Usually 'no' or 'as module' is a quite safe thing to answer, since you obviously didn't need it the last time you built.)

I wasn't trying to "hijack" anything. This thread was started as a way to enable 3D on many different cards. I tried following the directions set here, but I ran into some problems. I didn't want to start a new thread, if I found this one to be useful. Hence why, I used this thread.

On your other two points, the card is an MX4400. There are not any IRQ conflicts. I think I may be actually using an old driver from NVIDIA. I'll take another look at it when I get home/

Hmm... That card should be fine with the 8756 driver at least. I just had to buy one of those for my MythTV box (since it was actually cheaper than replacing the demolished fan on my 5200).