<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Maybe I am mistaken about the causes, but still, my system couldn't
load the nvidia module until I manually ran depmod -a on it.<br>
I will try to investigate the causes further and report any findings.<br>
<br>
Matt Zimmerman wrote:
<blockquote cite="mid20050928010737.GA10180@alcor.net" type="cite">
<pre wrap="">On Tue, Sep 27, 2005 at 08:59:48PM -0400, Dmitriy Kropivnitskiy wrote:
</pre>
<blockquote type="cite">
<pre wrap="">One of the strange things happened to my breezy (installed from colony 4
from scratch). Possibly this is a known bug, but I couldn't find it.
The nvidia modules are supposed to be dynamically built on startup, and
they are (I have the module in the volatile directory). Unfortunately it
looks
that depmod is called before the modules are generated, so modprobe
cannot find them. Running depmod and modprobe manually after boot
results in the module being successfully loaded. I hope that this issue
will be fixed by the time breezy is released. Thanks to all the
developers for great work.
</pre>
</blockquote>
<pre wrap=""><!---->
The modules are built by rcS.d/S15linux-restricted-modules-common and then
depmod is run at rcS.d/S20module-init-tools.
</pre>
</blockquote>
<br>
</body>
</html>