Apparently, though unproven, at 12:36 on Saturday 01 January 2011, Peter Humphrey did opine thusly:
> On Friday 31 December 2010 21:00:57 Alan McKinnon wrote: > > Apparently, though unproven, at 20:54 on Friday 31 December 2010, > > > > walt did opine thusly: > > > So, if you've ever run the NVIDIA install program manually, you > > > probably have two different nvidia.ko files in /lib/modules, and > > > the wrong one gets loaded automatically at boot time. Re-emerging > > > nvidia-drivers will build *and* load the correct kernel module > > > each time you do it. > > > > > > May not be your problem but it's easy to check, at least. > > I didn't think I'd ever run the nVidia installation program, and on > checking I see one nvidia.ko for each kernel version I have installed, > so that isn't the problem. > > > module-rebuild takes care of all that nicely. > > And it wants to rebuild the module again, even though I only remerged it > yesterday. > > Something is messing about with the nVidia module. That's how module-rebuild works, it's not broken. It *will* rebuild everything. It can't rely on the normal version numbers and USE flags to know if something needs updating, as the problem it is designed to solve is when you do a kernel upgrade and leave yourself without the out-of-tree modules you need in that new kernel version. If you use nvidia version X, then you need the version X kernel modules in every /lib/modules/<kernel>/ you use. So it just rebuilds everything every time. -- alan dot mckinnon at gmail dot com
