You have to rebuild the nvidia module if you compile a kernel. I would suggest using the SlackBuild at slackbuilds.org (if you are already using it, you should probably revert to the old X drivers before recompiling the nVidia module using nvidia-switch).

$>free -m
total used free shared buffers cached
Mem: 4051 283 3768 0 17 163
-/+ buffers/cache: 103 3948
Swap: 0 0 0

Yes! Thanks friends!!! I am running now Slackware 12.1 recognizing my 4Gb RAM.

The last thing I've done is to download the NVIDIA drivers:

wget http://us.download.nvidia.com/XFree8...43.05-pkg1.run

Give it executable permissions:

chmod 777 NVIDIA-Linux-x86-96.43.05-pkg1.run

Installing drivers:

sh NVIDIA-Linux-x86-96.43.05-pkg1.run

I didn't let the installer create a new xorg.conf since I already had one working fine.

Now, my system boots fine. I have to test it but I am sure it works OK (well. It's too soon to say so but I am an optimist :-)

T3Slider, I've just read your recommendation about installing nvidia driver from slackbuilds.org. You think I should do that or is it the same? You've also mentioned about reverting to the old X drivers. How should I do that?

One more question (Will it be the last one? :-) :

After testing the new kernel compilation. If I see everything works fine How can I get rid of the old kernel files? Would you recommend that to me?

Do these instructions do what I want? (I took this from one of Shadowsnipes previous replies):
cd /usr/src/linux-2.6.24.5-custom
make clean

Thanks to you all! I am very sorry because of the time you spent helping me. I really appreciate what you did and I've learnt a lot from you.

If you've already installed the nVidia drivers the normal way, then don't worry about it. I would normally recommend the SlackBuilds, but it's not worth the effort if you've already let the nVidia installer do its thing.
I would recommend leaving the old kernel files alone. They were the default included in Slackware, and there's no harm keeping them around (and if anything goes wrong, you can always revert back to using them).
That would probably be a bad thing. That would clean up your current kernel source directory. Some applications (mostly those that inject out of tree modules into your system) may need the kernel sources to compile. You should leave them alone. If you REALLY get strapped for hard drive space, you may be able to delete the /usr/src/linux-2.6.24.5/ directory (or uninstall the kernel-source-2.6.24.5_smp-noarch-2.tgz package), but I would not recommend it under normal circumstances.

OK T3slider, I'll leave everything the way it is. It will be safer, you're right.

The only thing I will do is comment those lines in lilo since I don't need them anymore (but this is just a detail). Thank you!

Thanks to all of you who help during this thread.

Glore2002.-

Gotta like it, seeing someone stick with it till the happy ending; congrats Glore

Sasha

PS - That's what the forum is all about!

It really is not that much effort. You simply need to run the uninstall routine on the NVIDIA .run file. It should restore the original mesa files. After that you can build and install the Nvidia driver and kernel packages.

I personally really like the nvidia-switch program. Granted, I don't really ever need to switch drivers, but it is useful in the unusual instances that I do. Plus, I simply like having all my software packaged.

If you want to pursue this, glore2002, let me know. I can help if you need it.

Well, it seems like unnecessary effort to me -- if you want to switch to the SlackBuilds, you have to uninstall the nVidia driver anyway, negating the benefit of the SlackBuilds. Maybe if an upgrade of the drivers is in order it would be worth it, but uninstalling the drivers to install them again seems pretty pointless to me when the drivers can just be uninstalled in the future using the same procedure, and then subsequently upgraded (possibly by using the SlackBuilds). I just don't really see any positives to using the SlackBuilds when the driver is already installed. But that's just me I guess (I am using the SlackBuilds, but if I hadn't in the first place I wouldn't have bothered to switch over). I guess if you REALLY need the nVidia installed files in /var/log/packages then I could understand it, though.

There is a benefit of taking care of it now instead of waiting until the next update. If you lose the .run file or some of the logged settings get lost then it will be harder to uninstall the drivers later.

Also, if there are some X related security updates then there might be conflicts. This is because the Nvidia drivers overwrite some of Slackware's files. With the SlackBuilds packages, you would just use nvidia-switch, upgrade the X packages that have updates, and then switch back with nvidia-switch. I guess you could just reinstall the Nvidia drivers after an update, so its 6 and 1/2 dozen.

Yes Shadowsnipes. If it is not a problem for you, I would like to learn how to uninstall and install that nvidia-switch program and the drivers from slackbuilds (it sounds great). With your guide I know I will be able to do it.

Thank you!

Nice words GrapefruiTgirl. This forum and you guys are great!

Glore2002.-

Uninstalling the Nvidia drivers is a simple as
You can see all of the basic options with
and Advanced options
For all of these you might of course need to change the version number.

The uninstall routine, in my experience, does a good job of restoring your original X files (I actually went through all the files to check this), assuming you have the original installer still and have not messed with any of its associated files.

The Nvidia Slackbuilds are very easy to use. If you have never used a slackBuild before I encourage you to read the SlackBuild HowTo.

Basically the steps are:

1) Download SlackBuild
2) Download the Source and check the md5sum
3) Untar the slackBuild
4) Place source (or link to source) in the slackBuild directory
5) Modify the build script as needed
6) Run the slackBuild
7) Install the created package

I personally prefer to keep my SlackBuilds in one directory and my downloaded sources in another. Because of this I create symbolic links to the sources in the untarred slackBuild directory. This is particularly useful for multiple slackBuilds that use the same source (such as the Nvidia SlackBuilds).
So for instance for Step 4 I might (in the slackBuild directory)
Step 5 is optional if you don't need to specify any options in the script. Usually the only thing I change is maybe the ARCH and the VERSION of the program. Things like this can actually be specified when you run the script, however. I prefer modifying the script instead of run-time options so that I have a record of how I built the package.

Run the slackBuild as ROOT.

For Step 7, by default the package is placed in /tmp. I suggest moving it to somewhere under root's home directory for safe keeping. The slackBuild files (expanded source, package files) are under /tmp/Sbo. You can delete them if you are done with them.

The Nvidia driver slackBuild provides the nvidia-switch program. It is automatically called after the drivers package is installed in order to switch to the Nvidia files. Later if you want to switch back to the stock drivers simply execute
You should do this before uninstalling or upgrading the Nvidia drivers package (As said in the SlackBuild README).

If you actually want to run X with the stock drivers be sure to change
to
in /etc/X11/xorg.conf

It does not matter which order you install the Nvidia SlackBuilds. Keep in mind that you can have multiple versions of the nvidia-kernel slackBuild installed (one for each kernel).

Do use common sense when installing, upgrading, or uninstalling these. In other words, make sure you aren't running X when doing it. A simple
as root should help when you are in runlevel 4.

I'm glad to help you, as I'm sure others are too, but you'll learn a lot more if you try searching the forums first, then the web, then reading man pages, and THEN asking your question if you still don't know how to do it. You need to live life on the edge -- instructions will not always be spelled out for you word-for-word. Try stuff and have fun -- if it breaks, then by all means, ask away.

It should be noted that shadowsnipes' instructions for building the nvidia packages are for the 169.12 version, whereas you appear to be using the legacy version based on a previous post. When you run the SlackBuilds, you should run them like this:

OK. I will keep track of all these advices.

Thank you!

Hello,

I have read this entire thread and I have some questions
about PAE (I'm using Slackware 12.2 on a PC with 4GB main
memory).

1/ Is it better to use the generic kernel, and lose more
than 700MB of memory, or to use a pae-kernel ? to be more
specific, is there stability issues related to PAE ?


2/ if i use a pae-kernel, is there some packages that
must be recompiled (except the nvidia and all packages
which are kernel dependent) ?

3/ is there more issues related to the nvidia driver when
used with a pae-kernel than when used with the generic-
kernel ?

thanks.

--
SeB

hi
when i was installing the ubuntu in my laptop my hardisk was format and tell me how i get my data back

and how i install the other application
can anyone help me?

thanks
sanjay