Problems? See this thread at archive.org.
How do I enable and disable SLI in Ubuntu? I entered the sli=on command and now it won't boot. How do I fix that and how do I enable and disable it in the future? I already installed Nvidia drivers from the terminal.
-
https://help.ubuntu.com/community/NvidiaManual
it's not as difficult as it seems.
-
Don't worry, none of this makes sense until later
But you can launch nvidia-settings and see the stats, bascially? Should be up and running then. The scripts in the package well tends to do the same as what you would run manually.
And.. no, not necessary to reinstall, etc. What you're going to do in that tutorial in the link is essentially.. download the kernel and the header files for a recent kernel version (skip the source download XD), a compiler if necessary, and the nvidia driver.
Once you've done that (through the package well/package system, which pulls in dependencies automatically, and downloaded the nvidia binary driver), you're going to unpack the driver and run a script created by nvidia that will compile a new kernel with the nvidia driver inserted.
At this point you should have two entries in the boot. The previous kernel you had, which probably uses module inserts or nouveau....(nouveau is a reverse rewrite of the nvidia-drivers in an attempt to make it possible to use nvidia cards with only open source drivers. Foss is preferable for all kinds of reasons and should be a goal, but not in your case). And the last one should be the newly compiled kernel with the nvidia driver. You can load back and forth between those kernels (unless some idiot has been "streamlining" the ubuntu boot process again, in which case you would have to manually launch the previous kernel from the grub command line, which is a pain in the ****).
So this driver may not load flawlessly, having to do with the way module inserts and so on could still be present and conflicting with the driver. Then you would need to blacklist nouveau modules and so on. But honestly this usually is taken care of with the many different pre-made scripts you can run.
I don't know. The things I didn't understand anything of at first was that all the edits you do to config files usually control states for modules that may not even be loaded. Say you want to make an edit to the boot parameters. Add the acpi_backlight=vendor acpi_osi=linux switches to the kernel, for example, to get the backlight to work. What you're actually doing now is that first you have to find a way to edit the bootloader's config files. In Mint, there's a way to do that in the GUI. In Suse, you /have/ to use the suse tools to do it, because the boot writes back several layers for consistency. In Ubuntu, there's another variant where the ubuntu config calls another tool to update grub. And all of these are different.
So what you have to do is to find a walkthrough that's specific for your distro, to find the right way to do the tasks. All of the tasks are the same - but the method is always slightly different.
For example, the entire nvidia compile. Most people use module inserts now, so that you don't need to deal with conflicts at kernel boot (i.e., black screen and no way to get any further). Also, don't need to recompile kernel, etc., etc. So that's much more preferable. But the wikis obviously don't say: "Oh, and by the way, all the stuff you just did is a waste of time!". You know.. there's degrees of things here. But what you essentially do is exactly the same as before. Compile kernel with option for module inserts, boot new kernel, launch config. Perfectly similar and needful process, all of the steps making perfect sense. ..in hindsight.
750m sli in Ubuntu
Discussion in 'Linux Compatibility and Software' started by Drewm3i, Sep 26, 2013.
