<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta content="text/html; charset=ISO-8859-1"
<body bgcolor="#ffffff" text="#000000">
On 07/19/2010 07:17 PM, David wrote:
<blockquote cite="mid:4C450741.firstname.lastname@example.org" type="cite">
<pre wrap="">On 7/19/2010 9:17 PM, Michael Miles wrote:
<pre wrap="">On 07/19/2010 05:51 PM, David wrote:
<pre wrap="">On 7/19/2010 7:41 PM, Bill Davidsen wrote:
Obviously the previous kernel worked correct? Why not use that one?
<pre wrap="">I am using the previous kernel.
I just like to keep up and it is a update
I would like to know why the kmod is for a driver that does not exist.
195.36.31-2 is the driver and the kmod for this driver and new kernel
195.36.31-1 which ends with the wrong number
Even the kmod for the previous kernel is mismatched and ends with -1
instead of -2
You really should ask this on the RPMfusion list. It is their package after.
I tried to get some info and I was also advised that some thing will be
The kmods there for the new kernel but the new nvidia driver ends with
a -2 and the kmod is labeled -1 ant the end<br>
This is on the mail RPM Fusion page<br>
You can get support for RPM Fusion in most of the usual Fedora
discussion places -- e.g. <a class="https"
<a class="https" href="https://fedoraproject.org/wiki/Communicate">#fedora
on freenode</a> and <a class="http" href="http://fedoraforum.org">fedoraforum.org</a>.