can't get nvidia drivers to work, stuffed up xf86 config
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
can't get nvidia drivers to work, stuffed up xf86 config
I tried installing the nvidia drivers following what the readme told me to do on the Nvidia site, i'm using a Riva TNT 64, i downloaded the correct drivers, and edited what i needed to edit I THINK, i changed nv to nvidia and added glx, but the readme told me to add something else and i think this stuffed me up, now all that happens is when X tries to start to go to the GUI log in screen it just keeps flashiing, i am not very good in editing files in console, but i had to try so i booted the cd-rom and ran rescue, cd'ed to the xfree86 config file emacs it and tried to edit it, i changed nvidia to nv again, took out glx, and i am not sure what to do now, it does the same thing while starting, just keeps flashing, can i just re-run the X config program, its Xconfigurator isn't it, cause i tried that, and the command wasn't found, i tried other variations aswell, and i pressed 'tab' to try find it and it wasn't listed...
VERY sorry for the long post...but i can't get into linux, so i am about to cry
Xconfigurator is in RH, so if this is RH, you will need absolute path (since you are in rescue mode), so let's say rescue mounted your drive in /mnt then:
might be the absolute path, not sure where Xconfigurator is, but I think you see the idea I am getting at.
Originally posted by neo77777 If you read the docs on nvidia site it is all there, get the NVIDIA_kernel and NVIDIA_GLX in tar.gz archives, unpack them
tar xfvz NVIDIA_kernel-blah.blah.tar.gz
tar xvfz NVIDIA_GLX-yada.yada.tar.gz
switch to runlevel3
then edit /etc/X11/XF86Config-4
Load "dri" # if it is there of course
Load "GLcore" #if it is not there yet
"nv" to "nvidia" in driver section
yeh well i got it working (thank god) but without the help of Xconfigurator, oh well, but still if i was in another situation and COULDN'T edit it by hand, then i would've been stuck, where the hell is Xconfigurator, i have it now, but not whilst in rescue, oh well...thanks MasterC!!!
I have one more question i read the tutorial here to dual boot more than one LINUX DISTRO, but its talking about installing them WITHOUT any distros on, but i have RH 7.3 and i don't want to delete RH just to have more than onde distro, if someone can please read the tutorial and find out if i can do this WITHOUT deleting RH i will be very thankful! Tutorialhttp://www-106.ibm.com/developerwork...=DualBootLinux
OMG that looks long! I will read it though, but here's a few things that might answer the question:
No you don't have to not have a distro to dual distro. You can keep everything the same, no need to delete RH. Here's a mini:
Install Distro A on /dev/hda1 You need to have a seperate partition still, for Distro B.
Install Distro B on /dev/hda2
Put the kernel from Distro B in the /boot directory of Distro A (this assumes ALOT, but you could go the other way if you prefer Distro B's LILO boot screen better, your choice) and add an entry in LILO to reflect the new kernel:
image = /boot/vmlinuz-DistroB
root = /dev/hda2
label = DistroB
Rerun LILO in Distro A to reflect the changes. Reboot, and smile, drink, and be marry
Ok, well that is definitely a mini, isn't all inclusive, but does show a few decent hints.
If that helps let me know. IF not, I will be reading the how to, and let you know how it goes.
Ok, I sorta skimmed it over, no you don't have to reinstall. The part where they are talking about partitioning your drive, you can do that using parted. If you already have a blank partition to put your second distro on, then you are pretty much all set. The tutorial you have there says to have a seperate /boot partition, this is not necessary, but will work just fine.
just one more question MasterC, if i do try to uhhhh install Mandrake is there a way to tell the installer to install the kernel of Mandrake into the boot partition, because if i can't will the Mandrake kernel go over the RH one, and also, what is the point of having a boot partition and ONE more do i move my Rh kernel to the boot partition aswell....?
You probably already have a boot partition - I believe it's the default setting under RedHat. Personally, I get along with a 100meg boot partition. Not sure what the official recommendations are. Anyway, if you do already have a boot partition created by the redhat installer, your kernel will already be on it. By default, the boot partition is mounted as /boot/.
I don't think the mandrake installer will let you manually specify a kernel location. What you'll be telling the mandrake installer to do is not create a swap partition (you've already got one), not to create a boot partition (ditto), and not to install a boot manager (like grub or lilo, again, you've already got one).
So basically what you'll end up with is one partition created by mandrake. This will probably be a logical partition, since you'll probably already have chewed up all your main (or primary, or whatever they're called) partitions. Shouldn't be a problem. Trying to boot off a logical partition can be a problem, but that's not a problem for you - the whole reason for copying the mandrake kernel to your boot paritition is that the boot manager won't need to know about your logical mandrake partition - it'll pass control off to the kernel image on your boot partition.
So you're done with the mandrake installer, and you reboot. Your system should just boot back into redhat, because you told mandrake not to install a boot manager (didn't you? :-)). At this point you'd copy over your chosen kernel from the mandrake partition (you'll have to mount it first) into your boot partition (probably already mounted as /boot/). Depending on how mandrake's configured (I haven't used it for several versions), you'll probably also need to copy an accompanying initrd file.
Finally, make the alterations to lilo that MasterC outlined, and you should be good to go.
I would recommend copying over the initrd file. You could probably boot without it, but it might compromise certain functions.
The initrd file is an image file which allows certain things like scsi drivers to be loaded ahead of the kernel. Mandrake will probably have (in the same directory as the kernel image(s)), corresponding initrd-<version>.img files, or something named similarly. Copy these over as you would the kernel images, and make sure that you include appropriate references to the initrd files in your boot manager configuration.