Which docs? The problem didnt occur with a video driver update, but something else within gentoo. I am not talking about the nvidia driver but the NVdriver as nvdriver has never been installed. It seems like the sudden failure of older systems to load the NVdriver is a gentoo problem.
Again, this is an existing, stable gentoo system that has been using the same NVdriver for some time, suddenly fails to autoload it! I have never installed an nvidia sourced driver or unstable emerged driver on this system, but always via stable emerge. I do not have many unstable packages installed, and can see that that could cause problems, but not in this case. BillK On Sun, 2003-02-16 at 17:02, Andrew wrote: > On 16 Feb 2003 16:43:41 +0800 > William Kenworthy <[EMAIL PROTECTED]> wrote: > > > or what seems more likely is that gentoo or nvidia has changed something > > that has screwed older systems, without telling people what they should > > do to correct the problem. How many people like me did an upgrade, only > > to find NVdriver no longer autoloads without any information as to why?, > > and therefore put it in modules.autoload (which after all is its > > purpose!) On my system, emerge nvidia-kernel builds NVdriver, no nvidia > > that I can see. > > > > BillK > > > > Read the docs, and you'll see that the drivers up to 3123 created a module called >"NVdriver" and that 4191 create a module called nvidia. Gentoo didn't do this, nVidia >did. And because so many people have issues with the newest drivers (4191) they're >marked as untested/unstable or ~arch. I bet on your system you don't use the >untested/unstable branch of Gentoo. > > Andrew > > -- > [EMAIL PROTECTED] mailing list -- William Kenworthy <[EMAIL PROTECTED]> -- [EMAIL PROTECTED] mailing list
