Kmod-nvidia and FC10 install kernel version
Hi all
When I still installed the nvidia driver "old style" (i. e. without using packages) I seem to remember that it was kernel specific, i. e. the nvidia driver, like all kernel modules, needs to compile against the running kernel's source.
As I understand it, if I install the kmod-nvidia rpm package from rpmfusion, I get a -binary- nvidia driver, that is pre-compiled against the standard FC10 kernel version? If not, how does it work? Does yum "know" to compile the just-downloaded rpmfusion'ed kmod-nvidia against the running kernel source? Doesn't this mean you MUST have a kernel source package installed, BEFORE installing kmod-nivida? What happens if I have a kernel that there isn't a kernel source package for? (Like, if I compile my own kernel with my own unique settings...?)
This is why I hate packages... too much odours of Windows.... - closed black boxes that either work or they don't, and if they don't, you're screwed...
If I now do have the above installed (i. e. a pre-compiled, packaged nvidia driver fo the standard FC10 kernel version) obviously I'll have major problems if I now go and upgrade the kernel? I. e. the nvidia kernel module will stop working / loading (since it is for an older kernel).
From a package viewpoint, what do I do then?
"Old style" I'd simply reinstall it against the new kernel's source and be done with it, but apparently this is a major no-no, especially in such a heavily "packaged" distro as FC10 seems to be?
It seems MUCH simpler to throw RPM out the window first thing and do everything "old style" - download a source tarball and compile, tarball -> compile, tarball -> compile... than fiddling with these infernally complex packaging systems that seem to put you in the same "pre-packaged" straightjacket type situation as Windows loves to put you in.
Last edited by rylan76; 01-09-2009 at 06:59 AM.
|