Sorry, this should have gone to the list.
Nope, it happened with the 3123. �I built a system last month and merged the Nvidia kernel and glx drivers - did not have to put in modules.autoload. � About two weeks ago I had to rebuild the same system to to disk problems - I wiped out all the partitions and started over. �Merged 3123 and it would NOT autoload. �I put it in modules.autload and things worked. > 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 -- Brett I. Holcomb AKA Grunt <>< -- [EMAIL PROTECTED] mailing list
