-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 06 November 2003 01:59 pm, Mark Knecht wrote: > So I look closer and guess what? I've built 3 kernels today. The > /usr/src/linux link was not pointing to the currently running kernel, so > the emerge was putting the nvidia stuff in a different /lib/modules > path. > > Is this considered a bug? I think it might be, in the sense that this is > the first thing I've ever personally encountered where that link made a > difference.
It is not a bug - it is a "feature" of the nvidia-kernel. It allows you to build modules for any given kernel by following the link in /usr/src/linux. This is not going to change anytime soon. Just be aware that if you need to update your drivers in the future that you should modify that symlink to point to the appropriate kernel source that you wish to build the modules for. Sorry, I forgot about this little "feature", else I would have warned you from the start. :-( Also - I read in another thread responding to this about running opengl-update nvidia - this is only necessary if you've changed your opengl drivers. The ebuild for nvidia-opengl runs this command for you once you've emerged the nvidia-opengl package. If, in the future, you upgrade XFree, you will need to run the command "opengl-update nvidia" again. It only needs to happen when your opengl libs have changed. Enjoy! - -- Matt http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7D81740A -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/qsvWZosHVX2BdAoRAvX7AJ9BmY5IWuMzwLde1d4i6Kjt0jIdjACfSsZh sPu0iS813rxXSjUeF3maoVQ= =JGHa -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
