Correct instructions for installing NVidia proprietary driver on Fedora 13?

[Michael Miles]

On 05/30/2010 04:47 PM, Steven P. Ulrick wrote:
>>> Hello Everyone
>>> I'm going to try all of this again.  This time, I'm going to give a precise,
>>> blow by blow account of what I am doing:
>>> 1. "yum update": No Packages marked for Update
>>> 2. [steve at localhost ~]$ /sbin/lspci | grep VGA
>>> 03:00.0 VGA compatible controller: nVidia Corporation G94 [GeForce 9600 GT]
>>>        
>> (rev
>>      
>>> a1)
>>> 3. Go to this address: http://www.nvidia.com/object/IO_18897.html
>>> I found this on that page: "GeForce 9600 GT  0x0622"
>>> 4. I SKIP this step "su -c 'setsebool -P allow_execstack on'" because I have
>>> SELinux disabled.
>>> 5. su -c 'yum install kmod-nvidia'
>>> Results:
>>> Package 1:kmod-nvidia-195.36.24-1.fc13.6.x86_64 already installed and latest
>>> version
>>> Nothing to do
>>> 6. su -c 'mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-
>>> nouveau.img'
>>> 7. su -c 'dracut /boot/initramfs-$(uname -r).img $(uname -r)'
>>> 8. "rdblacklist=nouveau nomodeset" at the end of the appropriate kernel line
>>>        
>> in
>>      
>>> "grub.conf"
>>>
>>> These 8 steps are the same ones that I follow every time I try this.  If
>>>        
> this
>    
>>> does not work, I am going to try 'blacklist "nouveau"' in
>>> /etc/modprobe/blacklist instead of "rdblacklist=nouveau" in grub.conf.
>>>
>>> OK.  Here we go...
>>>        
>> Hello Again,
>> I decided to re-compile the kernel because of the last two comments on this
>> page:
>> http://ubuntuforums.org/archive/index.php/t-701291.html
>>
>>      
>>> Tails9
>>> February 20th, 2008, 03:59 PM
>>> After reading alot, I guess I have to compile the kernel without the
>>>        
> nvidiafb
>    
>>> module, because I'd like to use the official nvidia drivers so I can run
>>> compiz (again), but this time without XGL (so I have direct rendering (so
>>> the videotearing will be gone) ). Tails9
>>> March 2nd, 2008, 02:13 PM
>>> I recompiled the kernel without the framebuffer support, reinstalled the
>>> nvidiadrivers with envy and the problem is gone.
>>>        
>> 1. "rpm -ivh kernel-2.6.33.4-95.fc13.src.rpm"
>> 2. cd ~/rpmbuild/SPECS/
>> 3. rpmbuild -bp kernel.spec
>> 4. "cd ~/rpmbuild/BUILD/kernel-2.6.33/linux-2.6.33.x86_64/"
>> vi Makefile"
>> EXTRAVERSION="-noframebuffer"
>> 3. "make menuconfig"
>> 4. "Device Drivers --->  Graphics support --->  Support for frame buffer devices"
>> 5. Uncheck "nVidia Framebuffer Support"&  "nVidia Riva support"
>> 6. "exit" back to the main menu.
>> 7. Select "exit" again, and choose to save my new configuration file
>> 8. "make rpm"
>>
>> It's building now.  We'll see what happens.
>>      
> OK.  The good news is that the RPM was successfully built.  The bad news is that
> the output of "rpm -ivh kernel-2.6.33noframebuffer-1.x86_64.rpm" is as follows:
>
> [root at localhost x86_64]# rpm -ivh kernel-2.6.33noframebuffer-1.x86_64.rpm
> Preparing...                ########################################### [100%]
>          package kernel-2.6.33.3-85.fc13.x86_64 (which is newer than
> kernel-2.6.33noframebuffer-1.x86_64) is already installed
>          package kernel-2.6.33.4-95.fc13.x86_64 (which is newer than
> kernel-2.6.33noframebuffer-1.x86_64) is already installed
>          file /lib/firmware/matrox/g200_warp.fw from install of
> kernel-2.6.33noframebuffer-1.x86_64 conflicts with file from package linux-
> firmware-20100106-4.fc13.noarch
>          file /lib/firmware/matrox/g400_warp.fw from install of
> kernel-2.6.33noframebuffer-1.x86_64 conflicts with file from package linux-
> firmware-20100106-4.fc13.noarch
>
> Any ideas?
>
> Steven P. Ulrick
>    



Hi there

Did you do a clean install?

When I did this the first time with F12 I did the steps in the rpmfusion 
howto: the only difference was not using yum

I did it through add/remove software

After the proprietary installed with the kernel mod for driver for the 
specific kernel

The metapackage for tracking in newest kernel was also installed.

rdblacklist= nouveau was then added to grub.conf before the reboot and 
presto there it was




If this does not work then try the akmod instead of the kmod

akmod will autotrack in newest kernel mod on boot


I have not installed F13 yet but the more I read the more I know I will 
be reformating this drive and doing a clean install.


Good luck

Michael