I emerged Nvidia kernel and glx 1.0.3123-r2 this weekend and found that I either have to load the Nvdriver before I startx or autoload it. �I know this was an issue with the 1.04xxx version but I think something's broken in the ebuild. �About two months ago I merged this driver version and did not have to start it manually - it automatically started if I remember correctly. �Now I have to load it via autoload or manually. From what I see on the mailing list it appears that 1.0.3x (some versions worked) but 1.0.4x did not work at all. It appears the module does not get installed in the correct place. With the fact it used to work but doesn't I'm assuming it's an ebuild problem at this point.
from ebuild: if you are not using devfs, loading the module automatically at boot up, you need to add "NVdriver" to your /etc/modules.autoload.
Okay, that raises some questions: I am using devfs 1. Why does this module, contrary to the behavior of all other modules, require that it be in autoload. Supposedly a module is loaded either via autoload or when required - is that not true? As I understand it a module is loaded when needed if it's not it autoload. 2. The response implies that it will behave differently with devfs - since I am using devfs I assume it should autoload. 3. Why did it work a couple of months ago but not now? Thank you.
