I am trying to install the ATI driver.
I issue the standard rpm command:
rpm -i fglrx*.rpm
It doesn't work:
root@hal:/home/jayhel# rpm -i fglrx*.rpm
error: Failed dependencies:
/bin/sh is needed by fglrx_6_8_0-8.8.25-1
libX11.so.6 is needed by fglrx_6_8_0-8.8.25-1
libXext.so.6 is needed by fglrx_6_8_0-8.8.25-1
libc.so.6 is needed by fglrx_6_8_0-8.8.25-1
libc.so.6(GLIBC_2.0) is needed by fglrx_6_8_0-8.8.25-1
libc.so.6(GLIBC_2.1) is needed by fglrx_6_8_0-8.8.25-1
libc.so.6(GLIBC_2.1.3) is needed by fglrx_6_8_0-8.8.25-1
libdl.so.2 is needed by fglrx_6_8_0-8.8.25-1
libdl.so.2(GLIBC_2.0) is needed by fglrx_6_8_0-8.8.25-1
libdl.so.2(GLIBC_2.1) is needed by fglrx_6_8_0-8.8.25-1
libm.so.6 is needed by fglrx_6_8_0-8.8.25-1
libm.so.6(GLIBC_2.0) is needed by fglrx_6_8_0-8.8.25-1
libpthread.so.0 is needed by fglrx_6_8_0-8.8.25-1
libpthread.so.0(GLIBC_2.0) is needed by fglrx_6_8_0-8.8.25-1
librt.so.1 is needed by fglrx_6_8_0-8.8.25-1
librt.so.1(GLIBC_2.2) is needed by fglrx_6_8_0-8.8.25-1
libstdc++.so.5 is needed by fglrx_6_8_0-8.8.25-1
libstdc++.so.5(CXXABI_1.2) is needed by fglrx_6_8_0-8.8.25-1
libstdc++.so.5(GLIBCPP_3.2) is needed by fglrx_6_8_0-8.8.25-1
But...
Evething is there!
I checked with find!
I don't understand.
Pls help.

Try converting it into a Slackware package.
$rpm2tgz package.rpm
#installpkg package.tgz

WTF? you can do that? So anytime I cant find a source but there is a rpm I can issue the above and install like that?

Yes, you can do that, but most of the time it does not work. The tgz usually doesn't install. I may be wrong, but I'm saying this by my own experience

Most of mine work, you have to use Redhat/Fedora RPMS but it does say in the rpm2tgz documentation that they are not guaranteed to work. Suse and Mandrake RPMS don't work very well on Slack.

from what ive experienced.. the -source- rpm's do just fine.. some ov the more specific rpm's have issues.
but yeah.. the -source- rpms are no problem

I believe you already have a previous version of the ati drivers in rpm format. Try the -Uvh instead of -i and see what happens.

Brian1
" Google the Linux way @ http://www.google.com/linux "

That error doesn't mean that he already has a version installed, it means that rpm seems to think that the dependencies for the driver he is trying to install are not available on the system. This is because he is trying to install an rpm on Slack and rpm probably cant read the default Slackware package database to determine whether the dependencies are already installed on the system.

yes although the libraries are there and installed certainly...

NEVER do the unhappy thing I've done the first times that it happened:
try to install ALL the dependencies
it's unuseful and frustrating...

Thank you reddazz
I did #rpm2tgz in the root dir (/) like you said.
et voila!
It worked perfecly.
The problem I have now is worse. Instaling fglrx erased some xorgconfig files. I corrupted X.
I had to reinstall Slackware 10.1...
The heck with these video drivers! Nvidia is even worse!
I will use the regular radeon driver that comes with Slackware.
I compiled a 2.6.10 kernel with the radeon option accordingly.
It's more than enough.

So there's now solution about using RPM under Slack ?

I really need to make this work well.

don't use them as rpm
use
rpm2tgz [packagename}.rpm
if you don't have rpm2tgz, then search and you'll find it.. install that, and then install the tgz with pkgtool (or installpkg {pkgname}.tgz)
this works best with SOURCE rpms.. may not work as well with -specific- rpms.

i just had a problem using qtella and converting it to tgz.. so not everything will work.

This may be off topic, but I'd like to share something about Slackware packages that you all may find useful, especially since you are using rpm2tgz to make Slackware packages.

Slackware packages are tarred+gzipped files with a .tgz extension. Let's look at installpkg. What's it really do? It takes the Slackware package and unpacks it in /. It then runs a script contained in the package called /install/doinst (or maybe it's doinst.sh, I'm not at my Slack box right now). The package description is also contained in the Slackware package under /install/desc. That's the description that you see when you are running installpkg. After that, a file named after the package is placed in /var/log/packages/ THe text file contains a list of all the files that were included with the package, along with a package description.

So how is all this useful? Let's say that I have an rpm package called package.rpm. I run rpm2tgz on that and end up with package.tgz. THe next step that everyone seems to be doing is "installpkg package.tgz". So why is that a bad idea? Well, you can see why earlier in the thread. Pre-existing files can end up being overwritten. Using "removepkg.tgz" does not help, because those files were included in other packages too, they are left on your system.

So what do you do with that package.tgz file? How about something like this:
So, what you have done is copied the package.tgz file to another directory. Then, you unpacked it. Now look at all the new files in the 'test' subdirectories that were just created. Are you going to be overwriting pre-existing files? Is that what you want to do? SHould you back up the pre-existing files first? WHat is under test/install? There is a doinst script. What's it do? Is it going to mess up anything?

Summary, it's a good idea to check out your .tgz files when you are using rpm2tgz.

Note that I have given a command line version here for what I would actually do. I use Gnome and there is a program called fileroller. You can use that to open up Slackware packages and see what the contents are and what the install script will do. It may be a good idea to look at some of the Slackware packages on an official install disc to see how they are set up. I an specifically thinking about how the official Slackware packages handle configuration files by appending a .new to them, checking for a pre-existing file with teh same name ( minus the .new extension ) and either keep or drop the .new extension based on whether or not a file by the same name existed.

I disagree with you about Nvidia, it's way easier to install Nvidia drivers on any Linux distro compared to ATI. Why couldn't you just reinstall X instead or reinstalling the whole distro? I didn't realise that ATI overwrote x.org files, if it's the case it's bad practice.

So you reinstalled whole of the OS just because you had corrupted xorg.conf?
Why you just didn't recreate it with xorgconfig??

Weird man......you like to suffer