-   Linux - Newbie (
-   -   help plez (

strider_D_3000 07-25-2003 03:00 AM

help plez
which of nforce driver from do i install first?
as u notice there are 2 downloads, the first then the kernel upgrade
what am i suppose to install first? the first or the kernel upgrade
from a redhat point of view

MasterC 07-25-2003 04:13 AM

You should only need to install a single file, not one then the other. If you follow the readme that is with that, it is explained in there.

Also, make sure you get the correct file to install for your version, to find out which kernel you have to match it up appropriately, type this into a terminal:
uname -r
And match that up with the version on their website.


MasterC 07-25-2003 04:14 AM

Moderator Note:
In the future, please make more appropriate thread titles. You are much more likely to get quality answers in a faster amount of time that way.

Thank You

strider_D_3000 07-25-2003 04:36 AM

i think my kernel is 2.4.20-8 but they only offer NVIDIA_nforce-1.0-0261.rh90up_2.4.20_6.athlon.rpm and a kernel upgrade NVIDIA_nforce-1.0-0261.rh90up_2.4.20_9.athlon.rpm
which am i suppose to install? (after further reading the readme how do i upgrade my kernel to fit these driver like 2.4.20-8 how do i turn the 8 into a 6
or do i just install the -9 because its a kernel upgrade maybe itll upgrade my kernel from an 8 to a 9 and also install the driver while it s upgrading :) if only it was that easy before i do anything ill wait for some help :) just incase i screw things up
thanks in advance

MasterC 07-25-2003 04:40 AM

What do you get from:
uname -r

And no, I highly (hopefully really) doubt that installing a newer Nvidia driver will upgrade your kernel. However... RedHat's up2date apparently makes upgrading your kernel as easy as point and click (I've never personally used it but read several threads on it), so if you wanna upgrade, that's probably going to be your easiest bet.


strider_D_3000 07-25-2003 05:03 AM

yeah my kernel version is 2.4.20-8 how do i update it to the latest one i the auto update dont seem to work im online right now using my old dsl card)
update:i think im downloading the upgrade right now if it is 2.4.20-9 do i download the 2.4.20-9 version from nvidia eventhough on the side it say kernel upgrade?
do i log into the 2.4.20-9 kernel and run rpm -i nforce2.4.20-9 one? and thats it?

strider_D_3000 07-25-2003 05:39 AM

wtf my new kernel is 2.4.20-19.9 wtf wut do i do. do i download NVIDIA_nforce-1.0-0261.rh90up_2.4.20_9.athlon.rpm? ooh man and i thought the kernel will uograde to 2.5.20-9...

Medic6666 07-25-2003 05:52 AM

What distro you using??

MasterC 07-25-2003 06:10 AM

Ok, got some tricky stuff if you wanna follow along...

Grab this:

Save it to /tmp

Now open up a terminal and type along:
cd /tmp (as a user for now)
tar xvzf NVIDIA_nforce-1.0-0261.tar.gz
cd nforce
cd nvgart
less README (now read those instructions until you are thoroughly confused or completely understanding... Not too far from each other really ;) )
Now we will need to diff the kernel, hopefully you've got your kernel sources install and the present working kernel is the one you've got sources for (if you are saying "Say what?" at this point, please let me know, I'm moving at a fast pace assuming you are just understanding me ;) ).
Hopefully you've got the source for the running kernel and it's setup properly, just to make sure post up what you get from typing:
uname -r
ls -l /usr/src

Assuming it's all well and good, let's diff that sucka!:
As root type:
cp nvgart/linux-2.4.20-agpgart.diff /usr/src/linux-2.4.20-19.9 (assuming the above is all saying we are running that kernel and we have the sources installed for it... )
Now for the diff:
patch -p1 < linux-2.4.20-agpgart.diff
And now we will compile a kernel. Woohoo!!

Ok, so at this point, I believe a kernel guide would be a great tool for consulting. However, I'll be happy to walk with you through a compile tonight OR if you just wanna try the:
And see if it'll work (probably best since you can ALWAYS just rpm -e it which will remove it...) then that's fine too.



strider_D_3000 07-25-2003 02:17 PM

:scratch: woa i guess before i try all that crazy confusing stuff lol ill try to install the 2.4.20-9 on my 2.4.20-19-9 hope it works lol

strider_D_3000 07-25-2003 02:36 PM

noo it didnt work it didnt dectect my adapter and now i cant uninstall it when ever i try rpm -e it tells me that i didnt install it yet but when i do rpm -i it tells me i install it
guess i got to to the hard way can u please explain those very confusing steps slowly lol

strider_D_3000 07-26-2003 12:53 AM

hope u can help me tonite masterc

MasterC 07-26-2003 03:40 AM

Hi there!

You can force a removal, and it's likely you aren't removing it correctly (remove the .i386.rpm from the package name when uninstalling).

After you remove give another package a try, after you've exhausted the 3 packages that are closest to your kernel, and if it still doesn't work, let's get on with the compile ;)

I'm here til at least 5 (that's about another 4 and a half hours from right now for me) :)


MasterC 07-26-2003 05:08 AM

Ok, the kernel compile (assuming you already tried to follow the various threads and guides and they didn't help...):

Grab the latest **stable** kernel: (2.4.21 is the latest stable click the "F" next to that)
Save it to a directory you have write privileges to (we are gonna move it after it's done).

Once it's done (assuming you saved it to /home/kernels) we will need to become root:
su -
ROOT PASS (enter root's pass there)
mv /home/kernels/linux-2.4.21.tar.bz2 /usr/src
Then we will change to /usr/src:
cd /usr/src
And untar the kernel:
tar xvjf linux-2.4.21.tar.bz2
If you have a fast computer, good, just sit back for a minute or 2. If you've got a Slow CPU and no RAM, go grab yourself a java, a cup of Chai Tea, have a round of golf, come back and have dinner, take a nap, and then come back to see it finish up (not really, but it could take a good 15 minutes depending on how slow, I just dropped down to a Pentium 1 laptop, it took me around 15 minutes on that thing! On my 900mhz Athy, ~1 minute ;) ).
After it's extracted you'll be returned to a prompt, so now enter the newly created directory:
cd linux-2.4.21
And (we should still be root):
make xconfig
The make xconfig requires you to be in an X session that root owns (meaning you will have to have started X as root or given root permissions using xhost or something similar). You can use other things like:
make menuconfig
However for first time kernel compilers this can look overwhelming (more so than xconfig does) but it's your choice. Whatever you have to do to get to the kernel compiling options screen, that's where you will want to be.

Now comes the part that really not many people can help you with, you have to find what hardware you have, and what is necessary for it's support and your day to day operations within linux.

Sounds scary doesn't it? Don't worry, nothing is set in stone, and EVERYONE has to do trial runs with their kernels to fine tune em. Go through and read the help files next to the options in each category. Notice the ones that apply to your hardware and needs, and use it. My personal rule of thumb for compiling in versus module (Y or M) is:
If I use it everyday, and it's a required option to get my system running, it's compiled in. If it's something I occasionally use, it's a module.

So go through, do your best, and when you are done, click exit. It will ask if you wanna save your current config, say yes. Then you will be returned to a prompt and it should suggest you run 'make dep' now; so we will:
make dep
After this finishes (go get some more chai tea and coffee)
We will clean it up, save ourselves some room, and make things tidy:
make clean
I wish I could clean my house this easily ;)
After that finishes we need to create the modules you decided you wanted:
make modules
We want to not overwrite the current setup, and we are gonna assume you are already using a 2.4.21 kernel (just for reference sake, not that it fits your situation, but you could use the info some day ;) ), so let's move the current directory containing the modules outta the way:
mv /lib/modules/linux-2.4.21 /lib/modules/linux-2.4.21.old
And now that we have finished the make modules command, we will install them:
make modules_install
It is now creating the necessary directories in /lib/modules/linux-2.4.21 (good thing we backed up the original working directory first eh ;) ) and copying the modules that were compiled into them directories, creating files that know where each module is for quick reference for module calls and other things we aren't too concerned about at this point in our linux days :)

Now we need to make the kernel. I prefer smaller size files for faster kernel loads (I'm a speed freak, what can I say :D ) so we will use bzip compression on the kernel with:
make bzImage
Sit back, grab yourself some water to help cleanse your system of all that coffee and chai tea you've been drinking all day, watch an episode of the Simpson's, and come back, hopefully there are no errors (with any of the steps) however if this is your first compile, it's likely there is. Usually due to dependencies. You should look at the error, see what's missing, open back up the kernel configuration tool you used (xconfig or menuconfig) and add that into your kernel too. Start back over, through each step, do this again and again until you finally get to the end and you have a complete kernel. To know when you have one, you should see a message saying something like:
kernel image is too big for standalone floppy. OR you will see the size of the bzImage and no errors. Either way, the kernel is done, and you can now copy it over to the necessary directory for booting it.

From the command prompt type:
cp arch/i386/boot/bzImage /boot/vmlinuz-newkernel
Where -newkernel is WHATEVER you want it to be, I tend to be simple and use pretty much 'newkernel' :D

Then copy over the system map:
cp /boot/ (remember, don't leave your kernel source tree, stay in the directory where you have been running make xconfig and everything)
And now, your distro utilized mkinitrd to get things setup, so (I've never had to use mkinitrd, so YMMV and I apologize if you have to go outside this thread (run a search) for this part of the compile):
mkinitrd /boot/initrd.linux-2.4.21 linux-2.4.21

And finally, let's make the symlink:
ln -sf /usr/src/linux-2.4.21 /usr/src/linux
This is necessary for certain applications that need to know what kernel version you are running.


As for adding it to your boot loader, consult your distro's documentation, or do a search on Grub (assuming you went with the default) on the site. I use LILO so really can't help ya there. But beware, do not overwrite your current, working kernel. You will want make another entry along side the existing one, then if the new one doesn't boot or whatever, you have somewhere to fall back to.

Good Luck, and HTH


strider_D_3000 07-26-2003 05:35 AM

woa by the frekin gods thanks a lot! ill try the tar one first before i do the kernel one hope it works
dangit it works fine untill i got to the make command it gave me somekind of error damn
illl let the computer rest and try the other way 2marrow
ps its 3am in the west coast so i gots to get some sleep :)

All times are GMT -5. The time now is 05:47 PM.