-   Linux - Hardware (
-   -   Help with Nvidia (

nymusicman 09-07-2007 05:57 PM

Help with Nvidia
I'm running Kubuntu Feisty 7.04 and I have a Nvidia MX 4000 video card. The driver I have to use is Latest Legacy GPU version (1.0-96xx series): 1.0-9639. Because this legacy driver is not in the repositories, I have to use the binary off Nvidia's website. Not really a problem. The problem is that I also have a few games installed on my Linux box which requires having mesa libraries. Nvidia's driver and mesa library have a conflict with the opengl files. Also not really a problem when my computer is running, I just install Nvidia's drivers after mesa and everything is overwritten and it works.

The real problem I'm having is that whenever I reboot the computer X won't start until I reinstall Nvidia's drivers. Now because X won't start I still really don't have a problem with this being the Nvidia's drivers require X to be closed. It is an annoyance but i really don't turn my computer off that much. But now I'm hearing that Gutsy will have an X safemode, so now I'm realizing I need to take care of this problem once and for all. Please help.

davesmith 09-07-2007 08:34 PM

I guess you're saying that every time you reboot, you lose the NVidia driver? Is that a fair suggestion?

Is it a conflict between a regular kernel module being loaded instead of the newer nvidia one at boot time? You'd be able to blacklist the regular kernel one, if that's the case.

Apart from that, I don't see Kubuntu reloading the mesa libraries at boot time ;)

can you find out, before and after loading the nvidia driver, what the loaded modules are? Here's a suggestion:
BEFORE loading nvidia driver:

# lsmod | sort > /tmp/nvidia-before
AFTER loading nvidia driver:

# lsmod | sort > /tmp/nvidia-after
# diff /tmp/vidia-before /tmp/nvidia-after

This should list any differences in the currently loaded modules before and after. We can then blacklist the ones we don't want to load.

nymusicman 09-08-2007 02:54 AM

Doing what you said I received these results.


< agpgart 35788 2 nvidia,via_agp
> agpgart 35788 1 via_agp
< nvidia 3930860 0
I'm not really familiar with how this works necessarily so it would be awesome if you could tell me what to do next.

njbailey 10-21-2007 02:37 PM

Let me translate this into English for you :)

Before, you agpgart was loaded and one module (via_agp) was using it.
Afterwards, both that module and the nvidia module were.

Afterwards, the (enormous!) nvidia module was loaded.

So maybe you want to put nvidia in the list of modules loaded at boot time? By sticking it on the end of the file /etc/modules perhaps. Just the word nvidia on a line by itself should do. This should work for you if you find loading it by hand fixes your problem (you'd type "modprobe nvidia" (no quotes) as root to see if it does).

There is a proper way, involving associating the nvidia module with appropriate device nodes, but it depends if you're happy with this hack...

Hope I understood the problem correctly.


All times are GMT -5. The time now is 06:59 AM.